Rendering Threads & Dynamic Ram

Back to post

Comments

Andrew B wrote on 3/13/2016, 4:59 PM
As always John, you are the voice of reason! ;)

It will be interesting to see how things roll out with the new 10-core consumer chips coming soon.
I am still leaning towards a couple of high clock-rate XEONs since I am trying to build a system that will work with well for our Vegas work AND Pro Tools, After Effects, etc.

Of course, as I price a system that will work with everything, I quickly realize it is probably cheaper to have one system for Vegas and another one (or two!) for everything else. That would also take care of our challenges of trying to render out 3 videos while editing another simultaneously.

The nice thing about technology though, is if you don't like your options today, just wait until next week.
(e.g. http://www.techpowerup.com/219275/intel-readies-a-5-1-ghz-xeon-chip-based-on-the-broadwell-architecture.html )

Andrew

ps - My personal rule of tech: "Nothing new ever comes out until I buy something."
john_dennis wrote on 3/13/2016, 5:16 PM
"Nothing new ever comes out until I buy something."

Two months before the first Intel DDR2 (edit: DDR) chipsets were available, I bought an 850E chipset motherboard and used RDRAM for four years after the rest of the world had moved on. Should I go on? When it's time to replace a system, I buy the best that I can at the time and only complain on an unrelated forum a decade or more later.
Andrew B wrote on 3/13/2016, 5:23 PM
"Two months before the first Intel DDR2 chipsets were available, I bought an 850E chipset motherboard and used RDRAM for four years after the rest of the world had moved on. Should I go on? When it's time to replace a system, I buy the best that I can at the time and only complain on an unrelated forum a decade or more later."

HA HA HA, I'm with ya!
We tend to save up a bit longer and buy the best quality we can. It let's us hold on to our gear for much longer. Better long term investment.
john_dennis wrote on 3/13/2016, 5:31 PM
Correction: It was the first DDR chipset. I knew it was coming. I just didn't wait. Maybe, I should tell you about my penny stock purchases?
Jason-Stoll wrote on 5/12/2019, 4:54 AM

P.S Know it's an old thread but the answer is still valid:

 

One way is to partition your project, annoying though it would be and assuming you don't have effects running over into the next section you can launch multiple vegas to spread the load onto your cpus by rendering them all simultaneously but in different processes. Video rendering is quite often single threaded simply because of the fact that one can't predict the state of the frames ahead until you know the state of the frames before and the processing still being applied.

So you could split your project for instance into 4 sections (you could use child projects i suppose to get the total view). You would then launch 4 Vegas and process the sections simultaneously and independently (you can render them to png to not lose any info). In the final stitching project you import the sequences generated and then encode to your lossy codec.In this way the effects processing has been done already and the only think to do with the sequences is now to compress them to codec of your choice.

 

P.S i just tried it got my render time down from 4 hours to 1 hour.