[Finished] Improvements to Live TV playback rate matching - for testing (2 Viewers)

[Palm_Maniac]

Hi,

since the evening with the two fierce statues there were no further problems. The error can be seen in the TSWriter.bak from 22:30.

I also have the EPG Grabbing active because I have channels in the list that are not supplied by TV Movie Clickfinder, and I have the Idle Scan active.

In addition, I had changed for testing something. Last week I provided the server with a 60GB SSD M.2 for the operating system. So can now also switch off this hard drive during periods of inactivity. Because I was curious and I wanted to leave no stone unturned, I have laid the Timeshift memory to the HDD on and off the ramdisk. The errors were less. There were noticeably fewer short stills and much less pixelation. At the moment, I still have the time shift on the HDD. Actually, should rather affect the other way around and make the ramdisk fewer problems.

I'll now be even Timeshift on the HDD and tomorrow switch to the RAM disk. Let's see if it somehow affects.

 

[Owlsroost]

Hi,

since the evening with the two fierce statues there were no further problems. The error can be seen in the TSWriter.bak from 22:30.

I also have the EPG Grabbing active because I have channels in the list that are not supplied by TV Movie Clickfinder, and I have the Idle Scan active.

In addition, I had changed for testing something. Last week I provided the server with a 60GB SSD M.2 for the operating system. So can now also switch off this hard drive during periods of inactivity. Because I was curious and I wanted to leave no stone unturned, I have laid the Timeshift memory to the HDD on and off the ramdisk. The errors were less. There were noticeably fewer short stills and much less pixelation. At the moment, I still have the time shift on the HDD. Actually, should rather affect the other way around and make the ramdisk fewer problems.

I'll now be even Timeshift on the HDD and tomorrow switch to the RAM disk. Let's see if it somehow affects.

OK, good


From post #100:

my first report for a movie night with the new TSWriter. Absolutely great. They're gone. No pixelation and no short stills more. Even the transitions between programs and commercial breaks are perfectly clean. It has given me almost brought tears to the eyes.

So is this still true - no pauses or pixelation with the latest TsWriter ?

 

[azzuro]

Hey in testing.
Nothing to say for now. At least ne error or freeze.
For information i have disabled dvb epg when the tuner is idle.
Also with 2 stream frin each tuner. On 2 client.

 

[Palm_Maniac]

So is this still true - no pauses or pixelation with the latest TsWriter ?

Yes absolutely. Never ran live TV on both clients as well as now. Also last night, absolutely no problems. Neither stills and pixelation, nor stuttering in the commercial breaks. Today I present shift back to the RAM disk to, then I can also report on it tomorrow.

 

[Palm_Maniac]

Hi, Today there was yet again a freezer, Live TV just stops. I then waited even longer if it continues on its own, but had to stop and restart again. Now I'm curious if it occurs again, because before the error I had the time shift memory switched back to the RAM disk.

 

[azzuro]

logs

 

[Owlsroost]

Hi, Today there was yet again a freezer, Live TV just stops. I then waited even longer if it continues on its own, but had to stop and restart again. Now I'm curious if it occurs again, because before the error I had the time shift memory switched back to the RAM disk.

If it *is* the recent mods to TsWriter causing the freezes, I'm puzzled because the changes between the 3.1.31.2 and 3.1.31.3 versions are very small (especially since it isn't actually crashing and 3.1.31.2 seems to be stable).

 

[Palm_Maniac]

Hi,

tonight I fell asleep while watching TV. When I woke up to 4am the television was still, however, the saver mode. After printing on the remote I saw a still image of the current program that I could not cancel. I had to turn off my clients to the "hard way". In TSWriter log dive for the period around 4 am the following entries to the all equal:

[2015-07-24 03:52:37,073] [8a65c18] [1f78] - MultiFileWriter: failed to create file E:\\live5-0.ts.tsbuffer5.ts
[2015-07-24 03:52:37,073] [8a65c18] [1f78] - Failed to reopen old file. It's currently in use. Dropping data!
[2015-07-24 03:52:37,573] [8a65c18] [1f78] - FileWriter: ParkFile(), m_hFile 0xffffffff, m_hFileParked 0xffffffff
[2015-07-24 03:52:37,676] [8a65c18] [1f78] - MultiFileWriter: failed to create file E:\\live5-0.ts.tsbuffer5.ts
[2015-07-24 03:52:37,676] [8a65c18] [1f78] - Failed to reopen old file. It's currently in use. Dropping data!
[2015-07-24 03:52:38,176] [8a65c18] [1f78] - FileWriter: ParkFile(), m_hFile 0xffffffff, m_hFileParked 0xffffffff
[2015-07-24 03:52:38,278] [8a65c18] [1f78] - MultiFileWriter: failed to create file E:\\live5-0.ts.tsbuffer5.ts
[2015-07-24 03:52:38,278] [8a65c18] [1f78] - Failed to reopen old file. It's currently in use. Dropping data!
[2015-07-24 03:52:38,779] [8a65c18] [1f78] - FileWriter: ParkFile(), m_hFile 0xffffffff, m_hFileParked 0xffffffff
[2015-07-24 03:52:38,883] [8a65c18] [1f78] - MultiFileWriter: failed to create file E:\\live5-0.ts.tsbuffer5.ts
[2015-07-24 03:52:38,883] [8a65c18] [1f78] - Failed to reopen old file. It's currently in use. Dropping data!

The Discontinuity Errors are definitely with me at last all past, but these entries are new. The Timeshift files were all still in the RAM disk, but was not crowded. Now I have changed a setting of the parameters RAM disk and watch the behavior today again. I have to point "Allocate Memory dynamicaly" off, which I had previously active. Now the appropriate size of the RAM disk is occupied at a time and not more dynamic.

Should these stills still occur, I ask again about to disk and turn the RAM disk. Thus, it was at least initially better.

 

[Owlsroost]

Hi,

tonight I fell asleep while watching TV. When I woke up to 4am the television was still, however, the saver mode. After printing on the remote I saw a still image of the current program that I could not cancel. I had to turn off my clients to the "hard way". In TSWriter log dive for the period around 4 am the following entries to the all equal:

[2015-07-24 03:52:37,073] [8a65c18] [1f78] - MultiFileWriter: failed to create file E:\\live5-0.ts.tsbuffer5.ts
[2015-07-24 03:52:37,073] [8a65c18] [1f78] - Failed to reopen old file. It's currently in use. Dropping data!
[2015-07-24 03:52:37,573] [8a65c18] [1f78] - FileWriter: ParkFile(), m_hFile 0xffffffff, m_hFileParked 0xffffffff
[2015-07-24 03:52:37,676] [8a65c18] [1f78] - MultiFileWriter: failed to create file E:\\live5-0.ts.tsbuffer5.ts
[2015-07-24 03:52:37,676] [8a65c18] [1f78] - Failed to reopen old file. It's currently in use. Dropping data!
[2015-07-24 03:52:38,176] [8a65c18] [1f78] - FileWriter: ParkFile(), m_hFile 0xffffffff, m_hFileParked 0xffffffff
[2015-07-24 03:52:38,278] [8a65c18] [1f78] - MultiFileWriter: failed to create file E:\\live5-0.ts.tsbuffer5.ts
[2015-07-24 03:52:38,278] [8a65c18] [1f78] - Failed to reopen old file. It's currently in use. Dropping data!
[2015-07-24 03:52:38,779] [8a65c18] [1f78] - FileWriter: ParkFile(), m_hFile 0xffffffff, m_hFileParked 0xffffffff
[2015-07-24 03:52:38,883] [8a65c18] [1f78] - MultiFileWriter: failed to create file E:\\live5-0.ts.tsbuffer5.ts
[2015-07-24 03:52:38,883] [8a65c18] [1f78] - Failed to reopen old file. It's currently in use. Dropping data!

The Discontinuity Errors are definitely with me at last all past, but these entries are new. The Timeshift files were all still in the RAM disk, but was not crowded. Now I have changed a setting of the parameters RAM disk and watch the behavior today again. I have to point "Allocate Memory dynamicaly" off, which I had previously active. Now the appropriate size of the RAM disk is occupied at a time and not more dynamic.

Should these stills still occur, I ask again about to disk and turn the RAM disk. Thus, it was at least initially better.

Can you attach the server and client logs please ?

I think what *may* have happened is that the client has frozen with the 'live5-0.ts.tsbuffer5.ts' file still open. This prevents TsWriter from deleting the file (so it can re-create it and re-use it), and means it will try and create a new (extra) buffer file instead. Eventually it will reach the maximum number of buffer files allowed and then it will just drop the data - timeshifting will stop at this point. But I need the logs for more info....

 

[Palm_Maniac]

Here the Logs.