Process previously/suspended queued jobs - how to resume?

[rogerg]

Hi,

 

I was recording video using a DSLR and BackyardEOS. At completion of recording it had 7 jobs queued to process. Hovering the "7" which was slowly flashing it showed text like "Suspended: 7 queued". It seemed the jobs weren't being processed, indeed suspended. A short time later BackyardEOS crashed and upon restart it doesn't seem to know the 7 exist. Is there a way to get BackyardEOS to now process the 7 jobs I have sitting in the BackyardTEMP]download directory?

 

Thanks,

Roger.

[admin]

Hi,

 

I was recording video using a DSLR and BackyardEOS. At completion of recording it had 7 jobs queued to process. Hovering the "7" which was slowly flashing it showed text like "Suspended: 7 queued". It seemed the jobs weren't being processed, indeed suspended. A short time later BackyardEOS crashed and upon restart it doesn't seem to know the 7 exist. Is there a way to get BackyardEOS to now process the 7 jobs I have sitting in the BackyardTEMP]download directory?

 

Thanks,

Roger.

 

Roger, how many recordings did you do?  You had to do more than 1 to get 7 items in the the queue; that I'm 100% positive.

 

Did you do 7 recordings back to back? 

 

The good news is that you have not lost anything.  The job in the queue is to take all these individual jpgs in the TEMP folder to encode into an AVI.

 

You can just as well take those jpgs and stack them as-is in Registax or other software.  In fact these jpgs are exactly the same one that ends up in the AVI, 1 for 1.  You can also use VirtualDub to encode them into an AVI... but staking the individual jpgs will give you the same exact result.

 

In v3.1 I have changed the way backend jobs are processed.  Basically they will get their own Windows process and have next to 0 performance impact on the actual BYE application UI.

 

Guylain

[rogerg]

Thanks Guylain,

 

I was doing a mosaic of the Moon, and rushing to get i done before the Moon set behind trees. So the captures were all back-to-back 1000 frame grabs at 5x. 13 were successfully processed with 7 unprocessed.

 

I'll do as you suggest and just load the JPG's in to Registax. I had wondered if they were equivalent but wasn't sure. Thanks! 

[admin]

Thanks Guylain,

 

I was doing a mosaic of the Moon, and rushing to get i done before the Moon set behind trees. So the captures were all back-to-back 1000 frame grabs at 5x. 13 were successfully processed with 7 unprocessed.

 

I'll do as you suggest and just load the JPG's in to Registax. I had wondered if they were equivalent but wasn't sure. Thanks! 

 

Yeah, in 3.0.x the processing of AVi in the queue is suspended during a subsequent recording.  The purpose is to leave as must CPU possible for the next recording to get maximum frame rate.

 

As I said in 3.1 they will continue to be encoded in a low priority thread under a different windows process.  My tests shows that this has next to 0 impact on the frame rate of subsequent recordings... which is not the case in 3.0.x <_>

 

Hope this helps,

 

Guylain