smartLabs tsMuxeR: Transport Stream muxer

[mrr19121970]

tsMuxeR_1.8.28(b) (http://www.smlabs.net/tsMuxer/tsMuxeR_1.8.28(b).zip)

[shon3i]

http://www.smlabs.net/tsMuxer/tsMuxeR_1.8.28(b).zip ;)

what is status about TrueHD and DTS-MA? is work correctly standalones?

We are very close to very stable, muxer/demuxer bluray muxer ;)

[mrr19121970]

1080i@60 VC1 video is not detected by any tsMuxeR version.

sample (http://www.sendspace.com/file/e8h77f)

I guess this is probably the same reason as my problem with VC1 1080i50

http://forum.doom9.org/showthread.php?p=1260835#post1260835

as a workaround, you can use tsREmux

[deank]

I tried with your sample and


MUXOPT --no-pcr-on-video-pid --new-audio-pes --blu-ray --vbr --auto-chapters=5 --split-size=4000MiB --vbv-len=500
V_MS/VFW/WVC1, "d:\downloads\fearless.planet.(1080i60.vc-1).ddx2.m2ts", insertSEI, contSPS, track=4113, fps=29.970
A_AC3, "d:\downloads\fearless.planet.(1080i60.vc-1).ddx2.m2ts", track=4352, lang=und
A_AC3, "d:\downloads\fearless.planet.(1080i60.vc-1).ddx2.m2ts", track=4353, lang=und

works... I was unable to play the result - but you can check...

You can also try --delPulldown.

GUI doesn't accept it, but CLI (.exe) does if you create a .meta... and tsmuxer accepts it in all its versions:


D:\multiAVCHD\tools>tsmuxer.exe D:\_TEMP\fearless.planet.(1080i60.vc-1).ddx2.meta 123456
SmartLabs tsMuxeR. Version 1.8.18(b) http://www.smlabs.net
Decoding VC-1 stream (track 1): Profile: Advanced@3 Resolution: 1920:1080i Frame rate: 29.97
0.2% complete
Decoding AC3 stream (track 2): Bitrate: 192Kbps Sample Rate: 48KHz Channels: 2
Decoding AC3 stream (track 3): Bitrate: 192Kbps Sample Rate: 48KHz Channels: 2
63.6% complete
Processed 696 video frames
100.0% complete
Creation of Blu-ray playlist
Creation of Blu-ray stream info and seek index
Mux successful complete.
Muxing time: 1 sec

[tebasuna51]

1.8.27(b) seems to fix the "add garbage add the end of wav file when demuxing" bug.

Can someone else confirm?

:)
My test (1.8.27b) are ok with 48 KHz samples, but with 96 KHz still there are problems, for instance:

Input file:
4_24_96.wav 23040092 bytes

Demuxed file:
V_42496.track_4352.wav 23045828 bytes

[mrr19121970]

GUI doesn't accept it, but CLI (.exe) does if you create a .meta... and tsmuxer accepts it in all its versions:


The same problem with mine, but the important part is:


I was unable to play the result


The results are useless, played at the wong speed, audio completely out of sync.

[thevoiceover]

played at the wong speed, audio completely out of sync.


Same thing that happened to me....



Thank you for calling the city wok.

Do you guys know if any toolkits are required for the OSX version? I get a crash everytime i try to load the .app

[kooibosmania]

Hi all

ihave noticed that from version 25 on, the tracks languages are not displayed is it me??

greatzzz:thanks:

[teox99]

hi,
i tried the GUI for Linux but append mode is still not working... what about? is it possible to repurt this bug?

[setarip_old]

@kooibosmania

Hi!

It's apparently you...

[SomeJoe]

Hi Gents,

I've been following this thread for a while, and I must say first that I'm very appreciative of all the revisions and fixes that have been coming out lately for TSMuxer. My hat's off to deank and the other programmers who develop it.

I did want to note that even with all the revisions, it seems that TrueHD muxing is still not working properly (see my separate thread, Still Having Problems with TrueHD (http://forum.doom9.org/showthread.php?t=143986). I've tried versions of TSMuxer up to 1.8.26b with the same results (distorted audio when played back on my system - see my thread for details).

I offer to deank and any other developers any information or testing data that they need to get a better understanding of, and hopefully a fix for the issue.

Thanks in advance.

[odin24]

Hi Gents,

I've been following this thread for a while, and I must say first that I'm very appreciative of all the revisions and fixes that have been coming out lately for TSMuxer. My hat's off to deank and the other programmers who develop it.

I did want to note that even with all the revisions, it seems that TrueHD muxing is still not working properly (see my separate thread, Still Having Problems with TrueHD (http://forum.doom9.org/showthread.php?t=143986). I've tried versions of TSMuxer up to 1.8.26b with the same results (distorted audio when played back on my system - see my thread for details).

I offer to deank and any other developers any information or testing data that they need to get a better understanding of, and hopefully a fix for the issue.

Thanks in advance.

Sorry if this was mentioned before... and sorry if this insults your intellignece, but; Are you using a v1.3 HDMI cable? Doesn't Iron Man have a high video bit rate, ~30mb/s and ~4.5mb/s 24 bit TrueHD track, wouldn't that most definetly require a v1.3 cable for bitstreaming?

[SomeJoe]

Sorry if this was mentioned before... and sorry if this insults your intellignece, but; Are you using a v1.3 HDMI cable? Doesn't Iron Man have a high video bit rate, ~30mb/s and ~4.5mb/s 24 bit TrueHD track, wouldn't that most definetly require a v1.3 cable for bitstreaming?

:) Yes, these are proper cables from Monoprice. The same cable carries the signal fine from the original BD, by the way.

By the way, in the technical sense, HDMI cables do not have a "version", as in 1.0, 1.1, 1.2, or 1.3. The versions of HDMI refer to the protocol used, which is embedded in the devices, not the cable. All HDMI cables are wired the same way, the only difference is the frequencies they support. Thus, it is proper to refer to a category 1 or category 2 HDMI cable, the former being certified for 75 MHz signals, which is sufficient for 720p and 1080i 8-bit color, and the latter being certified for 340 MHz signals, sufficient for 1080p/60 with Deep Color.

All of my HDMI cables are certified category 2.

We determined on about page 4 of that thread I referred to that my Pioneer VSX-1018AH AV receiver is highly sensitive to the TrueHD audio bitstream. In other words, the bitstream that results after TSMuxer has muxed it is slightly out of spec. The error is probably very minor, such that the majority of devices will still decode it properly without a problem (indeed, my Sony BDP-S350 standalone Blu-Ray player will play Blu-Rays muxed by TSMuxer with TrueHD perfectly when decoding the audio internally and sending PCM to the AVR). But when bitstreaming TrueHD audio to the Pioneer, the audio is distorted.

The identical behavior occurs on a Popcorn Hour A110 that is also connected to the same Pioneer AVR. (Audio correct if the PCH decodes internally, distorted if bitstreamed).

I feel it has to be a very minor error in TSMuxer that is causing this behavior, and I want to be able to provide deank with any information he may need to identify the problem.

[idbirch2]

My hat's off to deank and the other programmers who develop it.

I did want to note that even with all the revisions, it seems that TrueHD muxing is still not working properly...Firstly Dean, while an awesome programmer, is not involved in TSMuxer development, the resident dev here was roman76r but he sadly hasn't been attending for a while.

TrueHD is fixed for most people and definitely for those with PS3s so the best thing you can do is mail smlabs using this (mailto:tsmuxer@smartlabs.tv) address describing your issue in as much detail as possible. Users here, including myself, have had very prompt replies and fixes to issues we have reported.

[sebhag]

the resident dev here was roman76r but he sadly hasn't been attending for a while.

The replies i had from smlabs were from roman76r as far as i can tell. :) Emailed them about BDAV support for tsmuxer and he said he would implement this in the near future.

Btw, is there an english version of the readme somewhere?

[odin24]

:) Yes, these are proper cables from Monoprice. The same cable carries the signal fine from the original BD, by the way.

By the way, in the technical sense, HDMI cables do not have a "version", as in 1.0, 1.1, 1.2, or 1.3. The versions of HDMI refer to the protocol used, which is embedded in the devices, not the cable. All HDMI cables are wired the same way, the only difference is the frequencies they support. Thus, it is proper to refer to a category 1 or category 2 HDMI cable, the former being certified for 75 MHz signals, which is sufficient for 720p and 1080i 8-bit color, and the latter being certified for 340 MHz signals, sufficient for 1080p/60 with Deep Color.

All of my HDMI cables are certified category 2.

We determined on about page 4 of that thread I referred to that my Pioneer VSX-1018AH AV receiver is highly sensitive to the TrueHD audio bitstream. In other words, the bitstream that results after TSMuxer has muxed it is slightly out of spec. The error is probably very minor, such that the majority of devices will still decode it properly without a problem (indeed, my Sony BDP-S350 standalone Blu-Ray player will play Blu-Rays muxed by TSMuxer with TrueHD perfectly when decoding the audio internally and sending PCM to the AVR). But when bitstreaming TrueHD audio to the Pioneer, the audio is distorted.

The identical behavior occurs on a Popcorn Hour A110 that is also connected to the same Pioneer AVR. (Audio correct if the PCH decodes internally, distorted if bitstreamed).

I feel it has to be a very minor error in TSMuxer that is causing this behavior, and I want to be able to provide deank with any information he may need to identify the problem.

Good information, thanks.

[deank]

is there an english version of the readme somewhere?

It is sticky in the forum: tsMuxer Readme - English (http://forum.doom9.org/showthread.php?t=142559)

[jamos]

1.8.28 seems to work now with large WAV files..so perhaps we no longer need to use PCM then have to convert using pcm2tsmu for LPCM audio.

[quantum]

Chapter positions were not correctly retained when using the cutting feature and muxing to Blu-ray. Specifically they were incorrect if the cut started after zero, which would be the second half if you were splitting into two pieces.

Thanks to roman for fixing this.

New version:
http://www.smlabs.net/tsMuxer/tsMuxeR_1.8.29(b).zip

[sebhag]

It is sticky in the forum: tsMuxer Readme - English

Ooops, sorry! Thanks Dean.

[ron spencer]

was .24 the last version with a gui to download? I am getting lost in these updates LOL

thanks!!!

[jamos]

was .24 the last version with a gui to download? I am getting lost in these updates LOL

thanks!!!

yes just copy the .24 gui into the folder with the newer tsmuxer.exe's it will work with the newer versions as long as they are in the same directory.

[jamos]

Am talking with the TSmuxer devs on LPCM and WAV issues with 7.1 they admit there is some channel ordering problems..


From: xxx [mailto:@smartlabs.tv]
Sent: Saturday, March 14, 2009 6:08 PM
To: xxx
Subject: RE: LPCM/WAV 7.1 mixing channel order.



When tsMuxer create LPCM track from 8-th WAV file, muxer made next channel reordering:



5-th WAV channel ---> 4-th LPCM channel

7-th WAV channel ---> 5-th LPCM channel

8-th WAV channel ---> 6-th LPCM channel

6-th WAV channel ---> 7-th LPCM channel

4-th WAV channel ---> 8-th LPCM channel



1-th WAV channel ---> 1-th LPCM channel

2-th WAV channel ---> 2-th LPCM channel

3-th WAV channel ---> 3-th LPCM channel



Seems this reordering is invalid. I’ll recheck this function at nearest time.



I need a clean small sample pcm file to send them..hopefully they will clean up the error with large pcm files also.

[mrr19121970]

@Jamos

Perhaps you can mention this too:

http://forum.slysoft.com/showpost.php?p=183330&postcount=539

If i select BD/iso as final result, works great, all options i select are there, all is good. If i select mt2s as final result and audio is DTS-HD 7.1 on the source, the sound will always be just plain DTS 5.1

So to sum up:

M2TS
DTS-HD 7.1 works ok

Blu-Ray
DTS-HD 7.1 gets downgraded to DTS 5.1

[Ryu77]

I've also noticed that the append feature seems to be broken in tsMuxeR v1.8.24. It seems to work fine in v1.8.19 though...

Did anyone else notice this?

[shon3i]

http://www.smlabs.net/tsMuxer/tsMuxeR_1.8.29(b).zip :) is up

[SomeJoe]

Firstly Dean, while an awesome programmer, is not involved in TSMuxer development, the resident dev here was roman76r but he sadly hasn't been attending for a while.

TrueHD is fixed for most people and definitely for those with PS3s so the best thing you can do is mail smlabs using this (mailto:tsmuxer@smartlabs.tv) address describing your issue in as much detail as possible. Users here, including myself, have had very prompt replies and fixes to issues we have reported.


Thanks.

After reading a lot of posts in the thread, I was under the impression that deank was one of the developers.

I'll e-mail SMLabs and see if they can help out.

[tebasuna51]

I need a clean small sample pcm file to send them..hopefully they will clean up the error with large pcm files also.

You have a clean wav file with pcm contain.

[jamos]

@Jamos

Perhaps you can mention this too:

http://forum.slysoft.com/showpost.php?p=183330&postcount=539



So to sum up:

M2TS
DTS-HD 7.1 works ok

Blu-Ray
DTS-HD 7.1 gets downgraded to DTS 5.1

What I understand from that link is the opposite, dts-hd 7.1 works fine in bluray (which it does) and m2ts downgrades to dts 5.1.

[jamos]

You have a clean wav file with pcm contain.

did you check the m2ts file after you muxed it and made sure that tsmuxer did not mess with the channel ordering? according to smlabs it should mess it up. if i demux wav or pcm from it will it recorrect the order? I got a sample sent to them they are checking it.

[idbirch2]

Jamos is right, DTS-HD works fine with "BluRay Disc" output mode. Don't know about .m2ts output, don't use it.

[m1482]

http://www.smlabs.net/tsMuxer/tsMuxeR_1.8.30(b).zip

[Mtz]

Link not working.

[m1482]

Link not working.

Yes it is...Try again...

[jamos]

You have a clean wav file with pcm contain.

I also sent them a link to your pcm2tsmu thread and told them about the large pcm issue, so hopefully they will fix that also.

[videobelu]

Thanks for this beautiful prog!
The last version 1.8.3.0 have the GUI working for Join files
but there is no a way to select multiple file to join togheter....
when the files are many this will be very useful

Thanks

[Ryu77]

http://www.smlabs.net/tsMuxer/tsMuxeR_1.8.30(b).zip

This version seems to have corrected the issues in the Clip Information File (.clpi)... No more need to apply jdobbs's fixclpi patch! :D

[G_M_C]

Okay :)

Can we conclude most of the standing bugs are solved ?
CLPI's are build correctly ?
Pachetsize/filesize is set correctly ?
TrueHD is muxed correctly ?

How's fforwarding/reversing and/or chapter skipping working now ?

[shon3i]

How's fforwarding/reversing and/or chapter skipping working now ? Fine here :)

[idbirch2]

This version seems to have corrected the issues in the Clip Information File (.clpi)... No more need to apply jdobbs's fixclpi patch! :DThat was done several versions ago - see here (http://forum.doom9.org/showthread.php?p=1260807#post1260807) and here (http://forum.doom9.org/showthread.php?p=1260843#post1260843).

[Underground78]

Can we conclude most of the standing bugs are solved ?

I think there is something wrong with AAC tracks in MKV, they are not correctly detected by TsMuxer when importing the MKV and the only way to import them is to demux them from the MKV first.

[arrgh]

really nice to see, that here after some time further progress is done...

do these new versions recognize forced subtitles in bluray-mpls files?

[SeeMoreDigital]

How about the following changes to the (MPEG-2) "AR" layout: -

http://i40.tinypic.com/vg6jrm.png


Cheers

[Ryu77]

That was done several versions ago - see here (http://forum.doom9.org/showthread.php?p=1260807#post1260807) and here (http://forum.doom9.org/showthread.php?p=1260843#post1260843).

Ok, but the append feature was broken in the last version I tried (v1.8.24), which also had not corrected the clpi issues... So I didn't realise that was the case until this version. Thanks for pointing that out.

There have been several versions released within the last few days so I think I can be forgiven for being a little "behind" in the times. :p

[odin24]

Since the new versions have been coming out... and since the TrueHD bug has been fixed, has anyone experienced issues with TrueHD muxing?

I muxed a TrueHD movie maybe a week or 10 days ago, I cannot remember what version I used. The TrueHD does not play... sorta, the center channel is not present, surrounds and fronts are playing. The AC3 core works fine.

I'm demuxing from my AVCHD FAT32 collection and I'm going to re-process as a new THD+AC3 and PCM tracks... we'll see.

[jamos]

Since the new versions have been coming out... and since the TrueHD bug has been fixed, has anyone experienced issues with TrueHD muxing?

I muxed a TrueHD movie maybe a week or 10 days ago, I cannot remember what version I used. The TrueHD does not play... sorta, the center channel is not present, surrounds and fronts are playing. The AC3 core works fine.

I'm demuxing from my AVCHD FAT32 collection and I'm going to re-process as a new THD+AC3 and PCM tracks... we'll see.

true hd and dts-hd ma work fine but some persons have issues with bitstreaming it through hdmi from a standalone player.

[jamos]

Talked with smlabs folks and thier take on using pcm files is that they must contain the 4 byte HDMV_LPCM_audio_data_header on each frame before being used with tsmuxer..hence we may not be able to get rid of using pcm2tsmu on pcm files from eac3to.:mad:

they did slip me a bit of source code..hehe


This file does not contain LPCM audio headers, so tsMuxeR can’t recognize file format.

Each LPCM frame MUST be preced 4 byte HDMV_LPCM_audio_data_header





Syntax No. of bits Mnemonics

HDMV_LPCM_audio_data_header() {

audio_data_payload_size 16 uimsbf

channel_assignment 4 bslbf

sampling_frequency 4 uimsbf

bits_per_sample 2 uimsbf

start_flag 1 bslbf

reserved 5 bslbf

}

[odin24]

true hd and dts-hd ma work fine but some persons have issues with bitstreaming it through hdmi from a standalone player.


I'm using a PS3, FAT32 1TB external, and AVCHDManager. The problem is gone now. I demuxed, remuxed with the latest version of tsMuxeR, which I know handles TrueHD fine... and it works, both the TrueHD and the PCM file I created.

[jdobbs]

How's fforwarding/reversing and/or chapter skipping working now ? I think all that was fixed in v1.8.28.

[Edit] Looks like I'm behind in my reading... this has already been discussed... ignore this post. :)

[MAVLL]

greetings.

i use tsmuxer for create a blu ray structure, but the final size is to big to burn in a dvd-5 4.7gb. I use tsspliter but when i split the file i cannot see the subtitles. But in a another file and smaller file <4.7gb i can see the subtitles very well. Any suggestions??
thanks in advanced.