Engine DJ v3.0.0 Database issues when using third-party tools (Lexicon, De Cu)

Engine DJ Software Engine DJ (Mac & PC)
58

Well that’s the thing. I did experiments by deleting the lexiconId column but the error still appears in Engine. So it’s more than just that.

If you let Engine create an empty database (delete the Engine Library/Database2 folder) and then use SQLite to add a random column to the Track table, you’ll be greeted by the error.

Still working on figuring this out

1 Like
59

I really hope that Denon haven’t done this on purpose to lock out third party apps.

Engine DJ has been lagging behind the other major DJ/preparation apps for years, and tools like Lexicon made it so much easier to stay in the Denon ecosystem. Pulling the plug on this, while the software is still lacking important features, is a pretty bad decision. Even the more mature apps like Rekordbox, Traktor, Serato don’t do this.

I was really excited for the 3.0 release and love the features Denon is adding to Engine, but this is not a “cost” I am happy to pay for them. I hope this is an unforseen consequence and is fixed soon.

4 Likes
60

thx for helping, I just wish Denon would acknowledge that they have an issue and is addressing them. Engine OS is not the issue seems to work fine on my P4, P2 and Go.

61

They are usually pretty fast on things that break Engine, so hopefully they’re working on a fix in the background and will chime in soon.

2 Likes
62

I don’t think it’s intentional to lock out third party apps or make it difficult for them but more a way to make sure the database integrity is correct to prevent Bad Things™️ from happening.

7 Likes
63

This solution has resolved the issue for me and I hope it helps you too.

    • Create a backup of your database.
    • Open DB Browser for SQLite and select the “m.db” database.
    • Go to the “Track” table and check if the “lexiconId” column exists to determine if this is the specific issue you are facing.
    • Go to the “Execute SQL” tab and run the following commands:
DROP INDEX index_Track_lexiconId;
ALTER TABLE Track DROP COLUMN lexiconId;
    • If there are no errors, save the changes and test the database.
9 Likes
65

wow, i had used lexicon way way back but had no idea they altered the actual engine DB by inserting this column. Confirmed that once i removed the lexiconId column from the db, i was able to get everything up and running again in Engine DJ. Thanks Boka, Christiaan

3 Likes
66

Exactly. Mind blowing to me that someone would open a ticket and wasted Denon’s time because a third party software app doesn’t work after an upgrade. They don’t own Lexicon and don’t manage their code. How would one expect Denon to help? SMH

1 Like
67

Hi… I know nothing about sql but it looks easy to do that. After doing your solution….What is about using Lexicon again? Did it work then? I don’t think so.

Greetz Kai-Uwe

68

Engine DJ can’t read the dB the third party software can. Read before you write.

1 Like
69

Thanks for this solution! I had already downgraded to 2.4.0. I have now tested it again with the solution, updated to 3.0.0 and it works.

1 Like
70

I’ve made a little Video Toturial for it. Thanks for your help :slight_smile: Mine is working now !

8 Likes
71

I’ve tried this several times, but i can’t make it work. Anyone who can tell me what I’m doing wrong?

Execution finished with errors. Result: near “DROP”: syntax error At line 2: ALTER TABLE Track DROP

72

Thank you very much for this help.

It runs !

73

Are you writing it exactly in the following way?

DROP INDEX index_Track_lexiconId;
ALTER TABLE Track DROP COLUMN lexiconId;

Can you watch the tutorial made by @Justin_Roettgen to see if you’re doing something wrong

1 Like
74

Hi,

I’ve followed the video and copied the text correctly as in DROP INDEX index_Track_lexiconId; ALTER TABLE Track DROP COLUMN lexiconId;

and I also keep getting the error that djlasse is getting:

Execution finished with errors. Result: near “DROP”: syntax error At line 2: ALTER TABLE Track DROP

It doesn’t matter how i do it i keeps coming up with the same error!! Please help…

75

Thanks for your tipp.

Unfortunately it is not working for me. I had the lexicon entry and successfully deleted it. But after updating to 3.0 it still says Database not compatible. So the entry is gone but I still can’t update to 3.0 :frowning:

I’m afraid I’ll have to wait until an “official” solution, unless anyone else knows of another solution.

76

Did you check if there is an entry in “Track” called LexiconID?

77

yes there is an entry called LexiconID but still comes up with the error…

78

I’ve watched the video and I’m sure I’ve done it right…