Related
So which one do u choose ?
CorePlayer
Nitrogen player
Windows media player
TF3D music player
or others?
Plz post your reasons too
so? 90 views and no answers
i'm using pocket player . it works great
and i'm using it with jabra stereo blutooth headset.
TF3D music player
I've been using the TF3D music player on my tp2 for about a month now and it seems to be doing all that i need from it.
Simple to use and good quality output as well. Can't say much about other music players as I haven't used any recently.
in order to get as much music on my phone as possible i am using aac compressed audio (with SBR). This format provides 128kbit/s-mp3-quality at 48kbit/s (at least to my ears).
The only players that i know supporting this format are WMP and TCPMP. As TCPMP does software decoding the device gets slow during playback. WMP seems to have something like hardware acceleration for aac. therefore i am using WMP (with another skin as the default one is not very finger friendly).
thanks yeah i like the TF3D default myself too Nitrogen is good but i think the volume is a little low compared to TF3D player,i use coreplayer for movies and TF3D for musics,just wanted to know other opinions
while the htc audio manager is nice, NITROGEN is now my player of choice despite minor bugs.
WMP works well for me. Don't like the skin but I have downloaded an HTC-like theme so it is all good.
pocket player too
wide variety of audio format support (4.x supports aac), AVRCP support, plugin to add pitch adjustment
Power Problems
Mesquire said:
while the htc audio manager is nice, NITROGEN is now my player of choice despite minor bugs.
Click to expand...
Click to collapse
How did you get the player to play in power saving mode. with the screen off. Whenever I do this it stops the music, and some times, even unloads my memory card.
This has been my biggest bain and major issue with my tmobile tp2. I have tried Mortplayer and Nitrogen, the best IMHO and have had the same issue. I have tried different searches to enable the device to let the music play while the screen is off and none have worked. I am going to try S2P. My only gripe witht that program is that it does not play all file formats.
Oh well...
Coreplayer.
Has EQ, bass boost and pre-amp options and also is the best video player.
juliangun4ev said:
i'm using pocket player . it works great
and i'm using it with jabra stereo blutooth headset.
Click to expand...
Click to collapse
yeah,Pocket Music Player is the thing,it can auto power off and power on,holy ****,which else can be as nice as this one?
+1 for Pocket Player.
My reasons: AVRCP support (a must have feature for me), wide format support (many free players don't support wma, which is a deal breaker for me), equalizer, gapless playback(!), quite finger friendly (some buttons are rather small on the default skin, but it has kinetic scrolling etc.)...
Video support is a bit lacking, but then again I only use it for audio.
I use Pocket Player as well, mostly because it works well for both music and audio books. I am frustrated with whatever method it uses for shuffle, though. I've had 6 different songs play 2-4 times in 4 hours. I have nearly 1000 songs and 66 hours of music! Seems like I should not be getting that kind of repetition.
Pocket Player problems with playing large MP3 files...
One thing guys - and anyone who uses Pocket Player on the TP2 may have seen this... I listen to a lot of voice audio. I prefer to combine the files for audio and can sometimes have long audio files of 300 megs all the way to 1.2 gigs (I use a 16 gig storage card).
The problem i have seen is that sometimes the control that shows where you are in the audio file goes haywire and slides from the correct position all the way to the right - making the bookmarking feature fail and impossible to navigate. Additionally it appears Pocket Player somehow miscalculates the size and length of the audio - but it originally has the size and length correct - this only happens after a certain point (for me it seems after about 240 minutes or so - about 4 hours in).
WHat is so strange is this does NOT happen for all audio files on this device. Some of the large files seem to play fine without problem. Additionally when I compare this to another TP2 that has an installation of the competitor program Pocket Music, this does NOT happen. Also this never happenedon our original HTC Mogul from Sprint.
The problem is we need the AVRCP controls and we all know that Conduits is the only company that has addressed this. It's also pathetic that HTC themselves has continued down this path and refuses to even comment on this issue.
2 questions to this wonderful community of genius people who take it upon themselves to fix what should have been included in the first place:
1. Has anyone seen a hack / mod that will fix the AVRCP controls so that programs like Pocket Music and other players can be used via Bluetooth remote controls?
2. Has anyone seen this specific issue with Pocket Player (which has that beautiful speed plugin that does not alter pitch - love that) and if so - is there a fix or workaround for large files 'breaking' in the middle of playing so that you can no longer save your position or know the correct position of the player in the middle of the MP3 being played?
Thanks in advance to all of you who have any suggestions on either issue.
I'm using Kinoma Play, though mainly for its integration with Orb and video abilities.
For music it supports album art, but only has bass and treble adjustments, not an equalizer.
There is a Kinoma Free you can try.
I am searching for the perfect player and have been testing several of them to see how they work. In addition to some of the normal music player requirements I have 2 pet peeves in particular:
1) The player must support the "Album Artist" tag so that compilations are listed properly in the library.
2) Proper alphabetization - "The Beatles" should be listed under the B's not incorrectly under the T's.
I am testing Pocket Player right now. So far it is the only music player that supports and uses the "Album Artist" tag and it does so by default. It does not support proper alpha. AVRCP works fine out of the box.
The HTC player has the advantage in that it is the only player that can be integrated on the TF3D tabs but does not utilize the "Album Artist" tag nor uses proper alpha. It also has a serious bug that prevents it listing and playing a albums tracks in the correct order. AVRCP of course works well.
WMP supports proper alpha but not the "Album Artist" tag. Strange since MS pioneered the use of the "Album Artist" tag in the desktop version of WMP. AVRCP works fine.
CorePlayer is an evil company. I will never buy or use any SW they make.
Kinoma is next up on my list.
I wish I could find a music player that addresses both of my pet peeves and could be integrated into the TF3D tab replacing the HTC one. That would be the perfect player for me.
S
sleonard said:
2) Proper alphabetization - "The Beatles" should be listed under the B's not incorrectly under the T's.
Click to expand...
Click to collapse
I understand what you're saying but I would argue that any player that puts that artist name under B is the one doing it incorrectly. If you want The Beatles under the B's then you should rename those tracks to the album artist "Beatles."
For the people that got the TF3D music to work, please share your magic on having it identify your library from a storage card.
moSess said:
How did you get the player to play in power saving mode. with the screen off. Whenever I do this it stops the music, and some times, even unloads my memory card.
This has been my biggest bain and major issue with my tmobile tp2. I have tried Mortplayer and Nitrogen, the best IMHO and have had the same issue. I have tried different searches to enable the device to let the music play while the screen is off and none have worked. I am going to try S2P. My only gripe witht that program is that it does not play all file formats.
Oh well...
Click to expand...
Click to collapse
I know this question is like 2 months old but I use Nitrogen and its good enough for me...very finger friendly! And on the main screen there's a button that looks like a Power Button under the volume keys...thats how you put it into "sleep mode" and music will continue playing.
Hi,
I have all my music library encoded as eaac+ 48kbps parametric stereo as this allows me to fit my entire music library on my microsd card.
Been using my music collection on my HTC HD2 which i soon replaced with the Desire.
Thing is that after some of the tracks i've been listening to started sounding funny, i've investigated more on the issue to find out that the Android eaac+ encoder seems to be doing quite a bad job...
For example the .aac file i've attached sounds almost perfect on my laptop and HD2 (using the same hi quality Sennheiser headphones) but on the desire the low bass sounds are awful, it's just like someone is hitting on a broken drum.
Could someone please help me confirm this issue? Could you try playing the attached test .aac file on the htc desire and let me know if you encounter the same problem with it sounding awful? (Try also on a laptop with latest winamp to see the difference).
Thanks !
Hi ubik,
All my digital audio files are also eaac+ at 48kbps, but are in .m4a containers, not .aac, but that shouldn't make any difference (By the way aac+ with parametric stereo = eaac+). As I'm about to buy a Desire, your post made me think that maybe the Desire doesn't support eaac+, only aac+. Iphones and ipods only support aac+, so eaac+ files come out in mono and sound rubbish on those devices. HTC's website doesn't confirm if the Desire plays eaac+ files, so I contacted HTC via their website, and they confirmed that the Desire supports these audio formats .wma, .aac, .m4a, .mp3, .mp4 and .wav files And these codecs WAV, WMA, AAC, AAC+, eAAC+, M4A, MP3 and MP4. Therefore if it supports the eaac+ codec, you should get CD quality sound with your eaac+ files at 48kbps. Maybe you should ask HTC about this via their website.
SpaceGooner said:
Hi ubik,
All my digital audio files are also eaac+ at 48kbps, but are in .m4a containers, not .aac, but that shouldn't make any difference (By the way aac+ with parametric stereo = eaac+). As I'm about to buy a Desire, your post made me think that maybe the Desire doesn't support eaac+, only aac+. Iphones and ipods only support aac+, so eaac+ files come out in mono and sound rubbish on those devices. HTC's website doesn't confirm if the Desire plays eaac+ files, so I contacted HTC via their website, and they confirmed that the Desire supports these audio formats .wma, .aac, .m4a, .mp3, .mp4 and .wav files And these codecs WAV, WMA, AAC, AAC+, eAAC+, M4A, MP3 and MP4. Therefore if it supports the eaac+ codec, you should get CD quality sound with your eaac+ files at 48kbps. Maybe you should ask HTC about this via their website.
Click to expand...
Click to collapse
That's funny, I contacted HTC support about playing .m4a files and the reply was, and I quote, "You can not play the m4a files by default on your device and you need to search over the Android market for a compatible application with your device to allow you play such files on your device."
I myself haven't been able to playback .m4a files with several music players, including the default HTC one and players downloaded from the market.
Is anyone actually able to play this file type?
SpaceGooner said:
Hi ubik,
All my digital audio files are also eaac+ at 48kbps, but are in .m4a containers, not .aac, but that shouldn't make any difference (By the way aac+ with parametric stereo = eaac+). As I'm about to buy a Desire, your post made me think that maybe the Desire doesn't support eaac+, only aac+. Iphones and ipods only support aac+, so eaac+ files come out in mono and sound rubbish on those devices. HTC's website doesn't confirm if the Desire plays eaac+ files, so I contacted HTC via their website, and they confirmed that the Desire supports these audio formats .wma, .aac, .m4a, .mp3, .mp4 and .wav files And these codecs WAV, WMA, AAC, AAC+, eAAC+, M4A, MP3 and MP4. Therefore if it supports the eaac+ codec, you should get CD quality sound with your eaac+ files at 48kbps. Maybe you should ask HTC about this via their website.
Click to expand...
Click to collapse
What i did is dump my eaac+ converted music library as it sounded bad on my Desire and it was really a lot of music that i did not listen to; being a lot of media files, the music player was very sluggish. I reordered my original mp3s and made a selection of music that i do listen.
I admit, this is not the solution to the problem (using mp3s instead of eaac+ and using less files because the player is sluggish) but it is a great phone overall and who knows what the future brings (Android 2.2 Froyo for example).
I'm not impressed with how google has failed to respond my bug report, but it's hard for me to find faults with this phone, after using the HTC HD2 i'm wondering how i could live with winmo's faults all this time
Hey,
I plan to buy a Desire, but this could be a dealbreaker for me:
Does this occur with AAC+ (e.g. HE-AACv1, without Parametric Stereo) as well? My whole music library is in that format!
It would be really great if somebody could confirm the situation. If you don't have access to any AAC+ files of your own, I uploaded one to drop.io/3q2r8b7/asset/desire-heaac-test-zip in MP3, AAC+ (HE-AAC v1) and eAAC+ (HE-AAC v2).
Thanks!
hi,
all three files sound ok on my desire (i can tell very little difference between them)
maybe you should try giving me something with more base sound (this is where i notices the problem)
you gave me symphonic music which has more of the high notes
ubik said:
hi,
all three files sound ok on my desire (i can tell very little difference between them)
maybe you should try giving me something with more base sound (this is where i notices the problem)
you gave me symphonic music which has more of the high notes
Click to expand...
Click to collapse
Thank you very much for testing.
I've now uploaded another track with more bass in it: drop.io/3q2r8b7/asset/backleg-heaac-test-zip
Hi,
i've tried these three files on my desire and they sound just fine !
can you tell us the exact settings u've used for music encoding? we might be onto something here...
ubik said:
Hi,
i've tried these three files on my desire and they sound just fine !
can you tell us the exact settings u've used for music encoding? we might be onto something here...
Click to expand...
Click to collapse
I've encoded them with the Nero AAC Codec, Version 1.5.4.0, with the command line parameters -br 32000 for the v2 one, and -br 48000 for the v1 (Nero autoselects the appropriate codec for the chosen bitrate that way).
Did you encode your 48kbps files to HE-AAC v2? That could be the cause of your problem; v2 uses Parametric Stereo, which can improve quality for very low bitrates (<32kbps); but for 48kbps you usually get better results with just using HE-AAC v1.
Be sure to use the newest version from www .nero.com/enu/downloads-nerodigital-nero-aac-codec.php, as the change log specifically mentions some fixed incompatibilities with some hardware devices.
my files for the most part are AAC in mp4 or m4a extensions.
done myself with belight and neros AAC encoder. haven't had any problems at all with the default player or meridian
p.s some are about 2-3 years old at least and still play fine. older ones are mp3 though
I had a similar problem with my Desire. Music sounded AWFUL. Lots of clicks and pops on drum sounds. I normalized the mp3s to 90% and it seems to have fixed it.
I know that cyanogenmod supports wma in the music player, I was wondering if anyone knows if that be easy or difficult to port to xdandroid? (or a good way to get wma support)
thanks!
so, made a bit of progress. I looked at a cyanogen rom
I copied over the pvasf related files (file format for wma/wmv files) (in system/etc and system/lib)
and the libomx_wma/wmv decoder files (in system/lib)
and now I'm playing wma files perfectly on my sprint touch pro 2.
though, don't have meta parsing and it seems cyanogen does have support for that.
any chance this can be rolled into an xdandroid build?
WMA is probably the WORST format for media. Statistics have shown that it's even worse than MP3 for acoustic reproduction.
I would advise avoiding that codec like the plague.
arrrghhh said:
WMA is probably the WORST format for media. Statistics have shown that it's even worse than MP3 for acoustic reproduction.
I would advise avoiding that codec like the plague.
Click to expand...
Click to collapse
#1, I've read many things that seem to imply that its not worse than mp3 (and definitely better at low bitrates)
#2, does it matter if I already have a lot of music in WMA format that isn't DRMd so that reencoding it would make things worse (I didn't choose WMA for these tracks, but I dont want to reencode)
#3, why would it be an issue if as I've shown support already exists in android and can be easily included at the loss of a small amount of space (been playing wma all day on my xdandroid sprint touch pro 2)
Eh, no reason it shouldn't be supported in Android, I just know that it's awful - especially at low bitrates.
OGG Vorbis and AAC are the ONLY codecs I would trust at any bitrate that would be considered 'low'...
Let me find the research...
ok, so we agree. I wouldn't use wma for anything I make either, its more of a historical artifact that I have it (and was mostly a windows mobile user before when I collected it, so didn't mind).
I'm not sure how to get metadata working, but not the biggest deal
Is this working yet?
if you follow my steps, it works to play (though doesn't get any info out of the files).
I've stopped doing anything with this as bought an Epic 4G.
I have tons of wma's. This would be great if I could use them with out converting them to MP3's
Hi kwoodyusa, I guess you'll have to tweak your build by hand, following thetoady's directives in post 2.
sad0felix said:
Hi kwoodyusa, I guess you'll have to tweak your build by hand, following thetoady's directives in post 2.
Click to expand...
Click to collapse
what was said, it was pretty easy, I just copied files over and then it just worked.
thetoady said:
what was said, it was pretty easy, I just copied files over and then it just worked.
Click to expand...
Click to collapse
How about posting those files here? Please?
1) download hero rom from
http://wiki.cyanogenmod.com/index.php?title=Latest_Version
2) unzip it.
3) files are where I say they are in post #2 (though for system/lib they are system/lib/libpvasf*
arrrghhh said:
Eh, no reason it shouldn't be supported in Android, I just know that it's awful - especially at low bitrates.
OGG Vorbis and AAC are the ONLY codecs I would trust at any bitrate that would be considered 'low'...
Let me find the research...
Click to expand...
Click to collapse
Thats funny every thing I've ever read says AAC is the worst. and WMA beats MP3. And lets face it OGG is a non-factor.
genaldar said:
Thats funny every thing I've ever read says AAC is the worst. and WMA beats MP3. And lets face it OGG is a non-factor.
Click to expand...
Click to collapse
lol we're talking about the same bitrates right? WMA has a 'lossless' option, so if you're comparing that to MP3 then it's not apples-to-apples anymore...
I mean let's take one file. Compress it to 64kbps. Same song, same bitrate, different formats - which would perform the best? AFAIK, OGG would be #1. Then AAC, then MP3, then WMA last... WMA is a horrible format from what I remember reading, but I can't find the dang report I read - which was years ago, to be honest... But MP3 is 17 years old...
I just got an update today for both my Gnex and N7 and tested it out and it works!!! I am SOO happy now This has been bothering me for so long, but after the update, I put a live album on that is easy to tell and there were NO GAPS!!
I'm just mildly happy. It does work for MP3 and Vorbis files, but not for AAC which I happen to use for my audio collection. Haven't tested any other formats so far.
Definitely a step in the right direction though.
MoosDiagramm said:
I'm just mildly happy. It does work for MP3 and Vorbis files, but not for AAC which I happen to use for my audio collection. Haven't tested any other formats so far.
Definitely a step in the right direction though.
Click to expand...
Click to collapse
Well, I upload my music to google music, and all higher quality music just gets converted to the highest rate MP3 anyway. But that is good to know, thanks.
Listening to it now, love it.
#Galaxy Nexus HSPA+
I think this was done in time to appease people who buy the Nexus 4 and need a solution for music that they can't put on their phone due to the low storage space.
CADude said:
I think this was done in time to appease people who buy the Nexus 4 and need a solution for music that they can't put on their phone due to the low storage space.
Click to expand...
Click to collapse
And gapless playback helps this how?
rand4ll said:
And gapless playback helps this how?
Click to expand...
Click to collapse
People with a ton of music on their computer, especially live albums, tend to love things like gapless playback. If they can't play a lot of music on their phone locally, as is the case on the Nexus 4 with its limited storage which is also needed for apps, photos, video, etc, they will buy another phone or a dedicated mp3 player. However, now that Google music has gapless playback just in time for the sale of the Nexus 4, more people will warm up to the idea of playing their music over the cloud with a Nexus 4 and they will buy it.
This isn't related to cloud storage. Gapless playbck didn't work AT ALL in the Android music app until now, even for files stored on the device.
I've tested a different AAC encoder and the files it produced do play gaplessly.
Apparently, the gapless information stored by Nero AAC (current version 1.5.4.0) isn't supported by the Android music app. It does work an any other device/software player with gapless playback support I tried, so the problem is probably on Google's end. It even works on Apple devices.
Files produced by the Quicktime AAC encoder work fine.
Does it have to be in an album or what? And is the gap less trigger stored in the file itself?
There are some tracks - not live albums - of various artists that have gap less tracks (Green Day's Holiday and Boulevard Of Broken Dreams is an example, Royksopp's Melody A.M. album is another)... So how does it great those tracks in that case? Gap less, or standard?
Cheers. And sent from my mini tractor
You're confusing gapless with crossfade. Crossfade plays the second track before the first ends, merging them into one. Gapless just makes sure that there is no additional gap between the files, the second track is played exactly when the first ends.
As you can see, there is no reason to disable gapless for specific situations. It is never harmful.
I didn't mean cross fade; I know exactly what gapless playback is all I was curious to find out was are there certain rules where gapless playback kicks in, or does it apply on all tracks by default.
(In short - how the app knows when to remove gaps and when to treat it like normal files)
Because it was said that encoding it in AAC using Nero doesn't help, but QuickTime encoding works... So... Kinda confusing me.
sent from my mini tractor
aeoveu said:
I didn't mean cross fade; I know exactly what gapless playback is all I was curious to find out was are there certain rules where gapless playback kicks in, or does it apply on all tracks by default.
(In short - how the app knows when to remove gaps and when to treat it like normal files)
Because it was said that encoding it in AAC using Nero doesn't help, but QuickTime encoding works... So... Kinda confusing me.
sent from my mini tractor
Click to expand...
Click to collapse
Gapless playback under Android doesn't remove any data from the files or depend on any metadata scheme. It just plays the tracks back-to-back so that any silence between tracks is due to that silence being encoded in the files themselves.
The underlying mechanism for gapless playback was added to the Android SDK for Jellybean/4.1. I added it my music app a couple months ago. I was surprised that Google didn't add this into their player at the same time that Jellybean was released.
Oh... So there's no gap or delay when playing the files (or switching from one file to another), right?
I thought it involved using a buffer and cutting to the next file and whatnot.
So its all normal. Thanks.
sent from my mini tractor
Hmm some things are gapless others aren't. Really annoying.
Sent from my Galaxy Nexus using xda premium
aeoveu said:
I didn't mean cross fade; I know exactly what gapless playback is all I was curious to find out was are there certain rules where gapless playback kicks in, or does it apply on all tracks by default.
(In short - how the app knows when to remove gaps and when to treat it like normal files)
Because it was said that encoding it in AAC using Nero doesn't help, but QuickTime encoding works... So... Kinda confusing me.
sent from my mini tractor
Click to expand...
Click to collapse
Ah, now I understand what you mean.
Lossy audio compression (like MP3, AAC, whatever...) adds a bit of silence at the end and beginning of each track. It's part of how lossy audio codecs work.
In order to remove this silence during playback, modern encoding tools write some additional data to the compressed audio file that says "remove x milliseconds at the beginning and y milliseconds at the end" to restore the tracks original length. Players need to look for such data and skip the additional parts accordingly.
If you take an album that has silence at the end of tracks on the CD and convert it to MP3/AAC/whatever, it will add some more silence to it. A player that supports gaplesss playback will remove this additional silence, but keep the original silence that was on the CD.
AFAIK, there is no official standard on how to write this gapless information to the compressed audio file, so different codecs do it in a different way and developers of audio players must take a look at files produced by popular codecs to understand how each codec handles it and implement support for it.
Android 4.2 along with the latest version of the music app supports the format used by Lame MP3, Vorbis and Quicktime AAC (and probably others, these are just the ones I tested). AAC files produced by Nero AAC, which do have gapless data and work fine on other players, are not supported at the moment.
Ahhh so that's how it works. I've been a long time winamp user and use the silence remover capability in there...which does it on the fly! Never tried it with portable devices...but I think I may give it a shot this time.
Cheers!
sent from my mini tractor
I enjoy the cross-fade feature in PowerAmp, would be cool to see that implemented one day too.
Cross fading in those apps are basic i.e. they only work on a constant. Not sure if any of you guys know about this plugin for Winamp called Sqr Advanced Cross fader... it works based on the silence level of the currently paying song, and works wonderfully in most cases.
Then there are times when I end up cross fading songs myself in Winamp
sent from my mini tractor
MoosDiagramm said:
Ah, now I understand what you mean.
Lossy audio compression (like MP3, AAC, whatever...) adds a bit of silence at the end and beginning of each track. It's part of how lossy audio codecs work.
In order to remove this silence during playback, modern encoding tools write some additional data to the compressed audio file that says "remove x milliseconds at the beginning and y milliseconds at the end" to restore the tracks original length. Players need to look for such data and skip the additional parts accordingly.
If you take an album that has silence at the end of tracks on the CD and convert it to MP3/AAC/whatever, it will add some more silence to it. A player that supports gaplesss playback will remove this additional silence, but keep the original silence that was on the CD.
AFAIK, there is no official standard on how to write this gapless information to the compressed audio file, so different codecs do it in a different way and developers of audio players must take a look at files produced by popular codecs to understand how each codec handles it and implement support for it.
Android 4.2 along with the latest version of the music app supports the format used by Lame MP3, Vorbis and Quicktime AAC (and probably others, these are just the ones I tested). AAC files produced by Nero AAC, which do have gapless data and work fine on other players, are not supported at the moment.
Click to expand...
Click to collapse
Very nice explanation, thank you!
So I went ahead and listened to some of my lossy mixes, still .1 second gaps between songs... it hurts wish the player could analyze the spectrum and fix this... guess nobody at google listens to trance
On the plus side, I ran a local mix that was in FLAC, and it was truly gapless! Too bad that it every 30 seconds theres a .5 second pause.....
I remember not having these problems 2004, why do I have them in 2012
- sent from TW galaxy s3 4.1.1
Just use PowerAmp, you'll need to pay a few Euro's, but that player is just great! Gapless playback? Like that is a novelty! PowerAmp had Gapless playback 2 years ago already! Besides that, PowerAmp has a great Equalizer and a big deal of other settings to match it to your liking...
This is kind of old news, but I finally got around to posting on this. I've done some searching, and haven't found anything on it.
When Samsung sent firmware including Android 2.6, they apparently changed a mixer setting such that MIDI sounds are louder, and now many MIDI files are distorted on playback. It's STILL messed up, after several further Samsung-push firmware downloads.
I use Mort Player Music to play my music, which is mostly a mix of MP3 and MIDI files, with some other formats. The problem also shows up with the Android native player as well as Goolle Play Music.
Some incomplete info on media access from Java:
http://developer.samsung.com/java/technical-docs/Audio-Media-Controls
That's very geeky for me, and appears to be incomplete, anyway.
Does anyone have any idea how to adjust the MIDI-specific level (probably a setting relating software synthesizer output to mixer input?)