![]() Restored a table entry in the Fibonacci coder I accidently deleted this would cause video corruption or crashes when playing back high-resolution video.įixed some pointers being treated as 32-bit integers when instantiating the codec this could result in the pointer being trucated and the application crashing on 64 bit systems. Thanks to Peter Dimov for reporting this and providing a way to reproduce the issue. ![]() The issue still exists for 64-bit systems, but the fix for them isn't nearly as easy and it is a very rare issue so I am leaving it alone for now. I have a somewhat decent computer (Ryzen 5 2600, 16 GB RAM, GTX 1650 Super) so it should handle most codecs fine, but I'm wondering how much quality I can squeeze out of this limited amount of space.Fixed a crash that could occur when the source video buffer is not aligned to a multiple of 8 for 32 bit systems. The choices seem to be VP8, VP9, and x265. What I am not unsure of however, is what codec to use. The last time I did this was four years ago on a really horrible computer and it was 1500kbps and I swear I could count the pixels at times.Ĭurrently, it looks like I can digitalize at 8,686kbps and still maintain uncompressed PCM audio, since I heard that issues arise when you compress audio in VirtualDub2. I'm wondering what kind of compressed codec would work best for the job without having horrible compression artifacts and preserving the interlaced lines. Unfortunately, I ran the numbers and realized that would take around 4 TB of space, when I only have 710 GB to spare for this project. ![]() I am currently looking at converting 27 VHS tapes to digital, and originally I planned on using Lagarith and uncompressed PCM audio to do this. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |