[mythtv-users] Card 0 (type ) is set to start on channel 1 - Myth 0.21-159_trunk_r13460

[Michael T. Dean]

On 05/24/2007 10:30 AM, Brian wrote:
>> That means you didn't use the proper "Delete all capture cards" button.  
>> You may have used "Delete all capture cards on <hostname>".  There's a 
>> /huge/ difference.  One of them--and I'll let you guess which--leaves 
>> stuff around in tables that aren't the capturecard table.
> No, I used delete all capture cards. I was prompted with the Card 0 
> message when exiting mythtv-setup after I did this. I then dropped the 
> database and re-created everything. Saw the same message immediately 
> after that.
>
> I've deleted the cardinputid value from the database. We'll see what 
> happens. :)

OK, my saying that you didn't use "Delete all capture cards" was based 
on the assumption that card 0 was left over garbage from a previous 
configuration you weren't adding and deleting a capture card after 
"Delete all capture cards".

"Delete all capture cards" executes:
TRUNCATE TABLE capturecard;
TRUNCATE TABLE cardinput;

"Delete all video sources" executes:
TRUNCATE TABLE channel;
TRUNCATE TABLE program;
TRUNCATE TABLE videosource;
TRUNCATE TABLE credits;
TRUNCATE TABLE programrating;
TRUNCATE TABLE programgenres;
TRUNCATE TABLE dtv_multiplex;
TRUNCATE TABLE cardinput;

Whether you're using 0.20-fixes or SVN trunk.

So, TTBOMK, if you actually do a "Delete all capture cards" (or "Delete 
all video sources", there is no possible way you can have any left-over 
rows in cardinput.  Therefore, after you've cleaned up your DB, 
something in your setup procedure is creating a card 0, associating one 
of its inputs with a video source, and then deleting card 0 and leaving 
the cardinput configuration.

If in fact your DB were clean when you started adding cards, you'll have 
to explain the exact procedure you're using to add cards so I can either 
a) identify the bug in mythtv-setup or b) recommend changes to the 
procedure you're using.

Mike