You need a much faster CPU. Video editing is always going to be CPU intensive.How do I get round this MAX OUT situation?
The E5520 Xeon, like all the 55xx series, was as I recall a quad core processor with hyperthreading, so just one of them normally shows as eight cores in task manager (my i7 desktop does, for example and that's a quad core processor with hyperthreading. My workstation with two E5420s shows as 8 cores, as those are quad core without hyperthreading).I use the GoPro Studio software that comes with the GoPro.
CPU's max out when it is converting the final stage for youtube etc.
I have two Intel Xenon E5520 2.26 GHz processors fitted + 24GB ram
The E5520 Xeon, like all the 55xx series, was as I recall a quad core processor with hyperthreading, so just one of them normally shows as eight cores in task manager (my i7 desktop does, for example and that's a quad core processor with hyperthreading. My workstation with two E5420s shows as 8 cores, as those are quad core without hyperthreading).
There are faster pin compatible processors, but it looks like you're doing something that is CPU limited, so don't expect the percentages to go down with a faster processor, just the time taken to complete the action.
depends what your board will handle, socket 1366 (which the E5520 are) Xeons arent cheap though. even the E5520 are £300 each.
e: if it were me id look at selling the xeons and motherboards and funding a i7-5820K and motherboard and memory as thatll likely not be compatible (i7-5820K benches at 12975, dual E5520 benches at 7589 by the way)
I run an i5 as an ESXi server. Running a virtualised Linux system, it benches comparably with running the sdame software on an i7 (when you factor clock speed/no processors into the equation). The only thing Xeons have over the i7 is typically more cache (2-3x) and support for properly virtualising hardware (aka pass-through or VT-d) which the -K processors didn't have on (at least) the -2xxx or -3xxx lines.If the "desktop" i7 processors will actually perform this role better than a pair of Xeons from a few of years back and can use much cheaper (albeit not ECC) RAM then a rethink is in order.
Well, I think Neil et al have given better computer advice than I possibly could, but maybe you need a new kettle. That way you could leave the screen and brew a nice cup of tea in the time it takes to render down a short video clip.
If you had another pc attached to the display via a T-switch, you could set off your video rendering on machine A and the switch to machine B to carry on doing other stuff while the rendering chunks away in the background.
I often use VMs created by Virtual box to convert my DVDs to X-Vid.
In my particular setup I often have 8 VMs running , each one converting a different episode of a Series or maybe 8 different films.
However each VM is a stripped down version of XP running in just 1Gb space and using 1Gb RAM with the results being output to an external SSD.
It takes approx 1 1/2hrs or so to convert eight 40min episodes to X-Vid at 640x360.
Once set up they're a piece of cake to run.
.
good luck with that oneSeems a bit extreme, why duplicate the overhead of 8 OS instances when all you want to do is multitask?
Seems a bit extreme, why duplicate the overhead of 8 OS instances when all you want to do is multitask?
'Because I can' is a perfectly acceptable answer when it comes to such things of course![]()
You are duplicating the overhead of 8 OS' going through a virtualising server. I'm 99.9999% sure they would render quicker in a single OS with each one given their own directory to work on. But then your setup is up to youThought that was what I was doing
.
You are duplicating the overhead of 8 OS' going through a virtualising server. I'm 99.9999% sure they would render quicker in a single OS with each one given their own directory to work on. But then your setup is up to you![]()
PS. Yes, I have recoded more than one thing at once under a single OS.... but then I use a command line processor which is easy to run multiple times. Not sure about the software you are using....
Personally, on a clock-for-clock basis, I think you would be hard pressed to tell the difference between a VM on a Xeon and one on an i7 - as long as you aren't hitting a point where what you are trying to do fits completely in the cache (or memory) on a Xeon server but doesn't on an i7.
(and ultimately just doing it of my own accord), as our customers kept asking about compatibility of our products and various hypervisors.I still think it would be quicker in one machine.