My best guess is that the issue I'm having has to do with the "encoding method" of certain AIFF files. However, I'm on a Mac and can't figure out where "encoding method" is even listed on a music file.
The issue I normally have (and I'm sure most of us do) with the E-8305 error message is when bit rate or bit depth of a lossless file is too high. That isn't the case here.
Several files I've downloaded from Qobuz.com have been giving me this error message. I'm downloading in AIFF format, 16bit, 44.1 kHz. Certain Qobuz purchased files give me the E-8305 error message while others don't. The solution is for me is to re-export each problematic song in Audacity with the same settings, but I'm still trying to determine why some of the original files I've been downloading won't work.
I think what's going on is similar to what happened here with the files needing PCM encoding but I want to confirm because I haven't found any information online about this being an issue with AIFF files, only with certain types of WAVs.
Here is an example of two files, same song, one that was originally downloaded from Qobuz and won't play and one that was exported in Audacity and now works.
Original Qobuz download (gives E-8305 message and won't play):
https://drive.google.com/file/d/1PGMoB8l3y9F2XrdaUt-youC1oTFjPSvL/view?usp=sharing
Audacity re-export that now works:
https://drive.google.com/file/d/1KWXazDCojh0SHSl3aTXqGYkjowFmEri1/view?usp=sharing
Thanks for the help! It would be awesome if this issue could be resolved using a HEX editor so I don't have to re-export each file in Audacity and re-categorize it.
Post is closed for comments.
From a scan...
01 101 FM (Toddla T Remix).aif
000000000269 Framing: ID3 ' TDR' frame: Dropped ID3 v2.2 frame
000000148979 Framing: ID3 'TCON' frame: text string contains redundant trailing nil(s)
I'd say it's just bad header data.
I ran the repair; see if this version works.
The version from the repair works. Thank you!
Can you explain what program(s) you used to do the scan and repair. Also, is the original file itself able to be repaired or does it need to be re-exported each time?
I used the Audio File Health Check app which can identify the issues and create a log file, but requires Yate (an awesome Mac-basd metadata manager) to repair it.
Once you've fixed the app, it may need to be re-imported / re-analysed / exported again.
Awesome, thank you so much for the help!! :)
Is there an alternative for windows? I might be having the same issue.