TagCache hanging

[Paroxysm]

I've browsed thru pages and pages of threads but can't find any solution to the problem I have.

I can't seem to build my ID3 database. Whenever I go to TagCache - Initialize, it will say "updating in background" and the player will then HANG. I've tried tonnes of times and it's hung almost all the time. I went to debug and view TagCache info and it says initialising done but database is only 1% built. Leaving the player on doesn't seem to help and i can't view my songs via ID3 tags.. Anyone have any idea how to rectify this?

[Llorean]

If the player's hanging, how did you get into the debug menu?

Also, what format is your music in?

[Paroxysm]

I have to restart it (Menu + Select) then i'd go back to normal.

Most of my files are .mp3 but some are .wav

[dunno]

it could be a mp3 file which has corrupt headers, see bug report below for further details.

http://www.rockbox.org/tracker/task/5966

[bazmonkey]

I'm having this problem with the most recent build, too.

Even if it was a corrupt header, previous builds haven't had this problem.  I initially switched after the new scheduling code to stop skipping while scrolling through playlists, and switched to the current CVS build in an attempt to fix tagcache incorrectly ordering songs within albums.

I get "I40:PDIR1FULL at 0x000001".

[Llorean]

Okay, a specific "error" message is quite different from what he described. I don't think you're having the same problem.
 
That error message means something specific. It's already been brought up, by you, in another thread, where you received a suggestion that you never responded to.

Please, don't say you're having the same problem is you have other symptoms (for example, the error message) that the original poster has not yet described. You may ask "Does yours say PDIR1FULL" and then if they say yes, note that you and he have the exact same symptoms, so long as you both have ONLY those symptoms, but saying that you have the same problem when he has not yet confirmed that the symptoms match only muddies up the water.

[bazmonkey]

Sorry to cause any confusion.  I assumed that the original poster had his backlight off when the error occured, and couldn't read the error message.  Other than that, I believe it is the same problem.  I thought I would be making things more complicated by regarding it as a separate issue.  My mistake.

I did respond to the suggestion given... before reading this.

[Llorean]

Your response here is timestamped at  04:22:09. Your response there is timestamped at 4:32:15. It is evident that you responded here first. The response that you replied to at 4:32:15 was made at 4:05:49, 17 minutes before your response here, so there was plenty of time for you to reply to it. So no, you did not "respond to the suggestion given... before reading this". You in fact responded there 10 minutes AFTER responding here. Please, do not lie to me.

Also, do not *assume* that someone couldn't see their screen. As I said, *ask* if they got the same error message as you first. Assuming something happened can easily lead to misdiagnosis of the problem, and it doesn't harm *anything* to actually ask them more about their problem.

I don't see how making a *guess* can in any way seem like the best plan compared to actually getting useful information.

[bazmonkey]

Your response here is timestamped at  04:22:09. Your response there is timestamped at 4:32:15. It is evident that you responded here first.

Whoa, whoa.  I did respond there first.  I'm not trying to pick a fight, really, and I'm sorry for any trouble I caused thinking that we had the same problem, but I *did* followup with the suggestion given in the other thread before I read and responded to your thread here.

I wasn't trying to say that I posted http://forums.rockbox.org/index.php?topic=6523.msg50912#msg50912 before http://forums.rockbox.org/index.php?topic=6556.msg50910#msg50910.

I was saying that I posted http://forums.rockbox.org/index.php?topic=6523.msg50912#msg50912 before I read http://forums.rockbox.org/index.php?topic=6556.msg50911#msg50911 and wrote my previous post.  I was saying that I did already follow the suggestion given to me before you suggested that I didn't.  Yes, the post you made here was a few minutes before my followup to the suggestion given to me in the other thread.  I hadn't read your post yet.  That's all I was saying.

Please, do not imply that I am a liar.

Again, I'm really not trying to start trouble or be a moron user dancing around the forums, ignoring what I'm being told.  This was all a misunderstanding; I apologized, I did NOT lie, and I will be much more careful about how I word my inquiries on this board.

[Llorean]

Sorry. It's true, you didn't lie, but your explanation of what you said then makes it entirely irrelevant to my point.

But the thing is, the "this" you're referring to *now* is the post where I told you that you shouldn't have posted your PRIOR post before responding. The issue isn't posts 50912 and 50911 but 50910 and 50907.

You should've responded to http://forums.rockbox.org/index.php?topic=6523.msg50907#msg50907 before posting http://forums.rockbox.org/index.php?topic=6556.msg50910#msg50910 is what I said, and you then said that you'd responded there before reading here. It's irrelevant that you responded there BEFORE reading my post saying "You should respond there" since my topic was "You posted here AFTER a response there was already waiting for you."


Anyway, the point I'm getting across is this:
1) Don't bring up your problem on multiple threads, in general.
2) Check for a response to a previous asking of a question BEFORE posting the question again, always. You shouldn't be asking again in general, but if you feel it's necessary, check that the old one hasn't been responded to. The timestamps show that if you'd done that this time, you'd have found the response.
3) Before saying you have the same problem as someone else, take steps to verify that the problem is the same, rather than assuming that someone else has left information out.

[Didgeridoohan]

You guys are going off topic, and making me confused... It's to late at night were I am for that kind of stuff.

Edit: Language...