[mythtv-users] silence detection blocks jobqueue [ mythcommflag; silence.py ]

[Roger Siddons]

On Mon, 20 Oct 2014 11:05:36 +0100, Stefan Pappalardo  
<stefan.pappalardo at gmx.de> wrote:

> When I get it right then there are two ways to call the script:
>
> 1.) /usr/local/bin/silence.py --chanid %CHANID% --starttime %STARTTIME%  
> --loglevel debug --nodblog --syslog local7 --presetfile  
> ~/.mythtv/silence.preset
>
> or
>
> 2.) /usr/local/bin/silence.py %JOBID% --loglevel debug --nodblog  
> --syslog local7 --presetfile ~/.mythtv/silence.preset
>
> Which way do I have to store in the database in field "UserJob1"?
> The second way won't work in terminal, because there is no relation to  
> the recording. And where can I get the right JobId to use?
>
> Stefan Pappalardo
>

Correct. For user jobs use (2). For testing you can use either (1) or (2)  
without the --syslog. However (2) is easier.

When myth runs a job it is recorded in the database. I don't know how long  
it persists or when it actually gets cleaned up but I've still got jobs  
 from 2 days ago available.

In practice, this means that you can actually use a recent jobid from the  
log in your terminal tests. I suspect your 14065 is still there - if not  
run it again as a user job & get the new job id.

In theory "silence.py <job id> --loglevel debug" should be enough, as:

- /usr/local/bin should be in your path already
- I thought --nodblog was default now?
- you don't want to send output to the syslog; you want it to come out on  
the terminal
- this particular example isn't using a preset so the presets file is  
redundant.