Unregistered
|
Whatever priority you set to be the default priority, it ends up being "normal" priority (tho vdubmod (and vdub) will claim it's the set pri).
You'll notice the difference once you select the priority (again) to set the priority (this time, it works 
Vdubmod version 1.5.1_1
Vdub has the same problem, haven't tested it against 1.5.3 tho.
Example run :
queue up a few encodes, punch up job control (f4), set default priority to "lower", and start the jobs.
You'll notice a certain system lag (especially if you're working on a remote computer ). So punch up the vdub(mod) status window (notice the priority shown is indeed "lower", click on the combobox to make it expand, and choose (tadaaaa) "lower".
Now notice the increase in overall system responsiveness, indicating that vdub(mod) is now indeed operating at "lower" priority.
|
