News for hackers. Stuff that matters.

hlzhs

Re:Mixxx: GPL DJ Software on Monday January 20, 2025 @05:49PM (#42774058)
Just try it, it's completely free: https://mixxx.org/download/#stable

Mixxx is entirely community driven: There is no company behind it, everything is done by unpaid volunteers.

Re:Mixxx: GPL DJ Software on Monday January 20, 2025 @05:41PM (#42773973)
That is exactly the reason. Also, some libraries we are using are not on homebrew (and we cannot easily pin a specific version).

Another reason that we'd like to reduce the maintenance burden by using a similar setup for windows and macOS deps. Our dev team is small, and almost all of us use Linux. For macOS in particular we don't have anyone on the core team that uses it as their daily driver, which may also play a role when talking about the DX in macOS.

Re:Mixxx: GPL DJ Software on Monday January 20, 2025 @05:30PM (#42773868)
Mixxx dev and main author of rekordcrate here. The issue is that the format is an ancient proprietary format that does not have been reverse-engineered to a degree that we can properly write Rekordbox DBs yet (Rekordcrate is based on the work done here: https://djl-analysis.deepsymmetry.org/rekordbox-export-analy...)
Re:Mixxx: GPL DJ Software on Monday January 20, 2025 @05:23PM (#42773799)
Check the https://manual.mixxx.org/2.5/de/hardware/manuals for a list of built-in mappings shipped with Mixxx. There are also additional user mappings on the discourse forum: https://mixxx.discourse.group/c/controller-mappings/10

Personally, I use the Roland DJ-505: https://manual.mixxx.org/2.5/de/hardware/controllers/roland_...

Re:Mixxx: GPL DJ Software on Monday January 20, 2025 @05:20PM (#42773771)
Thanks, we wanted to honor our user's privacy when we redesigned the website.
Re:Mixxx: GPL DJ Software on Monday January 20, 2025 @05:14PM (#42773720)
Mixxx dev here. I'm sorry you had a bad experience. We are spending a lot of effort on making Mixxx rock stable.

Considering that this was more than a decade ago, I'm pretty sure that this bug has been fixed by now.