I did the same. updated to Engine 5.0.0 - exported to Harddrive - played at gig and crashed. The next day my Numark and Denon consoles requested an update to 5.0.1. I did that. no crashes so far.
I spent my weekend doing exactly this too. Very frustrating experience. I work almost exclusively from the prepare area and have done for the past 6 years. I search for the track I want and swipe left. I had a near disaster where I almost played the wrong song for the father daughter dance because I had it loaded in deck 1 and was gathering together a few songs to start the general dancing with into the prepare area, except I overwrote the loaded father daughter dance and only caught on as I was about to hit play, hence had about 10 secs awkward silence whilst I relocated the song!
Just adding a config option to allow us to choose the behaviour from the past 6 years or the new behaviour would make things so much better than making a major change to the workflow that I’ve been using all that time.
It’s a nightmare. There definitely should be a toggle to switch back to the old behaviour. For now I’ve had to turn on the track load safety setting which is annoying, as it also stops prev/next working, and I’ve not had track safety turned on in any controller or software for 20 years. It doesn’t stop you loading over songs you’ve already got cued up though, it’s very annoying.
Also, audio dropouts when loading, lots of audio dropouts with long files, still no fix for the tidal grid being out of line with the audio, etc.
100% the toggle keeps everyone happy. If that isn’t available in the next couple of weeks in an update I’ll just roll back to the previous version I think, especially as I seem to have been lucky so far in terms of audio dropouts - I’ve not had that at all. I only loaded one long file though that was a Mastermix Warm Up mix so was the very first thing I played, hence no audio was playing to drop at that point.
I’ve always had the track load safety setting on. Funny how everyone’s different in their preferences as I’d have thought most people would want that enabled, but of course if you use prev/next I can see why you wouldn’t want it!
Fingers crossed for a toggle to be added but not holding my breath as I expect there are lots of other priority items for the devs to be focussed on if audio dropouts are a thing.
I love how we are expected to create a feature request to make the hardware work like it did when we purchased it. I hate living in this timeline. I went back to 4.2.0
No feature request will fix the drop outs. Denon dropped the ball here.
Hopefully, those experiencing this problem can provide more details and clues on how to reproduce it. Until the cause is discovered, complaints are useless; they’re just complaints that lead nowhere. It would be helpful if those affected could submit a complete report detailing how they were using the device. Let’s see if we can find something in common that allows us to reproduce it—and there has to be something.
I agree with you; if there’s a problem that hasn’t been detected yet, we can all help solve it with positive contributions like yours.
What I think we shouldn’t do is troll about how bad Denon and its technical service are, since I have the opposite opinion and I’m making that clear. (If, in some cases, there’s a local technical service that doesn’t meet the customer’s expectations, that’s another matter.)
The fact that I and many other people can’t find the faults?.. is because we’re doing something differently, between those who find problems and those who don’t.
That’s why it’s not fair to criticize Denon, since it’s a great brand and they do much more than others to improve and offer the best service.
Thanks for your contribution; I had already seen it and wanted to try it, although sometimes Google translations make comprehension a bit complex.
But if I have any questions about how to play it, I’ll let you know. Thanks again, regards.
Hey mate, I’m having the same problem. Since updating to version 5.0.1, I never had this issue with any other version. In my case, it’s a Prime 4+. Every two or three times I change tracks, the audio flickers or stutters. It’s only for a split second, but it’s noticeable. It feels like the controller is lacking power, or at least that’s the impression it gives. I’ve formatted my USB drive and re-analyzed everything with version 5.0, but nothing has changed. I hope they fix it soon with an update. There are many of us affected. Sorry for my English. Cheers.
Unfortunately I had more issues come up. During the last hour of my gig on Monday, the knob locked up on my DENON SCLIVE 4 console so I could not scroll up or down to find and load songs. Even the songs were not loading properly so I had to swipe on the screen to find songs. luckily it was the last 1/2 hour of the gig and I managed to pull through but this update is proving to be buggy. What is reccomended here…go back to the older more stable version until all this gets fixed? And how do you do that?
I had this issue tonight, the only difference was I was using a very fast external SSD, when I switched back to internal SSD on my Prime 4+ the glitch on loading stopped. The load glitch btw was epic and very obvious & worrying at the same time. Happened after around 4 hours of use using the latest 5.0.1 build
I don’t know if the read speed of both hard drives can be different, since the speed of a hard drive in a PC isn’t the same as that of a USB flash drive, regardless of how fast the flash drive is.
I’m not referring to the speeds of both HDDs, I’m referring to the speeds that the hardware path is capable of processing through the two different paths.
Is that possible? Could that be the problem? Interesting discovery, my friend. It’s possible there’s a bottleneck in the hardware itself that’s responsible at high performance levels.
Perhaps someone more experienced, @denon, could check if the transmission speeds of the internal HDD ports are higher than those of the USB or SD card ports? This could be the reason for the problem. I only use an internal HDD and have never had any issues.
I’ve also encountered a total crash of my Prime 4+. Since the update, I’ve done five weddings. At four of them, I had a packed dance floor and encountered a complete crash right in the middle of a song. That’s totally unacceptable!
What I’ve noticed is that it seems to be when I’m searching for music in my Tidal service. The crash has happened during a song playing from my SSD, and while playing a song on Tidal.
Hoping for an update soon, or I will go back to the last stable version.
I had the same thing happen on my White Prime 4+ 2 times during a 3 hour afro house set while searching for tracks via beatport and switching back/forth between local library and beatport. I have a T9 SSD and had no problems or lockups previously. My screen froze and the song ran out because i was not able to control the deck anymore, even the vu meters locked up! i had to hold the power button in to reset it.
i am back on 4.3.4 now and have no issues anymore.
for me..
my english sux <3