Has anyone tried these iOS apps/bundle to route MIDI and audio to and from their idevice in Tracktion (I'm using Windows 10)? I can't for the life of me figure it out and I've spent hours so far. The best I can do is to play audio on the device and have it record in Tracktion, but it seems nigh impossible to have it send MIDI to the idevice and then have it capture the audio - as if it's a virtual synth (which it claims is easy to do).
Seems a shame to waste the $11 or so I spent on the apps when the promise seems so great and I read of how awesome it is for some people out there on the Internet.
I couldn't get it working in Tracktion on my Mac, either. Anyone else have success???
Studiomux/midimux in Tracktion?
-
vitocorleone123 vitocorleone123 https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=333504
- KVRAF
- 2504 posts since 30 Jun, 2014 from Pacific NW
-
vitocorleone123 vitocorleone123 https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=333504
- KVRAF
- Topic Starter
- 2504 posts since 30 Jun, 2014 from Pacific NW
Thanks in part to a little help on the audiobus forums I was inspired.... here's what I posted over there after someone gave some pointers.
-----
Ok. I found ONE way to accomplish my goal (you got me thinking about some other routing). So if I use rtpMIDI to send MIDI over wifi to trigger the synth, I can use audiomux to then capture the audio. Not sure of the latency yet, but it seems totally "ok" at the moment.
To make this work in tracktion, and I literally just did this so will be exploring other ways or alternatives (if any exist), I dragged the audiomux generator vst into a track, left the track destination as is (default audio), and then loaded a tracktion INSERT plugin, placed before the audiomux generator vst. In the Send Device drop down I selected my rtpMIDI desination and left the Return Device as (maybe there's a better choice?). In the idevice instrument, I select the rtpMIDI as the input and leave the output as whatever - and I'm running audiomux on the device as well, of course.
Now it seems I can play my USB keyboard (track input) and it gets routed over wifi to my idevice, plays the synth, and the audio gets routed via lightning cable back into the computer and captured by the generator plugin. I can record the MIDI notes I play and then it'll play back. Rendering does seem to require bouncing to a new track, meaning the track output is set to a different track that can then be rendered before exporting the whole thing as an mp3 (for example).
---
It could be that the app(s) I currently have don't support IAAP MIDI over the lightning cable, which is why I wasn't able to send MIDI over the cable rather than over wifi.
-----
Ok. I found ONE way to accomplish my goal (you got me thinking about some other routing). So if I use rtpMIDI to send MIDI over wifi to trigger the synth, I can use audiomux to then capture the audio. Not sure of the latency yet, but it seems totally "ok" at the moment.
To make this work in tracktion, and I literally just did this so will be exploring other ways or alternatives (if any exist), I dragged the audiomux generator vst into a track, left the track destination as is (default audio), and then loaded a tracktion INSERT plugin, placed before the audiomux generator vst. In the Send Device drop down I selected my rtpMIDI desination and left the Return Device as (maybe there's a better choice?). In the idevice instrument, I select the rtpMIDI as the input and leave the output as whatever - and I'm running audiomux on the device as well, of course.
Now it seems I can play my USB keyboard (track input) and it gets routed over wifi to my idevice, plays the synth, and the audio gets routed via lightning cable back into the computer and captured by the generator plugin. I can record the MIDI notes I play and then it'll play back. Rendering does seem to require bouncing to a new track, meaning the track output is set to a different track that can then be rendered before exporting the whole thing as an mp3 (for example).
---
It could be that the app(s) I currently have don't support IAAP MIDI over the lightning cable, which is why I wasn't able to send MIDI over the cable rather than over wifi.
-
vitocorleone123 vitocorleone123 https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=333504
- KVRAF
- Topic Starter
- 2504 posts since 30 Jun, 2014 from Pacific NW
So it turns out that it's easiest to get studiomux working if you first load audiobus 3, then add studiomux to it and launch it from there, and only use audiobus 3. Some AUv3s don't like to be played over network midi, so i use audiobus3 MIDI section to add network midi as the input and the troublesome synth(s) as the receiver of the midi. For example MiniMoog Model D.