14. Opciones Avanzadas
14.1. Mapeo de Mixx para controladoras MIDI/HID
Con docenas de controladores DJ soportados extraoficialmente, Mixxx le da un control integral del hardware para sus mezclas como DJ, see Using MIDI/HID Controllers.
Support for additional devices can be added to Mixxx by creating a new mapping file. This file tells Mixxx how to translate, or map, MIDI/HID messages from a controller into commands that Mixxx understands.
You can download and share custom controller mappings in the Mixxx User Controller Mapping forums.
For a list of controls that can be used in a controller mapping, see Mixxx Controls.
Asistente para la configuración de la controladora
Asistente para el aprendizaje de la controladora - Mapeo de una acción.
By far, the easiest way to create a new MIDI mapping is by using the Controller Wizard.
Conecte su controladora(s) al ordenador
Active Mixxx
Vaya a:menuselection:Preferences–>controladora
Seleccione su controladora de la lista de dispositivos disponibles izquierda y el panel de la derecha cambiará.
Active el :guilabel:”enabled’checkbox
Haga clic en :guilabel:”Learning Wizard” para abrir el menú de selección.
Haga clic en cualquier opción de Mixxx :term:”GUI”
Por otra parte, haga clic en el :guilabel:”Elija Control” botón y elija una opción del menú de selección.
Haga clic en configurar y luego utilice el control seleccionado o aprete un botón en su controladora para mapearlo. También se puede mover un control sin apretar el :guilabel:”learn” botón si está configurando muchas secciones.
Si está configurando una acción, aprételo únicamente una vez. Si está configurando una perilla o un fader muévalo en todo su rango o trayectoria.
After Mixxx detects the control, you may click Learn Another or you can click on another button in the Mixxx GUI to learn another control.
Cuando termine el mapeo de controles, haga clic en :guilabel:”Proceso Terminado”
También existen opciones avanzadas en el Asistente que quizá necesitará utilizar:
Soft Takeover: Use this option for knobs or sliders to avoid sudden jumps in when the knob in the GUI doesn’t match the physical knob. If you select this option, you won’t be able to perform super-fast motions as easily. (Recommended off)
Invert: Use this option for controls that you want to work backwards from how they were detected.
Modo de Activación: Utilice esta opción en controladoras que tengan controles que actúen como interruptores y emiten un valor la primera vez que pulsa, y uno diferente en la segunda pulsación. (Piense en un hardware o flip-flop de conmutación, o en un botón que se ilumina en la primera pulsación y se apaga en la segunda pulsación).
Plato / Perilla de selección: Use esta opción para perillas que no tienen un inicio o un fin, pero que giran de contínuo.
The Controller wizard saves the new mapping to the controllers directory in
the user settings directory, see The Mixxx Settings Directory.
You can then modify the XML file it creates (or any of the ones that ship with Mixxx) if you’d like to fine-tune it or add more mappings. For more information, go to https://github.com/mixxxdj/mixxx/wiki/MIDI-Controller-Mapping-File-Format.
El sistema de configuración de controladoras sólo funciona con sistemas MIDI. No se pueden mapear los botones de funciones (shift) y rotación de platos. En lugar de intentar esto use MIDI Scripting
Configuración de la Secuencia de Comandos MIDI.
Para poder se compatible con características avanzadas de muchas controladoras MIDI/HID, Mixxx ofrece lo que se conoce como Encriptación MIDI.
It enables MIDI controls to be mapped to QtScript (aka Javascript/EMCAScript) functions stored in function library files, freeing Mixxx from a one-to-one MIDI mapping ideology. These user-created functions can then do anything desired with the MIDI event such as have a single controller button simultaneously affect two or more Mixxx properties (“controls”), adjust incoming control values to work better with Mixxx (scratching), display a complex LED sequence, or even send messages to text displays on the controller.
For more information, go to https://github.com/mixxxdj/mixxx/wiki/Midi-Scripting and https://github.com/mixxxdj/mixxx/wiki/Hid-Mapping , as well as the Comonents-JS library which greatly simplifies mapping, for example effect units and complex behaviour like switching deck layers or pad grid modes. Note that this is the preferred way of mapping if intended your mapping to be included in Mixxx since Components-JS significantly reduces effort for both mapping and reviewing Pull Requests.
14.2. Cómo realizar un mapeo de teclado personalizado.
El <appendix-keyboard> mapeo por defecto del teclado se encuentra definido en un archivo de texto que se puede encontrar en la siguiente dirección:
Linux:
/usr/local/share/mixxx/keyboard/en_US.kbd.cfgmacOS:
/Applications/Mixxx.app/Contents/Resources/keyboard/en_US.kbd.cfgWindows:
<Mixxx installation directory>\keyboard\en_US.kbd.cfg
Depending on your system’s language settings, Mixxx might use a different
file as default, e.g. de_DE.kbd.cfg for German or es_ES.kbd.cfg
for Spanish.
It is not recommended that you modify the system-wide keyboard mapping file because all your changes may be lost if you uninstall or upgrade Mixxx. Instead, copy the default mapping file to the following location:
Linux:
~/.mixxx/Custom.kbd.cfgmacOS:
~/Library/Containers/org.mixxx.mixxx/Data/Library/Application Support/Mixxx/Custom.kbd.cfgWindows:
%LOCALAPPDATA%\Mixxx\Custom.kbd.cfg
Then edit this file and save the changes. On the next startup, Mixxx will check
if Custom.kbd.cfg is present and load that file instead of the default
mapping file. This has the advantage that you can always revert back to the
default mapping by deleting Custom.kbd.cfg.
For a list of controls that can be used in a keyboard mapping, see Mixxx Controls.
You can download and share custom keyboard mappings in the Mixxx User Keyboard Mapping forums.
14.3. Efectos Adicionales mediante Mezclador externo
Mixxx comes with a set of native effects. Additionally, using the external mixer mode you can route each deck directly to 3rd party effect hosts.
The following examples are only intended to encourage experimentation, they are not definitive guidance.
Effects via AU Lab on macOS
The Au Lab routing for external effects on macOS
On macOS there is a simple and free way to give Mixxx access to the collection of AU/VST/MAS plugins that are installed on your system.
Install the free SoundflowerBed, a system extension for inter-application audio routing.
Install the free digital audio mixing application AU Lab.
Consejo
macOS 10.15 (Catalina) introduces additional restrictions on running non-Apple software. Make sure to grant permission in System Preferences –> Security & Privacy –> Microphone –> AU Lab.
Alternatively, try Blackhole, a modern virtual audio driver that allows applications to pass audio to other applications with zero additional latency, and Hosting AU, a free micro-sized DAW that hosts Audio Unit instruments and effect plugins.
En Mixxx
Vaya a
Seleccione para Deck 1 the Soundflower 16 hardware con Canales 1-2
Seleccione para Deck 2 the Soundflower 16 hardware con Canales 3-4
Haga clic en el botón Apply
En AU Lab
Haga clic en el botón + para crear una nueva configuración.
Add 2 stereo input tracks in the Audio Input Tab
Añada 2 canciones entrantes en el apartado de Audio Input.
Haga clic en OK
Cambie la entrada de audio a Soundflower 16
Cambie la salida de audio, por ejemplo a Built-in Output
Haga clic en Crear documento
In the Output 1 channel, select an effect from the drop-down menu, for example
El efecto debería funcionar si usted hace sonar una canción en Mixxx.
Efectos via JACK en GNU/Linux
El enrutamiento para efectos externos en GNU/Linux
Use Jack to route each deck directly through JACK Rack effect racks, or for more control you can use Ardour (or another DAW) using sends for effects. This gives Mixxx access to the extensive collection of LADSPA plugins.
Make sure the correct multichannel audio interface has been selected in Jack (Jack settings visible bottom left). Note that Mixxx possibly labels its Jack ports as Portaudio.
14.4. Migrate your Mixxx library and settings to a new computer
If you move to a new computer, or to another operating system on the same computer, you can take your existing Mixxx setup with you. This includes your track library, settings, controller mappings and broadcast profiles.
You don’t necessarily need to be able to run your previous Mixxx installation, all you need is your settings directory and the music directories you imported into your Mixxx library via .
Preparation
If you still have access to your Mixxx installation open Mixxx, go to and uncheck Rescan on startup. If you are not able to start Mixxx anymore, e.g. if you only managed to recover your settings directory, you can do this manually in the settings file: open
mixxx.cfgwith a text editor, delete the line withRescanOnStartupand save the file.Make a copy of both the Mixxx settings directory and your music directories. Put all in a save place. Do not restructure your music directories!
Install your new operating system, get your new PC ready.
Get the current stable Mixxx version from the official download page.
Install Mixxx, though don’t run it, yet!
Migration
Copy your Mixxx settings directory to the appropriate location, see The Mixxx Settings Directory. In case you already started Mixxx previously, make sure to rename or delete your existing settings directory in order to avoid any file conflicts.
Copy your music directories to the new computer.
Start Mixxx.
If you’ve put the settings directory in the correct location Mixxx should not ask you for your music directories and all your settings should be as before.
Go to and Relink each of your music directories as described in Changing music directories.
Now, all your music files should be available, all your playlists, crates and your session histories be restored. A library rescan is not required. Configure a sound output and test if you can play all tracks as before. Note that this will obviously not include your external libraries (iTunes, Traktor etc.), you need to configure those again.
Known issues
If you migrated to another operating system, operating system version or another Mixxx version, the used audio decoders may have changed which may cause beatgrids and cue points to appear shifted, i.e. they are set off from the desired points in the audio stream. Unfortunately, there is no automatic fix available, yet. As of now you need to shift cues for each track individually with the cue shift buttons in the beatgrid editing controls section, see Waveform Displays.