Skip to main content ↑ ↓

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Topic: New Android Foobar2000 version(s) don't scan correctly some .m4a track length (Read 1203 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

New Android Foobar2000 version(s) don't scan correctly some .m4a track length

I moved my library to a different sd card and Foobar needed to rescan it.
Now I cannot play some .m4a tracks because their scanned length is fixed to 10 sec.
The same version of Foobar (1.2.22) was reading the same tracks correctly before the card switch, so it seems the problem is in the library scan, not in the decoding.
I added the tracks on September 2019 - the scan error was introduced between that date and now.
The problem doesn't show for tracks converted with the Nero encoder, only for some tracks obtained with an audio ripper to extract audio from web pages (I don't remember what one).
Checking the tracks with Foobar for Windows doesn't show any error.
Is this a known problem?
Is there a way to sanitize the tracks without re-converting them?

Thanks in advance,
simon_owl

Re: New Android Foobar2000 version(s) don't scan correctly some .m4a track length

Reply #1 –
Please upload and PM Peter with links to at least one broken file, otherwise he'll have to figure out some way to recreate your files with only the encoder.

Re: New Android Foobar2000 version(s) don't scan correctly some .m4a track length

Reply #2 –
Should be fixed in 1.2.25 beta, thanks for reporting.
Microsoft Windows: We can't script here, this is bat country.