If you have an x700 or x800m2, and you're trying to play back a Profile 7 file (ie a UHD with DV), use tsmuxer to create a BDMV folder output. Place the BDMV folder in the root of a USB drive.croweyes1121 wrote: ↑Wed Mar 20, 2024 1:37 pmHas anyone ever figured out a workaround for this issue that doesn't involve splitting the file (which I really would prefer not to have to do)? Surely there's some way to change a setting in tsmuxer that allows the file to be seekable...PlatypusW wrote: ↑Sat Dec 05, 2020 7:17 pmYes but that isn't enough for meRESET_9999 wrote: ↑Sat Dec 05, 2020 4:09 pm
I merged mine in a single TS file.
So if FF works for each individual part, that pretty much confirms the issue is related to the length of the movie.
thank you![]()
I still haven't got myself a x700 yet, but I dug out my old x800. It can't do dolby vision, but I had some time today and figured it should be close enough to see whats going on (they should be very similar internal players if not the same).
Started with the second hobbit film. The raw m2ts and the tsmuxer file both wouldn't seek. 'Operation not permitted'.
Tried cutting the file with tsmuxer to 2 hours and 45 minutes. Seek worked.
Then I went for 2 hours 50 minutes. Seek didn't work.
Something in tsmuxer caught my eye: "--cut-end=10200000ms"
To me that seemed like such a specific round number. I have now tested both hobbit 1 and 2...
If the file is 2 hours, 46 minutes and 39 seconds or shorter. The file will allow seeking.
If the file is 2 hours, 46 minutes and 40 seconds or longer. The file will not allow seeking.
Turns out in milliseconds that is:
9999000ms: Seeks
10000000ms: Does not seek
From all this, I believe that if the file is greater than (or equal to) 10 million millisconds then seeking will not work. Anything below seems to work fine.
Does this align with what you have experienced on the x700? Know any titles that might be under this 10 million ms 'limit' that don't allow seeking?
Note: For me, on the latest tsmuxer nightly, the resulting file was always 1 second less than what I put into the 'end'. So if anyone tries this, take this into account if you are trying to be precise.
Why there might be such a limit I'm not sure - maybe someone else might know that
Never seen something related to length in ms, at least 10 million...doesn't really strike me as a number that would normally cause issues in the computing world![]()
To my knowledge, there is no workaround for the seeking issue with TS files. I believe that is a device limitation.