Back to Blog
Losslesscut linux5/29/2023 ![]() Personally, for my old Samsung 3D TV, I use X264, CRF between 18 and 21, and Preset slow (1080p). It's the advantage of the CRF mode : it can compress different movies differently, always as much as possible without scarifying the quality. So, don't be afraid if the final size of some movies is very small. For example, an old, noisy 3D movie from the 50's is much more "difficult" to compress than a CGI animated film such as a Pixar movie, with very clean and smooth images. Note also that the compression depends greatly of the images and camera movements of the movie. You may therefore need to switch your player to 3D manually. Note also that X265 doesn't have the possibility to tag the video stream with the 3D format. A very slow preset can therefore produce problems such as a jerky playback on an old or not powerful enough hardware player.įinally, the X265 encoder produces a better quality for a smaller file size than X264, but the resulting video cannot be played on many hardware players (especially on most 3D TV or 3D BD Players). A slower preset requires more encoding time, and, more important, it requires also more CPU power to decode and play the video. CRF 0 is lossless, but produces a very big file !įurthermore, the Preset (medium by default) can also be modified to compress the file a bit more, with no or a very little quality loss. But you can lower that value for a better quality, at the price of a higher file size. The default (23 for X264 or 28 for X265) has been defined by the authors of the encoders because it offers a good quality and a very good compression. I recommend to use the CRF mode (certainly the best one, unless you need to control the final file size precisely). You can also control the quality and file size with the Encoder Options in the last tab. Of course, the quality is less good, but the gain in file size is important, and usually, 720p is sufficient for a VR experience. ![]() For a VR headset, I recommend to tick the option to resize the video to 720p. The quality and the final file size of the video stream depends of several things. For more info, contact Mosu (the author of Mkvtoolnix) here. Are you sure you have all Windows updates ? Or do you use a (very) old version of Windows ? IIRC, Windows 7 is not supported anymore by mkvtoolnix (but I may be wrong). So, sorry, but that means that you have two different problems: the ISO and MkvToolnix. Anyway, according to your log, the errors are in the ISO itself, and not caused by the program. The Entry Point Not Found error message is shown by MkvMerge, and not by BD3D2MK3D itself. Hence my remark above about the 6 missing frames. Furthermore, for a 3DBD, an sync problem between the left and right video views is totally unacceptable. But when you want to use the elementary streams for a re-encoding, or even for a remux, the time-codes are lost, and if a stream is damaged, it will quickly become out of sync. The error itself may be almost unnoticeable, especially for the audio streams. A player can usually skip the errors in the ISO because, after an error, it can re-synchronize the streams with the time-codes in each stream and in the MKV container.
0 Comments
Read More
Leave a Reply. |