AVI Plug for REndering Using All Cores?

Comments

John_Cline wrote on 1/29/2012, 5:10 PM
What is the source material from which you are converting in NeoScene? AVCHD?
Streamworks Audio wrote on 1/30/2012, 11:02 AM
As I mentioned (and shown in pictures) above.....

Yes the file is AVCHD. The source and the destination are the same. All aspects are the same in terms of input/output and codecs used.
Streamworks Audio wrote on 1/30/2012, 11:27 AM
Just to add...

I created a graph in Graphedit, the AVCHD file is decoded by ffdshow - I connected it to my Blackmagic MJPEG codec (I could not get Cineform to connect) and rendered it out to an AVI (using what I believe is Microsoft's Directshow AVI Muxer). With this graph, all cores were running at 100%.

I tried rendering to Blackmagic (again) from Vegas.... all cores at or just under 50%...

John_Cline wrote on 1/30/2012, 3:09 PM
I guess you're just not going to be happy until you see all your cores operating at 100% all the time. Rather than focus on how many cores are operating and at what capacity, what is the real world difference in time between rendering AVCHD to Cineform in Vegas vs. Cineform's HDLink?
Streamworks Audio wrote on 1/30/2012, 4:31 PM
Well I will have to time some render test to give exact numbers... but NeoScene is faster. Peter above also noted the speed difference...

"I rendered an AVCHD clip to cineform using Neo HD Link and it used about 95% CPU and took 70 secs.

I did the same using Vegas Pro 9c and it used about 30% CPU and it took 114 secs."

I am not always working with AVCHD, in fact I hardly work with it, most of my work is graphic/screen capture based (http://streamworksaudio.com/) - so it not a case of NeoScene is faster, but the fact that Vegas is not using the CPU to it's fullest... and in this game, time is money - so utilizing the CPU = less time which can lead to more money.

I only used NeoScene to check to see if the codec used 100%, which it did and Vegas did not - so I think it would be a huge benefit to many if it did (with AVI files).