Plugin: Sage Job Queue (SJQ)

[Slugger]

Originally Posted by personalt

This is somewhat of a loose SJQ question.

When i have SJQ run comskip I use :CPU LOW and runs as a low priority task as show in the taskmgr. However if I have SJQ run ffmpeg it doesnt seem to respect the priority and runs and 'normal' prioirty in task mangager.

is there a way to set this up to run at low priority?

Make sure the :CPU setting is set to "LOW" for both tasks (it is case sensitive).

Also, it's possible that ffmpeg is resetting its priority. Check for command arguments for ffmpeg that set the process' priority.

[waters10]

I have a quick question. I'm setting up comskip for the first time. For now, I just want some basic comskip functionality and the ability to not process some channels.

Do I still need comskip monitor or dirmon2 if I'm using this? Or does this effectively eliminate the need for those?

Thanks!

[Slugger]

SJQ would replace dirmon2 and comskip monitor. If you're just starting out, I would suggest starting with SJQv3 (since SJQv2, the topic of this thread, will no longer be supported once SJQv3 is moved out of beta). Feel free to ask any questions about SJQv3 in the SJQv3 thread.

[Slugger]

With the release of SJQv3 beta snapshot 659 (SJQ v3.0.0.659), SJQv2 is now officially at end of life. I will no longer support any version of SJQ from the 2.x or 1.x streams. Bugs found in these older versions will not be fixed (though a reported bug might be forward fitted to SJQv3, if applicable) and bugs found in SJQv3 will not be back fitted to these older versions, if applicable. All users are encouraged to upgrade to v3.0.0.659 or newer.

SJQv3 remains in beta, but at this stage it's just while final testing is completed and the beta tag is expected to be removed prior to Christmas. I have personally been running SJQv3 for about two months with no major issues. I consider SJQv3 to be as stable, if not more stable, than SJQv2 and it is the recommended version of SJQ at this time. Again, the beta tag only remains while the last bit of polish is applied to v3 - stability is not an issue at this time. All future support questions should be directed at the SJQv3 thread.

Thanks to all the testers and early adopters of SJQv3 for their feedback!

[phelme]

Silly question.

So I'm now using SJQ to transcode favorites using the built-in SageTVTranscoder by way of the AutoCompress STVi external .autoCompress file trigger. I'm using SJQ to get the conversions done outside of prime-time.

It all works great... but how do I now delete the .autoCompress file when the transcoding is finished? Is there a way I can delete non-media files with SJQ that I'm missing? (thus making this a "silly question")

The File Cleanup is not what I'm after because I'd like to delete the .autoCompress file immediately.

thanks.

[Slugger]

Originally Posted by phelme

Silly question.

So I'm now using SJQ to transcode favorites using the built-in SageTVTranscoder by way of the AutoCompress STVi external .autoCompress file trigger. I'm using SJQ to get the conversions done outside of prime-time.

It all works great... but how do I now delete the .autoCompress file when the transcoding is finished? Is there a way I can delete non-media files with SJQ that I'm missing? (thus making this a "silly question")

The File Cleanup is not what I'm after because I'd like to delete the .autoCompress file immediately.

thanks.

Is the file name based on the recording file's name? So if the recording is Seinfeld.mpg then there's also a file named Seinfeld.autocompress? If so, then just write a batch script that deletes the named file on the command line and then pass it %d%/%p%.autocompress and it should delete it immediately. There are some gotchas to this method, namely there's no way (within SJQ) to ensure that the autocompress completed successfully before running the batch file to delete the autocompress file. If that's not an issue then good, but if it is then you'll have to use some other mechanism to ensure that the batch file only deletes the autocompress file if it's known that the compression completed successfully.

There is no internal command within SJQ to delete arbitrary files.

[phelme]

Originally Posted by Slugger

There is no internal command within SJQ to delete arbitrary files.

That's kind of what I figured. I'll either use the batch file method or let the File Cleaner do it after all. Once its been converted to the .mp4 format, it really doesn't matter if the .autoCompress file is still there or not.

Thanks!

[personalt]

I am using SJQ to transcode shows into a new folder that is not inside the list of folders that sage is supposed to use. the problem is that the transcoded show end up on the list of recorded shows.

this puts me into an endless loop where SJQ keeps transcoding the transcoded files.

what I dont understand is that I have sage only storing shows in
v:\shows\ and the files are transcoded to v:\transcode\

is sjq doing something that would cause the transcoded file to get imported?

if [IsTV == "true" && IsActivelyRecording == "false" && IsScheduledRecording == "true" && (Title == "American Chopper" ||Title == "Disaster House" || Title == "Income Property") ] {
:PRIORITY 90
:TRANSCODEOPTS "iPhone-Widescreen" "true" "v:\\Transcode\\"
_TRANSCODE

[Slugger]

When using the SageTV transcoder, Sage will keep track of recorded files even if you move them outside of your listed SageTV directories. And since Sage still knows about the transcoded file, it keeps passing it to SJQ for processing.

The strategy here to avoid the endless loop is to check the file path and ensure it's not already in your archive directory. I'm assuming that your V:\Transcode dir is used only for the storage of transcoded recordings. So modify your rule to something like this:

if [IsTV == "true" && IsActivelyRecording == "false" && IsScheduledRecording == "true" && (Title == "American Chopper" ||Title == "Disaster House" || Title == "Income Property") && Filename !^ "V:\\Transcode\\"] {
   :PRIORITY 90
   :TRANSCODEOPTS "iPhone-Widescreen" "true" "v:\\Transcode\\"
   _TRANSCODE
}

Basically I'm just adding the condition that you shouldn't transcode files that are already in the V:\Transcode directory (i.e. prevent the endless loop you're seeing).

[ehfortin]

Hi,

I have installed SJQ sooner today and implemented a simple rule for COMSKIP. It grab all the files I was expecting it to and jobs are distributed over my 3 clients. The jobs seems to run correctly for some of them (I get some .edl file with data in it) but all the jobs appears in the "Failed Tasks" folder. Here is the end of a log for such a job as seen by SJQ:

 0:00:00 - 215426 frames in 6538.18 sec (32.95 fps), 4.69 sec (6.82 fps), 99%
215441 frames decoded in 6538.88 seconds (32.95 fps)
@ 00030A00]error while decoding MB 52 1, bytestream (-4)
[h264 @ 00030A00]concealing 3600 DC, 3600 AC, 3600 MV errors
[h264 @ 00030A00]mmco: unref short failure

Now, this is the end of the log as per Comskip:

215441 Frames Processed
################################################################
Time at end of run:
Fri Dec 11 15:58:50 2009
################################################################

There is no errors there so... I don"t know why they are moved to "Failed Tasks"... Now, it is hard to figure if they are or not failed as I have to verify individually the logs for each one...

Is that a know problem? Is there a way to correct it?

My config for a client is very simple:

COMSKIP {
   "C:/comskip/comskip.exe \"%c%\""
}

Can"t be simpler, right? BTW, everything is at the most recent version (jetty, SJQ 3.x) with SageTV last official version (no alpha or beta). Comskip is also at latest donator revision.

If you have any idea or comments, please let me know.


ehfortin

[evilpenguin]

@ehfortin

COMSKIP {
  :RETURNCODE 1
   "C:/comskip/comskip.exe \"%c%\""
}

This'll get you fixed up.

[Slugger]

With SJQv3 just about ready to come out of beta, I'm officially closing this thread and directing all users to upgrade to the latest version of SJQv3. With this final post, support for SJQv2 and SJQv1 has ended.

Please visit the new SJQv3 support thread for all issues and discussions related to SJQv3.