The constant 29.97 fps D2V file DGIndex creates, in contrast, presents AviSynth with a data stream in a format it understands and can work with. TDecimate might be able to theoretically scan the video stream and remove the duplicate images, but AviSynth doesn’t understand what the frame rate of the MakeMKV-derived source is supposed to be in the first place. This continues through Frame 329, but the output synchronizes again at Frame 330. Sisko’s mouth position in Frame 328 of the MakeMKV source is different than his mouth position in Frame 328 of the D2V source. In the D2V-derived file, Frame 327 is an interlaced frame containing data from the frame before (the two admirals sitting) and the frame to come (Sisko talking). In the MakeMKV file, Frame 327 is a shot of Sisko. Please ignore Sisko’s forehead tumor, he’s sensitive about it. Believe it or not, the frame on the right is the frame we want to process to unwind the frame rate properly. MakeMKV frame on the left, DVD Decrypter + DGIndex frame on the right. I can’t embed the slider, so I’ll also embed a screenshot below: Here’s Frame 327 from a 29.97 fps D2V-derived file broken down into its constituent frames, versus a Frame 327 from a MakeMKV-derived source. That doesn’t mean frame output between the two is always identical, however. A MakeMKV file and a D2V-created file at 29.97 fps track each other frame for frame, meaning Frame 500 from MakeMKV source contains the same moment in time as Frame 500 from the D2V-derived source. Here’s how I know that’s true: By default, the output from a D2V-derived file is 29.97 fps, unless you change it in some way. 23.976 fps is one pattern, 29.97 fps is another. Within the source, there are two types of content patterns encoded two different ways. ![]() MakeMKV-created footage only returns to the standard 3:2 format during scenes that were expected to play back at 29.97 fps. Internally, the frame rate of the MakeMKV-encoded file remains 29.97 fps. Instead of 3:2, it contained entirely progressive frames encoded in the following pattern: 1-2-3-4-4 (frame 4 repeats) or 1-2-3-4-5-5 (frame 5 repeats). The MakeMKV-created file contained a very different frame sequence. The first point I want to make is that there is a difference between what you see in a DVD stream when you play the file back - even if you go frame by frame - and the actual frame sequences stored on disk.Īll of the content written to an NTSC DVD intended for playback in a DVD player is “conceptually interlaced”, to borrow a term from HomeTheaterHiFi. There are aspects to this situation that I am still piecing together, so I apologize if I’m a little vague in places. But the problem goes a little deeper than that. This destroys any chance of synchronizing audio. Thus, AviSynth forces MakeMKV-derived output into a non-standard 24.6 fps rate in an attempt to harmonize the two. As from October, 2014 MakeMKV, MyBD and AnyDVD (AnyDVD is like a driver for decrypt purposes only) are able to decrypt Blu-ray disc protection as being are freeware applications.To be clear: Much of the reason why you can’t use a MakeMKV file in this process without hosing your motion is that MakeMKV creates variable frame rate files when used to archive an episode of Deep Space Nine, and AviSynth is not designed to edit variable frame rate files. Remaining existing US software have disabled the decrypt / unencrypt / de-lock feature that allows bypass the Blu-ray disc protections. Software tagged as "no longer available" is due to New York federal court by AACS group legal action in later March, 2014. ![]() 1.1 System support/minimum-requirementsĪpplications System support/minimum-requirements Blu-ray ripperġ0 MB for the program files, 30 GB recommended per disc īeta versions are free, but must be renewed every 60 days.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |