[mythtvnz] Install: trouble with starting channel

chris chris at thebayleys.net
Tue Jan 4 08:37:08 GMT 2011


On 04/01/11 13:46, Kenneth Dixon wrote:
>
>
> On 4 January 2011 13:13, Chris Bayley <chris at thebayleys.net 
> <mailto:chris at thebayleys.net>> wrote:
>
>     That's basically correct, trouble is 'StartingChannel' is a drop
>     down box that won't populate even after a successful scan!
>     Frustrating as I think that is the only staring between me and
>     myth nirvana. Interestingly there is a bug lodged against 0.23
>     which has another user experiencing the same problem with a DVB-T
>     card. That bug shows as fixed for 0.24(which I am using). It's
>     getting pretty close to 'Use the Source Luke!' time !
>     Curiously when I use setup to add a new capture card not one but
>     two cards are added to the database! Exiting setup gives me
>     warnings about startup channel on two cards.
>     I wonder what you have in your DB ?
>
>     Will now spend some time fixing motorbikes until frustration
>     subsides !
>
>     Kind regards,
>     Chris Bayley
>
>
> Ah I see, do your channels have a "Video Source"  in the backend setup 
> (or sourceid in channels table in DB)?
>
> looks like double tuner entry could be the "Max recordings:" setting 
> in capture card -> recording options. This produces extra entries and 
> allows multiple recording off one tuner as long as the recorded 
> channels are on the same multiplex. Mine is a dual tuner and has 6 
> entries in the DB all up and my "Max recordings" setting is 3 for each 
> tuner, so it adds up.
>
> Ken
>
>
>
> _______________________________________________
> mythtvnz mailing list
> mythtvnz at lists.linuxnut.co.nz
> http://lists.ourshack.com/mailman/listinfo/mythtvnz
> Archives http://www.gossamer-threads.com/lists/mythtv/mythtvnz/

I believe at present it might be some database related issue. I notice 
the following SQL error in the backend log which doesn't look too good:

SELECT channum, callsign, channel.chanid,        atsc_major_chan, 
atsc_minor_chan,        name, icon, mplexid, visible,        
channel.sourceid, cardinput.cardid, channelgroup.grpid FROM channel LEFT 
JOIN channelgroup ON channel.chanid     = channelgroup.chanid JOIN 
cardinput         ON cardinput.sourceid = channel.sourceid JOIN 
capturecard       ON cardinput.cardid   = capturecard.cardid WHERE 
sourceid='1';
ERROR 1052 (23000): Column 'sourceid' in where clause is ambiguous

That looks ambiguous SQL to me but maybe someone who knows SQL and it's 
versions distinctions better than I can comment ?

I am running 0.24 from pcmenery ppa and this upgraded the database from 
the 0.23 schema - potential stuff up ?

Also my MySQL is 5.0.3 (not so late) as it is on my NAS - maybe a problem ?

investigations continue....

Chris
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ourshack.com/pipermail/mythtvnz/attachments/20110104/a8e77600/attachment.htm 


More information about the mythtvnz mailing list