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: FB2K v2/v2.1 cannot support Monkey's Audio 4.11 version APE file (Read 2868 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

FB2K v2/v2.1 cannot support Monkey's Audio 4.11 version APE file

FB2K v2/v2.1 cannot support Monkey's Audio 4.11 version APE file
show ""Unable to open item for playback (Unsupported format or corrupted file):" error

v2 has built-in monkey’s audio components, and cannot replace the old version by itself :'(

Re: FB2K v2/v2.1 cannot support Monkey's Audio 4.11 version APE file

Reply #1 –
I downloaded Monkey's Audio v4.11 and created a test track with various compression levels. Everything works fine on foobar2000 v2.0 and the v2.1 preview.

You could try the file with latest version of official Monkey's Audio. If it doesn't work on it either, you could contact Matt Ashland and report the problem to the source.
Or you could share a sample file so people could try and figure out what's wrong with your track.

Re: FB2K v2/v2.1 cannot support Monkey's Audio 4.11 version APE file

Reply #2 –
、
Quote from: Case on
I downloaded Monkey's Audio v4.11 and created a test track with various compression levels. Everything works fine on foobar2000 v2.0 and the v2.1 preview.

You could try the file with latest version of official Monkey's Audio. If it doesn't work on it either, you could contact Matt Ashland and report the problem to the source.
Or you could share a sample file so people could try and figure out what's wrong with your track.

This is a file with playback errors, i try use old version monkey’s audio components like 8.7 is can play

link removed (preserved)

Re: FB2K v2/v2.1 cannot support Monkey's Audio 4.11 version APE file

Reply #3 –
The file can't be decoded with the latest MAC.exe v10.13. I don't see any mention of compabitility breaking between 4.11 and the latest version in the changelog. Perhaps @MonkeysAudio wants to take a look.

Anyway, foobar2000 uses the official Monkey's Audio decoder so any limits it has affect also foobar2000.

Re: FB2K v2/v2.1 cannot support Monkey's Audio 4.11 version APE file

Reply #4 –
No reply from the format author so I took a look myself.

I'm curious how the file was created. The file header has marked the file to be version 4.11 but Monkey's Audio 4.11 and even the latest 10.16 mark files as version 3.99.
Old Monkey's Audio decoder only checked file version field and resumed processing if the file was new enough. New Monkey's Audio checks in addition that version is 3.99 or older.

New decoder happily decompresses the file if I remove the <= 3.99 version check, but that might cause unexpected issues. I won't dare to suggest such change to Peter without understanding what this nonsense is about.

Re: FB2K v2/v2.1 cannot support Monkey's Audio 4.11 version APE file

Reply #5 –
MAC.exe versions 8.43 (that's before this format change, but that shouldn't matter for CDDA) 8.53, 8.97, 9.10 and 9.15 (edit2: and 9.20, both 32 and 64-bit) handle it, but (edit2: 10.07, both 32 and 64) and 10.08 do not.
Edit2: Tested a decode from an old MAC.exe: got a .wav that verifies AccurateRip. That also indicates the file is OK and the Monkey is ill.
Edit: old versions at https://www.videohelp.com/software/Monkeys-Audio/old-versions

Quote from: Case on
mark files as version 3.99.
Doesn't that apply to "everything" encoded with 4 and above?

Re: FB2K v2/v2.1 cannot support Monkey's Audio 4.11 version APE file

Reply #6 –
Thanks for the file.  It verifies fine if I simply remove the too new version check.

What version of Monkey's Audio was building files with 4110 as the version?

This has been the coded version number for a really long time:
#define MAC_FILE_VERSION_NUMBER                         3990

Thanks for the help.

Re: FB2K v2/v2.1 cannot support Monkey's Audio 4.11 version APE file

Reply #7 –
Was it encoded with some third-party tool?  I'm going back through my SVN history and it was 3990 even for releases 4.11 and around there.  Thanks.

Re: FB2K v2/v2.1 cannot support Monkey's Audio 4.11 version APE file

Reply #8 –
I added checking for versions newer than MAC_FILE_VERSION_NUMBER with the 10.0 release.  It was done so if the format gets incremented at some point in the future, old encoders wouldn't try and fail.  But I still have no idea what was building files with a newer version already today.  Thanks again.

Re: FB2K v2/v2.1 cannot support Monkey's Audio 4.11 version APE file

Reply #9 –
FWIW, every GitHub search hit on "#define MAC_FILE_VERSION_NUMBER" returns 3990.

Somebody has experimented with their own build, found it works, shared the album out on the 'net and ... here we are?

Re: FB2K v2/v2.1 cannot support Monkey's Audio 4.11 version APE file

Reply #10 –
And then ppl are told to support said rubbish.

Why?

Re: FB2K v2/v2.1 cannot support Monkey's Audio 4.11 version APE file

Reply #11 –
I had another user email me a file with 4110 for the version.  He said he downloaded it some years ago.

I could easily add support for the files, but would really like to understand where they came from first.  They seem to decode fine using the same code I'm using for modern files.

Thanks for any tips.

Re: FB2K v2/v2.1 cannot support Monkey's Audio 4.11 version APE file

Reply #12 –
I put a test build here and it worked:
https://www.monkeysaudio.com/files/MAC_1026_x64.exe

Would still love more details on what made the files.

I'll probably release it more widely after I'm back from vacation this week.  Thanks all.

Re: FB2K v2/v2.1 cannot support Monkey's Audio 4.11 version APE file

Reply #13 –
@MonkeysAudio : You might have googled it up already, but even a couple of years before you got the issue up in the JRiver forum, it was reported here (July 2014). With a link to DeaDBeeF's lost old space at code.google.com, before the developer went to GitHub. You might contact him and ask if he remembers that issue that far back? Although from the linux.org.ru thread, it seems it was sent just an untagged file of unknown source.