tsMuxer Open Source

[MrVideo]

I agree, that at smaller screen sizes, it will be tough to notice a difference. But, when starting with 100" home theater configurations, the loss of pixels should be noticeable. The 960 pixels being stretched to 1920 pixels will result in artifacts. I'm putting together a home theater setup that will have a screen a little over 100", so I want all the available pixels.

[Bgalakazam]

Is the last nightly from February? Or am I looking at the wrong place. Thanks.

[a5180007]

Originally Posted by r0lZ

tsMuxeR crashes when it demuxes the BD files, and it should not. Perhaps it's a problem with the decrypter process (before the demux), or something strange with the BD.

Hi r0lZ, please give me references or links to crashing 3D muxes, I'll have a look.

[r0lZ]

I don't have that problem myself. My post was a reply to MrVideo to try to explain how to interpret this post:

Originally Posted by rickyshamilton

Last week I downloaded the latest version of your tool and tried to process two movies. Both failed for the same reason. Tsmuxer crashed. I was trying to process Hubble 3D and Star Trek Beyond in 3D.

Perhaps rickyshamilton can provide a sample.
Anyway, thanks for your proposition.

[von Suppé]

You can try a workaround for the errors that tsMuxer sometimes throws with a 3D demux.
First, create a (3D) mkv from the bluray/ISO using MakeMKV. After, import that mkv in tsMuxer or BD3D2MK3D and try again.
This saved me a couple of times (also for 2D BTW).

[zeropc]

When I want to demux a video file I get the following error message

PGS file

Non standard fps value are not supported for PGS streams

SRT file

Can't find ttf file for font Arial

The font is installed on my system. If I change the font, I'll get the same error, but with the newly selected font missing info. Why should it matter what font is used on a demux?
IIRC it used to work to demux any file from a container like M2TS or MKV.
Any idea what I can do?

TSMuxer running on macOS Big Sur.

[varekai]

@justdan96 | a5180007 | BloodyRipper
Thanks for the update, much appreciated!
Couldn't do without this gem!

[yannick92]

Hello
small problem on the last version of TsMuxer: muxing stop with an error:



I also noticed that TsMuxer finds a frame rate of 90000 on the file while MediaInfo tells me that it is indeed at 25000?



what about it?
thank you very much, and see you very soon.

Sample link: https://uptobox.com/yb8grssa6p7i

Full link: https://uptobox.com/mj7mlqv09r6a?aff_id=4860501

Yannick

[kpic]

Cannot seem to import HEVC file created by Premiere Pro (The original imports no problem). What I am doing is running the original through Premiere to lower its bitrate some for placement on BD-50 disc.

The latest Premiere is being used and I am matching the exporting from Premiere to the original version settings (H265, HDR etc.) and end up with a .mp4 compliant (according to mediainfo) file and it plays fine through MPC.

I don't think it is a file error as I made a much shorter clip using the same settings (about 1 minute) and Tsmuxer imported it fine - when I made a 4 minute clip using all the same settings (about 1.2gb in size) and try to import it in TSmuxer does nothing, I get no error message nothing.

I have tried to change its extension to no avail as well.


Using the latest nightly build from April 30

[a5180007]

Originally Posted by yannick92

Hello
small problem on the last version of TsMuxer: muxing stop with an error:

I also noticed that TsMuxer finds a frame rate of 90000 on the file while MediaInfo tells me that it is indeed at 25000?

@yannick92 The h264 stream vui is incorrectly stamped at 90 fps. Therefore the video and the audio get quickly desynchronized when muxed, which provokes the buffer overflow.

MediaInfo gets the 25 fps info from the mkv container.

Edit: the h264 should be repaired by simply changing fps to 25 and selecting "always rebuild SEI and VUI data".

[MrVideo]

Win7-64 4/30/21 nightly build

Tsmuxer doesn't like the following audio format in a M2TS file (mediainfo):

Audio #1
ID                                       : 4352 (0x1100)
Menu ID                                  : 1 (0x1)
Format                                   : AC-3 MLP FBA 16-ch
Format/Info                              : Audio Coding 3 + Meridian Lossless Packing FBA with 16-channel presentation
Commercial name                          : Dolby TrueHD with Dolby Atmos
Muxing mode                              : Stream extension
Codec ID                                 : 131
Duration                                 : 3 min 58 s
Bit rate mode                            : Variable
Bit rate                                 : 640 kb/s
Maximum bit rate                         : 5 895 kb/s
Channel(s)                               : 8 channels
Channel layout                           : L R C LFE Ls Rs Lb Rb
Sampling rate                            : 48.0 kHz
Frame rate                               : 31.250 FPS (1536 SPF)
Compression mode                         : Lossy
Delay relative to video                  : -778 ms
Stream size                              : 18.2 MiB (1%)
Service kind                             : Complete Main
Number of dynamic objects                : 15
Bed channel count                        : 1 channel
Bed channel configuration                : LFE

Why?

What I wanted to do was remux the M2TS file without the DolbyVideo stream. I can't do that now because tsmuxer is not including the audio stream.

[SeeMoreDigital]

Originally Posted by MrVideo

Tsmuxer doesn't like the following audio format in a M2TS file (mediainfo):

Why?

Are you sure the Dolby TrueHD audio stream also contains a Dolby Digital core. Which is a mandatory requirement of the Blu-ray disc specification...

[MrVideo]

The M2TS file originally came from a UHD Blu-ray disc. Even if it didn't it shouldn't throw away the file, as the output wasn't to a BD structure. Hell, the output wasn't even selected yet.

[SeeMoreDigital]

Originally Posted by MrVideo

...Even if it didn't it shouldn't throw away the file, as the output wasn't to a BD structure...

Hmmm...

Unless TSmuxer GUI has been updated in the last few weeks any Dolby TrueHD audio stream that has been de-muxed from an .mkv file wont be accepted, regardless of whether you're creating a Blu-ray disc compliant encode!

[yannick92]

Originally Posted by a5180007

@yannick92 The h264 stream vui is incorrectly stamped at 90 fps. Therefore the video and the audio get quickly desynchronized when muxed, which provokes the buffer overflow.

MediaInfo gets the 25 fps info from the mkv container.

Edit: the h264 should be repaired by simply changing fps to 25 and selecting "always rebuild SEI and VUI data".

Ok greats, many tanks, I will test this as soon as possible!

Yannick

[MrVideo]

Originally Posted by SeeMoreDigital

Unless TSmuxer GUI has been updated in the last few weeks any Dolby TrueHD audio stream that has been de-muxed from an .mkv file wont be accepted, regardless of whether you're creating a Blu-ray disc compliant encode!

The source was not MKV, it was the original UHD M2TS.

[SeeMoreDigital]

Originally Posted by MrVideo

The source was not MKV, it was the original UHD M2TS.

So you said...

[MrVideo]

Originally Posted by SeeMoreDigital

So you said...

Then I am confused as to why you brought up the MKV issue. I know that MKV and Dolby don't get along.

[SeeMoreDigital]

Perhaps some of the streams in your 4K UHD back-up have become corrupted.

I guess you could try backing up your 4K UHD disc again...

[MrVideo]

Originally Posted by SeeMoreDigital

Perhaps some of the streams in your 4K UHD back-up have become corrupted.

This is one of those movies where the movie is split among 10 streams. I checked all 10 streams with tsmuxer. What is strange is that one of the streams was accepted by tsmuxer. Mediainfo shows the same info for the one that works and those that don't.