been getting out of lip sync on timeshift

Hi there, I have been getting a couple of times where I have paused a programme, went to go play it again and the speech is not synced up to the lip movement.
I have changed the 320GB mechanical Hard drive for a 1TB SATA SSD so I am thinking it might be that maybe?
 
Lip sync should be automatic but Humax and hdmi is a pita at the best of times. ANY trick play can / will upset lip sync as will severe errors (glitches) in the received transport stream.

Some say you can even get lucky in rewinding the resumed live stream a bit and force a se-sync... You might also try switching TV source away from foxsat and back (as that forces a new hdmi handshake).

Safer to hit the red <record> button (twice iirc) to make the foxsat record the rest of what is being watched... then watch the recording... when a stop play then restart almost invariably (in my experience re-syncs in the case of any errors).

NB live stream buffer is the 0.ts file and writes/overwrites the same bit of the disk... eventually corruption on spinny disks has caused some to rename it as 0.ts.old or similar and then the foxsat uses a different disk area to create a new 0.ts file... Modern SSD with wear levelling and such may be more immune to the repeated use of the same sectors? or not?
 
NB live stream buffer is the 0.ts file and writes/overwrites the same bit of the disk... eventually corruption on spinny disks has caused some to rename it as 0.ts.old or similar and then the foxsat uses a different disk area to create a new 0.ts file... Modern SSD with wear levelling and such may be more immune to the repeated use of the same sectors? or not?
The SSD may only wear level within the disc partition the timeshift buffer is in. If that is small the SSD won't have much space to wear level in so it won't achieve much. I don't know where the Foxsat HDR puts the timeshift buffer.
 
I can correct lip-sync by cycling the TV through its own tuner and then back to the HDMI from my Humax, so the HDMI interface has to re-handshake. That indicates (in my case) it's a HDMI problem, but that could be the TV as opposed to the Humax.
 
How does the SSD know about partitions, let alone files?
Depends where the wear levelling is being done. It could be in the operating system recognising an SSD is in use and levelling within the partition. I've worked on devices using flash directly (not an SSD) that do wear levelling that way. Or it could be the SSD itself in which case as you say the SSD doesn't know about partitions and could wear level across the entire free space on the drive.
 
It could be in the operating system recognising an SSD is in use and levelling within the partition.
Assuming you are talking in general here, although it seems quite niche even then.

TRIM support wasn't introduced into the Linux kernel until 2.6.33 or thereabouts. The HDR Fox T2 has 2.6.18 and the Foxsat is probably earlier (can't easily check), so they won't have it.
This is bad news for use of SSDs on these models, AIUI anyway.
(I have one on my HD Fox, but the TSR is turned off and it does almost no recording and very few disk writes, so it will probably last longer than the unit itself, or broadcast TV, or me.)
 
Last edited:
Back
Top