@Mufasa, Are all of the following records your top most playlists?
sqlite3 m.db "Select id, title from Playlist where parentListId =0 order by nextListId;"
431|THEMES
1|2024 SMARTS LXC
2|REGGAE FEST PARTY SET
3|LIBRARY 2425
4|AFROBEATZ
7|NuDiscoX
19|Old Quick Hits Crate - AfroParty
25|REGGAE FEST EP
35|RNB HITS
57|RNB
69|RNB MAIN
70|FLXGRD
88|CHARTS, RADIO, TOP40
91|SMART CRATES
92|#KAYTRA FUTURERNB
93|2024 PARTY
94|2023 TOP40
95|2022 RNB BANGERS
96|FUNK DISCO GIG
101|AMAPIANO AFRO
117|AFROBEATS HITS
118|DALYS GARDEN
162|Mini Sets
163|SCRATCH SAMPLES
164|Disco and Funk
165|90s 00s RNB THROWBACK PARTY
172|BANGERS
194|BAR GIGS
232|BOOMBAP @ JOHN DALYS
242|DANCEHALL REGGAE
243|DANCEHALL_RIDDIMS
248|DJ EFFECTS & TOOLS
271|FESTIVAL
285|HEAVY HITTERS PEAK HOUR QUICK FIRE
290|HIPHOP URBAN CLASSICS
315|Hip Hop
324|HOUSE
335|LATIN PARTY 2020
336|lovers rock
337|Master Chic
338|MC BATTLE BEATS
339|Nu Disco
353|Oldies
367|SAMPLER CRATES
368|SKA BANGERS
369|Spanish Hits
383|STUDIO 54 DISCO HITS
388|Transitions
396|Wedding Events
397|70s ROLLER DISCO
406|WEDDINGS
416|MOTOWN STUFF
422|PRIVATE PARTIES SET
Also, I wrote some utilities to look at my own database to detect orphan records. All that I can find in what you shared thus far is orphan AlbumArt records in m.db
This is because all of the source databases are structurally sound. Queries to all tables net data and pragma integrity_check returns 0 all the time.
In my database instance, i’m noticing playlists who have a parentListId = 0 but should have been deleted. I’m wondering if this is what is tripping up Engine DJ. From what i can tell, parentListId = 0 means it’s a “root” playlist.
Until now no solution, no reaction from Denon? If i use 4.0 i got the Corrut Database and if i switch back to 3.4 there is no sync back from the Controller to Engine (After editing Cues, Grids etc.)……
Even though we’ve not heard anything publicly, they are aware of the problem and working on a fix. Quite a few of us in the community that are trying to figure out what is wrong.
This is not a solution but a temporary workaround. I am having the corrupt library (on export) problem since updating to 4.0. Went back to 3.4.0 and the problem remains.
So working under 4.0, I am exporting two of my 3 main playlists (with lots of sub directories in them), into my SD Card. This is working fine. No Corrupt Library message, and all the music files and directories from those two main playlists are exported to the SD Card. Did it twice with no issues.
Next, insert another USB drive and export just the remaining playlist to this other drive. This worked fine, twice. So I have all my music and playlists but on two different drives. For some reason the full export to a single drive keeps failing, the Corrupted Library message pops up, and although the music is copied, there are no playlists in it.
Needless to say, both drives have more than double the required space for a full export, so insufficient space is not the issue.
No problem, hope it works for you. I dunno why it happens like that. Here is a thought that I haven’t tried: create a PHANTOM PLAYLIST that you don’t need. Then try to export all of the other playlists (actually all of your other playlists) leaving out the phony playlist - all to a single drive. This would be equivalent to just exporting everything - like we are unable to do now, but tricking the program into thinking that this is just a PARTIAL export. Sounds crazy, but so is this weird issue!
A little update. Creating a phantom playlist and copying just the real ones in the Sync Manager has failed. The idea was being able to click on selected playlists individually without having the full export modality kick in. I have no rationale behind this approach, but only to continue investing hours and hours each day trying to resolve this in any way possible. So it did fail almost at the end of the run. This time, not only the music was copied to the drive, but playlists as well. They were actually visible and clickable in Engine DJ, but they were all empty. Sadly, my unscientific theory about doing manual exports from the sync manager was wrong. Next.
Now I am trying another approach, which is foregoing the Sync Manager altogether, and dragging individual playlists within the DRIVES column. From my main drive, into my USB’s collection. I have successfully exported all of my playlists to my SD card this way. After many days trying to work things out, this method is now a viable workaround. The problem is still there, but copying manually instead of using the Sync Manager stands as a viable temporary solution.
I’ve got the exact same problem with syncing to my SD Card. It has only started after the 4.0 update. So very annoying. I had friends over yesterday and was just syncing my SD Card on Friday for the Saturday party and this issue messed up the party. Fortunately I Algoriddim DJAY saved the day…Hooked up my ipad directly to the SC Live 4 and worked like a charm.
I’m now trying to sync playlists one at a time…seems to be working so far but its going to take a whole day.
3.3 seems to be ok for database additions / removals in regards to the desktop app - both 3.4 and 4.0 come up with “corrupt” DB when attempting to import tracks or analyse ones that are in the DB already, I’m sticking with 3.3 on my prime 4 and go at the moment until this is resolved as re-analysing and reimporting several 1000 tracks each time is just not a good workflow.
The latest firmare update on the machines seems to be stable, and brings great functions. It is only the Engine DJ desktop app that is exhibiting these problems, at least for some people.
It worked for me. I dragged one playlist at a time within the DRIVES window in Engine DJ, NOT the Sync Manager which did fail. I only have 3 Playlists in my upper hierarchy, but many others inside them. Anyway, the poster below is claiming that rolling back to 3.3 will solve these issues for now. Best of luck.
I experienced the same database corruption issues on 2 separate sync actions, one to a sandisk SD card and another to a samsung ssd drive which is installed to the prime 4 plus device. The SD card threw the corruption error almost immediately in the device. The SSD worked okay for awhile but threw the corruption as well.
I have a external ssd with a database from prior version of Engine for PC and it worked fine. Played from the drive for 5 hours straight, no issues. Tracks have been synced to the ssd from version 4, so not sure where the issues lies.
I’m going to downgrade the version on the pc and rebuild the database. Then ill re-sync to both the SD and the internal SSD and see if the corruption error reappears.
