<div class="gmail_quote">On Fri, Sep 11, 2009 at 11:38 AM, Michael T. Dean <span dir="ltr"><<a href="mailto:mtdean@thirdcontact.com">mtdean@thirdcontact.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On 09/11/2009 11:29 AM, Kenneth Emerson wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="im">
On Fri, Sep 11, 2009 at 10:03 AM, Jay Roberts wrote: <br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
In trying to troubleshoot intermittent recording problems on a multiple<br>
encoder system, it would really help me to be able to determine which<br>
encoder recorded shows recorded on using info in the database.</blockquote></div></blockquote></blockquote><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">One of the problems I see in tracking the encoder number with the recording<br><div class="im">
is that this number is not cast in stone.<br>
</div></blockquote>
Yeah, and it's generally meaningless information in the long term, so wasn't considered worth saving in the database.<div class="im"><br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Any time you delete and re-add<br>
tuner cards, the encoder numbers change. It would be up to the user to<br>
delete/add tuner cards in the exact same order each time in order to keep<br>
the tuner IDs the same.<br>
</blockquote>
</div>
And, really, on many systems, the "tuner number" or "card number" or ... doesn't mean anything as the order in which physical cards are init'ed is likely to change on reboot (meaning kernel order will change) unless you explicitly add udev rules or module options to prevent. On a system with multiple identical capture cards, few users take the time to lock the card order.<br>
</blockquote></div><br>I was trying to troubleshoot tuner audio issues (similar to Jay's predicament), and I found that i had to revert to the log to find the tuner that was used for the recording. I was able to do it, but it was a bit tedious.<br>
<br>How about adding a 'displayname' column to the recorded table that would be populated with the 'displayname' of the tuner that was used for the recording? That would have made my troubleshooting SO much easier... ;-) IMHO, this would be much more useful than just the 'cardid' which, as already noted, will often change upon system upgrades. <br>
<br>A column with this data would also be extremly helpful with the 'borked recordings' detection being talked about in other threads... ;-) <br><br>J-e-f-f-A<br>