Seems it was largely a Mixxx one as there was no logging of issues in the Mixxx log (it showed the midi data being sent, and no errors I could find). Until then, I had the _QLC_ controller showing in Mixxx and the MIDI throughput 0 showing in QLC, but the midi events weren’t going anywhere it seemed (kmidimon was only showing subscribes and unsubscribes, and it wasn’t clear if this was a kmidimon issue, a QLC one, a linux kernel/module one or a Mixxx one)… Just updating this because it took me a couple of hours to track down that I needed to run Added a cue list with a sequence with infinite duration per step to the virtual console and connected the ‘Advance cue’ command to the BPM ‘button’ and then everything goes kind of automatic. I haven’t researched the tempo and MTC features, nor the VU metering.Īnyway: this worked. Anyway, this made it easy to get the correct notes for the beat. I named the D3 event BPM and the other one BPM2, both are ‘button’ actions. Midi Monitor said D2 and E2, but the wizard found D3 and E3 as the keys. Using the wizard in the script window (and starting mixxx with a song) I simply extracted the two notes that mixxx is spawning. ![]() Then I followed the guidelines given on github for QLC+. ![]() The script by Michael can be attached to this controller. Now restarting MIXXX adds the BUS 1 controller as an IAC controller. Here a virtual midi cable can be created in the block IAC Control. Instead of using an additional app like midipipe to provide the link through a virtual midi cable, I used the MIDI studio (audio/midi configuration, Window-menu and then select the midi studio). If can contribute, maybe by writing howto’s or other forms of documentation, please let me know. Anyone who has such a configuration up and running? Any help would be appreciated. Is this maybe because of a bug in the build I’m using? Or isn’t the script (2015_03_01) compatible at this moment? Note that the portname showing in Mixxx is the ‘ output’ port for Midipipe.Īs an alternative I tried MIDI Patchbay 1.0.3 In Midipipe I defined a pipe with just an input and an output. To be able to patch through the MIDI, I use Midipipe 1.4.6 and as a monitor for peeking into the MIDI data, I use Midi monitor 1.3.2. I assume this is a JACK feature people are referring to, and as such it is not the way it should work on OS X. I wasn’t able to bring up a “MIDI Through” port in Mixxx, even though I’ve started with the -developer command line option.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |