View Full Version : AC-3 file issue? non-compliance checking
Ghitulescu
30th January 2014, 09:28
I believe this thread belongs here.
To make a long story short, I combined 5 DVDs of a documentary series into a single "large DVD" then passing it through DVD2BD express (free version) to get a BD. After this I tried to join all the episodes into a single M2TS. And here my troubles began.
All went ok until the last episode. All new versions of tsmuxer failed with an unknown error, tsremux 1.10.6 could do it (but not the joining), so tsremux. In the end I traced down the problem to the French AC-3 audio track.
Since it appears that I cannot join my episodes via playlists (to keep the chapters), I am now forced to see whether this audio track is defective.
My question is therefore is there any software to check the compliance (or non-compliance) of an audio file encoded in DD?
tebasuna51
30th January 2014, 11:58
To join several AC3 files all must have the same parameters (Channels, Samplerate, Bitrate).
You can use DelayCut to know these parameters of each file, also you can PROCESS the files to see if someone is corrupt.
Groucho2004
30th January 2014, 12:16
is there any software to check the compliance (or non-compliance) of an audio file encoded in DD?
Try Azid:
azid --no-output track.ac3
However, I don't know how the interpret the errors it reports (CRC error, etc).
Ghitulescu
30th January 2014, 15:05
To join several AC3 files all must have the same parameters (Channels, Samplerate, Bitrate).
You can use DelayCut to know these parameters of each file, also you can PROCESS the files to see if someone is corrupt.
All corresponding streams are identical.
TsMuxer also gives and unknown error (the standard error box of Windows with no message and an Ok button :) ) when I try to remux the separate elementary streams back into an M2TS file. Version 1.10.6 can remux all items together, newer ones however cannot. TsRemux can also remux the original file.
It's not a question of joining, but one of (mis)interpretation of a file.
I have yet to trace down the error to tsmuxer or to its GUI.
I processed the file through delaycut, it provided no errors, and a FC /B also indicated no differences between the corrected version and the original one. TsMuxer still issues an error with no error message attached.
I processed the file in azid with --no-output, no error
tebasuna51
31st January 2014, 01:22
Then AFAIK is not a problem with AC3 tracks.
Ghitulescu
31st January 2014, 08:05
Maybe, maybe not.
If tsmuxer loads 2 DD files but refuses a third one, all obtained in identical mode, from a professionally authored disc, there must be something with that file. This seems logic to me.
It may be a bug in tsmuxer or its GUI. tsmuxer may react to "something" in the (most probably) header, as the error is almost instant.
Is there any tool to rewrite the DD file like a demuxer/remuxer? To copy the data but to rewrite/update the header accordingly?
tebasuna51
31st January 2014, 09:42
Well, DelayCut read the most important data from AC3 header but maybe you can try LeeAudBi (http://forum.doom9.org/showthread.php?p=1522330#post1522330) than read all the data header and compare.
setarip_old
31st January 2014, 19:05
Hi!
Try using a hex editor such as WinHex...
vBulletin® v3.8.11, Copyright ©2000-2026, vBulletin Solutions Inc.