5.0.3 is live!

Improvements and Fixes

  • Fixed an issue that could lead to audio interruption when loading tracks with high resolution album art to deck

  • Improved system stability when editing playlists after navigating from the History view

Has anyone updated and tested it out? Rolled back to 4.2.0 and am hesitant to test it out…

So far so good, no audio interruptions and its stable thus far.

It’s great that the InMusic guys are delving into firmware issues so quickly.

Sure, some ne’er-do-wells will say “err well , it shouldn’t ave appened in the first place” or “they should ave beta tested it for 10 years before releasing” but get real - even Microsoft, Apple and Android have bugs.

This loading glitch was narrowed down pretty quickly to being related to oversized album art. I think we can be sure that beta tests in the future will have a test for bloat-art in the future. Maybe engine DJ will warn us when it analyses tracks with huge album art. But for the meantime, 5.0.3 gets around the issue.

There’s probably already a 3rd party app for automatically resizing chunky plus-sized album art as a batch process - fitting the “one-click-fix” requirement of some users.

It’s good that they’ve found the issue with loading glitches, but no news on whether this will fix the random shutdowns, freezes and reboots that people have been seeing.

Unfortunately, in my experience it can happen after 5 minutes, 30 minutes, a few hours or not at all in any given session, so I don’t think it is an easy fix for them.

I’m sure it’s been the case in years gone by where Denon’s library software rejected files with artwork over [size] or with incompatible formats…

When I bought my HS5500s I used Denon Music Manager to curate things and send tracks to the HDDs in the players, and it would refuse to add certain files, which is why most of mine now don’t have any artwork at all.

Doesn’t bother me TBH. I’m playing audio. I’m not displaying cover art to my audience on giant screens.

Credit where credit is due. Thanks EngineDJ devs.

Communication-wise I think the persons speaking up have still a valid point. Hopefully the issue and the customer-facing communication will be reviewed and learnings applied.

Well done, now let’s move forward! :slightly_smiling_face:

No software is perfect, that’s a given. But bugs are recognised and fixed pretty quickly, so that’s great. I just enjoy seeing things improving over time.

In my case the “random” reboots/freezes were due to the loading issue. So hopefully this fixes everything.

Why only 2 bug fixes(one minor) , if the list is of requested features is longg…

Because its not a feature-update, but a bug-fix

Requested features?

They mostly don’t happen.

Because of great beta testing

Pretty sure the RGB waveforms introduced in v5 was a rather requested feature? :blush:

Mostly

:man_facepalming: :man_shrugging:

The RGB one has only just been added…after nearly FIVE YEARS - and that’s just one of many that are as old or older.

Many of us here have all our votes tied up on legacy requests, which is why if you look at the request list, so many have either no votes (not even from the requester) or single digits.

5.0.2 worked better for me… Prime 4+, internal hdd, 2x lc6000. Audio struggling while loading tracks - also on 3-color waveforms now. That wasn’t issue before the update. Had some issues with color waveforms but I managed to fix that by rendering all tracks in engine dj and syncing to prime4+. Anyone else has this issue?

The shutdowns were mentioned as fixed in part 2 of the update notes

I have no idea what you mean by part 2 of the update notes, the only notes on the download page don’t mention shutdowns at all. Is there somewhere I should look to find this?

…aggiornato alla versione 5.0.3 continuo ad avere wave form dislpay che va a scatti soprattutto mentre carico traccia nel deck nella Prime 4 +.

Possibile che non riescano a risolvere?

E’ veramente fastidioso.

I didn’t know you could use Denon Music Manager to do that, but I never bothered putting CD players or hard drives in the 5500s. I forget what I used DMM for… maybe creating the database on them faster so you didn’t have to wait for the players to build it?