Personally, having started with vinyl in '91, I don’t care about the rhythmic grid or if the BPMs aren’t right; I know my tracks, so I know where to place the hot cues. My ears are my tools!
With the CDJ500 Limited and the CDJ1000, there was no rhythmic grid; loops were created on the fly and by ear.
I was old when I decided to start my hobby dj:ing 4 years ago (41). It was a friend that thought I should dj as a hobby cause I always listened and loved music.
He told me i should buy a used pioneer xdj-r1 and use it in standalone mode so that i get used to mix music by ear and not by visual. Best advice i ever got from a friend 
I did this for 1 year before buying the prime 4+. This is something i can recomend for everyone. For example I can always line up phrases just by listening to the beats and counting and if the grids are wrong just set the temp cue in the right place. But yes, i understand that if you always want to use sync, then the grids needs to be in the right place. But if you have started dj with sync then you really need to learn how to manually beatmatch.
Still using the r1 from time to time just to not get locked in with the screen on the p4+
Well, my brother works for NASA. He said read this…
Previously, he told me they run three versions of the software on a consensus basis.
Meanwhile, there is no real comparison between what we do. Except, as professionals we want to offer our audience a perfect experience.
Yes there is - Even at $1M / line of code, there are bugs. All software has bugs and if any company were to strive for perfection, they would never ship code. Full stop.
“Perfection is the enemy of good enough.” And, software that is good enough ships.
Yeah, true. He also said, "Spacecraft software is far less buggy than commercial software. Software is one of the highest development costs of a mission. Software engineers at NASA have a saying…..”Software will eat your lunch”. “We have lost missions because of software issues. Checkout the link above.”
But, DJ software is much less complicated. In my case, everything is working fine at 4.1 OS and Lexicon DJ for desktop, so no need to update at this point.
You have a lot of assumptions my friend. 
Back to the beginning: the audio glitches that occur when loading a new track are really something inMusik should immediately identify as the top priority and push for a fix through support. If we can no longer use the Denon system safely in all its aspects, it’s damaging to business. And with hardware that costs several thousand euros and can no longer be used simply because loading a new track causes the output signal to stutter, this is a whole different level—one that can lead to problems, including financial ones due to increased expenses. The question is how we want to handle this. Let me rephrase the question: does Denon DJ want to be a product for occasional home hobby DJing? Or should it be a professional setup for all kinds of occasions?
best The Voice
Yeah, you’re right—we can only hope there are beta testers out there. But I don’t think be inMusik has that feature. Maybe we could just offer that option to the whole community.
Personally, I have Sony PSN beta tests and EA beta accounts. They have strict testing and approval procedures there. That’s what I’d like to see for us. Maybe we could set something like that up here for Denon DJ.
By the way, I’m a full-time internet security consultant, and I can only say that major updates are never installed here. So if there’s a version 1.0.0, no. Only when it becomes version 1.1.0 do we discuss whether it would be an option to install it. Security hot patches are a different matter, but fortunately we don’t have that problem here.
Best the Voice
Communication anno 2026 https://www.reddit.com/r/sonos/s/LpJk2hm1pP Sonos CEO
(Finally!) An update.
Back in February I posted here and committed to being more present and more transparent about where we’re headed. Time for an update.
We’ve been working through a long list of improvements, and we’re now in the final stretch of getting them ready. I know it’s been a decent interval of quiet on my end. Thanks for your patience. We’ve been reading the posts.
What I wanted from this work was simple: a series of enhancements that make Sonos easier to learn and easier to use. The team has spent hundreds of hours over the past year watching real customers use the Sonos app, longtime owners and brand new ones alike. We’ve learned a lot about what hangs people up, what’s confusing when you’re new to the system, and what slows you down when you’re just trying to change the darn volume.
…
Stepping back: this is the beginning of a different way of working here at Sonos, where what gets built, and in what order, is shaped by the conversations here and with all our customers.
Thanks for the inspiration and thanks for sticking with us.
Did you know that you’d pasted a SONOS email in an InMusic Forum ?
True, reduced overflow text. My point is communication style. Sonos ceo fully embraced previous mistakes, sets an outline, invites people for the beta program and promises to listen. InMusic is not in such a bad PR state (yet), but highlighting the customer appreciation of a communicative CEO or company on this forum might trigger just the right people within InMusic - ie in a previous post some employees commented that they read the forum posts - a signal which was received with massive positive feedback - but the lack of communication follow up (especially in the light of the 5.x updates) is.. Surprising. There is so much to gain, just by binding with your customers.
But InMusic have already reached out, several years ago in the prime line-up and already have an active beta tester base
Appreciated, but cherry-picking. I’ll go along. InMusic has reached out for beta tester (good!), years ago (questionable), and has an active beta tester base (which apparently was insufficient as a protection layer for critical production bug). Would such an event not trigger somebody within the company to dust off their account, hit the password forget button and manage customer experience?
Zooming back out - ofcourse it’s up to the company and employees. As a customer I’m just indicating my expectations and experience about the (lack of) communication with my vendor.