-
Notifications
You must be signed in to change notification settings - Fork 70
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Channel Coupling #69
Comments
Thank you. How might I determine this? I notice Original:
Deleted up to and including “mdat” (
Not-partially-formed M4A file from same source;
facmwfa.latm:
Possibly of note: The latest
|
You cannot just cut away everything up to the Plain .aac files, on the other hand, usually contain an ADTS stream that embeds the ESC into frame headers. Other formats for .aac files are ADIF and LATM. But you cannot convert an .mp4/.m4a file to any of these formats simply by cutting something off the beginning of the file. The only case in which this might work is if the MP4 file does contain LATM packets and the ESC is multiplexed into the packets. This is a possible scenario, but would be extremely rare. Anyway, in your case, there are no LATM packets. Your file with the cut-off head is missing the LATM sync bits, so it's probably just raw AAC frames. The LATM sync signature is 0x56E or 0x56F (only the first 11 bits are considered) and can be seen in the file provided by @ValZapod, but not in your file. You are basically feeding random data to faad here. This is not a faad issue. |
@fabiangreffrath: according to @enzo1982 comment we can close this issue; channel coupling is still not implemented, but that would be a feature request, not a bug. |
Well then... |
Deleting a partially formed M4A file's header up to the "mdat" and attempting to decode results in the following:
Are there known workarounds? Thank you.
The text was updated successfully, but these errors were encountered: