HTC Desire eaac+ decoding - problem with android decoder? - Desire General

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.

Related

Is there solution to the problem with films of HTC HD?

Ultimately, what is the best video player for the HTC HD now?
Problem as the phone was out that the core player play good films, but does not support all audio codecs (it is a film without sound) and does not support subtitles.
Free version of TCPMP do play all movies whit sound and subtitles, but movies go very slowly rather than smooth.
So my question is, since my information is from 4-5 months before, are there any new development on the subject. Is there a player who goes smoothly converted video and subtitles supported?
If there is such a miracle, I'll be happy to drop a link?
What is the latest version of core player and are solved the problems there?
Latest version was 1.3 I reckon. They plan on introducing AC3 audio codec support which is the most widely used audio codec for ripped movies etc in a 1.5.x version.
But yeah, Coreplayer is at the moment still the most top notch player imo.
This is a list of the supported audio and video codecs:
Audio : MP3, MP2, AAC, MKA, WMA, Midi*, WAV, OGG, Speex, WAVPACK, TTA, FLAC, MPC, AMR, ADPCM, ALaw, MuLaw, G.729, GSM
Video: H.264 (AVC), AVCHD, MKV, MPEG-1, MPEG-4 part 2 (ASP), DivX, XviD, WMV*, Theora*, Dirac*, MJPEG, MSVIDEO1
Another Coreplayer user here!
Works great for me.
scbg said:
Ultimately, what is the best video player for the HTC HD now?
Problem as the phone was out that the core player play good films, but does not support all audio codecs (it is a film without sound) and does not support subtitles.
Free version of TCPMP do play all movies whit sound and subtitles, but movies go very slowly rather than smooth.
So my question is, since my information is from 4-5 months before, are there any new development on the subject. Is there a player who goes smoothly converted video and subtitles supported?
If there is such a miracle, I'll be happy to drop a link?
What is the latest version of core player and are solved the problems there?
Click to expand...
Click to collapse
It all depends how you encode the video files... I can play a whole movie without any lag.
yes, but I want to play unconverted video..
The main reason why I use coreplayer is because it can play unconverted video, I have too much video to even be coverted and it's generally just too much of a hassle to me. You can't watch a 4.7 gig dvd unconverted if that's what you mean but dvd ripped avi filea from like 700 mb play without any lag at all using coreplayer.

WMA Playback

Got my desire today. Been playing around and noticed that my WMA files are not showing up. I'm WM veteran but a complete novice with Android.
According to HTC's page on the desire
http://www.htc.com/www/product/desire/specification.html
it should play WMA files.
Can someone please assist me here? All my music is encoded as WMA 10 Pro and I'd like to be able to listen to it.
BUMP!
Still can't find a solution to this.
I am also looking for any solution how to play my WMA Lossless audio files. Unfortunatelly I have all my music library in this format. I am hoping that there will be soon native support for this audio format.
at least you using a lossless codec. you could just reencode as ogg files. I'm using lossy wma so I think I might end up having to convert to lossless then reconvert to a lossy code like ogg.
Sent from my HTC Desire using Tapatalk

Sound Enhancer only works with certain formats

I had been encoding all my music in wma 10 pro as it provided the best integrity of the lossy formats supported by wp7. Not everything was encoded in the same format, though. HTC Sound Enhancer didn't seem to be working and I thought it was a hardware issue because it was universal with every rom I used. Then, I noticed that sometimes the enhancement would work with certain songs. I took a look at them and realized it was the wma 10's that didn't work with it. I transcoded them to m4a's and now they work with the enhancement.
I just thought it was an interesting find and thought I'd share it.
I think I should clarify that by it not working, I don't mean it would crash; there was simply no difference in the sound between settings. Everything was the default flat sound.

AAC+ playback issue

Hi,
I recently bought a Galaxy W (Middle east), The phone is not able to play aac+ or eaac+ files properly. 1st thing is it wont even recognise the tags, if i use media fixer then the phone will recognize the tags, but the quality is very low.. ie the phone is not recognizing the file as aac+ or eaac+, its recognizing as aac, so aac+ at 48 or 64kbps is playing as 48/64kbps normal aac. If anyone is able to play eaac+ or aac+v2 file in this phone with audio effects in default player, please mention your firmware version here.. my firmware version is JPLM7_ojplm4
nobody in XDA has knowledge about this! ?
Anyone? no one here use HE-AAC files? Is there any workaround or fix. Is anyone able to play 64kbps encoded HE-AAC music files in this phone with quality? 64kbps HE-AAC is supposed to give 192kbps Mp3 music quality.. i've been using HE-AAC on my xperia and previous smartphone.. however HE-AAC files are not at all working properly with samsung phone, its not androids fault as my xperia can play them. However samsung wave 3 and galaxy w is unable to decode them properly, they are decoding HE-AAC as LC-AAC
have u tried using another music player from playstore ?
mosta_9741 said:
have u tried using another music player from playstore ?
Click to expand...
Click to collapse
Players with its own codecs will play the file.. ie players like jetaudio, but players (ie MIUI or doubletwist) which use decoder that built in stockROM will not be able to decode HE-AAC files properly, they decode them as LC-AAC. Is there any fix available for the inbuilt decoder in stock ROM. I am using Jetaudiopro now to play tracks. I absolutely hate MP3 files, AAC audio is much cleaner and Opus codec is much better. Sadly, the only player that support Opus playback is rockbox for android.
i guess ull have to contact any dev thats interested in audio codecs so he tries to implement ur desired codec into a rom (or figure out a mod that can b applied in any desired rom )
mosta_9741 said:
i guess ull have to contact any dev thats interested in audio codecs so he tries to implement ur desired codec into a rom (or figure out a mod that can b applied in any desired rom )
Click to expand...
Click to collapse
i agree

New Update on Google Music Now Supports Gapless Playback!!!!

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...

Categories

Resources