FLAC problem on H120

[lufc28]

Hi i have just installed the latest build of rockbox. Everything seems great bar my flac files constantly pausing for 1 second as if its buffering the content.  Is this a known problem? Is there anything i can do to stop this?

All other codecs work ok as far as im aware just FLAC.

[Llorean]

How often do you mean by "constantly?"

[XavierGr]

You will have to give more details in order to help you.

Do you mean that playback stops for 1 second every so and then?
Do you use any plugin when this occurs? This can appear if you quick scroll for too long in a big directory or a playlist. Though it is very rare and due to be fixed.

[lufc28]

It plays for say 5 seconds then 1 second pause(well no sound) then 5 seconds play etc...
This also happends with m4a files in the same way.

The FLAC files are approximatly 60 mins long each.

I dont use any plug in, im not scroling through anything either just playing the file.

[XavierGr]

This is very strange!!!

FLAC is the most optimized codec in Rockbox. It shouldn't skip even in heavy usage.
I assume that you are running the latest official build?

[Llorean]

With the latest official build, see if you can go into the Audio Thread screen in the Debug menu, and describe to us roughly what you see happening there when it skips.

[Assimalyst]

With the latest official build, see if you can go into the Audio Thread screen in the Debug menu, and describe to us roughly what you see happening there when it skips.

Info --> Debug --> View Audio Thread 

[Cousin Patty]

I am having the same problem. The HD activity light comes on for a second and the music stops for a second then resumes. Sometimes it will skip to the next song.

I had to go back to the 7-31-06 build to fix the problem. Seems like it would a pretty easy thing to fix considering it happens from one version to the next...

[Llorean]

Please, never say "Seems like it would be a pretty easy thing to fix" unless you actually *know* how easy it is to fix. Sometimes changes have unintended consequences, and what you changed isn't the actual code that causes the new problem.

Regardless, you're responding saying that a 7-31 build doesn't do it, to a thread reporting a problem from two weeks prior. You're experiencing a different bug. One that should already be fixed if you tried moving to a newer CVS instead of going back.

[Cousin Patty]

Sorry about my comment. You're right.

This sounds like the same problem I was having though. I had an old version of the firmware from months and months ago. I updated to the newest version and encountered this problem, then went back to the version from 7-31-06 and the problem stopped.

[Llorean]

What version is "The newest"? Newest as of when?

It's really essential for you to actually post what specific build you're using, for us to have a good idea what you're working with.

[Cousin Patty]

the newest being yesterdays build. Im at work right now so I havent had a chance to try todays build.

[Llorean]

So, it was a daily or CVS? If CVS, at what point during the day?

As I said, the bug SHOULD'VE been fixed if you moved to a newer build than the daily for yesterday, as it was fixed after the daily was made, but the fix was available in newer CVS builds, ones that were available BEFORE you made that post.

[Cousin Patty]

Sort of confusing. What I got yesterday was not a bleeding edge build. I went to the download page and got the latest build for yesterday. You're saying that I need to get the bleeding edge build for today or what?

[Llorean]

Today's daily should work. But if you have a bug, you should always download the latest bleeding edge and see if it's gone, before reporting it.