Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Fix link failure with gcc-9 and wl,asneeded flags
Author: Gianfranco Costamagna <locutusofborg@debian.org> Last-Update: 2019-06-11
- Loading branch information
920ec98
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Somehow this commit? BREAKS playback of many AAC streams causing broken play and floods of errors in Audacious media player (v2.8.8-3 works fine, v2.8.8-3.2+ FAIL) and this is the only thing mentioned in the changelog for v2.8.8-3.2. Please investigate.
ERROR aac.cc:449 [play]: Channel coupling not yet implemented.
ERROR aac.cc:449 [play]: Unexpected channel configuration change.
Example stream: https://c4icy.prod.playlists.ihrhls.com/3379_icy
Thanks,
Jim (turnerjw784@yahoo.com)
920ec98
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
With these I guess you are referring to Debian package revisions? Well, there was 2.8.8-3.1 between them and this contained far more invasive changes than the changed linker line in 2.8.8-3.2. You might want to check this one out first: https://snapshot.debian.org/package/faad2/2.8.8-3.1/
@hlef Do you think one of your security patches might have introduced this behavior?
920ec98
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, this is probably a consequence of 3b80a57.
In short, this commit adds a check to reject specific broken AAC streams. Those streams previously "seemed" to be supported by FAAD2, but this support heavily relied on undefined behavior, and contained security relevant issues. I don't think the output was valid / reliable.
Now I hope we're not rejecting valid streams with this check. I spent a lot of time on this patch, this seems quite unlikely to me. But still, I might be mistaken. I will try to take a look at this during the week-end.
thanks for reporting this.
920ec98
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the quick responses!
Yes, I'm referring to Deb. package#s. I'm using Antix, a derivitive rolling distro of Debian Testing and it skipped v2.8.8-3.1. I went ahead and installed v2.8.8-3.1 from the snapshot link above (libfaad2_2.8.8-3.1_amd64.deb) and, as I suspected, it failed too (I doubted that the simple 2.8.8-3.2 patch was the culprit). Anyway, the example stream I included was a commercial radio station on IHeartRadio (https://www.iheart.com/live/lone-star-925-3379/: Lone Star 92.5 - Dallas-Ft. Worth's Classic Rock). Here are a cpl. more commercial station examples from IHeartRadio: https://c10icy.prod.playlists.ihrhls.com/2241_icy (97.1 the EAGLE) and https://c11icy.prod.playlists.ihrhls.com/7094_icy (Bloomberg Radio - 24/7 Global Business Coverage).
All 3 seem to play fine under v2.8.8-3, which I've rolled back to for now.
Hope this helps and let me know if I can be of further assistance.
920ec98
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I can confirm the issue for Mixxx after we received the first error report from an Arch Linux user: https://www.mixxx.org/forums/viewtopic.php?f=3&t=13157
920ec98
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I see v2.9.2-1 has come out, but b4 I upgrade, has anything been done a/b this yet? (I didn't see anything related in any of the commits since)