it does not prime, sorry. i kept it a changer-only app so as not to unintentionally interfere... not knowing
Originally Posted by Cyberai
what each user's end-use might be.
it would be easy enough to do what you want, however. wrap the changer command in a bash script and call that from
mythv for channel changing. i am not sure what sort of issues you have with the stbs going off-line, so relying
on the changer failing as indication that the stb is unstable is not a guarantee... you might be able to do the
channel change but still have an un-primed box.
my recommendation follows... assuming you are targeting the stb by GUID:
command for mythtv-backend channel changer parameter would be something like:
where GUID is the manually-entered GUID of the target stb. each tuner entry should correspond to the correct
primechange $channel GUID
GUID for that stb.
if myth is changing a channel, you know it will likely be recording and want to make sure it is primed...
primechange script pseudo-code would be something like:
that would be your best bet... but with a potential down-side: if it does encounter and unstable stb and primes,
mythchanger -c $CHANNEL -g $GUID (and any other arguments you might run it with)
returns ok, exit
mythprime -c <your safe priming channel> (and any other arguments you might run it with)
mythchanger -c $CHANNEL -g $GUID
it would likely interrupt any recordings in-progress on the other stbs, as they are all primed blindly by mythprime.
it was intended to be run when starting/restarting the backend only, so was written to prime everything, and not
if that is an issue for you, i can add the prime by GUID code to mythprime when i have the chance. feel free
to email me if this is the case and i'll see what i can do.