Processing thread priority ?

[RobertElfstrom]

Hi

What does the Processing thread priority setting do ?

Will it increase the priority on then encode process or will just give more priority to the preview ?


I can't see any increased FPS when i set a higher priority...
(Maybe because my comp. sucks :D)

[gr0x]

It increases the priority on the encode process. As you said.

If you enjoy using your computer in the meantime, setting it on the idle process will make your experience more... enjoyable.

~g

[tmpy222]

Hi,
I think Vdub has a bug on processing priority. It seems that it's always setting the priority to "high" when doing frame serving. And when you stop the frame serve, it's still set at high priority. The priority setting in preference doesn't seem to do anything at least on my win2000.
Also it's almost impossible to use the computer if vdub's priority is set to high and you're doing encoding... I had to set it back to "normal" manually each time.

Hope this gets fixed soon.

Thanks.

[Acaila]

Hmm, I've never had any problems with thread priority while frameserving. Please note that there are actually two settings in Preferences. One is for preview thread priority (the first), the other for encoding thread priority (the second). Maybe you set the wrong one to high?

[tmpy222]

Hi,
Both were set to normal. It didn't matter what I set in the preference. Vdub always sets its priority to high when frame serving. And it doesn't set it back to normal even after stopping frame serving. You can check the Vdub priority in win2000's task manager.

Thanks.

[Milkman Dan]

Might I ask what you're frameserving to from virtualdub? Because AVISynth is a more flexible and faster solution.

[theReal]

I found out lately that if you change the priority of VDub, you don't change the priority of avisynth as well - so unless you change avisynth's process priority, the VDub process will try to steal cpu power from avisynth ("idle" by default), which makes some percent end up in the system idle thread in the worst case.

Setting VDub to "idle" seems to be the best solution, unless you really stress your system while encoding - then setting VDub AND avisynth to something higher would be beneficial for the encoding.

btw. to check and change the priorities of processes and SUBprocesses, you can use this great tool:

http://www.iarsn.com/index.html#/download.html

[tmpy222]

How do you change the subprocess in taskinfo? Were you able to change the priority of avisynth.dll?

[theReal]

Double click on the main process (VDub), it opens the subprocesses then. Right click on one of them, choose "set process priority" and click on what you like. The subprocesses' priorities are shown in numbers like 4/4 or 7/8. I think the second number is the maximum you set by chosing a certain priority, the first is determined by the system.

I haven't tried avisynth actually, but it worked with every process I tried so far.

[Lord_Magneto]

Vdubmod's thread process priority seems to be functioning improperly for me. It was fine for most of yesterday then last night it changed. I always use Idle setting, and it has always run at a good speed(20+fps), but starting last night it take a couple of seconds to get it to do three frames in idle setting. When I change to other settings it gets normal. Also once it gets to 100% the program freezes.

I am using VirtualDubMod1.5.10.1, job control, AviSynth, and XviD1.1.0. Any help on the matter would be greatly appreciated.

[LoRd_MuldeR]

Vdubmod's thread process priority seems to be functioning improperly for me. It was fine for most of yesterday then last night it changed. I always use Idle setting, and it has always run at a good speed(20+fps), but starting last night it take a couple of seconds to get it to do three frames in idle setting. When I change to other settings it gets normal. Also once it gets to 100% the program freezes.

I am using VirtualDubMod1.5.10.1, job control, AviSynth, and XviD1.1.0. Any help on the matter would be greatly appreciated.

Well, in "idle" setting VDub will only use the CPU when it becomes idle, that means no other app is using the CPU. So "idle" mode might work fine when you don't run other CPU hungry apps at the same time. But once some app starts to use the CPU permanently, VDub will "freeze" in idle mode. Maybe that's the problem??? Did you check in Taskmanager if some other app took a lot of CPU time? If so, that would be the solution...

[squid_80]

This could also be due to a bug in xvid's multi-cpu support. Do you have a dual-core cpu, Lord_Magneto?

[movmasty]

Note that if you run only vdub, will be a little faster using lower priority.

if you use others progs, obviously will be faster with high, but the other prog will stuck,

so always better to use lower priority.

[Lord_Magneto]

I found what was wrong, I added a line from my previous encodes in the avs file. It was the line for TextSub, everything worked fine with it when I opened the avs file in vdub but the program would freeze when I tried to close the file and it would freeze when it was 100% completed in the encoding process. I guess I should switch to the subtitle topics. Thanks the assistance.

EDIT: I was able to solve the problem, I had a line in the avs file that was unnecessary LoadPlugin("C:\Apps\Encoding Tools\AviSynth 2.5\plugins\VSFilter.dll") I thought I had to load the filter but apparently I don't and that was causing the problem.