E2 box, DVBS2 live TV pause/rewind/buffer. What and how?

[Joe_90]

Thanks @ccs - that confirms that the support files (.cuts .ap .sc and .meta) are built on the fly while the main .TS file is being created from the timeshift data. I presume the background process is "throttled" to reduce load on the system so that normal recordings etc. are not affected? This is all good background info. Question is - do we want to do anything with it? Is there an actual problem?

[ccs]

.... I think different boxes could well behave slightly differently. Is there an actual problem? Not sure really, I found it difficult to get my head round it to start with.
My advice (and I think yours) would be to use timers if you want to keep recordings and not to rely on timeshift unless you understand its potential limitations when saving recordings.

[ccs]

Last post:

Recorded 9 hours of timeshift without any issues, movielist accurate, and the .sc file took 13 minutes to get sorted.

nb. Initiated timeshift by pausing live tv, as it's configured off on my boxes by default.

[adm]

Last post:

Recorded 9 hours of timeshift without any issues, movielist accurate, and the .sc file took 13 minutes to get sorted.

nb. Initiated timeshift by pausing live tv, as it's configured off on my boxes by default.

So is the conclusion leave enough time between a request to convert timeshift to a record and actually viewing it? Perhaps 2 to 3 minutes per hour of recording dependant on SD or HD.
And even if viewed too early all that is likely to be wrong is the indicated length in the movie list but the actual recording length will be correct?

One other test - what happens after lengthy timeshift is told to convert to a recording and very shortly afterwards the channel is changed (before the convert process has finished)