Separate names with a comma.
Discussion in 'TiVo Roamio DVRs' started by brianric, Sep 7, 2013.
Been happening since around the last update. Definitely CBS shows for me.
The S3 hasn't seen a software update in years. If this existed in the S3 software we'd have heard about it long before now.
Yes, it appears that it is CBS shows. I watched about 5 NBC shows last night and it never happened once. Checked some previously recorded shows on other networks like USA and such and it never happened.
The audio/video glitch happens right about the 30-40 sec mark into playback, I clocked it on about 6-7 recordings, although on "The Millers" if it was there I never noticed it, the rest clearly had the glitch.
This happened/happens on both the S3 and the Roamio.
My local station is CBS O&O(owned and operated) KPIX in San Francisco and I see that you are located in NH so I'm guessing you have CBS-owned WBZ? Curiously enough my local CBS-owned The CW, which broadcasts out of the very same room as KPIX did not exhibit the issue on this week's "Supernatural"
So, I'm not sure where to go from here, maybe a moderator could split this conversation into a new thread? As far as it being a TiVo issue that doesn't seem likely if the S3 hasn't had an update in years.
That makes sense. Thanks for pointing that out Dan!
Actually the S3s recently went from 11.0k to 11.0m to straighten out the "expired cookie--no TiVo Desktop transfers" problem, right around the time that S2s went from "b" to "c" (9 point something, not 11).
Fortunately S3s don't seem to be choking on the reboot and partition switch as much as some S2s seem to be.
I am still having this issue. Does anyone know when it will actually be fixed. With 6 tuners there should be no overlapping recording glitch on the same channel with back to back shows.
They turned this feature off for a while and just brought it back in 20.3.8.
Just curious but are the channels you're recording MPEG-2 or H.264? Knowing what I know this feature is going to be almost impossible to do perfectly in H.264.
I'm sorry. Yes, the glitch has returned. It will be resolved again in the next update. I apologize for the trouble.
"resolved again in the next update" is great Marketing speak.
Does that mean the functionality will remain, it will just work now? (unlikely)
Or will they just turn it off again? (likely)
With the word "again" I'm guessing they'll just turn it off. Must have been a regression that was missed.