mixxx 1.7.0 beta released today, including midi improvements
hi, was surfing around the mixxx site and saw that they came out with a new release today:
http://mixxxblog.blogspot.com/2009/0...-released.html
Quote:
The Mixxx development team is proud to announce the first beta of Mixxx 1.7.0. This latest release is the culmination of six months of work by over a dozen contributors, and contains several exciting new features as well as many bug fixes.
Some of the new changes in Mixxx 1.7.0 Beta1 that we'd like to highlight are:
* Cue points are now saved in the library for each track, with "auto-recall" cue option added to preferences.
* The default skin is now widescreen, and fits nicely on netbook sized screens.
* Stereo master VU meter added.
* MIDI overhaul:
o MIDI learning wizard
o MIDI mappings table editor
o Upgraded, faster mapping system
* QtScript/JavaScript-based MIDI Scripting Environment - Code up complex behaviour for your MIDI controller without recompiling Mixxx!
* MIDI output now fully supported on Windows, OS X, and Linux.
* Added full support for the Stanton SCS.3d on all platforms.
* Added Mixman DM2 mappings for Linux and OS X.
* Vinyl Control:
o Scratching responsiveness improved, with needle-skip prevention option added.
o Signal quality indicators added to vinyl control preferences.
* Merged the mixxx and mixxx-data packages for Ubuntu users into a single mixxx package.
* Fixed about 40 bugs, including:
o Browse mode no longer disappears in certain situations
o Skin changing is now much faster
o Tooltips now work again
o Fixed rare instabilities caused by certain OGG and MP3 files
o Minor improvements to the BPM detection
o Fixed some OpenGL issues
o Fixed a handful of obscure issues that may have prevented Mixxx from starting up on Windows
o Play nicer with Ubuntu systems that are running PulseAudio
Aside from these more visible changes, there was significant work done on less visible parts of Mixxx. This includes many improvements to the organization and cleanliness of our source code, as well as a lot of work on features that didn't make it into the final 1.7.0. release. Improving the overall codebase is important for us because it makes it easier for new developers to contribute, and it was these new contributors who helped catalyze the overhaul of our MIDI system.
Back around December, we started toying around with the idea of something we called MIDI scripting. The idea of MIDI scripting is that having a small scripting engine sitting on top of our regular MIDI mappings would allow our users to code complex behaviour for their MIDI controllers using a JavaScript-like language. Soon after this idea hatched, we realized MIDI scripting would make it much easier for us to support new controllers in the future, and this attracted the attention of a handful of our developers.
probably play around with it after work today.
