dir buffer full again

[batko]

Hi!

Sorry to bring it up again, but I can't find an answer to my problem in any of the previous posts.

I'm using a 070527 build on ipod video 80GB. Both my limits (files in dir & playlist) are set to maximum, but I get DIR BUFFER FULL message in MOST PLAYED TRACKS and RECENTLY PLAYED TRACKS.

I tried everything (even installed today's build - which used up battery like crazy), but after importing my database modifications I got the same message again and again.

Setting the limits to higher numbers used to help, but as I've said - I've reached the end of the scale...

Any chance to set the limits even higher in my current build? And what should they be anyway, if the total number of entries in my database exceeds 18,000?

thanks

[Llorean]

That's a build over half a year old. Even if you tried today's build, then went back to it, if you're using it, you shouldn't be asking for help or reporting problems here.

You can set the limits as high as you'd like if you compile a custom build for yourself.

[bzavala]

I tried everything (even installed today's build - which used up battery like crazy), but after importing my database modifications I got the same message again and again.

batko:

how long did it take to import the database modifications? I'm also on the latest build (from last night) and Rockbox just hangs with the "Loading" message. I'm starting to think that the database_changelog.txt file might be corrupted?

By the way.. I have some customized database queries where I also get the dif buffer full, no matter how large I set it up, I also get it. And I only have less than 7000 entries on my database...

Ben

[batko]

It took quite some time - 15 to 20 minutes - almost as long as the database initialize process itself. But I suppose it depends on the number of entries and specific database fields (different tags, user ratings...)

I really hate this dirbufferfull business, as I use the DB all the time... Unfortunately can't get any solution.

[pondlife]

How is your music arranged?  I've got nearly 20000 tracks on my H380 and am not seeing this message.

FWIW, I have set my limits to:
Max Files In Dir Browser = 1000  (it could probably be much smaller, but for a bug where list acceleration resets every 1000 entries)
Max Files In Playlist = 20000

My music is all stored as \artist\album.

pondlife

[batko]

OK, I found a solution.

I simply set the MAX FILES IN DIR BROWSER limit to 20,000 instead of 10,000.

Of course this wasn't possible INSIDE rockbox system settings, as the highest number available is only 10,000. Instead I changed the setting in config.cfg file while connected to the PC.

MOST PLAYED and RECENTLY PLAYED are up and running again!

I'm affraid I'll have to change the limit each time the number of actually played tracks exceeds the setting. Wander what the cause on battery life might be... say, after couple of years (I listen to 20,000 songs a year).

[Llorean]

If you're listening to 20,000 songs a year, that's approximately four hours of un-repeated music every day. Assuming normal human wakefulness that's an approximate maximum of each song being played, on average, 4 times a year. Why do you need the "Most played" and "Recently Played" lists if you almost never repeat songs?

[PaulJam]

I'm affraid I'll have to change the limit each time the number of actually played tracks exceeds the setting. Wander what the cause on battery life might be... say, after couple of years (I listen to 20,000 songs a year).

Hi,

i think the database only stores when a song was played last, and not the complete history, so even if a song was played twice it'll only appear once in that list.

[bzavala]

My "directory buffer is full" issue is also fixed. With playing with those 2 options,  I left them at:

Max Files in Dir Browser = 2500
Max Playist Size = 2000

Anything lower than those 2 brings the message.

I was particularly getting the message on one of my custom queries, the least 100 played songs:

%format "f_least_played_100" "%2d|%3d %s (%s) " playcount autoscore title artist %limit = "100"
"English Least 100" -> title = "f_least_played_100" ? composer ~ "english"

I guess the query used to break because it was bringing all the songs, then sorting by playcount and then filtering.

I use this one all the time because I want to rotate my songs and bring back the ones with less playcounts.