![]() In the meantime I made tiny batch file (compiled to an exe) that invisibly disables AnyDVD, waits for MakeMKV to do it's job, when MakeMKV is closed, AnyDVD get's re-enabled. I'm hoping there's a very simple, lightweight Bluray ->MKV app that doesn't have copy protection removal builtin nor transcoding capabilities just remuxing to MKV with good subtitles/audio file support. I would much rather pay for a Bluray->MKV app that has a developer who listens to what people want to see unless they want to just give it away for free. This has been suggested several times on the MakeMKV forum. To me, it seems a little bit extreme to have to click "Yes" to the below message every time to be sure you're reminded of that or not consider the possibility to use AnyDVD for copy protection removal since afterall, it's pretty much a standard on HTPCs. I guess he thinks that "the most sophisticated protections" should be left up to makemkv, not AnyDVD. Unfortunately, it looks like the guy who made MakeMKV doesnt seem to like AnyDVD-HD a whole lot. The only way to know if that's likely to be the problem is to see the scripts StaxRip was creating for encoding.I would love to use MakeMKV for simple BD->MKV conversion and is pretty good at it. That'd cause ffms2 to decode everything at 29.970fps, and then you'd have to apply IVTC and/or deinterlacing as required. ffms2 needs to be told to obey pulldown flags with the rffmode option. Or it told ffms2 to obey the pulldown flags It's probably not MakeMKV's fault.Īll the above is theory, but it's a logical reason. ![]() Maybe when you switched to opening the vob file, StaxRip switched to decoding with DGIndex instead and it decoded the source differently. 24.586fps would be the average frame rate. The small section at 29.970fps would explain why the frame rate is shown as something a little higher than 23.976fps. I don't use StaxRip, but by default ffms2 ignores pulldown flags and outputs the average frame rate. The majority of it has pulldown flags so it's 23.976fps, but some of it, even just the studio logo at the start, or maybe the credits, is either interlaced or hard telecined, making those sections 29.970fps. It sounds like a small section of it is either hard telecined or interlaced. Sometimes the combing is worse in other parts of the video, ect. I am 100% sure it is not from a film reel (telecined). I'm re-encoding to save space and fix the mastering errors. And it looks like using DVDShrink (disabling VOB splitting and compression) and opening that VOB in StaxRip fixes the issue. It's progressive but poorly mastered so there's combing on the raw video. Why are you re-encoding, anyway? Isn't your playback system smart enough to play MPEG2 video files? Why MKV? It's progressive but poorly mastered so there's combing on the raw video. You could use the free DGindex to make demuxed m2v video and AC3 audio files and tell DGIndex to ignore pulldown flags to get the original 24fps without pulldown flags. I don't use any of those free push-button automated converters, but maybe someone can make a better suggestion. What you need to do is learn to use real software, not MakeMKV. Why are you re-encoding, anyway? Isn't your playback system smart enough to play MPEG2 video files? Why MKV? ![]() You can't use QTGMC or similar deinterlacers on telecined video because soft-telecined video isn't interlaced. Likely as jagabo says it's progressive with pulldown flags of some kind or other. So what do I need to make a proper encode? Progressive video doesn't have combing effects. The video is progressive (with combing, QTGMC fixed that). The VOB files can contain a mix of progressive with pulldown, true 29.97 fps interlaced, and any lower frame rate with hard pulldown to 29.97i. The pulldown flags tell the player how to produce 59.94 fields per second from those progressive frames (this is the 29.97i that is constant on all DVDs). The progressive frames can be any frame rate from 19.98 fps to 29.97 fps. DVDs can contain progressive frames with pulldown flags.
0 Comments
Leave a Reply. |