XMPlay Apple Lossless plugin

Started by Sebastian Andersson,

Sebastian Andersson

I have finished an Apple Lossless Audio Codec (ALAC) input plugin for XMPlay which is available here:

http://www.un4seen.com/filez/2/xmp-alac.zip (updated: 4 Apr '11)

It should support all the usual stuff... but currently lacks the streaming support and tags. Please report any bugs and issues in this thread.

Thanks to David Hammerton and Ian Luck!

triplex

xmplay just suts down when attempting to play .m4a(apple lossless). itunes 7.0 installed

Ian @ un4seen


triplex

It is seems ok now with Itunes 7.2 installed (or maybe you've done some changes in plugin)

But now - what about 24 bit alac support? Itunes only seems to be able to code 24bit alac and xmplay just "shuts down" on such files...

Ian @ un4seen

I don't have any 24-bit ALAC files, so please upload an example to have a look at here...

   ftp.un4seen.com/incoming/

triplex


Ian @ un4seen

Looking at it now, I see the ALAC decoder library used by the plugin currently only supports 16-bit. If you really need 24-bit support, you could try bribing the author to add it :)

David Hammerton

Author here.. Yeah bribes would be good - I'm broke :)

But seriously, I was never able to make iTunes create 24bit alac files, so I never made my decoder capable of using them; but that was back in the day... I wonder if newer iTunes does 24bit ones instead? Weird..

Can someone provide me with a URL to a bunch of 24bit alac files please?

Thanks

David



Ian @ un4seen

It doesn't seem to crash here, so please upload your drwtsn32.log file to get some clues about it...

   ftp.un4seen.com/incoming/

sergos

Here is a screenshot of my VS attached. As you can see it's an entry to some routine and parameter obtained from [esi == ecx] contains a pointer (edi) that can not be read with +2 bytes offset. And edi itself is pretty close to the page size (3ffe) so that we miss the page and sigfaulted (excepted). I bet that some pointer either has wrong value or should not be read with +2 offset. it's hard to reproduce if you have different mem layout.
I think I can debug (if the effect will not gone) the xmp-alac.dll along with the .pdb file. it'll be worse if the effect will not lasts after build with debug info, but you still can find the routine with the same assembly? It looks like the dll mapped starting 10001000 either 10000000

Ian @ un4seen

I didn't make any changes specifically for your problem, but there have been some code changes since the plugin release (in 2005), so here's an updated build to try...

   www.un4seen.com/stuff/xmp-alac.dll

If you still get crashing, please upload a drwtsn32.log entry for that.

   ftp.un4seen.com/incoming/

sergos

With this new version the playback is just stopped and the track is overstriked red.
Although it is better than fault yet no my favorite Prokofiev :)

WonderSlug

Quote from: sergosWith this new version the playback is just stopped and the track is overstriked red.
Although it is better than fault yet no my favorite Prokofiev :)


I figured out the problem.

I was having the same issue that you were, and tried playing it in several other media players which it did fine.

I then examined the encoding properties and it's AAC 44100 Hz Stereo 128 kbps.

This means it's not ALAC but AAC, so you need to download and install the XMP-AAC plugin.

Once I did that, the file plays fine in XMPlay.

Tsorovan

#15
I uploaded 04 Chain.alac. alac.exe can decode it. The ALAC plugin cannot.



amit

When starting xmplay with the current alac plugin I get a message "The application has failed to start because MSVCRTD.dll was not found. Re-installing the  application may fix this problem". Xmplay then starts but unable to play alac files. The previous plugin version (from 2007) crashes xmplay whenever I try to add alac file.

Ian @ un4seen

Oops, an updated build that doesn't require MSVCRTD.DLL is now in the 1st post.


shrisha

Unfortunately I still have no luck with 24/96 files. Should I upload some files for you to check? May be it's depends on what software was used for compression?

Dotpitch

Quote from: shrishaUnfortunately I still have no luck with 24/96 files. Should I upload some files for you to check? May be it's depends on what software was used for compression?
Quote from: Ian @ un4seenLooking at it now, I see the ALAC decoder library used by the plugin currently only supports 16-bit. If you really need 24-bit support, you could try bribing the author to add it :)
Perhaps you should ask the author the revive the project, the latest decoder is from September 2006.


shrisha

Goodness!!! 24/96 finally supported! Thank you sooooooooo much!!!