[Bajanjack]

I should have know better....for yesterday's Eagles-Giants game I set BOTH of my HR20s for 1 and 1/2 hours additional time which should have totaled 4 and 1/2 hours. Guess what....both recorders stopped recording at 3 hours and 10 min!...The recording stopped with 7 min left in the game....I am aware of the "work around" to record the following shows to add time, but I thought this was fixed with the last update?..

 

[Steveknj]

I should have know better....for yesterday's Eagles-Giants game I set BOTH of my HR20s for 1 and 1/2 hours additional time which should have totaled 4 and 1/2 hours. Guess what....both recorders stopped recording at 3 hours and 10 min!...The recording stopped with 7 min left in the game....I am aware of the "work around" to record the following shows to add time, but I thought this was fixed with the last update?..

I had the same problem (which really bites because that last 5 minutes or so of the game was critical to the outcome, last Giants TD and the Eagles FG). It was my understanding that the bug was on "on the fly" padding, meaning I'm padding while the game is actually recording. So I fully expected the padding to work if I did it in advance. Guess I learned my lesson. I should have backed up the recording with one on my SD Tivo and I would have been covered.

 

[bonscott87]

Weird, I record several NHL games each week and always add a 30 min pad at the end when I setup the recording and I've never had a problem with it stopping.
I've never actually added padding after the recording started though.

 

[Earl Bonovich]

The extra padding is hit or miss right now.

Sometimes it works... Sometimes it is short by only a few minutes, other times it flat out doesn't do what it is supposed to.

DirecTV does know the problem exists though.

 

[tawnee]

Bajanjack, Steveknj, did you have any problem with about 3 minutes before halftime with pixelation? I am in Reading, PA. Had the problem for a short time then it went away. Just wondering if it was my HR20 or the feed?
Thanks

 

[Bajanjack]

Bajanjack, Steveknj, did you have any problem with about 3 minutes before halftime with pixelation? I am in Reading, PA. Had the problem for a short time then it went away. Just wondering if it was my HR20 or the feed?
Thanks

I did have a minor problem, yes....not sure as to the exact timing, I'm betting it's the feed...........

 

[Bajanjack]

The extra padding is hit or miss right now.

Sometimes it works... Sometimes it is short by only a few minutes, other times it flat out doesn't do what it is supposed to.

DirecTV does know the problem exists though.

I learned my lesson the hard way on this..(it's bad enough the Giants lost!)...from now on I'll record the following scheduled show to pad the time that way.......

 

[Steveknj]

Bajanjack, Steveknj, did you have any problem with about 3 minutes before halftime with pixelation? I am in Reading, PA. Had the problem for a short time then it went away. Just wondering if it was my HR20 or the feed?
Thanks

I had pixelation issues pretty much all weekend on the MPEG4 (local feeds). I did see it at one point in my recording, but I don't remember the specific time.

 

[LI-SVT]

I too padded the game and it cut off about the same time as the OP.

 

[christo76]

How well would recording the following show work with the HR20. I only ask because I recently noticed, while recording a Mythbusters Marathon, that the HR20 does not seem to continously record. It appears to stop the first program at X:59 and start the next show at Y:00 meaning it loses at least a minute.

With mythbusters it meant one stopped while they were discussing the outcome, and the next one started after they new show started and were discussing the new myth. BUT with football that could mean you end at 3rd and 1 in the red zone and the next one starts and somehow the opposing team has scored....

 

[rsblaski]

I had the same problem with the Giants/Eagles game. Exactly 3:10 recorded even with a 30 min pad.

The day before, however, I had 30 minute pads for both playoff games (one game on each of my hr20s) and the pads on both games/machines worked fine.

Another observation: during the Giants/Eagles, trick play was EXTREMELY choppy. FF and rewind would take one or two seconds to even begin, and then FF would stutter, stop, stutter.

The Jets/Patriots game was just fine. It was recorded on my other HR20 so I don't know if it was a hardware or software problem.

On the same machine I had the stutter problem, I also had a BSD on a Saturday recording of a program on Speed Channel.

Next week, I will record the playoff games on both machines and see if (both/neither/only one) have any problems. If this week's problem hr20 is the only one with problems, it may be time to consider that it may be in the hardware.

 

[Bajanjack]

I had the same problem with the Giants/Eagles game. Exactly 3:10 recorded even with a 30 min pad.

The day before, however, I had 30 minute pads for both playoff games (one game on each of my hr20s) and the pads on both games/machines worked fine.

Another observation: during the Giants/Eagles, trick play was EXTREMELY choppy. FF and rewind would take one or two seconds to even begin, and then FF would stutter, stop, stutter.

The Jets/Patriots game was just fine. It was recorded on my other HR20 so I don't know if it was a hardware or software problem.

On the same machine I had the stutter problem, I also had a BSD on a Saturday recording of a program on Speed Channel.

Next week, I will record the playoff games on both machines and see if (both/neither/only one) have any problems. If this week's problem hr20 is the only one with problems, it may be time to consider that it may be in the hardware.

Interesting on the "trick play" issues, I had the same thing watching the Giants game....the "skip back" was ineffective compared to my previous use...it would not really go back properly and often go a few frames ahead so I would miss part of the down......

 

[jjn]

I should have know better....for yesterday's Eagles-Giants game I set BOTH of my HR20s for 1 and 1/2 hours additional time which should have totaled 4 and 1/2 hours. Guess what....both recorders stopped recording at 3 hours and 10 min!...The recording stopped with 7 min left in the game....I am aware of the "work around" to record the following shows to add time, but I thought this was fixed with the last update?..

Same thing happened to me and boy was the wife abit miffed about it. And this is not the first time that its happened.

 

[swartzentruber]

I should have know better....for yesterday's Eagles-Giants game I set BOTH of my HR20s for 1 and 1/2 hours additional time which should have totaled 4 and 1/2 hours. Guess what....both recorders stopped recording at 3 hours and 10 min!...The recording stopped with 7 min left in the game....I am aware of the "work around" to record the following shows to add time, but I thought this was fixed with the last update?..

Glad to see this post. I padded on the fly (adding 1.5 hours), had the identical thing happen (quit recording a 3'10"). At least I know it's not just my machine.
Earl, if this is a known problem, I'd say it needs to get prioritized quick, as it's a pretty nasty bug for any sport event recording. I thought maybe it was just mine. Maybe knowing that everyone stopped at 3'10" will help debugging.