Prime 4+ – Audio stutter and lag when loading tracks (Engine OS 5.0.0)

If you place a .PNG logo in the Engine Library folder, it will take priority as the display on the P4/P4+, SC6000, and non-motorized SC5000!

For those with players that don’t have the option to display a logo in the jog wheels, try a version of a playlist without album art, with approximately 30 GB of content on a USB drive or external SSD. Do this without modifying your main library to see if the audio problems persist.

To remove all album art, you need to use tagging software such as TagScanner, Mp3tag, or Jaikoz. You can also delete and replace the tagged image with a suitable resolution or simply reduce the size of the original image.

My library contains 8892 files. My Raspberry Pi has a 512GB Samsung Series Pro 850 SSD, and my Pentium 4+ has a 500GB EVO 860 SSD.

I don’t use a streaming platform, so I don’t use Wi-Fi. I sometimes use Bluetooth if someone requests a track that isn’t in my library (this only comes in handy about three or four times a year).

My original library was almost 30,000 tracks; I could have had five times as many… but there’s no point, so I reduced it. (However, I store these files on a 2TB SSD at home, just in case I need to retrieve tracks later.)

I use a tagging program on my Mac called Jaikoz. It allows me to normalize ID tags and remove certain special characters and images. I make sure that the file names are identical to the metadata “Artist, Title”.

MP3Tag can indeed do that, but unfortunately, it didn’t help. Even removing the cover art from the tags had absolutely no effect on the behavior.

Do you know if support escalates higher than 2nd level?

I’m getting pretty basic responses, after I’ve done all the recommended steps (DB cleanup, factory reset, yada yada yada), and telling me to test only with demo tracks and no drives. Yeah, sure, even if it would work without issues with the demo tracks, I’m not gonna do gigs with demo tracks.

It’s like they are completely missing the point that I could trust the device at 4.3.4 and now at 5.0.1 I cannot (same song database, same internal SSD).

I assume support is already aware of the issue by now, especially since similar reports are increasingly appearing not only here, but also across Facebook groups and Reddit discussions.

Whether this can still be escalated further, I honestly do not know.

What I do know is that, in its current state, version 5.0.1 personally does not give me enough confidence for live use. At the moment, every track load feels like waiting for the next dropout.

I’m actually heading off to a gig right now and will once again be using an XDJ-AZ from storage as a fallback system instead of my own Prime 4+.

Not necessarily because I prefer it — but simply because I currently trust it more in a live environment.

Moin @U-w-B ,

At the moment, every track load feels like waiting for the next dropout.

…using an XDJ-AZ…

…instead of my own Prime 4+…

absolutely scaring and I hope as well, it will be improved asap

good luck for your GiG and happy Whitsuntide

Brgds from HAM BeatMaster

At all. Devs are on it, if my info is correct. They monitor this topic as well.

I noticed that while playing continous, the next track plays for about half a second, then a short pause and then continues. This is reproducable; happens every time. Tracks from internal SSD. Not experiencing whilst playing from usb. Could be that the internal SSD is still on the old DB format?

I’m on a Prime 4+, running 5.0.1

Hi everyone,

I can confirm the same issue on my Prime 4+ running Engine OS 5.0.1.

I experience audio dropout and stuttering on the playing deck whenever I load a track on the other deck. Additionally, I have noticed that enabling RGB waveforms makes the problem significantly worse — the audio on the playing deck starts to distort and stutter immediately when loading a track on the slave deck. Switching back to Tri-band waveforms reduces the problem but does not eliminate it completely.

In my case, the issue seems clearly related to CPU overload triggered by the combination of track loading + RGB waveform rendering simultaneously.

I was on 4.3.4 before and never experienced this. This makes the unit unreliable for live use in its current state.

I will wait for the fix before updating my workflow. Please prioritize this — it is a critical bug for any DJ using this unit in a professional environment.

Thanks to everyone contributing to this thread.

Device: Denon Prime 4+ Engine OS: 5.0.1 Previous version: 4.3.4 (no issues)

I’ve stayed on 4.2, I see no reason to update, I prefer the clean look of engines tri-band, I even changed my RB on PC to tri-band as well not interested in rgb.

Why are you getting rid of your player? :thinking:

The products receive feature updates and bug fixes, so you can expect one or more fixes very soon.

Nothing’s stopping you from downgrading the version in the meantime!

But hey, it’s your money! Elsewhere… it’s hardly any better, with updates every 3 or 4 years, if not longer, and whether it’s for new features or bug fixes, they cost twice as much.

Moin dear all,

I read this thread with my utmost interest and I will use this place for a compliment to Denon’s staff in three concret points; imo they are most important or even of the essence:

  1. Performance Library view: Tapping the running track, you will get the overview. So you can inform about the just running version (e.g. Dance Version or DUB or deep house …) Sorry I don’t know the name of the field)

image

  1. showing the cover in the History (i’m so glad to see the cover, when scrolling through the history)

  2. absolutely my favourite: Preparing in Engine DJ a smart playlist (sql query) and activating this playlist on your gear (P4 / P4+) the selection will be achieved

  • (still missing a second criterium like selceting BPM after selected key)

these three features had been three of my feature requests

btw: I will trust in Denon’s staff performance to improve the system continually (e.g. :

  • BeatGrid amendment our never ending story,

  • RGB Waveforms: Imo it’s difficult to use, it’s my challenge to create a 100% correct beatgrid. Then I can use the FX during a transisition and even more two tracks, or using all four tracks) so many users had waited sooooooooooo long for this tool :innocent: )

  • Maintenance of the “issues” detected after publishing the UpDate

Even building up Rome took more than one day

sorry, I’m not an English native speaker

brgds BeatMaster

i found that turning the platters off stops the stutter and sound cut-out

Platter off on a Prime4+?

i meant the vinyl from scratch to bending

I repeated the test as i described before with vinylmode disabled.

The problem remains on my device. :frowning:

Ok. :slight_smile:

I was very excited that i can do the track-ratings on the device! This is the feature i was missing :slight_smile: been a real nice quality of life improvement.

I also have the same issue with the audio stutter and lag , the night after the update, i just updated just to be safe and fix some bugs or something (im thinking in my head) the next day i had an event , not a big event (40 people or so) but its still an event and everyone noticed my audio stuttering and some even came over and asked me if my equipment is faulty :sob::melting_face: … i did not have a fun night, everytime i had a track load i was just praying to not stop for 1-2 seaconds… Please Staff Fix this issue as fast as possible I even have a mix witch i wanted to put on a radio show and you can clearly hear the 1-2 seaconds pause

Huh, so you go from a standalone Prime4+ flagship to a DDJ-FLX4 software beginners controller!? I would have expected an XDJ-AZ tbh.

next improvement of the essence :bottle_with_popping_cork::radioactive: