I think this has to do with the aac format itself. It takes
considerably more processing power to decode AAC files than it does
for mp3's. What's probably happening is that the Ipod is still trying
to decode the aac file while loading and speaking the voice file.
What happens if you stop playback of the aac file and then enter the menus?

At 04:56 AM 8/23/2006, you wrote:
>Hi,
>
>I just tried the latest CVS and one of the updated voice files on my
>Nano. The iPod doesn't crash when I go into the file browser or
>context menu while playing an AAC file, which is certainly an improvement.
>
>However, the response time is very slow while an AAC file is
>playing. I tried going into the context menu, increasing the pitch
>significantly (to about 1.5 times normal, I think) and returning to
>the WPS, then going back to the context menu to return the pitch to
>normal. The first time I went into the context menu, it might take
>30 seconds to get speech. Once I got speech, it worked reasonably
>well and I was able to increase the pitch. After I increased the
>pitch, however, I was sometimes unable to get it back to normal
>without turning off the iPod. The menu started talking much more
>quickly than the first time I entered the context menu, but speech
>was more sluggish as I scrolled through the menu. It was often
>chopped off so that I couldn't hear the end of the prompt. There
>was also a lag of several seconds, I think, between when I scrolled
>to a new choice and that choice was spoken. And in one file, music
>playback stopped every 10 seconds or so even when I was in the WPS
>instead of the context menu, as long as the pitch was at 1.5 times normal.
>
>My battery is low at the moment - maybe that has something to do
>with this. I will charge it overnight and see if there's a
>difference tomorrow. But responsiveness was much better with MP3
>files, so I doubt the battery is the main problem.
>
>Sorry to be the bearer bad news.
>
>Regards,
>Anna
Received on 2006-08-23