USB Database corrupt

Don’t Delete the Music Folder, delete the other files in the folder and start over again in the Engine Prime Software on your computer.

But backup your music somewhere else. Always keep things in two different places. You should always have a copy of your USB somewhere. A mirror on a second USB or on your computer.

Alright, so when i delete everything except music folder the engine prime software creates the same files again. And it no longer says the usb is corrupted, but it still doesent show up any playlist or any music at all. I guess thats because i deleted the file that organizes everything. Everything else works its just like a wiped out usb even tho my music is still in the music folder… hmmm

I guess you didn’t read or answered my options for you. Now you have no database anymore and you’ll need to rebuild your entire Engine Prime collection including beat grids, cue points, loops etc.

Sorry mate, i did read it, and i also copied the whole usb to another folder, i didnt even touch the original usb. What do you mean repair the database? I looked for the software you talked about but didnt find anything, i guess i will give it another look.

The music is still there and i tried to import a few songs to the engine prime and the cues were gone. Also i tried to just copy the files to another usb, and the usb is readable for about 2 secs, if im fast i can click playlists and view them but the software instantly crashes.

The options i see for myself is basically just importing all the music to my engine prime again and making new playlists and music folders, which really ■■■■■ because the software is so ■■■■ at organizing at this point and i will lose all my cuepoints. Or ill just do the organizing in serato and then import the folders to engine prime. Thanks for trying to help me

In essence you have nothing but a corrupt database and not a corrupt USB stick.

Try this, absolutely not supported, option:

Then at least you have something more than nothing and you can fix whatever mishaps would be left if repair doesn’t fix them all.

After that. Backup 3-2-1.

The last step got me a error message. I think i have tried everything now. but it looks like its the m.db file that is damaged, idk if thats where the quepoints are stored but if the quepoints are stored somewhere else maybe i can use those databases for my new usb.

Mmm okay. M.db contains all the meta data, crates, playlist etc etc.

P.db contains the performance data like waveforms etc.

Ahhh thats unfortunate… Thanks for trying to help me and let me know if you find a fix :slight_smile:

1 Like

Could you upload the m.db and DM me a share link?

1 Like

Yeah for sure. I’ll do that right away.

Hi,

The main file are m.db The ‘m’ database is the main location for storing metadata about music/audio tracks. The ‘p’ database is the main location for persisting analysed performance information about tracks, such as cues, beat grids, and waveforms.

For a details of all database and table :

https://www.mixxx.org/wiki/doku.php/engine_library_format

1 Like

I tried your sqlite method, but i got an error when importing the sql file. Do you think i’ll be able to recover cuepoints if i make a new library and copy my old P file?

what is the size of your file p.db?

I can try to repair manually the database next week if you upload the file

Its just above 0,3gb. But its the m.db file that is corrupted it seems like, the m file is 0,04gb.

Maybe there should be a single email address or ftp upload site given by denon or any other database specialist for all of us to send our corrupt databases to.

Maybe there’s a common factor as to why the engine prime database seems more fragile than a glass egg and as volatile as some “do not shake” liquid explosive, on a washing machine on its final spin cycle.

Like is engine prime leaving records open after writing? Is the last hot cue in the last file in a database most commonly going to corrupt? Is the corruption more likely to happen if a hot cue is deleted (shift + hot cue pad)? Is the corruption more likely (or only) on the remotely connected networked player not the player with the hard drive plugged in? Does corruption happen when the mixer is doing something in particular (as the mixer is the network hub for separate primes)? Does searching for songs confuse the writing back to the database? Does writing to the played history file foul up the database writing to the individual music files? A file is only considered “played” if it’s been playing for 30 seconds - so if a different database action is performed in this 30 seconds, does that writing to the played history file get askewed? We often DJ through midnight… from one day into another… so if database record is opened on 16th May but isn’t closed until 17th May, does that confuse things? What if we Start to play a track at 15 secs before midnight and the played history 30 seconds then happens 15 seconds into a totally different day… does that corrupt things? Like this stupid muscle memory thing, where the cue point changes to being the end of the track because we pressed cue to stop the song playing when we’ve mixed out of it, somehow set the cue point to a negative value, when the databse only wants absolute positive values?

Maybe the debug route is to have a whole list of database actions with on/off switches in the preset menus and switch all of them off bar one (at a time), use the players at home (we’re all at home now right) and see who gets a corrupt database when they’ve only got the “erase deleted got cues” option switches on etc, to narrow down the database event that’s causing so much corruption.

Indeed, given the capricious state of the database,

Denon should schedule a test each time it starts, a single command line “PRAGMA INTEGRITY_CHECK”.

Test OK: Nothing to do.

Test Not OK: Restoring the backup.

When switching off, test “PRAGMA INTEGRITY_CHECK”:

Test OK => Automatic backup.

1 Like

Well Graham.O fixed it, i dont know how but you saved me a lot of time, thank you! I also wanna thank everybody else who took their time to try and help me.

2 Likes

Nice one @Graham.O.

There were a lot of rows/indexes missing or not? Fix was a manual task? I’m no DBA, so thanks for the assist.