Topic: XMPlay AAC & MP4 plugin

[SmartOne]

The buffer problem only occurs with AAC files.  It also happens without DirectSound.  Tested on two separate audio devices.

[Dotpitch]

The buffer problem only occurs with AAC files.  It also happens without DirectSound.  Tested on two separate audio devices.

And is that only with DirectSound, or with WaveOut as well? I take it you don't unload the file when you stop playback?

[SmartOne]

Same result with WAV Writer.  Unloading the file (stop twice) gives a fresh start.

[Ian @ un4seen]

... if I play, stop, and then play a file again, I hear a bit of unflushed buffer before the new playback begins.

Yep, I can reproduce that with MP4 AAC files (plain AAC seems fine?). I'll look into it.

[Ian @ un4seen]

OK. Here's something to try...

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

[SmartOne]

Thank you.

[JustForMyMemory]

The year tag of AAC/M4A files displaying in XMPlay (example) like 2009-10-23T07:00:00Z not 2009 in other players (Windows Media Player 12 & foobar2000).

I know the tag 2009-10-23T07:00:00Z is actually written on the file. But, other players can display only year.

Why can't XMPlay? Any fixes?

[saga]

The year tag of AAC/M4A files displaying in XMPlay (example) like 2009-10-23T07:00:00Z not 2009 in other players (Windows Media Player 12 & foobar2000).

I know the tag 2009-10-23T07:00:00Z is actually written on the file. But, other players can display only year.

Why can't XMPlay? Any fixes?

What, you're asking XMPlay to show less than it can? Isn't that kind of a regression?

[JustForMyMemory]

The year tag of AAC/M4A files displaying in XMPlay (example) like 2009-10-23T07:00:00Z not 2009 in other players (Windows Media Player 12 & foobar2000).

I know the tag 2009-10-23T07:00:00Z is actually written on the file. But, other players can display only year.

Why can't XMPlay? Any fixes?

What, you're asking XMPlay to show less than it can? Isn't that kind of a regression?

No, I just want XMPlay to be smarter, recognizes the date format and show the year just (example) 2009 (like other players).

[wrkq]

And we're asking why you want it to show less information when more is available. Don't hide stuff from the user!

[JustForMyMemory]

And we're asking why you want it to show less information when more is available. Don't hide stuff from the user!

Here is my problem:

[Dotpitch]

Here is my problem...

Instead of %4, use %cut{%4|4|} in your title formatting as a workaround. I've put your suggestion on the list for xmp-aac, be patient.

[wrkq]

You know that this is the first time you pointed out (implicitly) that you mean the %4 title formatting component?
For me, "date tag" is what you can see in info window, and that one should be as detailed as possible. And well, agreed, this in title looks a bit weird.

Instead of %4, use %cut{%4|4|} in your title formatting as a workaround. I've put your suggestion on the list for xmp-aac, be patient.

And yay, I was just going to ask if such functionality exists!

[JustForMyMemory]

Here is my problem...

Instead of %4, use %cut{%4|4|} in your title formatting as a workaround. I've put your suggestion on the list for xmp-aac, be patient.

Thanks for that workaround.

May be only me need to use  %cut{%4|4|} in my title formatting because only I set to display the year tag. Problem's solved

Please don't put my suggestion on the list for xmp-aac anymore, this problem made very small impact.

[JustForMyMemory]

You know that this is the first time you pointed out (implicitly) that you mean the %4 title formatting component?
For me, "date tag" is what you can see in info window, and that one should be as detailed as possible. And well, agreed, this in title looks a bit weird.

I agree. Just let XMPlay displays what is written in M4A/AAC tag.
The problem is now solved. Only me need to use it.

[JustForMyMemory]

A tiny tweak:

> If the AAC plug-in is still using "technology" of year 2003 and 2005, please update it to the latest version.

> If the AAC plug-in used the latest version, please update the year number (to let people know that it is updated).

(This feedback aloso applies for FLAC plug-in and APE plug-in)

[Pike84]

Even though the AAC encoder has been updated and improved over the years, that doesn't mean that there needs to be something changed in the decoder (the plugin). I'm not an expert at this, and I guess it'd be fine to check it out in case, but an update is probably not needed.

[edit]Those years of copyright are not an indicative of the age of the plugin itself or the "technology used".

[saga]

Also, this shows again how useless copyright "years" are - or rather, how they are abused. Programs just writing (c) $currentSystemClockYear are even more silly.

[JustForMyMemory]

Also, this shows again how useless copyright "years" are - or rather, how they are abused. Programs just writing (c) $currentSystemClockYear are even more silly.

And I think if some company wrote "Copyright (C) 19XX-present. All rights reserved.", they're so cool (literally).

[Zarggg]

That's not how copyright works.

[Alex K.]

Hello. You guys are cool! And XMPlay is very cool. ASIO is also great. But, unhappily, XMPlay can not play some (or most of) .m4a files. This format is a part of AAC, which is possible to decode with this subject's plugin, accordingly to people's posts. Can you provide an information whether it's possible to listen to .m4a encoded music with current XMPlay or will be possible in future versions?

Here, I provide you with an example of problem file:
http://exfile.ru/347398

[Chinese Sausage]

You need the ALAC plugin to play that file.

[Alex K.]

Thank you. It's working. God bless all of you, people! XMPlay rocks, so do it's users! 

[Ajaja]

Have problems with playing files encoded by ffmpeg using libfdk_aac library with aac_he_v2 profile. Example "xmp_aac_unsupported.m4a" uploaded to ftp.un4seen.com/incoming/
XMPlay v3.7, xmp-aac.dll rev.7a
Other players (foobar2000 and others) plays this file normally.

[Ian @ un4seen]

Here's an update for you to try...

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