Prepare list does not save changes when you restart in 2.0

[mufasa]

@Rips

I would not assume all DJ Engine changes are intentional because Denon is moving fast with releases now and that is a challenging thing to get right.

Scary stuff.

Imagine waking up to realize that your master collection stored in HFS drive is no longer working.

I’m getting tired and now I’m just waiting to see where all these is headed for.

[SlayForMoney]

@Rips

From my experience as a Digital Product Owner it’s usually because:

• Feature was not reimplemented as part of a major code rewrite
• Feature was lost by accident during an unrelated code change
• Someone assumed the new behaviour is optimal and didn’t bother telling us

I would not assume all DJ Engine changes are intentional because Denon is moving fast with releases now and that is a challenging thing to get right.

There’s also a variety of issues with Engine OS not remembering the state of screens and lists so it’s possibly all related.

• Feature was not reimplemented as part of a major code rewrite - Link (“export”) mode lost in the Engine .1.5 → Engine Prime 1.0 code rewrite

• Feature was lost by accident during an unrelated code change - Active Loops

• Someone assumed the new behaviour is optimal and didn’t bother telling us - this Prepare list change

Add to the list weird non-performance bugs like that front LED light and this JSON error and you get a sense what a poop-show this software development is.

PS the Link ommision in the code rewrite might have been deliberate because of a) marketing of “no laptop need” b) lack of IP rights on player/mixer firmware that was designed under D&M Holdings (previous owner of Denon DJ brand) - most likely outsourced to a 3rd party and so not included in Denon DJ brand purchase

[Rips]

All I would add is that developing a single OS for multiple hardware platforms is not easy, doesn’t really matter who’s doing it.

Denon could show they are listening to the community by focusing on fixing bugs and improving workflow stuff for the next few releases.

I think people are mostly quite forgiving but there are limits to that.

[djkarlos]

totally agree, there are many errors and crashes with the units, denon would have to focus on correcting them and then continue making improvements, what is not normal is that each patch we have something new but the errors still exist

[Cadillac]

I would love to see the prepared folder back.

[Wyley1]

Thanks for reminding me of this. I tried it once but found it was easier to use the prep list which the properties of it has now changed.

[Nikdo]

I really do not see how this is any scarier than one’s HDD on their computer that has pictures of their family from 20y ago being the only copy. And people being naive enough to think that HDD will never fail and thus backups are only for network admins to worry about.

I do not worry about Engine OS losing my data ever, because it is extremely simple to just backup the db and songs onto another medium as a backup. One cannot ever trust any software not corrupting the data or losing it altogether.

[Nikdo]

From my experience as software dev:

• no release ever fixes all bugs. There are always outstanding bugs. What matters is if they are prioritized well enough
• Saying Denon never fixes bugs is a little harsh. Next time you are downloading a new release, go into the release notes and notice that plenty of bugs have been fixed.

Again, it is about priorities. Being relatively new to Denon, I cannot yet comment if they have the priorities right when it comes to bug fixing. I am sure others can comment on that better than me. I just wanted to comment on your post because I do not think that was a balanced observation on the state of bug fixing.