"this track is not clean..." message

[Thunderbolt]

For some tracks eac3to outputs a "this track is not clean..." message when performing an option, e.g. dialnorm removal. I wonder what this message exactly refers to, in which situations it does usually occur. Does anyone know?

It also happens rather frequently when using DEE to convert an Atmos 7.1 THD audio track to 7.1 DDP with 1664 kbit/S (=5.1 AC3 EX Core with 640kbit) and then trying to remove dialnorm with eac3to from said created DDP track. I would assume that an official program like DEE wouldnt output faulty audio code? So Im wondering whats exactly up with this 'not clean' message.

[Curly]

Sorry for the delay responding. We've been facing medical issues for DG and Sweetie Pie lately.

Can you provide a short source sample I can use to check it? Possible causes: the audio format changes in the stream, the stream is corrupted, the stream has been cut badly. With your sample I can determine the specific cause.

[Thunderbolt]

do you mean the converted "source" EAC3 track here which was created from the Atmos 7.1 track?

[Curly]

I mean whatever you passed into eac3to (the output of DEE I suppose). Also your command line that produces the error.

[Curly]

Sample is in hand, thank you. Investigating...

[Curly]

There is one frame in your source file that looks like this:

0b 77 1c 58 f9 db ...

The db translates to a bsid = 27 [(db & f8) shr 3]. According to my reading of the ac3/eac3 spec, values > 16 shall be muted. I don't know why it is there. eac3to is warning you about it. Maybe you could follow up with the DEE people. Please let us know if you find out anything useful.

"decoders compliant with this Annex shall mute if the value of bsid is 9, 10, or greater than 16, and shall decode and reproduce audio if the value of bsid is 0 – 8, or 11 – 16"

I'll mark this resolved for now but we can re-open it if needed.

[Thunderbolt]

is this specific frame present at the beginning of the file and present just once? or does it occur repeatedly?

[Curly]

Just once. Not at the start.

[Thunderbolt]

I noticed that this track (or also other 7.1 DDPs, created from 7.1 Atmos THD) is indeed objevtively a bit too loud, meaning theres too much vibration in the speakers compared to all other normal tracks to which you can apply dialnorm removal (but this does not automatically mean that, the other way round, for every track I get this "not clean" message that this applies to these ones as well (other than said 7.1 Atmos tracks))

is this "not clean" warning message only related to the process of dialnorm removal? or could it also apply to faulty audio frames and appear in other contexts as well?

[Curly]

Not just dialnorm removal. It is detected every time an audio frame is parsed.

[Emulgator]

We've been facing medical issues for DG and Sweetie Pie lately.

My best health wishes go from Berlin to Frostbite Falls, Minnesota. DG and Sweetie, get well soon !

[DG]

Thank you, sir. I am on the mend and Sweetie has a Dr. appt. this morning.

[Rocky]

Maybe the warning text could be changed to be more clear about what is happening.

[Bullwinkle]

Frostbite Falls, Minnesota

[Emulgator]

Now that is enlightening ! Classified weather...From when ? 1961-1962.

[Rocky]

1961-1962.

Correct, see 13:17 in the video.

[Thunderbolt]

Maybe the warning text could be changed to be more clear about what is happening.

yes, this would be helpful

[oniiz86]

Maybe the warning text could be changed to be more clear about what is happening.

Is this warning text something that could be adjusted by @Curly in a future release or not necessarily worth the effort?

[Curly]

There are a lot of occurrences of this generic "track is not clean" message. I don't have time to try to analyze them all to replace the messages with appropriate text. And I don't remember which one I had traced it to so as to modify just one of the messages. We have so much other (important) work to do that you're just going to have to live with it.