Procoder takes 100% CPU

[thecenter]

Hey.

I'm Using Procoder, an whenever I convert a dv-avi file to Mpeg2 the
cpu usage is at maximum - 100%. it never happened before in my old computer. Is it a hardware problem ???? or the procoder settings ?

thanks.

[redwudz]

Most encoders use 100% CPU. That's what you want for total utilization of the speed of the CPU. Is that causing any problems?

EDIT: I'm running a Divx6 encode right now and it is also 100% CPU.

[thecenter]

I used to work with Procoder on my old computer - it wasn't like that there, I could work while it was encoding and most important - it's not even faster now !!!!

I work with Tmpgenc once in a while and it doesn't require 100% usage of CPU.

[adam]

Well this is a good thing in my opinion.

Its not a problem unless you want to do other things while encoding. If so then do control, alt, delete to open the task manager. Find the Procoder program on the Processes list and right click and go to Set Priority and set it to whatever you want. If you set it to below normal then it will use less cpu cycles for each new program you open.

If procoder ran with less CPU usage on your old computer then you may have had the priority set lower than you do now, or there might have been some bottleneck in your system keeping you from maxing out your pc. Maybe you didn't have enough ram or maybe had a reaaaally slow hard drive or something.

[reboot]

Hit CTRL+ALT+DEL and right click Procoder.
Select, Go to process.
Right click the process, and drop the priority.
It will simply add a little time to the encode, depending on what else you're doing on the computer.
Mainconcept is also a CPU hog, and I do this all the time.

[Rasaraja]

If you go into Windows explorer and just click on a mpg file, does the CPU go to 100% too?

[lordsmurf]

Doing "other stuff" while you encode is the leading reason for "boogers" in the final video files.

If you need to do "other stuff" buy another computer, or learn to do one thing at a time.

[mickdarson]

I found on another website and tried on my PC XP-SP2, this feature may not exit on XP1 or 2000, encoder is CCE 2.7 and It speed was 1.32 before and now is 1.64 ( Procoder from 10 to 11.2fps). I am not sure it will work for everyone. If somebody mind to try, please post back results. Thanks
Procedure:
All Window's apl are closed. From start button > Run >gpedit.msc >Administrative Tempplates >Network >QoS Packet Schedule >Limit reservable bandwidth >enable > enter 0 >apply and exit

[Jester700]

Doing "other stuff" while you encode is the leading reason for "boogers" in the final video files.

If you need to do "other stuff" buy another computer, or learn to do one thing at a time.

Any technical explanation for this? It doesn't make sense that a PC program should allow this; if an excel file could be boogered just because you were browsing at the time, all hell would break loose. I know these are different things, and I'd like to know specifically why.

[junkmalle]

Doing "other stuff" while you encode is the leading reason for "boogers" in the final video files.

Only if there's something wrong with your computer. Like you're running Windows or something!

In all seriousness, I'm often converting with VirtualDubMPEG2, capturing with my Hauppauge PVR-250, browsing the internet, copying/moving files around, watching an AVI, etc. Never have any problems under Windows XP SP2.

[adam]

The only thing I can think of is if you run out of memory and it messes up the program, but then that would probably result in a hard crash. Otherwise all you are doing is throwing less CPU cycles at it. Its still doing the exact same processes exactly the same way, it will just take longer.

I've never heard of anyone getting stream errors due to multitasking either...

[reboot]

It's probably more to do with too much hard drive activity, than CPU cycles.
Always capture to a separate drive (not just a partition), away from the drive that contains the OS/programs.