Closed gdavis closed 2 years ago
This is happening on this file because it is a "non-optimized" M4A AAC file. Being non-optimized means it does not include the header information at the start of the file, so determining the file format fails when trying to parse the file data.
So far I'm unsure how to go about fixing this without having to convert the file when it is downloaded. Technically, this could be considered a feed error since the file is not optimized for streaming when serving an online podcast file. Ideally, we'd be able to work around this and get AudioFileStreamOpen
to properly stream the file, even without optimized compression.
Some helpful information here: https://stackoverflow.com/questions/23503117/fail-parsing-m4a-aac-file-with-apple-audio-file-stream-services-ios-7?answertab=scoredesc#tab-top
and here: https://www.cocoawithlove.com/2010/03/streaming-mp3aac-audio-again.html
Thank you for looking into this! Hopefully Sony gets their encoding working optimally for future episodes! And, at least the feed is good, so I can still use Mimir to know when there are new episodes, even if the episodes continue to be sent in the same format
@verumsolum Hopefully since its a new feed its a mistake they will fix, or maybe we should contact their feed admin to let them know about this. If it continues to be a problem with future episodes they release, please let me know. Maybe I can escalate trying to figure out a fix for this on my end if it prevents the feed from being usable.
@verumsolum If it continues to be a problem with future episodes they release, please let me know. Maybe I can escalate trying to figure out a fix for this on my end if it prevents the feed from being usable.
I will. I believe the first "full" episode is supposed to be released sometime today and weekly after that, so there shouldn't be too much wait to see what they release.
And the first full episode is playing properly through Mimir, so presumably the podcast's producers have made the appropriate change
Ah, fantastic! I'll go ahead and close this issue in that case. Thanks for checking!
User report: