All red (again...)

[Christiaan]

@Hans_Beuzel Are you still getting slow syncs?
How large are all your Engine m.db files? I’m wondering if maybe it has to do with that

[Hans_Beuzel]

Hi Christian, since I don’t analyze anymore on the MacBook in Engine DJ, but on the SC6000’s, it’s useable. It takes a bit of time for the SC6000’s to analyze, but I can live with that. The Engine m.db files are 955,5 MB. Thanks for coming back to this topic!

[Christiaan]

Can you upload both your Lexicon database and the m.db once more? I’m going to try to recreate this problem again, it bothers me that this is still not fixed…
This is the upload link: http://upload.rekord.cloud

[Hans_Beuzel]

Done. It could take a while before I react again. Now working on two gigs for this weekend, so my focus lies there… But it’s great to see how involved you are!

[djjatoro]

Could be related, perhaps, the issue/problem reported by @Hans_Beuzel with what I mention in my post?

@djjatoro

If the database has not been created and analyzed before in Engine, when exporting to Engine the waveforms do not appear visually created, even though they are (internally in the db), in each of the tracks. This implies that they must be loaded, at least once, so that Engine recognizes them.
What is the point, therefore, of doing all this preparation work on the desktop of the computer, if then when you go to the unit it takes about 5-10 seconds for it to recognize the beatgrid the first time (even if it is the correct one created in Traktor ). It is a time that in the middle of a session, in addition to despair and nerves, can lead to error.
Please, I suggest you check this point.

And to which @Christiaan replied:

@Christiaan

You have to understand that I do check all these things and I do want it to be 100% perfect but Engine is not my software so sometimes we have to accept that things are the way they are.

By the way, an answer that I still haven’t forgotten to this day.

[Hans_Beuzel]

Something I discovered recently. I did a full Engine-sync to an external drive. That’s something I haven’t done for quite a while. Mostly I just sync playlists. It took all night to sync. And now comes the strange part. At night a had another screen open on my MacBook, because I was simultaneously doing a RekordBox-export to another drive and looking at that screen. When I got back to the Lexicon-screen, it was at 50% but then it went fast to 51… 52… 53%. Like the syncing had been stopped because I got to another screen. Is that even possible? By the way, this was happening on a HDD-drive, when I sync to an SSD, it’s (of course) a lot faster.

[Christiaan]

I think that is a Windows thing, I notice the same thing here when I switch virtual desktops. Seems like it gives it less performance or pauses it or something when you’re not actively doing anything with it.

[Christiaan]

There was a different user this week who had huge performance problems when trying to import from their Serato library. Turns out they had a 2TB exFAT drive that was either not defragmented or just exFAT being slow. But after a format and change to macOS journaled file system, the problem was gone and performance was way higher.

Maybe that is what is going on here too? I suspect for Windows NTFS would also be a lot faster than (ex)FAT

[StuR]

But NTFS won’t work with Engine DJ, it has to be either FAT32 or exFAT

[Christiaan]

Right… Maybe the FAT drive is so fragmented that causes this huge performance drop?

[Hans_Beuzel]

I don’t think that could be the case, Christiaan. At least, not in my case. Then the drive should be this defragmented directly after formatting it. For me the ‘solution’ has been a: not analyzing tracks in Engine DJ (so I let the SC6000 make the preview, which takes more time loading, a bit annoying) b: be very patient when syncing c: don’t plan syncing right before a gig.