Kevin Bugay
Forum Replies Created
-
I suppose you’re right. As long as I’ve found a method for getting reliable renders I shouldn’t complain about the extra clicking/waiting I have to do.
Still though, I 100% blame the programming of Sony Vegas which defaults to “insert black frame” rather than “wait until loaded into memory”, and then doesn’t have the politeness to tell you how many frames were lost in the render. It’s nothing we can do about it, but I’m leaving this here for the record. Sony needs to fix that.
-
It’s an AVI recorded with Action!. I definitely think the Action! codecs are proprietary and not very compatible with just about anything. I’m probably going to switch to Dxtory or something if I can’t figure this out. It baffles me that Sony Vegas can (somewhat) tolerate these videos but Handbrake can’t read them at all.
166 Mbps means “megabits per second”, or 21,248 KB/s. The file is 714 MB and 1:38 long, giving an average bitrate of 7,285 KB/s. The higher number represents the “current bitrate” of that spot in the video with lots of water particles moving around. I can’t open the video in Bitrate Viewer because “AvLib/FFMpeg Error: Codec not found.” Which is not surprising.