tsMuxer Open Source

[glc650]

The final build fails to open for me on macOS 15.4.1:

"tsMuxerGUI.app" is damaged and can't be opened. You should move it to the Trash.

[Selur]

@glc650: both command line and gui work fine here. Did you call:

xattr -rc "Path to ssMuxeRGUI.app"

to remove all those quarantine flags macOS adds when the source isn't registered/paying?
(Apples habit of telling the user something is broken, when the problem is a flag it itself added is the reason, is hilarious in a bad way.)

[glc650]

Originally Posted by Selur

@glc650: both command line and gui work fine here. Did you call:

xattr -rc "Path to ssMuxeRGUI.app"

to remove all those quarantine flags macOS adds when the source isn't registered/paying?
(Apples habit of telling the user something is broken, when the problem is a flag it itself added is the reason, is hilarious in a bad way.)

Never had to do that before but that did the trick, thanks.

[qyot27]

Originally Posted by Selur

@glc650: both command line and gui work fine here. Did you call:

xattr -rc "Path to ssMuxeRGUI.app"

to remove all those quarantine flags macOS adds when the source isn't registered/paying?
(Apples habit of telling the user something is broken, when the problem is a flag it itself added is the reason, is hilarious in a bad way.)

Wow. That would have definitely spared a lot of time messing around with Gatekeeper while prepping the latest AviSynth+ release.

It's even worse:

If you unpack a tar archive which has this attribute, all the unpacked files inherit the attribute. If an unpacked file is an executable and you try to execute it, you get the message ‘Operation not permitted’ and the execution fails.

So it's good to know that there is indeed a way of fixing downloaded stuff without having to suggest users disable part of the OS' security. That's just a bad look, even if the feature in question is more frustrating than helpful for anyone that knows what they're doing.

The funniest part is that aparently curl bypasses it entirely, because it doesn't set the attribute; web browsers do, but a literal downloading application does not (although I wonder how long until Apple starts shipping a custom version which does).

[Lucius Snow]

Hi all,

I have this error "TRUE-HD stream (track 3): bad frame detected at position... Resync stream." when trying to mux a Dolby TrueHD MLP to make a Blu-Ray. Any ideas?

Thanks.

EDIT: The old version from 2014 doesn't display theses errors. Why?

[MrVideo]

Does it have a core AC3. tsMuxer doesn't support coreless Dolby TrueHD

[Lucius Snow]

Yes, it does.

[MrVideo]

Then there might be a bug, which isn't going to get fixed any time soon.

[DanDare1983]

I know tsmuxer isn't being updated anymore but I have a couple of simple questions hopefully someone can answer. Firstly when I add a blu-ray playlist with multiple m2ts files (seamless branched discs) when I check the resulting stream folder I only see one m2ts instead of 2 or 3. I understand that when m2ts files are joined together audio frames need to be dropped in order for the m2ts files to sync up? Does tsmuxer do this? Also I like to create a simple main movie of my blu-rays, does tsmuxer do this perfectly fine or is there any additional setting i need to check. I know that when I add an m2ts file and not a mpls tsmuxer creates chapters if I don't check the 'no chapters tab'. Finally i've noticed that when I add a movie with dolby atmos the atmos track is out of sync, to get round this I use the embedded ac3 core which is fine. Is this a known problem or is it just me? Thanks again

[taurusus]

Hi DanDare1983 tsmuxer can create only one m2ts file, it is not necessary to separate audio from video, it can assemble with all audio and subtitles and I did not notice any desynchronization in the Atmos track.

[DanDare1983]

@taurusus when you have multiple m2ts files you will get overlapping frames. Tools like eac3to and DGdemux will reduce frames in order for the m2ts files to sync up. In regards to the Atmos TrueHD track I ran it through DGdemux and the resulting audio file was in perfect sync with the video so it's obviously done something because it's now in perfect sync.

[ocean]

Originally Posted by DanDare1983

with dolby atmos the atmos track is out of sync, to get round this I use the embedded ac3 core which is fine. Is this a known problem or is it just me? Thanks again

Hi DanDare1983, I'm only replying to you about the Atmos track for seamless branched discs:

https://forum.doom9.org/showthread.p...10#post2022510

[DanDare1983]

Hi Ocean, just checked the link and I can confirm that by extracting the 'full' truehd track with dgdemux and adding it to tsmuxer it works fine. Just a quick question if you can help....I see options such as "Do not change SEI and VUI data" and the box "Continually insert SPS/PPS" both unchecked. Do I need to check these? I'm not sure what they're actually for?

[ocean]

Supplemental enhancement information (SEI) and video usability information (VUI):


https://forum.doom9.org/showthread.p...80#post1209880

[Hellboy.]

DanDare1983
What version of tsMuxer are you using? I don't see any sync problem.

[DanDare1983]

Hellboy
I'm using the latest 2.7.0 release. Its weird because i tried another blu-ray folder with TrueHD Dolby atmos and that one worked fine. I've also just realised that tsMuxer is no longer being developed and that the latest 2.70 release is final. Thats a shame as i think its a handy tool to have.

[Hellboy.]

Maybe the disk have a delay in the audio and tsMuxer doesn't see it.

[DanDare1983]

The actual disk in question was actually fine when i run it through dvdfab so i don't know whats wrong with it. Do you know how well the latrst version deals with UHD 4K disks? I'd like to make a simple main movie into Blu-ray folder with them too.

[Columbo]

Regarding your async with THD Atmos, something in the process has to correct for the gaps between the M2TS files. When you used DGDemux, it did so. Perhaps your process is using tools that don't support gaps correction for THD, which can be tricky.

[DanDare1983]

Hey Columbo, the disc in question only had one m2ts file and not multiple m2ts files. I can understand sync issues with movies with multiple m2ts but not one. I knew by running the THD file through dgdemux the audio would be fine. Which did confuse me was that other THD tracks work fine so i'm not sure whats going on. Whilst wer'e on the subject of multiple m2ts files and gap correction, does tsMuxer work well with them kind of discs (seamless branched discs)? I've been leaving them for the time being and focusing primarily on discs with one m2ts file.