VideoReDo Batch Manager has stopped working

Rau

New member
Vsn 637.
The Batch Manager is failing with the completion bar showing 99%. "A problem caused the program to stop working correctly. Windows will close the program and notify you if a solution is available."

The job is a Joiner Compilation, but note that the 'join' is towards the start, not at the finish. The output file (H264/.ts) does appear to be fine and 'complete' for all practical purposes. There is a 2nd job in the batch queue, but I assume it is the first which is the problem.

Here is the tail-end of the Log File:

H.264 Encoding Done.
2012-05-12 11:48:57 H.264 encoder info: --------------------------------------------------------------------------------
2012-05-12 11:48:57 H.264 encoder info: Frames: 72013 incoming, 72013 encoded
2012-05-12 11:48:57 H.264 encoder info: Bits written: 10639279.68 kbits (1329909.96 kbytes)
2012-05-12 11:48:57 H.264 encoder info: Avg. Bitrate: 3693.53 kbits per second
2012-05-12 11:48:57 H.264 encoder info: Time elapsed: 1374.94 seconds
2012-05-12 11:48:57 H.264 encoder info: --------------------------------------------------------------------------------
2012-05-12 11:48:57 Output muxer processing thread complete. Video in: 72014, Out: 72014, Buffer: 0
2012-05-12 11:48:57 Output muxer processing thread complete. Audio stream 0 In: 120019, Out: 120019, Buffer: 0
2012-05-12 11:48:57 Muxer add / delete audio: stream: 0, add: 1 delete 0, sync: -64.00
2012-05-12 11:48:57 H264 encoder: Process thread complete. Video frames, In: 72013, Out: 72014
2012-05-12 11:48:57 Output complete.
Input file: D:\Recorded TV\Silk_ABC1_2012_05_10_20_23_06.wtv
Output file: V:\TV Viewing\Mark Zuckerberg- Inside Facebook (2011)_ABC1_2012_05_10_21_34_20.ts
Mode: Frame Accurate
~ Output file: V:\TV Viewing\Mark Zuckerberg- Inside Facebook (2011)_ABC1_2012_05_10_21_34_20.ts

TS Video packets: 7272809
TS Audio packets: 600095
TS PSI packets: 48588
TS Null packets: 0
TS MUX Rate (Mbps): 19.20000
-TS Discontinuities: 1
Video output frames: 72014
Audio output frames: 120019
Processing time (secs): 2054
Processed frames/sec: 35.05
Actual Video Bitrate: 3.69 Mbps
* Audio resync frames added: 1
 

V7Goose

New member
I saw this one time before with 637 a day or two ago, and I just hit it again. In my case, I am outputting .mpg files re-sized from letterbox to widescreen.

In the first instance, the batch had two jobs in it, and the error happened at the end of the second job. In this instance, the batch has three jobs in it, and the error hit at the end of the first job. In both cases, the output file exists and seems to be complete and without errors.

I restarted this batch, removed the first job (which did seem to complete, despite the crash), and the second job completed without errors. The third and final job in the batch is still running...
 
Last edited:

harveyge

Member
Get same problem when running batch. Stops with an error but file is completed and looks fine. Deleting entry in btach queue and then starting batch completes the remaining files in the batch queue provided it does not stop again with errors.
 

Danr

Administrator
Staff member
V7Goose and harveyge, We've seen this here too on occasion. In the interest of trying to duplicate your issue:

1) What type are your source files, SD or HD?
2) What CPU type and OS are you running?
 
I had a similar problem with the batch manager failing on every other queued job. Since the problem popped up out of the blue one day, I figured the only thing that changed on my system was an antivirus update, so I disabled real-time virus scanning and then the batch manager processed all jobs as it should. After that, I setup exceptions for the various VRD exe processes and the WTV file extension; I have not encountered the problem since then.

This occurred with Microsoft Security Essentials running on Windows 7 64-bit and an Intel Core i7. Source files are HD MPEG-2/AC3 WTV files.
 

V7Goose

New member
I believe that all instances for me were with SD input files in .TiVo format; although, it is possible the first time was an HD .TiVo file - I just cannot remember. I do know that the majority of times were with SD input files.

In every case where this happened, I was doing a full recode due to dimension changes. I think about 50% of the batches like this have experienced the problem, and those batches only had two or three jobs each. I have run one 87 job batch that did full recodes of just 10 second clips from .ts to .mpg format, and that batch did not experience the problem.

I am running an AMD Phenom II quad-core processor and W7x64 Pro.
 
Last edited:

V7Goose

New member
This problem is still there in 641a. The very first program I ran in batch crashed at 99%. The output file seems to play OK, all the way to the end, but the time stamps are messed up in VLC player.

This error is more than just a minor irritant since it causes the output stats for an entire batch run to be just discarded. In this case it happened to be the first job in the batch, but in many others, it happens later in the run and I am left with no way to know if the previous jobs worked properly or not.

This job is an SD letterboxed 4:3 TiVo program being zoomed and converted to 16:9 (still mpg output). As in the OP, the job has a very short join at the beginning (a 9 second intro clip). I will leave the same job in the batch queue and run it again later today to see if it continues to fail.

UPDATE:
When I re-ran the identical batch (same job still queued from the crash), it ran without a hitch. The time stamps in the output file are still messed up when playing with VLC, just like they were in the one where the batch crashed. This is odd to me because a previous run of the same job done several days ago with a slightly lower bit rate does not have any problems with the time stamps.
 
Last edited:

Danr

Administrator
Staff member
This sounds like two issues.

1) Regarding batch, email me at support. I'll send you some test versions to try out. In the meantime, if you can replicate the batch issue, try this: Instead of running the output in batch, have the batch manager create a command file, and run the command file. This is similar to the old batch, and may help us isolate where the problem originates.

2) Regarding the time stamps, can you be more specific about what's going on? Can you duplicate with a short file?
 

V7Goose

New member
I cannot replicate the batch problem on demand. Yesterday I ran maybe 15 different batches for testing (including the one above that was the not re-created but still queued from the first crash), and I think three or four of them crashed at 99%. In each case, the resulting output files were complete and played to the end without errors - it is just the batch manager that crashes when trying to wrap up the job.

In the first crash, the batch had two jobs - it crashed at the end of job 1, and job 2 was never started. The re-run of the same batch went fine. In each other case yesterday where the batch manager crashed at 99%, there was only one job in the batch. In the past (while running 638), I have had this crash happen in batches of all different sizes, and the crash is NOT always on the first job. I will contact you by email on this as requested.

I agree that the time stamp issue seems to be unrelated, and I do have some interesting observations on it from my tests yesterday. I will start a new thread on that problem as soon as I pull my notes together.
 

harveyge

Member
Seems to be related with the updating of some file or data at the completion of an individual batch job. There is no pattern to the batch manager crashing. Happens with SD or HD and converting HD to SD. The last file where the batch manager stops always seems to have completed without errors and can be played without problems. Occassionally the meta data has not been updated or is incorrect. Sometimes a day will go by without erros and then all of a sudden every batch job will stop. Am now trying to run batch jobs by creating a batch job command file to see if they also fail. I am running an i5 processor with Windows 7 Professional and also an i5 processor with Windows 7 Ultimate and both computers have shown the same error. When it fails the last batvh job is still in the batch queue. If this batch job is removed and the batch jobs restarted all is well. The batch manager stopping seems to be after the indivdual job has completed but before the job is removed from the queue and the next job commenced. The log file has not been updated so there is no indication of the error.
 

Dan203

Senior Developer
Staff member
I think it has to do with some sort of timing issue when the batch manager tries to get the output complete info. We're looking into it

Dan
 

harveyge

Member
I ran multiple jobs in batch using batch command line file and none failed, but this may just be todays results. Will keep you informed and continue to use batch command file until it fails.
 

harveyge

Member
Performed tests of creating batch queuse with batch manager, saving command file and runing batch jobs both using batch manager as well as commanf file. Command file never failed, whereas batch manger had problems 30% of the time. Batch manager always fails at the end of a job while trying to upadte some file data. Last job processed is fine but job entry remains in batch queue. Deleting this last job from queue and restarting batch manager jobs then completes the outstanding jobs. Again I can confirm that Batch manager does not always crash, but an unable to help with what is causing it to stop.

Thanks

Geoff
 

Danr

Administrator
Staff member
@Geoff, I had asked V7Goose to try this (haven't heard back yet), go to Tools>Options>Completion Alerts, and Check "Bring to front steal focus" option. This is the old style method of displaying the file completion dialog, and while it doesn't affect the batch manager display, it does change internally where the output statistics are collected.

We are still trying to pinpoint whether the problem is in the batch manager itself, or something in VideoReDo that is causing a failure in the batch manager.
 

V7Goose

New member
I just sent you an update, but to keep the information together in this thread, I'll post it here too.

I had a batch job that had failed at least five times in a row, so I was keeping it for testing this problem. I changed the Completion Alert option and re-ran the batch - it worked fine.

But then I reset the Completion Alert, recreated the same batch job, and it also worked. So unless we can find a way to reliably reproduce the batch crash on demand, we still do not know if any successful run is anything more than just chance.
 

harveyge

Member
Did "Tools>Options>Completion Alerts, and Check "Bring to front steal focus" option". Thought all was fine but on the last file in a batch of 20 jobs the error occured. Output file was fine. Just last failing job left in batch queue. No log entries. Also ran same batch job in command line and no errors. It is difficult to get the error to occur non randomly.

Geoff
 

Danr

Administrator
Staff member
@harveyge, Been working on this for a couple of days, and I can't duplicate it at all. However, I did find a couple of timing related issues which have been fixed now for 642.

I'm running a few fast outputs and major recoding jobs overnight. If they work OK, I'll post the 642 build in this thread as an alpha for everyone to try out.
 

harveyge

Member
You are most probably right. Looks like a timing issues to me. I have confirmed that running jobs in a batch command line does not seem to have any problems are at least it has not failed yet in batch command line. Look forward to trying the alpha.

Geoff
 
Top Bottom