tsMuxer Open Source

[von Suppé]

Is it possible to add files with .eac3 and .truehd+ac3 extension to the "All supported media files" ?
It would be nice when they would show by default in tsMuxer's browsing windows.

[medikoo]

Thanks to tsMuxer I'm capable to mux UHD discs and burn them on BD-R media.

Still, I found that my player (Panasonic DP-UB9000) while supporting UHD written on BD-R DL discs, occasionally stutters when playing them, as if the discs were slow (or the player not reading them at needed speeds).

I wonder whether it can be a media issue (I use Verbatim M-DISC BD-R DL), and can be improved by trying some other BD-R DL disc (?) or is it something related to how this player reads BD-R DL discs, potentially capping them to the certain speed limit, and that's not solvable with given player.

Did anyone try to burn and play UHD on BD-R DL with success? Note I mux discs simply to replace audio files (to get a version in my language for my kids), I do not do any size squashing and I'm not interested in that.

[SeeMoreDigital]

@medikoo,

Which 'git' version of TSmuxer GUI are you using?

[a5180007]

Originally Posted by medikoo

Still, I found that my player (Panasonic DP-UB9000) while supporting UHD written on BD-R DL discs, occasionally stutters when playing them, as if the discs were slow (or the player not reading them at needed speeds).

Test the read speed of your discs. With 128 mbps UHD you need a read speed of 4x throughout the BD-R.

[von Suppé]

for eac3 and thd showing up in the browsing windows

[medikoo]

Originally Posted by SeeMoreDigital

Which 'git' version of TSmuxer GUI are you using?

It's git-aed1949 (but I don't think it's related to the problem)

Originally Posted by a5180007

Test the read speed of your discs. With 128 mbps UHD you need a read speed of 4x throughout the BD-R.

I tested and tried two different BD-R DL media, and read goes as 16MB/s at start, but shortly after settles on 20Mb/s+ for rest of a disc. It's what I get with LG Drive on macOS system.

UHD at highest moment may need 144Mbp/s (18MB/s), so that should be fine.

I suspect that Panasonic player reads it unconditionally at x2.

And seeing that maximum standard rotation for BD DL BD-ROM media is x2 (http://www.hughsnews.ca/faqs/authori...-reading-speed) I assume that's very likely :/

Pity it doesn't support BD XL at UHD reading speeds, that would solve it.

[von Suppé]

Originally Posted by von Suppé

Is it possible to add files with .eac3 and .truehd+ac3 extension to the "All supported media files" ?
It would be nice when they would show by default in tsMuxer's browsing windows.

I haven't checked since what version, but latest nightly build does show .ac3+thd extension, where .thd+ac3 don't show by default in browser window. Can you fix it please?
Thanks in advance

[filler56789]

SUGGESTION:
give to the periodical official releases better names than the unimaginative and unhelpful
mac.zip lnx.zip w32.zip w64.zip.

After many years of the infamous vcredist_x86.exe and vcredist_x64.exe I thought that everybody would have already learned the lesson.
Sadly I was wrong.

[gonca]

For LPCM tracks, would it be possible to demux to W64 to avoid splitting larger tracks?

[von Suppé]

Nice to see both .thd+ac3 and .ac3+thd files are showing up in the browser windows.
for the fix.

[varekai]

Thanks for the update and the continued impressive work with this one of a kind absolutely necessary tool!

[d3rd3vil]

Whats the problem when converting a Dolby Vision mkv to m2ts leads to gray bars (instead of black ones)?

[SeeMoreDigital]

Originally Posted by d3rd3vil

Whats the problem when converting a Dolby Vision mkv to m2ts leads to gray bars (instead of black ones)?

What are your playback display device/eqipment?

[d3rd3vil]

Its a 2016 Oled with an Oppo 203. Sometimes it works/worked with black bars but nowadays its usually grey bars

[Kuler087]

Originally Posted by d3rd3vil

Its a 2016 Oled with an Oppo 203. Sometimes it works/worked with black bars but nowadays its usually grey bars

your content is probably cropped and it's not a tsmuxer issue.
The oppo and sony x700/x800m2 will produce grey letterbox if you play a DV video that was encoded without black bars (3840X1600).

[d3rd3vil]

Well ok then what a shame. Any way to get the black bars back with tsmuxer or makemkv or sth? Or does it have to be encoded again

[Kuler087]

Originally Posted by d3rd3vil

Or does it have to be encoded again

yes

I use my TV internal PLEX app for cropped DV video.

[varekai]

Originally Posted by d3rd3vil

Well ok then what a shame. Any way to get the black bars back with tsmuxer or makemkv or sth? Or does it have to be encoded again

I use PotPlayer (displaying subtitles below cropped areas) when playing cropped mkv's and also on an OPPO95.
But, text subtitles do not, sadly, render well on the OPPO...
Someone (Groucho2004) a very skilled person in this forum, presented this bat file for me some years ago and it works like a charm.
I use this bat script, using ffmpeg, for adding black bars on top and bottom for mkv.
There are several guides how to setup ffmpeg.
To test if you got the ffmpeg setup right open a command prompt and type ffmpeg -version.
Use 2 HDDs, for fastest encoding, one for source and the other for target.
I think (-crf 18) is supposed to be "placebo" but I have used lower values and still not getting monstrously big outputs.
Depending on your setup it can take some time to encode, but it works like a charm!
Copy to notepad, save as .bat in the extension.

*** (script starts here exclude *** and text)

@echo off
set SOURCEPATH=X:\SOURCEPATH
set TARGETPATH=Y:\TARGETPATH

if not exist "%SOURCEPATH%" goto ErrorSource
if not exist "%TARGETPATH%" goto ErrorTarget

for %%i in ("%SOURCEPATH%\*.mkv") do (
  start/b/wait/low ffmpeg -i "%%i" -vf "pad=3840:2160:(ow-iw)/2:(oh-ih)/2" -c:v libx264 -preset slow -crf 18 -c:a copy "%TARGETPATH%\%%~ni.mkv"
  echo.
)
goto Exit

:ErrorSource
echo Source path "%SOURCEPATH%" does not exist.
goto :eof

:ErrorTarget
echo Target path "%TARGETPATH%" does not exist.
goto :eof

:Exit
echo Done.
echo.

*** (script ends here exclude *** and text)

[d3rd3vil]

Sounds interesting god bless you.
The mkv keeps the Dolby Vision? And it says nonstop "skipping NAL Unit 62". Apparently thats because ffmpeg doesnt know what to do with the DV-layer. But as long as it doesnt touch it its fine.
Lets see what will happen.
CPU-load 100%, good to grill sausages on the cooler.

[varekai]

I have absolutely no idea about Dolby Vision and if it's working in ffmpeg, that question may be answered by the skilled persons in the forum, and that's not me...
Yup, have the sausages close when encoding...

Edit: I found this and it's waaay over my head but I think ffmpeg can handle Dobly Vision, but don't take my word for it.
https://codecalamity.com/encoding-uh...s-with-ffmpeg/
I found the old thread where Groucho2004 helped me...
Time flies when having fun!