Using 0.8b5, when transcoding to mp3 (CLI) the lame process eats almost all the process power of my pc, and only a few applications works.

I set the priority balance to the minium in the encode propierties page, but lame works in "below normal" priority (I watch to it on the windows XP task administrator). The computer works better if I set manually the priority of lame to low in the task administrator, but when foobar finishes encoding a file and starts the nest one, the priority goes back to "below normal", and the computer gets inusable another time. What can I do?

yeah, i've noticed this, too.. similar things happen to me when i use EAC to rip with lame... lame just seems to be a not very nice program.

A great option, though, would be the option toi set a process priority in the CLI encoder. (don't know much about how the process priority system in wondows works, can it be set at execution?)