Taylor Jacob wrote:
Quoting Steve Davies <[EMAIL PROTECTED]>:
>
2) channels.chanid - I was under the impression that chanid was meant to
be in the range (sourceid*1000) to (sourceid*1000)+999. I do not know
whether this is a tradition or a requirement, but I have 2 sources, 1
DVB and 1 non-DVB. The DVB scan created all new chanid numbers to
continue from the highest existing number, rather than checking for the
highest number in the appropriate range. This meant that the end result
was much more confused and the chanid and sourceid no-longer matched.
Can you give me some specifics? It should have used sourceID * 1000 as the base
for the chanid..
I just worked out my problem :) I had a source 2 record in the table
with a chanid of 3014 - I put it there to save some data from
deletion... This will have thrown off the next-number calculation. I
should have changed sourceid to "3" in this saved record to prevent this.
Sorry :-)
Steve
--
Steve Davies [EMAIL PROTECTED]
PGP Fingerprints:
DH/DSS : 5D85 8164 91D7 E9CC 4F80 842B AB86 93D9 8938 7612
RSA : 4E2E E60F 3D76 9E7E 70F9 901B 70FA 56C8
RSA4096: 02BE 5C0E EFA2 E1E4 EA89 C9CC 1E4F F654 3BC7 B65E
_______________________________________________
mythtv-dev mailing list
[email protected]
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev
