[mythtv-users] liveTV ok, recording fails

[John]

On 12/12/2018 13:18, Tim Draper wrote:
>   ---- On Tue, 11 Dec 2018 22:18:22 +0000 jksjdevelop <jksjdevelop at gmail.com> wrote ----
>   > a quick test shows that that channel does not work for me either
>   >
>   > run a query like this
>   >
>   > mysql -umythtv -ppassword --database mythconverg
>   > select serviceid,channum,sourceid,callsign,mplexid from channel order by
>   > mplexid,channum;
>
> +-----------+---------+----------+-------------+---------+
> | serviceid | channum | sourceid | callsign    | mplexid |
> +-----------+---------+----------+-------------+---------+
> ...
> |      8315 | 100001   |        5 | Bloomberg TV       |     172 |
> |      8316 | 100001   |        5 | Bloomberg TV       |     172 |
> |      8311 | 100001   |        5 | Bloomberg TV       |     172 |
> |      8312 | 100001   |        5 | Bloomberg TV       |     172 |
> |      8314 | 100001   |        5 | Bloomberg TV       |     172 |
> |      8313 | 100001   |        5 | Bloomberg TV       |     172 |
> |      9225 | 100001   |        5 | Bloomberg TV       |     172 |
> |      9208 | 122      |        5 | E4                 |     172 |
> |      8305 | 122      |        5 | E4                 |     172 |
> |      8300 | 123      |        5 | E4+1               |     172 |
> |      8340 | 124      |        5 | More4              |     172 |
> |      8341 | 301      |        5 | Film4+1            |     172 |
> ...
>
> results are on all the 172 multiplex.
> ignore the 'bloombergTV' results - my channel script had an oversight on it so any of my disabled channels (channum >10000 ) got its callsign changed to bloomberg! based on your example & digitalspy forums, they should be channel4+1.
>
>
>
> _______________________________________________
> mythtv-users mailing list
> mythtv-users at mythtv.org
> http://lists.mythtv.org/mailman/listinfo/mythtv-users
> http://wiki.mythtv.org/Mailing_List_etiquette
> MythTV Forums: https://forum.mythtv.org

Yes that looks correct but the mux has changed frequency so did a rescan 
not fix it.