disable multi-processor avi rendering

xberk wrote on 5/27/2008, 4:45 AM

I imagine that this is suppose to turn off the multi-core rendering feature of Vegas. If you don't have a dual or quad core processor, nothing would happen. But I have a Quad core and it is set to render on 4 threads. I know this speeds up rendering times enormously (as it should). I went ahead and checked the box to disable multi-processor avi rendering. Nothing happened to my render times. Zilch. AVI files or otherwise. I checked the "internal" settings and no such setting appears. There is a setting for "disable multi-core rendering". This did not mention AVI. Despite the check marked box on the preferences, my internal setting was still showing "FALSE" (which meant that it is NOT disabled). I set the internal setting to TRUE. Wham! My render times shot way up on AVI or any other type of file. I used John Cline's rendertest.veg in all cases. Anyone know what goes on here?

apit34356 wrote on 5/27/2008, 5:38 AM

AVI impact..... a quick answer in general, remember all FX, motion, etc are performed "per frame' in AVI BEFORE being passed to the encoder. So, there is a lot of processing being performed for each FX, then passed to the next chained FX, then any track blending, all being passed in AVI then to main encoder. Plus, there is no restricted that stops simple dv tracks from being expanded in parallel for blending or any composite render using multi cores vs just a single dv avi track expansion before doing the next track. Again, most of these restrictions are more design and programming issues. Like expanding dv avi may considered a waste using multi-cores, but expanding compressed avi 1080p may see noticeable playback, in a multiFX, mutli track composite when changing avi settings.

TheHappyFriar wrote on 5/27/2008, 9:07 AM

could this of been an option just in case you couldn't change the affinity of processors/core's manually? Perhaps so you can run vegas & other programs with no big draw on a multi-core/cpu system?

xberk wrote on 5/27/2008, 9:30 AM

I really couldn't follow apit's explanation. What I'm seeing is that the check box
refered to in the orig post does zero. I can't see what, if anything it does. In the "internal" settings there is a different description of what may or may not be the same item as the check box. It DOES do something. Setting the "disable multi-core rendering" to TRUE slows down the CPU -- way down - no matter WHAT TYPE OF FILE. Not just AVI .. (as far as I can see. I didn't test every type of file)...I can see using this setting if your renders are locking up all other ap's and you want to limit it's use of a 2 core/4 core/8 core cpu. Still confused on the check box. Why have a check box that doesn't function and doesn't relate to anything in the Internal settings. ?

kb_de wrote on 5/27/2008, 4:58 PM

I have similar opinion like xberk and apit's answer does not satisfy me, especially, I am sure its not an issue as programming etc. otherwise the sony engineers should not put it as a check point.
my doubt is, this choice could be a matter for server-computer which must have some cpu-resource for its procedure.
but...maybe the sony experters can give us a reply.

also, i found this item in the internal preferences in Acidpro.

DrLumen wrote on 5/27/2008, 5:59 PM

Maybe it only drops to one cpu when the system starts getting loaded down or vegas drops to a background process (loses focus).

Have you all tried rendering while surfing or listening to music? Like kb was inferring, maybe it only applies to network rendering?