Submitted by Matt Clifton on Sat, 29/08/2009 - 23:39

Hi

I'm running VoltaicHD 1.8.7 on a 2008 Mac Pro (3.0GHz, 8GB RAM, OS X 10.5.6), and have queued up several movies from my Canon HF11 (24p mode, full quality) to convert. The only preference I've checked is "Export as 24p / Autodetect". The VoltaicHD process is only taking 0.8% total CPU usage with 28 threads. I'm not running anything else processor-intensive, so I'd like Voltaic to take advantage of as much CPU as it can get - and, of course, speed up the conversion if I can.

Is there anything I can do?

[Edit: I now see that there's a single-thread "Voltaic_b" process which does take up 85% of a core. I guess I don't fully understand the use the program is making of the multicore system. Can anyone elucidate?]

Thanks!

Matt

‹ Bad video quality Version 2.0 problem with GH1 files ›

VoltaicHD and multi-core usage

Submitted by justin on Sun, 30/08/2009 - 20:37.

Hi Matt,

VoltaicHD currently only uses one CPU for processing. This is a limitation in the way we do the conversion. We don't have firm plans to upgrade to multi-core conversions in the near future.

The only upside to this (for the usual MacBook Pro users) is that VoltaicHD 'plays nice' while converting (using one of the available 2 cores), rather than killing the machine (as the iMovie/Final Cut converters do).

Multi-core usage

Submitted by topherharris on Thu, 10/09/2009 - 02:12.

With conversion taking such a long time (12x running time?), wouldn't it be beneficial to have a multi-core option? I would like the ability to begin a conversion session before I leave work, have it use all available cores, and chug through all my conversions. We are getting projects coming to us at work that have to be converted, so getting conversions quicker would be great.

I guess you might call this a "feature request".

Thanks,

Christopher

Multi-core

Submitted by justin on Thu, 10/09/2009 - 06:40.

Hi Christopher,

speeding up Voltaic is something that we plan to do, but for now we are focused on various features around native AVCHD editing.

Once we get through this we will be having a look at performance and multi-core usage.

Thanks

Justin