Bluray playback stutters due to delay reading next .m2ts file

[mythtv@…]

While watching BD disks stored on a remote backend, there are occasional stutters at fixed points during playback (i.e. repeatable each and every time). Upon investigation, it looks like the stuttering occurs when it reaches the end of one .m2ts file and starts the next. Looking at the frontend log, it seems that there is a ~2 second period where it stops requesting new data at the end of a file, then starts looking for the next file. I suspect that this drains the buffers, causing stuttering until the next file is opened and the buffers are filled again. I have attached the part of the frontend log with --loglevel debug and -v network which shows the pause.

[mythtv@…]

I should probably clarify that this is a disc backed up using makemkvcon backup --decrypt, not a BD ISO.

[mythtv@…]

I tried implementing a 'preload' of the next m2ts file in the playlist to reduce the time taken to switch to the new file, but the problem still persists. It would seem that bluray.c would need to be changed so that it was aware of the fact that it is reading from a buffer, and signal the buffer to reading from the next file once the buffered reads reached the EOF.

[jameswalker@…]

I can confirm the same behaviour which unfortunately makes MythTV a non viable bluray playing option until it is fixed as over 50% of my library uses the multiple m2ts approach.

I am on the latest update for 0.25 (fixes branch).

[Nicolas Riendeau]

Please no "me too"...

[peper03]

The problem is not caused because the next file is not preloaded but rather because the timecode jumps when reading from the next file (turn on the 'playback' logs to see it). This causes the player to think there's a sync problem and so there's a bit of a stutter until it's satisfied everything is back in sync again.

[Richard Hulme <peper03@…>]

In d5ba36f7c39f544a189097f52a8ef4453990e21f/mythtv:

Flatten Blu-Ray timecodes when switching from one clip to another to avoid pauses due to the player thinking there's a huge AV-sync issue.

Fixes #10294