OMG, NOT another firmware update

Engine DJ Hardware Media Players
44

You know, I’ve gotten my thoughts together and came up with this…it expands on an earlier statement that I made.

ALL of these frustrations that I’ve been reading from users over the past weeks/months could be squashed simply by Denon hiring some liaisons that act as intermediaries between us and the team. Imagine if there was someone that came into all such threads and simply stated, “these are really good ideas, and I’m going to forward them to the development team”. That simple statement by someone that we all know is part of the team could alleviate so much of the frustration. Hell, Serato Forum had several such team members. They actually became our friends. It went a long way!

I’m done venting now.

1 Like
45

When I read the title, I misread is as “OMG, NOT another whinging user” - must get my specs sorted!!!

1 Like
46

Forum members and product owners are entitled to complain or express their feelings. Good or bad.

1 Like
47

Can’t agree more - perhaps a little bit less drama though?

2 Likes
49

I guess the question is: what would that change really?

That person still cannot disclose development information. He/she will also still state “we’re working on it”, only much more of those sentences. Soon…

2 Likes
51

Spot on, Kradcliffe!!

52

I think the translation from my language to English would be “putting paper over the cracks”, but if that helps to please people, who am I to judge.

1 Like
53

It’s hard when people compare a hardware company to ansoftware company. Both Traktor and Serato have public versions of their betas along with private versions of their betas. So, open communication about current development is a bit easier. They still tend to avoid discussing anything that is not currently publicly available in the public beta, though. I’ve only been on the Serato forums for 5 years, but this has always been the case with NI.

There’s a greater competition divide in the hardware side of the market, so strict NDA’s and secrecy around current development are a must. God forbid your competition is able to reverse engineer a piece of product that has not yet been able to covered under the manufacturer’s copyright.

In the Pioneer, Elektron, and Korg forums, there are still people who will complain, even with a liaison (sometimes dev team directly in the case of Elektron) between customers and development.

1 Like
54

@Anthony_DDJ is on to assist

3 Likes
55

Hey @blackavenger - Completely understand your frustrations and are happy to help. If you need anything feel free to direct message me anytime.

3 Likes
56

It would be great if there were 3 ( or 6 or 12 or 52 ) Christmas’s a year, instead of just 1 (and a birthday) and you always got everything thst you wanted and no space under the tree was wasted on presents for other people.

The comment above about an extra liaison not being able to say anything more than what beta testers (the hard working, communicative ones) or “staff in the know” is nice but unrealistic. A person employed to say “all sorts of nice things coming - wait and see” would be a waste,

That said, I think one thing that used to happen, and that is now really missed, is where someone/anyone “in the know” would edit the firmware requests with “cannot/will not implement”.

That practice was great! It managed users expectations, and better yet, it was denon discussing firmware upgrades (in a way). It meant also that what was actually times where denon “had their head down working on the next set of firmware features” was no longer thought of (incorrectly) as “nothing’s happening” or “silence” or “they’ve obviously stoped working on firmware”

There are high hundreds of feature requests on the forum already (if not over a thousand), some ideas that would be used by thousands of users, others more niche and specialist and frankly not viable and never likely to have hundreds of hours of development person-hours spent on it, for a couple of users benefit.

Too many requests for anyone at inmusic to “blitz” them and update each of the requests in one go. So if that someone (doesn’t have to be Jwills necessarily) at inmusic, was to update a half dozen or so of the requests each week with “cannot/will not implement” then the “there’s only silence / nothing happening” incorrect comments would be quashed, as topics about firmware would be seen to be managed.

Sure, there might be some people who were thinking “I’ll buy a x if they add my feature” but hey, denon have announced thst they can’t add mic eq to the Prime Go, and the Prime Go is still selling very well, judging by all the posts from new users about how amazed they are by it all.

So come on… manage expectations. Even if we can’t get firmware every other month, let’s have some “virtual” updates about the existing requests (cannot implement, will not implement, under review, being researched, with developer).

1 Like
57

You know this is just a forum right?

2 Likes
58

As Jwill said, big things take longer. New implementations in alpha and beta builds often bring new issues or quarrels that need to be addressed and resolved to get a stable release. No one is happy when a newer firmware is released too early and some bugs or freezes affect the devices.

2 Likes
59

This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.