Support and General Use > Audio Playback, Database and Playlists
Data Abort at 0004ECCC (0)
erdnuesse:
[Update:]
So, finally i killed the db again, means deleted the according files, and initialized once again. Seems like the db should only be initialized once and, after that, only should be updated. Oops, i guess that's the kind of stuff to be in a manual (which i did not read, because rockbox is so good, it's just self explanatory :D - shame on me...) After that I re-enabled the "load to ram" function, since I don't bother the slightly longer startup, but can't stand the seconds while browsing my database.
Right now, it's all working.
After all, the "load to ram" was a test to ensure that this is not the root of the problem. I guess, it would have worked without changing it. I could downgrade to stable to reproduce the error and give more detailled information, but deleting the db-files, run an upgrade, and re-initialize from zero should do it just fine.
But now, there's another thing, about which I am not sure that it results from the same problem:
I can now not play directly the files in my folder structure. But - if I go for the files I want to play in the database - I can play them. As far as I know by now I have the according files only copied into my folders directly, means not via syncing with any Itunes-like client (Itunes itself, mediamonkey, etc.) So I wondered first why these files should be in th db in the first place. On the one hand it's a strange behaviour, on the other hand, I can play them via the db. (But I admit that I do not know whether rockbox adds the files, which lie under any custom folder, automatically to its own database)
[tbc.]
--
"because I can."
Chronon:
The database might be finding files that were added in MTP mode. These won't be located in the normal /Music directory.
I don't use the database much but I tried to replicate this: I installed 3.8 on my e280 v1 and initialized the database with no problem (tried it both with and without "Load to RAM" enabled). My database was not initialized prior to this.
PickupBetty:
I got a similar Data abort, at 0004ECB8, on my Ipod Photo 4th Gen. I deleted the database files but left Rockbox Stable as is. I rebooted, then disabled "Load database to RAM." Rockbox regenerated the database and seemed to play fine.
However, I couldn't play from the File menu. So I reinstalled the current build, and got the Data abort at 0004ECCC (O). Installed the current build, and all seems happy again.
I should note that I had edited the metadata on the two files I'd loaded before the Data abort, which may have funked the Ipod out. I deleted them before installing the current build. After installation, I re-loaded them and generated a database. No problems!
I've loaded the same edited files on my Sansa e200, with no problems whatsoever.
erdnuesse:
Well, in conclusion to everything we've tried, I'd say the "load to RAM" Option was only for narrowing th source of the error, but has nothing to do with it.
My solution: If you haven't got the current release but the 3.8 stable on an Ipod Photo 4. gen. you HAVE TO get the current release in order to fix the error, but first, you have to delete the database.
Having edited metadata in the files was no part of my scenario, so I would exclude that possibility.
However, I know now how to fix it for me, but if you (developers) want to trace the error/bug down, you could tell us what to do, maybe we can help. (maybe starting with the debug mode)
[Edit:]
I was wondering whether I should open a bug report for 3.8 stable, even whe the issue seems fixed in the current release.
Suggestions?
AlexP:
If these issues are fixed in current, then we can do an 3.8.1 with just the fixes. I'll try to have a look at the status this weekend.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version