House record prob. log attached, what's it mean?

[Opus4]

Originally Posted by gmijackso

I can see how disconnecting the cable would tell me which mobo slot a named card was in but not sure how that helps determine where something had recorded.

The Recording Detail screen in the default STV gives the name of the tuner used to record a show, after "Encoded by:".

The only thing I can think of to try next is to disable fox from card 1. But since both cards are using the same lineup, I'm not sure it's possible without creating a new lineup, which is always difficult to impossible for me since the entire las vegas area uses the same cable provider with the same lineup (the pick a similar area trick doesn't work here).

You can go through the process of changing the lineup from the Source Details screen & then choose to copy the lineup when asked. Since those cards both use the same physical connection, you'll have to set this property first:

epg/force_ask_to_copy_lineup=true

I'm not sure if you would need to rescan the channels.

- Andy

[gmijackso]

Originally Posted by Opus4

The Recording Detail screen in the default STV gives the name of the tuner used to record a show, after "Encoded by:".

Well, the Fringe episode that recorded after house was recorded by what I've been calling card 1 (the card without the #2). In looking at the log for Fringe, it too has the line that has the -0 at the end and the very similar line without it. So it's probably safe to say that Fringe recorded last week just fine on the same tuner that caused problems leading to an erasure of Terminator this week. House last week appears to have the same setup info as well. This means that House and Fringe were recorded back to back using the same tuner on the same channel last week, House was deleted, Fringe remained fine.

To further complicate the problem, this is the same tuner that is tuning the wrong channel right now (but obviously not always).

Originally Posted by Opus4

You can go through the process of changing the lineup from the Source Details screen & then choose to copy the lineup when asked...

Does that mean that both cards will have different lineups at that point even though the lineups are the same (i.e. both cox, and copies of one another)? Also, I thought the HD cards (or maybe just the guide?) were heavily dependant on the channel name (i.e. KVVUDT in this case). Does this account for that as well?

Please pardon my ignorance here. :-)

[Opus4]

Originally Posted by gmijackso

To further complicate the problem, this is the same tuner that is tuning the wrong channel right now (but obviously not always).

I can't help with that; maybe support will have some way to track that.

Does that mean that both cards will have different lineups at that point even though the lineups are the same (i.e. both cox, and copies of one another)? Also, I thought the HD cards (or maybe just the guide?) were heavily dependant on the channel name (i.e. KVVUDT in this case). Does this account for that as well?

They will be different lineups & separately configurable. The channels will be listed in the guide just like they are now.

- Andy

[gmijackso]

Ok, thanks Andy. I'll give that a shot tomorrow I think, provided I have time. I have to get off to bed now.

Thanks for all your help!

[gmijackso]

Finially got a reply from support today, though it's very vague... I've sent a follow up asking for much more clarity. Here is a copy of the email.

Fred,
Sorry for the delay.
One of the developers looked this over and said it deleted the file because
it was a partial recording. There's a bug in the current version and it's
been fixed for the next release.
Thanks,
George Oms
SageTV, LLC

I asked what exactly the "bug" is, deleting the files or fragmenting the files? Noted that it was odd that it was in the current version, though I'm not using the current version and asked what verstion the bug exist in. Asked when the next version is slated for relase since it's "fixed" there. And asked about my tuner tuning the wrong channel periodically.

Any ideas decoding the message? What do you think George meant?

[Opus4]

The file was deleted because it was not completely recorded.

It was suggested to me that you use the bug submission form next for further help to see if there is a way to determine why the recordings did not complete successfully in the first place. There's a link for that on the forum's main page, in the beta forums area.

- Andy

[pgman]

I just wanted to jump in here again and say that everything recorded fine this week. "House" and "Fringe" were both in my "recorded TV" bin when I got home. I don't know what is different - I changed nothing.

[gmijackso]

Well, mine recorded fine, but didn't. My server recorded an hour for House, and an hour for Fringe, but both hours were of the HD2 channel instead of the HD1 (which is the tuning problem discovered last night).

Now I wonder if I have 1 problem presenting itself in 2 ways, i.e. tuning wrong and segmenting files, or if I have two problems. I don't have a lot of free time this evening, so I haven't had any time to do anything to fix the problem, so for now I removed the offending source.

In another thread I did get the suggestion to have it not auto-delete broken files. I'll probably give that a shot when I can, but I think the first thing to fix now is the tuning problem since it doesn't matter if the programs are segmented if it's not recording the correct channel anyways.

[3rob3]

I just wanted to chime in that this issue appears to be happening to me also. Last night I saw my server recording Fringe from 9-10. I went to watch it at 10:30 and there was nothing there, no evidence of any recording. I have mine set to not auto-delete. This is on a HDhomerun, so it's not tuner specific.

[gmijackso]

Got another response from support yesterday. I've been super busy and haven't had time to do anything with Sage, including watch shows.

Here is the response... why won't they answer questions asked? And why is the standard answer to any problem upgrade? It was fine, it's not now. No versions changed, and no specifics are being given about this "bug" he claims exists, so why would changing versions be better? GRRrrr.

Fred,

No there isn't. The capture card stopped producing data and Sage then had to
restart the recording.

Try upgrading the drivers for the capture card and see if that makes a
difference and also upgrade Sage to the current version as well.

George

-----Original Message-----
Is there any indication as to the cause of the partial recording? It
appears that the tuner used is occasionally tuning the wrong channel (tuning
the channels HD2 instead of the primary) even though the same channel map is
used for both of my HD tuners. Do you have any suggestions for this
problem?

You say there is a bug in the current version, but I'm not using the current
version, I am using 6.3. This problem has not aways existed though I've
used 6.3 for a LONG time. What exactly does this bug you speak of do and
what verstion does it exist in? Since this bug is fixed in the next
release, when is that release scheduled?

Thanks
Fred

[Opus4]

I don't see how support's reply was ignoring your questions.

You asked whether there was any indication about the cause of the recording problem. The answer was that there was no info about that in the log.

You said you are using an older version. It is often suggested to try upgrading to the latest version because there are improvements & bug fixes made all along, or there wouldn't be a point in new versions. Support also suggested checking to see if there was an updated driver for the tuner -- maybe a newer tuner driver could better handle whatever the recording problem was.

But, I suggested above that you file a bug report. Did you do that? The developers might be able to do some further logging to see if it can be determined what the recording problem was. They've also changed how the determination is made to remove corrupted recordings like you have had. If it isn't missing too much of the recording, maybe it won't delete it with the concept that some of the show is better than none. That would be the 'bug' that is referred to.

- Andy

[kaseyq]

The first 5 minutes of House this week were corrupt on my system. I'm using the HVR 1600 and the HVR 1800 ( aka 418/885 ).

[gmijackso]

Originally Posted by Opus4

I don't see how support's reply was ignoring your questions.

I asked about my channel tuning problem, which I totally understand if ignored since it's somewhat of a different problem, though I believe they go hand in hand.

I asked what the symptoms of this "bug" is and got no response. I asked what versions this "bug" is known to exist in since in their first reply he said it was in the latest version. If it were in no previous versions, it wouldn't exist in the version I'm running. I asked when the release of the next version without the "bug" was scheduled.

So you're correct Andy, he answered 2 questions, but seeing as how I asked at least 6, I would consider acknowledging <50% of questions asked, ignoring my questions.

Frankly, I don't believe for a moment that this "bug" exists, or has been fixed in the next version. I believe I got a canned response, that is given when they don't know or don't care. How could this be a bug that has been fixed in the next version if support can't find a cause in the logs?

Originally Posted by Opus4

But, I suggested above that you file a bug report. Did you do that?

Honestly I have not yet. As reported earlier I've been super busy. The post earlier was after checking my e-mail while at work as a matter of fact. I haven't even had time to split the channel maps as you had suggested, it was just faster to remove the source until more time is available.

I will submit requested bug report in mere moments.

[Opus4]

Originally Posted by gmijackso

Frankly, I don't believe for a moment that this "bug" exists, or has been fixed in the next version. I believe I got a canned response, that is given when they don't know or don't care.

You aren't being lied to, so I don't think they would appreciate that comment. I know I wouldn't.

In my previous post, I told you what the bug was considered to be that support is referring to. It has nothing to do with the tuner problem; it has to do with how the resulting partial recording is handled, depending on how much of it exists. Personally, I wouldn't call it a 'bug' but just a change of parameters for how the partial recording is handled, at least according to what I understand.

How could this be a bug that has been fixed in the next version if support can't find a cause in the logs?

You don't seem clear on what the log does/doesn't show. The log doesn't indicate what went wrong on your tuner. That's the part that has no cause in the log. It is quite clear in the log why the file was deleted & that's the action that is being changed.

- Andy

[gmijackso]

Originally Posted by Opus4

Personally, I wouldn't call it a 'bug' but just a change of parameters for how the partial recording is handled, at least according to what I understand.

Nor would I, which is probably why I overlooked the possibility that the purposeful programming that results in method in which partial programs are handled is a bug. But if that's what they're suggesting that's fine, and I apologize for hurting any feelings.

But the fact still remains, that the question was asked, and not answered (except by you after posting the lack of an answer).

Originally Posted by Opus4

You don't seem clear on the concept that the log doesn't indicate what went wrong on your tuner. That's the part that has no cause in the log. It is quite clear in the log why the file was deleted & that's the action that is being changed.

I'm very clear on that. My misunderstanding was in what exactly they were calling a bug. Since the program was written to handle partial files in the manner it does, I wouldn't have expected them to consider it a bug, nor call it a bug. This lead me to believe that there was some other bug pertaining to my actual problem, the breaking of the file in the first place.

Since the log doesn't give any indication as to why the file was broken, and with me believing that the bug of which they spoke was about the breaking of the file, it seemed a bit odd that the "breaking of the file bug" could have been fixed in the next version if it was the cause was yet unknown. Do you see my fairly logical progression here?

I now understand (again from you, not from any answer to direct questions asked of support) that the "bug" was actually a change to the way partial files are handled.