btmoore
04-25-08, 10:55 PM
Looks like it is time to revive it, everything that old is new again, the new but old Catalog of HR2X BUGS.
These bugs appear to be back in force, please add you own, I pulled these oldie moldies from some posts over 1.5 years ago and didn't bother editing them because they are basically the same as what we are seeing now.
Here is what I am seeing:
Unwatchable Bug AKA Black or Gray Recordings
IKD BUG (Instant Keep Or Delete)
Partial Bug (13)
771 Bug - you get 771 but your signal strenghts are just fine
Here is the original Catalog of HR2X Bugs (http://www.dbstalk.com/showthread.php?t=74448) from 2006
and it's predecessor (http://www.dbstalk.com/showthread.php?t=81939&highlight=catalog+of+bugs)from 2007
Bug Name: Unwatchable Bug or negative number recording, Older names include BSOD and Black Screen, these older usages of the names did not describe lockups in the HR20, rather just a black screen associated with playback and the death of that recording. These older names should not be confused with the newer more lethal bug now called the black screen bug these usages are listed here for historic reasons.
First Identified Report: 08-30-06, 05:17 PM by Wally_Gator (http://www.dbstalk.com/showpost.php?p=641100&postcount=89)
Prognosis: Loss of recording, no recovery
History/Status: Currently active in 0x10b (http://www.dbstalk.com/showpost.php?p=757695&postcount=145)has been in every release of code, bug may be on decline, fewer reports noted. For a period of time some users called the unwatchable bug the Black Screen of Death
Postings of interest on the subject:
Unwatchable Recording and Partial Lost Recording Thread (http://www.dbstalk.com/showthread.php?t=67998&highlight=unwatchable)
How to: replicate a unwatchable bug (http://www.dbstalk.com/showthread.php?t=70665&highlight=unwatchable) Still works under 0x10b
Is the HR20 fundamentally flawed? (http://www.dbstalk.com/showthread.php?p=720768&posted=1#post720768)
Unwatchable recording (http://www.dbstalk.com/showthread.php?t=65303&highlight=unwatchable)
Symptoms: When a recording is selected for playback, user will experience a black screen. User can use trick plays but there will be no change in video status, if the trick play has a counter, it will increment but screen will continue to be black. Users may notice that the time code may contain a negative number but it may also contain just zeros, example 0:-59 or -1:-29 or 0:00. Click here for many examples of the negative time code. (http://www.dbstalk.com/showpost.php?p=720288&postcount=3)If a recording is currently in progress and trick plays do not work, it is highly likely that this recording will suffer the Unwatchable Bug, this same symptom was also experienced with the Partial Bug (potentially eliminated under latest versions of the code). A reboot will remove all recordings with the Unwatchable bug
http://www.dbstalk.com/attachment.php?attachmentid=6449&stc=1&d=1161542139
Example post of the Unwatchable Bug in 0x10b
http://www.dbstalk.com/showpost.php?p=757695&postcount=145
http://www.dbstalk.com/showpost.php?p=757765&postcount=150
Treatment: Delete the recording or reboot the HR20, your recording is lost.
__________________________________________
Bug Name: IKD Bug, AKA Instant Keep or Delete bug, unplayable bug, no play bug
Prognosis: Possible loss of recording
History/Status: Currently active in 0x10b
First Identified Report: 09-27-06, 07:56 PM dervari "Recording problems still - Unable to playback" (http://www.dbstalk.com/showthread.php?p=668564&highlight=Keep+Or+Delete#post668564)
Symptoms: Upon playing a recorded program you will instantly be prompted to Keep or Delete that program. A reboot may remove shows with the IKD bug. Some users have noted that repeated retires of playing a program with a IKD bug may result in successful playback.
Treatment: Attempt to replay the recording multiple times, this may result in a successful playback, rebooting may result in a recording that can be played back or it may be removed from the playlist.
__________________________________________
Recording
Bug Name: Partial Recording Deleted (13) by tibber
Items scheduled to record do not record completely and are deleted from the Playlist.
Prognosis: Loss of recording, no warning or workaround.
History/Status: Currently active in 0x10b.
Symptom: A scheduled event does not appear in the MyPlaylist. History for the item displays the following message: "This episode was partially recorded because it became unavailable. (13)"
Treatment: There may be two or more triggers for this defect: 1) the event was to record from a channel that is transient in nature, eg. channel 95, the sports subscription channels in the 700s, etc. 2) Guide data might be changing during the recording.
Version 1, where the channel for the event is transient and perhaps causes the HR20 to think that a recording was unsuccessful or partial. Seems to be most often reported on sports subscription channels such as NFL ST, NHL Center Ice, and channel 95.
Version 2, three consecutive recordings for December 21, 2006, on SLC local OTA channel 2-1 KUTVDT generated this error. The first, "Rudolph the Red-nosed Reindeer" did not record at all. The next two, "CSI" and "Shark", generated two history items each. The first, at the correct time, was this error. The second history item for each was 3 minutes past the hour and was a successful recording and seemed to be nearly complete. Each recorded for 59 minutes.
__________________________________________
And from my post on 10/29/06 (http://www.dbstalk.com/showthread.php?p=704860&highlight=771+bug#post704860)
771 bug - Searching for sat on tuner 1 or 2, I have see this message where both tuners are active and recording, where one tuner is blank and I had to stop the recording change the station and come back where it works just fine. I am assuming that there is some variability in how fast the unit can lock in to a transponder and that is causing some kind of time out error in the HR20. I wonder if there needs to be some more robustness in the coding here to make it more tolerant, perhaps some more retries or it could be that some status bit is not being set, but this need to be fixed because it causes a failed recording when the transponder are fine and all the cabling is fine.
These bugs appear to be back in force, please add you own, I pulled these oldie moldies from some posts over 1.5 years ago and didn't bother editing them because they are basically the same as what we are seeing now.
Here is what I am seeing:
Unwatchable Bug AKA Black or Gray Recordings
IKD BUG (Instant Keep Or Delete)
Partial Bug (13)
771 Bug - you get 771 but your signal strenghts are just fine
Here is the original Catalog of HR2X Bugs (http://www.dbstalk.com/showthread.php?t=74448) from 2006
and it's predecessor (http://www.dbstalk.com/showthread.php?t=81939&highlight=catalog+of+bugs)from 2007
Bug Name: Unwatchable Bug or negative number recording, Older names include BSOD and Black Screen, these older usages of the names did not describe lockups in the HR20, rather just a black screen associated with playback and the death of that recording. These older names should not be confused with the newer more lethal bug now called the black screen bug these usages are listed here for historic reasons.
First Identified Report: 08-30-06, 05:17 PM by Wally_Gator (http://www.dbstalk.com/showpost.php?p=641100&postcount=89)
Prognosis: Loss of recording, no recovery
History/Status: Currently active in 0x10b (http://www.dbstalk.com/showpost.php?p=757695&postcount=145)has been in every release of code, bug may be on decline, fewer reports noted. For a period of time some users called the unwatchable bug the Black Screen of Death
Postings of interest on the subject:
Unwatchable Recording and Partial Lost Recording Thread (http://www.dbstalk.com/showthread.php?t=67998&highlight=unwatchable)
How to: replicate a unwatchable bug (http://www.dbstalk.com/showthread.php?t=70665&highlight=unwatchable) Still works under 0x10b
Is the HR20 fundamentally flawed? (http://www.dbstalk.com/showthread.php?p=720768&posted=1#post720768)
Unwatchable recording (http://www.dbstalk.com/showthread.php?t=65303&highlight=unwatchable)
Symptoms: When a recording is selected for playback, user will experience a black screen. User can use trick plays but there will be no change in video status, if the trick play has a counter, it will increment but screen will continue to be black. Users may notice that the time code may contain a negative number but it may also contain just zeros, example 0:-59 or -1:-29 or 0:00. Click here for many examples of the negative time code. (http://www.dbstalk.com/showpost.php?p=720288&postcount=3)If a recording is currently in progress and trick plays do not work, it is highly likely that this recording will suffer the Unwatchable Bug, this same symptom was also experienced with the Partial Bug (potentially eliminated under latest versions of the code). A reboot will remove all recordings with the Unwatchable bug
http://www.dbstalk.com/attachment.php?attachmentid=6449&stc=1&d=1161542139
Example post of the Unwatchable Bug in 0x10b
http://www.dbstalk.com/showpost.php?p=757695&postcount=145
http://www.dbstalk.com/showpost.php?p=757765&postcount=150
Treatment: Delete the recording or reboot the HR20, your recording is lost.
__________________________________________
Bug Name: IKD Bug, AKA Instant Keep or Delete bug, unplayable bug, no play bug
Prognosis: Possible loss of recording
History/Status: Currently active in 0x10b
First Identified Report: 09-27-06, 07:56 PM dervari "Recording problems still - Unable to playback" (http://www.dbstalk.com/showthread.php?p=668564&highlight=Keep+Or+Delete#post668564)
Symptoms: Upon playing a recorded program you will instantly be prompted to Keep or Delete that program. A reboot may remove shows with the IKD bug. Some users have noted that repeated retires of playing a program with a IKD bug may result in successful playback.
Treatment: Attempt to replay the recording multiple times, this may result in a successful playback, rebooting may result in a recording that can be played back or it may be removed from the playlist.
__________________________________________
Recording
Bug Name: Partial Recording Deleted (13) by tibber
Items scheduled to record do not record completely and are deleted from the Playlist.
Prognosis: Loss of recording, no warning or workaround.
History/Status: Currently active in 0x10b.
Symptom: A scheduled event does not appear in the MyPlaylist. History for the item displays the following message: "This episode was partially recorded because it became unavailable. (13)"
Treatment: There may be two or more triggers for this defect: 1) the event was to record from a channel that is transient in nature, eg. channel 95, the sports subscription channels in the 700s, etc. 2) Guide data might be changing during the recording.
Version 1, where the channel for the event is transient and perhaps causes the HR20 to think that a recording was unsuccessful or partial. Seems to be most often reported on sports subscription channels such as NFL ST, NHL Center Ice, and channel 95.
Version 2, three consecutive recordings for December 21, 2006, on SLC local OTA channel 2-1 KUTVDT generated this error. The first, "Rudolph the Red-nosed Reindeer" did not record at all. The next two, "CSI" and "Shark", generated two history items each. The first, at the correct time, was this error. The second history item for each was 3 minutes past the hour and was a successful recording and seemed to be nearly complete. Each recorded for 59 minutes.
__________________________________________
And from my post on 10/29/06 (http://www.dbstalk.com/showthread.php?p=704860&highlight=771+bug#post704860)
771 bug - Searching for sat on tuner 1 or 2, I have see this message where both tuners are active and recording, where one tuner is blank and I had to stop the recording change the station and come back where it works just fine. I am assuming that there is some variability in how fast the unit can lock in to a transponder and that is causing some kind of time out error in the HR20. I wonder if there needs to be some more robustness in the coding here to make it more tolerant, perhaps some more retries or it could be that some status bit is not being set, but this need to be fixed because it causes a failed recording when the transponder are fine and all the cabling is fine.