Log in

View Full Version : How to demux-remux-play your uncompressed, lossless, lossy HD audio BD/HD rips


rica
14th September 2008, 16:52
Hi,
You audio entusiasts may want to make your own BluRay backups keeping the audio as it is:
How to extract audio and how to remux it without any loss?

Your HTPC and your traditional A/V receiver with analog cables will be enough.

Lets take a look at BD/HD HD audio formats:

Uncompressed:
PCM/LPCM

Lossless:
Dolby TrueHD, DTS-HD MA (Both- variable bitrate)

Lossy HD:
Dolby D+(eac3), DTS_HD HR (Both- constant bitrate)


Here eac3to will be used for demuxing and TSMuxer/TSRemux for remuxing.


Lets start:

_ _ _ _ _ _ _ _ _ _ _ _ _

UNCOMPRESSED:

PCM:

Uncompressed:

PCM/LPCM:

A PCM track is an exact replication of the studio master, encoded on disc without compression if the replication is exactly the same as the studio master as un-downconverted. -edited-
The benefit to this is that it maintains the purity of the source without any loss of fidelity that may come from compression.

All Blu-ray disc players are required to support PCM audio while PCM is not a very popular due to the enormous amount of disc space required,PCM is not a very popular option on HD DVD.

demux:
eac3to input.m2ts output.pcm

reorginising pcm with Pcm2Tsmu to be recognized by TSMuxer:

Pcm2Tsmu input.pcm output.pcm -i 16

Remuxing to m2ts with TSMuxer.

_ _ _ _ _ _ _ _ _ _ __ _ _ _ _ _ _

LOSSLESS:

Lossless:

TrueHD:

Dolby TrueHD is a "lossless" compression codec. Although it is compressed to take up less disc space than a PCM track, once decoded it
is bit-for-bit identical to the studio master.

Support for TrueHD up to at least 2 channels is mandatory on all HD DVD players, but the majority will support it all the way to 5.1.
Discs with TrueHD tracks must also contain a Dolby Digital Plus track for 5.1 compatibility.
TrueHD is an optional format on Blu-ray. And since TrueHD is not built in a core+extension configuration, Blu-ray discs that contain a TrueHD track are also required to contain a standard Dolby Digital AC-3 track for compatibility with players that don't support TrueHD.


DTS-HD Master Audio:

Another lossless audio codec similar to Dolby TrueHD.
The difference between the two is that DTS-HD MA is built in a core+extension configuration (just like DTS-HD HR).
DTS-HD MA works in a core+extension configuration.

DTS_HD MA is optional for both BD/HD so the players which don't support DTS-HD MA, will extract the standard DTS core.


TrueHD:

BD Dolby TrueHD \It has to carry an ac3 since trueHD is an optianal format for BD:

eac3to\eac3to.exe "F:\INPUT\00002.m2ts" 7: "C:\output.thd+ac3"
------------------------------------------------------------------------------
M2TS, 1 video track, 5 audio tracks, 13 subtitle tracks, 1:44:15
1: Chapters, 16 chapters
2: h264/AVC, 1080p24 /1.001 (16:9)
*********
7: TrueHD/AC3, English, 5.1 channels, 48khz, dialnorm: -27dB
8: Subtitle (PGS), English
***************

[a07] Extracting audio track number 7...
[a07] Removing AC3 dialog normalization...
[a07] Removing TrueHD dialog normalization...
[a07] Creating file "C:\output.thd+ac3"...
Video track 2 contains 149977 frames.
eac3to processing took 18 minutes, 22 seconds.
Done.

As seen this process is just an extraction of ac3+ truehd.


HD-DVD Dolby TrueHD/mandantory format for HD-DVD: (doesn't include any ac3 since it is mandantory)

eac3to\eac3to.exe E:\HD\BLOOD_DIAMOND_HDDVD\HVDVD_TS\feature.evo 4: C:\TEST\test_02.thd+ac3
------------------------------------------------------------------------------
EVO, 2 video tracks, 6 audio tracks, 6 subtitle tracks, 1:11:18
1: VC-1, 1080p24 /1.001 (16:9) with pulldown flags
*********
4: TrueHD, English, 5.1 channels, 48khz, dialnorm: -27dB
5: E-AC3, French, 5.1 channels, 640kbps, 48khz, dialnorm: -27dB
***********

[a04] Extracting audio track number 4...
[a04] Removing TrueHD dialog normalization...
[a04] Extracting audio track number 4...
[a04] Removing TrueHD dialog normalization...
[a04] Decoding with libav/ffmpeg...
[a04] Encoding AC3 <640kbps> with libAften...
[a04] Creating file "C:\TEST\test_02.thd+ac3"...
[a04] This audio track has a constant bit depth of 16 bits.
Video track 1 contains 102564 frames.
Video track 2 contains 128146 frames.
eac3to processing took 4 minutes, 35 seconds.
Done.


As you see, eac3to adds an ac3 interleaved as madshi said:

If you want to make a demuxed HD DVD TrueHD track (or a Blu-Ray TrueHD track demuxed by an older eac3to version) fit for Scenarist Blu-Ray muxing you can do this:

Code:
eac3to source.thd dest.thd+ac3This will automatically create an AC3 track and interweave it with the TrueHD track. Of course if your source is an HD DVD folder,
you can directly do e.g. "eac3to hddvdMovie 1) 1: video.mkv 3: audio.thd+ac3". That will demux the TrueHD track and interweave an AC3 track at the same time.

If you just want to make the TrueHD track Blu-Ray compatible, but don't want to actually *ever* make use of the embedded AC3 track, you can ask eac3to to use
a really low bitrate to save space, e.g. "eac3to source dest.thd+ac3 -192".

Please be aware, though, that there's no TrueHD encoder available at this time (at least not for us consumers). So you cannot convert LPCM tracks or any other
formats to TrueHD. You can only convert TrueHD tracks to TrueHD/AC3 or vice versa. Please also be aware that you cannot specify an external AC3 file
to be used for interweaving. eac3to will always create a new one (by transcoding the TrueHD track to AC3 during processing) - except when demuxing
a TrueHD/AC3 track from a single-part m2ts movie.

So the method i follow:

demux:
eac3to input.m2ts(/evo) output.thd+ac3

Remux to m2ts with TSMuxer first,
Remux this m2ts with TSRemux to m2ts again.

NOTE:Some Blu-ray disks which have playlists containing multiple m2ts files carry audio ovarlaps/gaps.
If this audio file is a TrueHD, this can't be corrected by eac3to. In this case truehd must be converted to pcm or flac.

DTS_HD MA:

demux:
eac3to input.m2ts(/evo) output.dtshd (or dts)

Remux to m2ts with TSMuxer.

_ _ _ _ _ _ _ _ _ _ _ __ _ _ ___

LOSSY:

Lossy :

DD+

An enhancement over standard Dolby Digital, DD+ offers higher bit rates and more efficient compression, resulting in improved sound quality.
It can also support movie soundtracks up to 7.1 discrete channels.
DD+ is the base standard audio format for HD DVD. Unlike its application on Blu-ray, DD+ on HD DVD does not utilize a core+extension configuration.
Unfortunately, DD+ is optional on the Blu-ray format, and not all disc players are required to support it. Many players will simply read
the 640 kb/s core and disregard the extension.
As a result, most movie studios prefer to use either basic Dolby Digital AC-3 or some of the other advanced formats.

DTS-HD (HR):

Similar to Dolby Digital Plus, DTS-HD High Resolution is an enhancement over standard DTS that offers higher bit rates and better compression.
DTS-HD HR is also encoded as an extension to a "core" DTS track. (Note that DTS-HD HR is sometimes referred to as just "DTS-HD", which can be
confusing and possibly misleading).
Since this codec is optional for both on HD-DVD and Blu-ray, many players will only extract the (edited) DTS core and ignore the extension



DD+:


demux:
eac3to input.evo output.eac3

Remux to m2ts with TSMuxer.


You can do that. But playback will probably only work on HTPCs (if at all). Blu-Ray standalone players will not support this. And external media players (e.g. TViX and NMT) will probably not support it, either. HD DVD style E-AC3 tracks are simply not Blu-Ray compatible.

Yes, he is right. So forget it. I was just investigating whether the selected audio is working or not; i've missed the BD compatibility point. In that case convert it to ac3: use ac3 instead of eac3 (edited)

DTS-HD HR:

demux:
eac3to input.m2ts (/evo) output.dtshd (or dts)

Remux to m2ts with TSMuxer.

_ _ _ _ _ _ _ _ _ _ _ _ __ _




Playing:

First of all i remuxed all induvidual audio tracks (-without video) into m2ts and opened them on GraphStudio.

The chain was:

FileSource(Async) > Arcsoft MPEG Demux > Arcsoft audio decoder HD > Default Direct Sound Device.

Of course you can't be so sure which format you are listening since properties pages of the DS filters don't give the right info-except splitter-

This time i made short BluRays adding the video to the raw audio files and finally checked from info of Arcsoft TMT.
Everything was fine, i saw all the disks i made showed the right audio info.

Finally i compared audio only m2ts files with the BDs; i felt no difference.

Btw, thanks to nautilus7 for his help.


Some additional notes:

1) Don't confuse the core dts( existing in both DTS-HD formats) with additional ac3 to Dolby TrueHD on BDs.
Core dts is a must for decoding process of DTS_HD while additional ac3 is a should for backward compatibility. (on BD)

2) Pure TrueHD can be found on HD_DVDs and no any other program can recognize it except eac3to.

3) I think we can go on...(with some suggestions from the experts?)

Sources:

http://www.highdefdigest.com/news/show/1064

http://www.tomsguide.com/us/high-def-audio-hdmi,review-1088-4.html

Dolby and DTS white papers.

dts.com/DownloadDocument.aspx?q=a7beda1e-cfe6-4ca4-b6b2-cda9554bb6a5

download DTS-HD whitepaper, i strogly suggest this one for whom is confused with connections between A/V receiver and player.
_ _ _ _ _

sehgal.v7
14th September 2008, 17:00
Nice one Rica!!

EPiPH0NE
14th September 2008, 19:48
Nice...this looks familiar though :P

madshi
15th September 2008, 00:48
many players will only extract the 1.5 Mb/s DTS core
The DTS core doesn't have to be 1.5Mbps. I've seen cores with smaller bitrates, IIRC, although most often it's 1.5Mbps.

demux: eac3to input.evo output.eac3

Remux to m2ts with TSMuxer.
You can do that. But playback will probably only work on HTPCs (if at all). Blu-Ray standalone players will not support this. And external media players (e.g. TViX and NMT) will probably not support it, either. HD DVD style E-AC3 tracks are simply not Blu-Ray compatible.

A PCM track is an exact replication of the studio master
Dolby TrueHD is a "lossless" compression codec. Although it is compressed to take up less disc space than a PCM track, once decoded it is bit-for-bit identical to the studio master
Not necessarily.

You've copied these comments from HiDef-Digest, I guess? Sometimes the studio master is 24bit while the tracks on Blu-Ray/HD DVD are downconverted to 16bit. In this case the PCM/TrueHD/DTS-MA tracks are IMO *not* an exact replication of the studio master.

rica
15th September 2008, 01:09
Thanks for the feedback madshi.


You've copied these comments from HiDef-Digest, I guess? Sometimes the studio master is 24bit while the tracks on Blu-Ray/HD DVD are downconverted to 16bit. In this case the PCM/TrueHD/DTS-MA tracks are IMO *not* an exact replication of the studio master.

Yes, all those quotes are copied from the source which i gave as the first link so as to give an idea to the beginners; it is not a secret.
I know your comments at the forum of that site and if you noticed i didn't quote of that section since i agree with you.
So, lets edit as "if the replication is exactly the same as the studio master as un-downconverted."


You can do that. But playback will probably only work on HTPCs (if at all). Blu-Ray standalone players will not support this. And external media players (e.g. TViX and NMT) will probably not support it, either. HD DVD style E-AC3 tracks are simply not Blu-Ray compatible.

Yes, you are right; thanks. I will edit.


_ _ __

shon3i
15th September 2008, 21:34
You can do that. But playback will probably only work on HTPCs (if at all). Blu-Ray standalone players will not support this. And external media players (e.g. TViX and NMT) will probably not support it, either. HD DVD style E-AC3 tracks are simply not Blu-Ray compatibleSo that means we can't simply transcode HDDVD to Blu-Ray using of some TS Muxers? and make it full compactible with upcoming BD players?

Is there some chance to extract AC3 core from E-AC3? and what should be optimal possible way to keep quality of audio on some HDDVD when transcoding it to Blu-Ray?

rica
15th September 2008, 21:59
So that means we can't simply transcode HDDVD to Blu-Ray using of some TS Muxers? and make it full compactible with upcoming BD players?

Is there some chance to extract AC3 core from E-AC3? and what should be optimal possible way to keep quality of audio on some HDDVD when transcoding it to Blu-Ray?

eac3to input.EVO output.ac3

This is gonna work; don't worry.

EPiPH0NE
16th September 2008, 07:57
LOL....Yeah there is really no DD+ on BluRay except like one demo disc and as far as DD+ on HD-DVD goes IMHO:

640K -> 640k AC3 (as above)
768k/1536k -> DTS


This will technically give lossy results but I can almost guarantee you your ears will not know the difference ;)

lithiumus
7th November 2008, 02:28
I started a thread about TrueHD overhead when muxing to m2ts. I figured since you have all the HD audio formats listed here, it makes sense you ask you what you are seeing in terms of overhead when muxing each of these to m2ts.

I recall that LPCM has slightly higher overhead than DTS 1536 and DTS-HD HR/MA both have similar overhead. It was TrueHD that was the shocker for me which yielded a 62% overhead when muxed into a m2ts container. I'm testing this again and will make a conscious effort to test some of the other streams. I could post results here to add a bit more info to your thread or just post results on my original thread. LMK.

rica
8th November 2008, 02:50
lithiumus, thanks for the contribution.

I've just given it a try with a THD;
here are the results:
demux to thd+ac3 with eac3to > 9 GB
remux to m2ts with TSMuxer > 11 GB
remux again to m2ts (or BD) with TSRemux > 11 GB.
Overhead seems to be over than the expected as % 7 to 15; ie %20 but not % 62.

nautilus7
8th November 2008, 10:32
Which movie is this that has a 9 GB TrueHD/AC3 track?

rica
8th November 2008, 11:21
Which movie is this that has a 9 GB TrueHD/AC3 track?

Live at Radio City- Dave Matthews and Tim Reynolds.
Duration is 02:49:02.

flyingernst
18th November 2008, 08:43
I now want to try to make a movie with scenarist. Movie will be a seamless branched one (can fly, can drink...)

I think the line
eac3to "K:" 1) 2: "F:\******\film.h264" 4: "F:\*******\Englisch.thd+ac3" 6: "F:\*******\Deutsch.thd+ac3"

will be the right one. The last time I used scenarist, nothing worked, because it asked for a mpl file, when I choosed TrueHD to import. Can you please tell me if I use the right commandoline for demuxing and give me perhaps a link how to handle the TrueHD Stream in Scenarist?!
I want to use scenarist to mux a seamless branched movie (after demuxing it with eac3to) to bluray (for PCH) since TSmuxer destroys some TrueHD Informations and makes a second remux necessary

Thank you very much,
Greetings, Michael

rica
18th November 2008, 16:00
Hl, i don't use Scenarist sorry but let me guess; you can author Blu-Ray with TrueHD if it is not a seamless braching one, do you?

flyingernst
18th November 2008, 19:19
yes, when they are in one part i can play them right copied from the BLuray or I can remove some Streams via TSremux. Both are working then on die PCH. Best is the original m2ts

rica
18th November 2008, 19:58
BD audio files inside the seamless branching playlists always have audio gaps and overlaps. Correction of this gaps and overlaps done by eac3to in second pass.
At the end of the first past of demuxing you get some info on the log file like this:

v02] Creating file "G:\Out\video_BD.h264"...
[a04] Creating file "G\Out_audio.dtshd"...
[a04] Audio overlaps for 7ms at playtime 0:23:06.
[a04] Audio overlaps for 6ms at playtime 0:26:06.
[a04] Audio overlaps for 11ms at playtime 0:30:37.
[a04] Audio overlaps for 6ms at playtime 0:34:03.
[a04] Audio overlaps for 6ms at playtime 0:37:20.
[a04] Audio overlaps for 7ms at playtime 0:41:25.
[a04] Audio overlaps for 13ms at playtime 0:45:19.
[a04] Audio overlaps for 9ms at playtime 0:58:47.
[a04] Audio overlaps for 12ms at playtime 1:03:58.
[a04] Audio overlaps for 6ms at playtime 1:04:39.
[a04] Audio overlaps for 8ms at playtime 1:13:48.
[a04] Audio overlaps for 10ms at playtime 1:15:44.
[a04] Audio overlaps for 6ms at playtime 1:16:41.
[a04] Audio overlaps for 5ms at playtime 1:20:28.
[a04] Audio overlaps for 9ms at playtime 1:21:15.
[a04] Audio overlaps for 9ms at playtime 1:34:00.
[a04] Audio overlaps for 9ms at playtime 1:34:34.
[a04] Audio overlaps for 10ms at playtime 2:11:04.
[a04] The audio file was demuxed without making use of the gap/overlap information

[a04] Please rerun the same eac3to command line. That will correct the gaps/overlaps

So you have to repeat the same command (shift+upper arrow) to correct them.

You will get this info at the end of the second pass:

Audio gap description file detected, will be used for processing...

In the first pass, eac3to determines the gaps and overlaps and creates a gaps file to find out and correct them in the second pass.

But unfortunately, eac3to can not correct the gaps/overlaps in TrueHD technically.

And you should get a similar caution on the log file of the first pass.

This is why you can not use them.

What i suggest is to convert thd to pcm; this will fix the issue (alternative is to convert to flac (lossless as TrueHD) but i don't think Scenarist accepts that):

(first pass log)
command line: eac3to\eac3to G:\HDBACKUPS\CETK 1) 3: C:\THD\audio_new.pcm
------------------------------------------------------------------------------
M2TS, 1 video track, 2 audio tracks, 20 subtitle tracks, 2:17:13
1: Chapters, 20 chapters
2: h264/AVC, 1080p24 /1.001 (16:9)
3: TrueHD/AC3, English, 5.1 channels, 48khz
4: DTS Master Audio, English, 5.1 channels, 24 bits, 48khz
5: Subtitle (PGS), English
6: Subtitle (PGS), English

**********
[a03] Extracting audio track number 3...
[a03] Extracting TrueHD stream...
[a03] Decoding with libav/ffmpeg...
[a03] Swapping endian...
[a03] Remapping channels...
[a03] Creating file "C:\THD\audio_new.24bit.pcm"...
[a03] This audio track contains more than 16 bits of information.
[a03] This audio track has a constant bit depth of 24 bits.
[a03] Audio overlaps for 5ms at playtime 0:58:47.
[a03] Audio overlaps for 5ms at playtime 1:34:34.
[a03] The audio file was demuxed without making use of the gap/overlap information.
[a03] Please rerun the same eac3to command line. That will correct the gaps/overlaps.
Video track 2 contains 197424 frames.
eac3to processing took 26 minutes, 58 seconds.

(second pass log)

aec3to\eac3to G:\HDBACKUPS\CETK 1) 3: C:\THD\audio_new.pcm
------------------------------------------------------------------------------
M2TS, 1 video track, 2 audio tracks, 20 subtitle tracks, 2:17:13
1: Chapters, 20 chapters
2: h264/AVC, 1080p24 /1.001 (16:9)
3: TrueHD/AC3, English, 5.1 channels, 48khz
4: DTS Master Audio, English, 5.1 channels, 24 bits, 48khz
5: Subtitle (PGS), English
6: Subtitle (PGS), English
**********
Audio gap description file detected, will be used for processing...
[a03] Extracting audio track number 3...
[a03] Extracting TrueHD stream...
[a03] Decoding with libav/ffmpeg...
[a03] Swapping endian...
[a03] Remapping channels...
[a03] Realizing RAW/PCM gaps...
[a03] Creating file "C:\THD\audio_new.24bit.pcm"...
[a03] This audio track contains more than 16 bits of information.
[a03] This audio track has a constant bit depth of 24 bits.
Video track 2 contains 197424 frames.
eac3to processing took 33 minutes, 47 seconds.
Done.



_ _ _ _ _

flyingernst
18th November 2008, 21:26
if there are gaps in the VideoFile too, will they get removed when I demux the movie in one commando line like:

eac3to moviesource 1) 2: Video.mkv 4: audio.pcm
(with 2 passes)

it realy seems to be the best way to recode them to PCM...
Thanks
For the Moment i got some TrueHD Movies running, but they donīt work as free of problems like with DTS-HD Ma on the PCH

rica
18th November 2008, 21:44
if there are gaps in the VideoFile too, will they get removed when I demux the movie in one commando line like:


(with 2 passes)

it realy seems to be the best way to recode them to PCM...
Thanks
For the Moment i got some TrueHD Movies running, but they donīt work as free of problems like with DTS-HD Ma on the PCH

You're welcome.
I haven't seen any gaps/overlaps in the video files until now.
Another point: i'd never advise to remux to mkv, especially if the video is vc1.
Btw, it was already reported that PCH has issues with THD files for the time being.

flyingernst
18th November 2008, 22:52
oh ok, my knowledge grows every day I am here :)

odin24
19th November 2008, 09:44
Nice, informative and helpful! One suggestion though;

demux:
eac3to input.m2ts output.pcm

reorginising pcm with Pcm2Tsmu to be recognized by TSMuxer:

Pcm2Tsmu input.pcm output.pcm -i 16

Remuxing to m2ts with TSMuxer.


Not all tracks will need the 16 bit parameter set, and other parameters might need to be set as well. If the source is 16 bit, or 7.1 channels, demuxing with eac3to there ar no other options required. However you must indicate this with pcm2tsmu or it will output it's defaults, no matter what the source is.

Defaults for Pcm2tsmu are:
24 bits [-i ##]
Defaults are 6 channels (5.1) [-c ##]
48000 Hz [-s #####]

You did some testing with Dave Matthews & TR, L@RC, for example, if the TrueHD track (which is 96/24) was converted to PCM via eac3to, then worked through pcm2tsmu without any parameters set you would get a 48000 Hz/24 bit output which would cause a considerable sync issue.

Also, if you prepared any 24 bit pcm file with the -i 16 parameter you will lose quality... sorry to point out the obvious.

I bring this up only because I found this out the hard way processing some tracks of my own. Thanks for the thread and support.

lithiumus
19th November 2008, 15:14
lithiumus, thanks for the contribution.

I've just given it a try with a THD;
here are the results:
demux to thd+ac3 with eac3to > 9 GB
remux to m2ts with TSMuxer > 11 GB
remux again to m2ts (or BD) with TSRemux > 11 GB.
Overhead seems to be over than the expected as % 7 to 15; ie %20 but not % 62.

Very interesting. Maybe the larger thd+ac3 tracks yield a much smaller overhead and the smaller (possibly more compressed - lossless of course) will yield a much larger overhead.

Try again with a much smaller thd+ac3 stream i.e. under 2gb and see what results you get.

rica
19th November 2008, 18:59
Nice, informative and helpful! One suggestion though;




Not all tracks will need the 16 bit parameter set, and other parameters might need to be set as well. If the source is 16 bit, or 7.1 channels, demuxing with eac3to there ar no other options required. However you must indicate this with pcm2tsmu or it will output it's defaults, no matter what the source is.

Defaults for Pcm2tsmu are:
24 bits [-i ##]
Defaults are 6 channels (5.1) [-c ##]
48000 Hz [-s #####]

You did some testing with Dave Matthews & TR, L@RC, for example, if the TrueHD track (which is 96/24) was converted to PCM via eac3to, then worked through pcm2tsmu without any parameters set you would get a 48000 Hz/24 bit output which would cause a considerable sync issue.

Also, if you prepared any 24 bit pcm file with the -i 16 parameter you will lose quality... sorry to point out the obvious.

I bring this up only because I found this out the hard way processing some tracks of my own. Thanks for the thread and support.

You are welcome and thanks for the contribution.
As you guess, the original track was 16 bit in my sample.
But you are right, i should have made more explanation.
Thanks again.

Very interesting. Maybe the larger thd+ac3 tracks yield a much smaller overhead and the smaller (possibly more compressed - lossless of course) will yield a much larger overhead.

Try again with a much smaller thd+ac3 stream i.e. under 2gb and see what results you get.

OK, i will try; thanks.

odin24
19th November 2008, 23:44
FYI rica,

I just remuxed a 2 hr (3.8GB)TrueHD track... not quite 2GB, but considerably smaller than 9GB, the resultant was a 5.1GB m2ts file, a 1.3GB difference.

-Cheers.

jamos
27th January 2009, 02:25
rica is there any advantage other than removal of dialog normalization to using eac3to vs. tsmuxer to demux audio from m2ts? from what I have seen they both are the same exact file size streams.

:thanks:

tebasuna51
27th January 2009, 03:35
At least wav files (PCM) have bugs

madshi
27th January 2009, 07:58
rica is there any advantage other than removal of dialog normalization to using eac3to vs. tsmuxer to demux audio from m2ts? from what I have seen they both are the same exact file size streams.
With AC3 there should be no difference (except dialnorm removal), as long as the movie only has 1 part. If there are multiple m2ts parts, eac3to removes the audio overlaps, while tsMuxeR does not. So the only proper way to demux audio from such movies with multiple m2ts parts is to use eac3to. And as tebasuna51 already said, with some audio formats tsMuxeR has bugs, while I'm not aware of any audio demuxing bugs in eac3to right now.

rica
28th January 2009, 00:04
rica is there any advantage other than removal of dialog normalization to using eac3to vs. tsmuxer to demux audio from m2ts? from what I have seen they both are the same exact file size streams.

:thanks:

If we are talking about BD audio formats, TS muxer has issues with:
Single m2ts mpls:
THD
PCM

Multiple m2ts mpls:
Gaps/overlaps can not be repaired by TSMuxer.

_ _ _ _ _

odin24
28th January 2009, 00:34
If we are talking about BD audio formats, TS muxer has issues with:
Single m2ts mpls:
THD
PCM

Multiple m2ts mpls:
Gaps/overlaps can not be repaired by TSMuxer.

_ _ _ _ _

What's the issue with single m2ts MPLSs?

It should also be known that tsMuxeR remuxes PCM from a BD rip/m2ts just fine... it's the demux that's buggy.

rica
28th January 2009, 00:41
What's the issue with single m2ts MPLSs?

it's the demux that's buggy.

Yes, that is what i was trying to say. Demux via TSMuxer is buggy. Also remux without Tebasuna's tool is impossible for pcm.

ddeell72
12th August 2010, 05:57
nice tip .....