www.makemkv.com

As per subject. The latest version, 1.10.1, on OSX El Capitan, is starting up full screen with no window decorations (titlebar, close/minimise/maximise or draggable edges. It fills the desktop (but doesn't go into its own Space) and I can't get it out of this mode into just being a normal resizeable...

By chance I just got this too, and like you found the URL leads to a 404. But in my case the actual rip seems to be progressing normally anyway. So the reason I was going to look at that URL was to see if it would tell me what it's actually needed for in this instance, and thus whether to actually i...

Getting same problem as described with Interstellar, on makemkv 1.9.3 on OSX Yosemite

Only difference to the poster two posts up is it's a Samsung SE-506CB, not AB.

EDIT: on reinsertion (everything worked)

Still hangs on start. Fixed in 1.8.7 , available for download. Confirmed for me. :) That is, fixed dynamically linking to the new ffmpeg built as described above and installed in /usr/local, so never got around to trying the statically-linked method described in the announcement post, though I'd gu...

FWIW added --enable-pic to those flags as per thread http://www.makemkv.com/forum2/viewtopic.php?f=3&t=7225 but it didn't make any difference. Still hangs on start.

Re-downloaded, rebuilt 1.8.5. it works.

Guys, hate having to go there, but... I am a paying customer, and now it's broken, for the sake of a feature I don't even want.

This needs a fix.

Make debs that work. Statically link ffmpeg.

I got this to work by changing the config options for ffmpeg when building from source. This works on Linux Mint 16 so I'm assuming it will be the same for all Ubuntu 13.10 derivatives. I used the latest ffmpeg 2.1.1 source from their website. Configure with these options: ./configure --enable-shar...

I had similar error but `ffh263_vaapi_hwaccel` after recompiling ffmpeg with --enable-pic I now get I different error. /usr/bin/ld: /usr/local/lib/libavcodec.a(mqc.o): relocation R_X86_64_32 against `.rodata' can not be used when making a shared object; recompile with -fPIC /usr/local/lib/libavcode...

It isn't an issue with film rate, but rather with standards. Europe mostly adopted a 25 FPS framerate for their media and broadcasts, so they just sped up the Film framerate from 23.976 to 25 fps. It's not a matter of being able to play it back, but having to convert the framerate back to it's orig...

hey, the site's back! (It went down literally a few minutes after I posted my last post just above which, although I didn't mention it, the sharp-eyed might have noticed I was describing ripping a rental disk. I thought it was *my* account that had been suspended; took a while to establish it was th...

Framerates are different in the UK on *DVDs* but not on Blu-Rays. Unless the rest of the world isn't using 23.976fps for movies suddenly? :) I see precisely one title that's 2:22:33 though it isn't 41.8GB. (it's 41.3GB; thinking this may be a difference in available audio tracks - there's only Engli...

i think i may have just answered my own question. Handbrake, of course, doesn't handle bluray PGS subtitles, so doesn't try to read those tracks. So running makemkv again and deselecting the subtitle tracks (and the commentary tracks for good measure, might have been them as I don't think I made han...

Tried to use makemkv as normal to take a copy of The Woman in Black blu-ray. This initially failed with many many thousands of error messages of the form: "The source file '/BDMV/STREAM/00000.m2ts' is corrupt or invalid at offset <n>, attempting to work around" for increasing values of <n>...

In fact the open source decoders (most importantly for xbmc/handbrake users, ffmpeg) can read *progressive* VC1 just fine. It is only interlaced that seems to be beyond them at the moment. I'm also a Mac/Linux user, and use Handbrake there, but for those disks, and they're mostly BBC disks, I use Ri...

I just had this on a v15 disc (Last Chance to See disc 2 - disc 1 had been fine). makemkv 1.6.2 on linux (ubuntu maverick) 64-bit. I rebooted, all the while thinking, there's no good reason to expect this to work, but it did. Disc is now ripping. :-) if there is a good reason, it's probably that the...