Delay correction in HeadAC3he 0.23a ?

[user]

How can correct the delay of an *.ac3 file in latest Headac3he ?

If I load an ac3 file, then there is shown automatically the correct delay of the stream under "source file".

Does this mean, that this delay is corrected/applied automatically if this ac3 is converted later on to wav eg. ?

Or do I have to put in the delay manually in "Start frame", where I would be able to correct the delay on a frame to frame basis ?



I remember, that in some earlier Headac3he versions, the delay was corrected automatically and shown in "start frame".

Today, 0.23a, the delay is shown under "source file", but the "start frame" remains at beginning, first frame, zero seconds.
Does this mean, that I have to select the "start frame" manually for correcting delay, or is the delay already corrected automatically, because under "source file" the delay is shown ?




Don't worry about this long text, it is ONLY ONE question, in fact !
Many thanks for answers.

[user]

aha, I have found out:

If you set the delay (which is set even automatically) in "delay" under "source file" , then the delay is corrected.

So you do not need to select "start frame".

So it is very easy for "users".

Please correct me, if I should be wrong.

[user]

Dark Avenger's explanations

translation by user:

The delay is corrected independent from the choice of start frame (v0.22 has had a bug),
*but* no o frames are added, if you have *.ac3 as target. So positive delays are not corrected.

Delays at *.ac3 target are corrected only in steps of 32 ms (otherwise you would have to reencode completely). (Look at the log.)



If you select a start frame 2 , and now you have for example a delay of -32, then effectively you will result with a "correction" of -64 ms.
At every target (decode) it is similar, but every delay is corrected without exceptions.

Values in ms are only valid for 48 kHz files.


D A





German original text:

delay wird unabhängig von Wahl des Startframe korrigiert (v0.22 hatte nen bug), *aber* es werden keine 0 frames angehängt, wenn du als target ac3 hast, also positive delays werden nicht korrigiert. delays werden bei ac3 target nur in 32ms Schritte korrigiert (sonst müßtest du komplett reencoden). (Achte auf den log.)

Wenn du nun ein startframe 2 wählst, und du hast etwa delay -32, wird effektiv auf -64ms "korrigiert". Bei jedem anderen (decode) target gilt analoges, nur das jeglicher delay ohne Einschränkung korrigiert wird.

Die ms Angaben beziehen sich nur auf 48kHz Dateien.


D A