Support and General Use > Hardware

Sansa e200 v1: HE-AAC/AAC+ playback

(1/2) > >>

vinnie97:
I had been out of the Rockbox loop for a while but upon checking in the last few days and updating to the latest version, I see that they've managed to incorporate an open source decoder for this excellent-sounding format.  The one caveat I've experienced with his hardware/codec combination is interrupted playback, making it unlistenable.  I tried disabling features in the options but couldn't get smooth playback.  Is this just a CPU limitation or will further decoder tuning garner any possibility of smooth playback in the near future?  I fear it may be due to the former and I may need to get a Rockbox supported player with a faster CPU if I want the feature.

EDIT:  And NOW I found this thread:  http://forums.rockbox.org/index.php?topic=21991.0

It confirms my suspicion that the v1 clock is to blame.  Blast!

saratoga:

--- Quote from: vinnie97 on March 12, 2010, 09:12:30 PM ---The one caveat I've experienced with his hardware/codec combination is interrupted playback, making it unlistenable.  I tried disabling features in the options but couldn't get smooth playback.  Is this just a CPU limitation or will further decoder tuning garner any possibility of smooth playback in the near future? 

--- End quote ---

AAC-HE is one of the slowest formats in widespread use, but it should eventually be possible to decode it on the e200v1.  We've been slowly improving the AAC decoder, but not the HE part yet. 

vinnie97:
^That's great news, thanks!  So there is room for further fine-tuning in the HE dept (I thought it was added relatively recently).  Do you have a ballpark estimated timeline on when the code will be efficient enough to run smoothly on this device?  It makes sense that it's the most resource-intensive, as it also produces the greatest transparency around 64kbps (or at least that was the case a few years ago and Vorbis and WMAPro were the only actively developed formats that came close).

Llorean:
Timelines are impossible. It's entirely possible nobody will ever bother working on it. It's entirely possible someone will show up with a patch 5 minutes from now that they'd been working on recently.

It's a volunteer effort. Please, just don't ask for estimates on when things might be done.

saratoga:

--- Quote from: vinnie97 on March 13, 2010, 03:56:26 AM ---^That's great news, thanks!  So there is room for further fine-tuning in the HE dept (I thought it was added relatively recently).  Do you have a ballpark estimated timeline on when the code will be efficient enough to run smoothly on this device? 

--- End quote ---

Probably not too long after someone takes an interest in working on it.

Navigation

[0] Message Index

[#] Next page

Go to full version