Closed VoidXH closed 7 months ago
If I can help in this process I would be delighted. I have the latest Nuendo and Pro Tools to test ADM imports. Don't hesitate and thank you once again for these superb tools Bence!
This task wasn't successful, as Cavern always generated files recognized correctly by DACT. This leads to a conclusion, for supporting the ADM BWF standard, Cavern is currently stable. Since DACT has no problem with imports, a conversion with it to another format and back, maybe to the same format, will likely solve import issues.
The root cause of having to talk about this in the first place is likely Dolby having yet another handling of ADM that differs from the standard, maybe from the RF64 standard. If there's no proper error messaging from their end, this issue is not solvable.
A notification was added regarding this problem to Cavernize GUI in 14f642899211377962a3dd195b2ebfc93171143b, included in the latest release.
Mediainfo got recently updated and it now warns on some of produced ADM RF64 files
the source for this ADM is this one https://drive.google.com/file/d/1L7hYPf4tdbSGpFhlt6w4CKSTSb6ULPlY/view
While RF64 is supported, ADMs over the (
u
?)int32
size limit can't be imported into DAWs.Tasks: a) Have a sample code that generates large LAF files as it's stable, to be converted to ADMs with Cavernize for testing the limit. b) Check all
int
time conversions, uselong
instead. c) Add an ADM validation point that checks if timestamps are in incrementing order.