render to imtermediate... bloody slow...

DJPadre wrote on 11/21/2007, 1:03 AM
in the past i never had much of an issue rendering MPG2 (M2t) to intermediat cineform... it used to be about realtime as im nto changing much aside from the codec.

Now though, its less than 4 frames a second render... this is crazy...
Any ideas? Ive still got v6 on this machine but im running V7 till V8 stabilises

Comments

farss wrote on 11/21/2007, 2:48 AM
Are you running the latest version of the codec?
Laurence wrote on 11/21/2007, 3:23 AM
Make sure you haven't accidently changed your compositing mode on any of your video tracks to "3d source alpha" rather than "source alpha". I found out the hard way that doing that will make any Vegas render something like 20 times as long!
DJPadre wrote on 11/21/2007, 3:42 AM
im running v2.5 of the codec
Their website is a mish mash of info which gets me nowhere
i wouldnt know where to find an upgrade/update aside from neo

i havent changed anything in compositing, and i just checked and is all good..

:(
DJPadre wrote on 11/21/2007, 3:47 AM
ok thi sis wierd..

Cineform and Soy YUV do not use more than one core to render... which is bloody wierd because i never had this problem before..
Ive also got my render threads set to 4, but ive only got 2... ive changed this to 2, but still.. slow as buggery..

SOny YUV renders considerably faster, but still.. hmmmmm
John_Cline wrote on 11/21/2007, 4:13 AM
Go to Cineform.com, get the free NeoPlayer software and install it. It will upgrade the Cineform codec in Vegas to v3.12 which is reported to give higher quality encodes and unlike v2.5, supports SSE2 which will make renders faster. See this thread:

http://www.sonycreativesoftware.com/forums/ShowMessage.asp?ForumID=4&MessageID=531362

Also, it's no wonder that the Sony YUV codec renders so fast, it isn't doing any compression whatsoever. It is, however, writing huge amounts of data to the drive which can be a bottleneck.

John
megabit wrote on 11/21/2007, 5:57 AM
The Cineform 3.3 rendering performace is still very slow with 32-bit video (40% CPU max). Switch it to 8bit, and it files at 100%!

AMD TR 2990WX CPU | MSI X399 CARBON AC | 64GB RAM@XMP2933  | 2x RTX 2080Ti GPU | 4x 3TB WD Black RAID0 media drive | 3x 1TB NVMe RAID0 cache drive | SSD SATA system drive | AX1600i PSU | Decklink 12G Extreme | Samsung UHD reference monitor (calibrated)

DJPadre wrote on 11/21/2007, 9:07 AM
Its in version 7, so 32bit is non existant..
One thing i also noticed, HuffyYUV was also much faster, but all of these renders only used 1 core..
Funny thing is, playback is fine on M2ts on the timeline even with 3 or 4 filters chained up.... its just not juicing the CPU during renderi guess... i dont know why... wierd..

Ill try the neo player.. i just hope it doesnt nuke anything
DJPadre wrote on 11/21/2007, 9:26 AM
ok well i installed neo... its at 3.3 now or something..
its a tad faster, but the cpu is now riding on 60%

Most of that is from the second core when checking through task manager, and the pagefile is maxed outits now telling me that a 10minute clip will take 23minutes to convert.. and this is without any filters.. just a straight conversion..
teaktart wrote on 11/23/2007, 2:05 PM
Your 10min/23min render sounds about the speed I would get when doing a capture/convert using NEO on a dual core machine.

I recently had a bunch of hardware failures and in the process of fixing those chose to bite the financial bullet and upgrade to QuadCore and had to also upgrade MOBO, Ram, and reinstalled XP Pro and now.....
Wow, its almost in real time the NEO capture/convert , a huge difference especially if I'm capturing full tapes, where its now saving me literally hours of processing/rendering time. And the CPU in general is using less effort % wise and isn't a "floor heater" while doing the work like it was with the dual core.

Just add "mo'money" and everything speeds up!

Eileen
John_Cline wrote on 11/23/2007, 2:14 PM
Doing anything HD in Vegas (or any other NLE for that matter) requires a minimum of 2 gig of RAM. If you're just running 1 gig then it will be hitting the swap file hard and seriously slowing down your render/conversion.