Unofficial VirtualDub Support Forums [Powered by IB Forums]

Printable Version of Topic
Click here to view this topic in its original format

Unofficial VirtualDub Support Forums > Newbie Questions > Job Queue Stops Working Until You Kick It

Posted by: Hellerick Apr 16 2013, 02:27 PM

Hello.

I'm trying to use VirtualDub to convert a bunch of soft-subbed MKV-based AVS-files into hard-subbed AVI-files. I have 66 files to be converted, and of course I don't want to process them manually, so I made JOBS file to process them all. Here it is (uh, it looks pretty ugly): http://pastebin.com/4FMUDTwh

Everything works fine except one problem. After one job is completed (its status changes to "done"), the next job doesn't start (its status remains "waiting"). Only after I manually remove the completed job, the next job switches to "In progress" and actually starts being executed. So now every half an hour I have to check VirtualDub and remove the completed job -- it won't work any further without it. Of course, it's better than doing everything manually, but still I doubt it's supposed to work this way.

What Am I Doing Wrong?

Posted by: dloneranger Apr 16 2013, 04:05 PM

There's nothing unusual about your jobs file (just for info, that's how I use vdub 24/7, but in master/slave mode)

What does taskmanager show virtualdub's doing cpu wise after one finishes? thrashing or idle?

You could try running the jobs file from a command line to see if it's a problem with ending/starting a job, or the job file monitor
(edit paths for actual locations)
Vdub.exe /x /s "c:\mydir\virtualdub.jobs"

[edit]
What happens if you load the mkv's directly instead of using avisynth?
Is the jobs file anywhere 'weird' - mapped drive letter etc?

Posted by: -vdub- Apr 16 2013, 08:24 PM

Part of your script

VirtualDub.Close();
// $endjob

// $job "Job 4"

Try with this below added via a text editor to each job end

//
//--------------------------------------------------

Your script would then be

VirtualDub.Close();
// $endjob
//
//--------------------------------------------------
// $job "Job 4"

Posted by: dloneranger Apr 17 2013, 05:50 AM

@vdub, that shouldn't make a difference
Virtualdub just uses the $job and $endjob to mark the start and end of each job
All the other // etc's that don't have a $command in them are just to make it more readable to users and ignored

Posted by: Hellerick Apr 17 2013, 11:29 AM

QUOTE

You could try running the jobs file from a command line to see if it's a problem with ending/starting a job, or the job file monitor
(edit paths for actual locations)
Vdub.exe /x /s "c:\mydir\virtualdub.jobs"

Thanks, now it works just fine!

QUOTE

What does taskmanager show virtualdub's doing cpu wise after one finishes?

While converting a file, it was taking 90% of CPU and 250 MB of RAM. While waiting for the new job it was taking 50% of CPU and 25 MB of RAM.

QUOTE

What happens if you load the mkv's directly instead of using avisynth?

I wish I knew how to do it

Thanks again!

Posted by: dloneranger Apr 17 2013, 01:23 PM

How odd, looks like it's hanging when deciding what job to do next.....
I'm guessing you have a dual core cpu and one core is thrashing

You might be interested in the master/slave mode for using virtualdub
An old post about it http://forums.virtualdub.org/index.php?act=ST&f=4&t=18260&hl=master,and,slave

For mkv's
You can use the Directshow plugin, or the mkv plugin (there are other plugins for various types as well)
http://forums.virtualdub.org/index.php?act=ST&f=7&t=19488
They go in the same plugins32 folder that filters go into
When you open a file - in the dialog box, click the file you want, then change the dropdown at the bottom for the plugin you want to use

The Directshow one will use all the codecs etc that windows media player uses, so that's easiest to use
The mkv one will need the right codecs installed if they're not in the system - the link to fcchandlers page has got an aac codec, and ffdshow has a config page for vfw codecs where you can turn on eg h264 etc

Posted by: -vdub- Apr 17 2013, 09:20 PM

@dloneranger It was the only difference between my jobs list and hellerick job list apart from other details settings and files etc. Actually mine could be a job list from Virtualdub Batcher II v1.2.8 by Beppe which works fine with all virtualdub releases. Which I Use for large batch jobs in 3 steps (actually 4) Load Drag'n'Drop files, load settings, add to batch list, save batch file filename.jobs

There are a few virtualdub batch tools unknown if they all work with current version. I may try some others soon to see if have other extra options for batch processing. To see if any have ability where can choose decoder to use for multiple files drag'n'drop without having to edit the .jobs batch list manually for this.

Posted by: dloneranger Apr 17 2013, 09:29 PM

Yeah, they're just for readability though and don't do anything

Posted by: phaeron Apr 23 2013, 03:28 AM

It's been a while since I looked at this code, but I'm pretty sure this is happening because of the duplicated $id lines in the jobs file. Jobs with duplicate IDs is a no-no. Simply leave off the $id lines when generating a new job script and VirtualDub will generate new IDs on load.