Bill Clotz
Forum Replies Created
-
I use the effect Audio>Stereo Mixer.
It displays the sound as a percentage from 0% to 100%. It’s a bit annoying because you have to keyframe both the left and the right channel though. You can just save it as an animation preset though, and then just drop it onto a layer whenever you want. -
Grab Virtualdub ( https://virtualdub.org/ ) and take a look at your video in there. Is it still grey, or does it appear white? If it appears white, then this is a playback issue on your computer, probably related to your video card settings or drivers. If the color is incorrect in virtualdub as well then, it must be a problem in the encoding itself.
-
Very nice, thanks 🙂
-
If there is even a 0.01% difference in Lagarith -> Lagarith or uncompressed -> Lagarith, then there must be some sort of bug in whatever software you are using for the conversion or the measurement :p
Lossless means lossless. 0% difference.
-
According to this site: https://www.bhphotovideo.com/c/product/487942-REG/Adobe_19600057_Upsell_to_Production_Premium.html
It means if you already own one of the single cs3 apps, you can upgrade to the full suite.
-
I personally use Lagarith for all of my work these days. As long as your computer is even decently fast, the speed difference shouldn’t be much of an issue at all. I’m running a 3 year old 2.26ghz pentium 4, and it seems to do all right. In fact, sometimes Lagarith can even outpurform Huffyuv for me, because of it’s smaller files hard disc throughput is less of an issue. I would particularly suggest Lagarith if you have a multi-core processor, since Lagarith can take advantage of it.
-
Ok, that’s definitely odd. I’ve never experienced any issue with exporting out of After Effects. Sounds like this might be a different problem than what I’m familiar with. You get this when exporting with ANY codec, or only when you export with huffyuv? Did you check the always suggest rgb box?
-
Premiere Pro is extremely buggy at exporting to avi files using almost any codec. If you are going to export to an avi in premiere pro, always use only “uncompressed”. This problem is pretty well documented on various forums across the net, and I have been reporting the bugs to Adobe since Premiere Pro 1.0, and they continue to ignore the problem.
The problem very likely exist in your huffyuv files if you saved exported them out of premiere, and I don’t believe it can be fixed. You can try checking the box “always suggest rgb for output” in the huffyuv compression settings and see if that helps though. When you see that stuff in the frames though, I’m almost positive that premiere actually wrote that image into the video instead of what was supposed to be there–so in other words it can’t be corrected without going back to the original source.
This problem shouldn’t occur when exporting to huffyuv from After Effects or any other application–only from premiere.
-
I just bought an Intel Q6600 processor yesterday. It’s pretty much the same processor as yours, except it has 4 cores instead of 2. If you have nucleo pro and enough ram (4gb at least) you might be able to see close to twice the performance that your current system gets. This processor can also be overclocked to 3ghz fairly easily, which would get you a free 25% performance boost (note the risks associated with overclocking though). The Q6600 just had its price slashed to around $300 about a week ago.
-
I doubt it would do much for AE. The money would be better spent on more RAM or a faster CPU. As for other 3d apps, I don’t really know. There might be some advantage, but even then I doubt it would be the best place to spend the money.