[mythtv-users] Events at the beginning of a recording

Jan Ceuleers jan.ceuleers at gmail.com
Sat Feb 4 07:04:18 UTC 2023


On 04/02/2023 07:27, Jan Ceuleers wrote:
> On 03/02/2023 21:24, Klaas de Waal wrote:
>> The REC_PENDING event is now coming before the REC_STARTED event, as
>> committed to master and fixes/33.
>> See Forum discussion https://forum.mythtv.org/viewtopic.php?f=9&t=5263
>> <https://forum.mythtv.org/viewtopic.php?f=9&t=5263>
>> I think this was the same problem as what is discussed in this thread.
> 
> I'm on fixes/32 so will have to upgrade, but thank you very much for
> tracking this down.
> 

I upgraded to fixes/33, but I still see the incorrect ordering.

<190>Feb  4 07:50:50 mythtv[2909935]:
/home/mythtv/system-events/recording-started called with parameters 32
20230204075100 by PID 2909935
/home/mythtv/tuner_command[2909943] hdmicap1.xperim.be 121
<190>Feb  4 07:50:50 mythtv[2909938]: /home/mythtv/tuner_command called
with parameters hdmicap1.xperim.be 121 by PID 2909938
/home/mythtv/tuner_command[2909946] hdmicap1.xperim.be 121
<190>Feb  4 07:50:50 mythtv[2909938]: /home/mythtv/tuner_command called
with parameters hdmicap1.xperim.be 121 by PID 2909938
/home/mythtv/tuner_command[2909946] hdmicap1.xperim.be 121
<190>Feb  4 07:50:50 mythtv[2909951]:
/home/mythtv/system-events/recording-pending called with parameters 32
20230204075100 -241 by PID 2909951
/home/mythtv/have_video_lock: hdmicap1.xperim.be returns 0
/home/mythtv/start_streaming hdmicap1.xperim.be
/home/mythtv/start_streaming: URL
http://192.168.1.69/dev/info.cgi?action=streaminfo&rtp=on&multicast=on&mcastaddr=192.168.1.60

/home/mythtv/blast_arduino.sh: 1 121
/home/mythtv/tuner_command[2909946]: exit 0

This log is produced by my own scripts, including the recording-pending
and recording-started scripts, as well as various scripts invoked
through mythexternrecorder configuration.

As you can see the recording pending event is fired during the same
second as the recording started event, but later, and with a negative
SECS parameter (-241 in the above example). This log is for a recording
that was due to start (according to the schedule data) at 7:55am, with
zero preroll in the recording rule itself, with RecordPreRoll set to
250, and with WakeUpThreshold set to 5.

Perhaps the fix hasn't made it into the mythbuntu ppa yet; will test
again tomorrow.

Cheers, Jan




More information about the mythtv-users mailing list