Hacker News new | ask | show | jobs
by weinzierl 313 days ago
I love Mixxx, I use it daily as a music player. I know it is a virtual DJ deck, but it is also a fantastic music player.

That being said the following sentence makes me a bit concerned "The current user interface of Mixxx has served us well, but as technology evolves, so must we."

As far as I know QWidget is neither deprecated nor are there any plans for that. I think Mixxx has one of the best UI's I ever encountered, in design and execution. Please don't botch this.

4 comments

Yeah, I know both QWidgets and QML quite well and I also don't see a strong reason to port. Genuinely custom painting of highly detailed elements in QML is either pretty annoying (comparable to doing it in OpenGL, and then you still need to do user interaction without much help from the framework) or slow if cobbling it together from existing items or using a canvas. I've helped fix particular issues on a project that needed highly detailed custom painting in QML (think rendering text in an editor component, though it wasn't that), but in the end it failed for performance reasons. I knew of some really good developers on that project, so it wasn't plain incompetence. Edit: I think it can be done, it's just a lot of avoidable work.

Mixxx might not have that problem, not sure. The waveform view is presumably custom painted, but shouldn't be too difficult. There may or may not be others.

Every user who uses a screen reader has been asking for this. Also, though I can't speak to this personally, apparently the theming engine is much easier to maintain in QML which is a big time saver for the devs.
The one killer feature any DJ software can have - and it's a tough one - is....

Not crashing during playback.

But hey why refine and fix bugs when you can constantly iterate on new features no one asked for (sadly this applies to most open source software).

FWIW I've found mixxx to be much more stable than serato or traktor (commercial stuff). I can't say whether they focus on bugs or features like your criticism suggests.
As a Mixxx user of 8 years with many life shows and even longer ones at home I have never had Mixxx crash on me, not even once.

I had some UI annoyances, so I support the effort and trust the devs to make the right choice. Otherwise I can still just run the old version till 3.x turns stable.

I have no problems with Mixxx in that regard. I run it on Linux and for me it is rock solid. It can't help if your computer crashes though.

I used to use mpd for a while which automatically continues playing where it left off after a reboot.

What I learned from that phase is that the music I enjoy in the evening is rarely the same I like blasted in my ears mid-song at full volume in the morning. Terribly annoying feature, will not use again.

I am intrigued, what makes it a good music player for non-DJs?
I like the way you organize your music in crates and playlists, which are permanent structures and then you arrange everything for the occasion[1] in the AutoDJ, which is ephemeral.

I also like the BPM and key display.

[1] In my case just my current mood

I use Apple's app Music on my Mac. Unfortunately, still the best music library I know about for macOS. But maybe others have other suggestions.
I recently looked and bought into the DJ tech today. I know mixxx, used it many times. And Rekordbox isn't perfect either. But you can't even compare. If the one is Dj Software, mixxx right now, is just a music player with DJ theme
An alternate view on this is Rekordbox is software that you have to pay for, tries to upsell you to a monthly subscription, has arbitrary limitations on what hardware it will work with and by default sends data about every track you play to some 3rd party service.

Mixxx doesn't do any of that and it's absolutely powerful enough to use for DJ sets.

I bought the hardware without knowing that and have a device bound license. It's weird that the software literally degrades when the device isn't attached.

The hardware limitations are crazy and weird, especially when you realize that parts of the limits are purely trough the visualisation. But when you have a supported device the performance is amazing even on older hardware. (I run it on a Wyse 5070)

Like all non free (or any software) it's a double sided sword. However it's one of the few industries where the monopoly software is actually not bad at all and doesn't force you into monthly payments when you buy their devices (which is basically industrie standard anyway, and not actually that much more expensive).

I don't mean to suggest it's a weird situation - requiring people to pay for the software (directly or indirectly) makes perfect sense commercially.
I’d be interested to know what the main differences are