Hello,
I am currently using RME Fireface audio interface.
How can I run the Roland driver (SY-1000) to access the Hex signal and the RME fireface on a Windows PC ?
Running the Roland device as my main and only interface would not be my favorite solution.
So, SY1000 ASIO driver for input, and RME ASIO driver for output?
As many ASIO drivers are not multi-client, itās not generally possible right now, without making an aggregate device (which would run with additional latency, best case). However, this kind of things is exactly something weāve been working on the last weeks, and (probably) going to be part of the next update.
Another option is to buy a USB compliant interface like the IKM iRig-USB that doesnāt need a dedicated ASIO driver and is still very fast. This you can run in parallel with the SY-1000 on a win system.
hereās one more option - use mg3hex standalone with the sy-1000 and run your vstās in a daw connected to the rme. use tools/caster to transfer audio and midi or a virtual midi port if you donāt need audio.
will we be able to run the interfaces at different sample rates? that would be real nifty.
@kimyo, you describe my hopes exactly 
Iām in Studio One, which canāt yet process MPE from VST MG3 internally, so I have to rely on standalone MG3 and Loopmidi.
I have 2 audio interfaces which unfortunately are not multi-client capable and also have different audio sample rates.
Your suggestion would be very helpful!
Thanks Kymio for the creative solution. I am working on this. I have set mg3 to use the sy-1000. No hex for now. it receives the signal.
When you say āuse mg3send to transfer audioā could you explain a bit more.
I have not been able to locate this mg3send tool or to find a way to send mg3 output to use in Live or Gig Performer (basically second application running on the RME interface).
Best regards
i misspoke, sorry. the module you want is called ācasterā. it is in the ātoolsā group.
you would put that on the standalone copy of mg3.
in the daw copy of mg3 select the tracker on the far right, it is called āmg3 networkā.
fyi: the future of mg3 network hasnāt been established yet.
Thanks Kimyo for the detailed informations.
I successfully transfer MIDI information from the standalone mg3hex to Ableton Live using this method.
Same precision as in the standalone version and did not felt any added latency.
Impressive results and innovative approach.
iām glad to hear it is working.
you should be able to run the standalone copy at 64 samples if you like, or possibly even 32.
splitting the input and output over two interfaces seems to enhance performance in my case, please let us know if this is also your experience.
part of it is latency-based, but also it feels like the robots in the mg3 factory arenāt operating near their limits, as it sometimes does when using a single interface.
Maybe off topic from the config question.
Where can I define the transmit channel that is sent by the tracer in MG3Hex.
Ideally per string.
Right now whem I use a Midi Monitor it seems to float even for each note.
for fixed midi channel per string use midi 1.0 multichannel in the midi output module.
mpe uses āfloatingā channel assignment, ie: note1 = channel 1, note 2 = channel 2, regardless of string.
Working on this. The behavior seems to be different in Ableton Live from Gig Performer.
In ableton Live I had different results at different time. At first using a multi timbral synth like Spectrasonics Omnisphere, I was receiving signals on channel 2 to 7 in MPE or MIDI 1.0 Multichannel. Later all signals were on Midi channel 1 whatever the mode I used in the Midi Output of the MG3 VST.
Is there anything to set on the standalone MG3 Midi also to transmit the proper output mode to MG3 VST ?
In Gig performer I could monitor the changes as I was switching from one mode to the other in MG3 VST receiving the Midi tracer from the standalone.
In Ableton, Maybe the MIDI track receiving the signal from MG3 is acting differently. when I select the MG3 as Midi source there is no midi channel selector. I used the Midi monitoring tool in Ableton but not sure how accurate this tool is.
Still in the early stage of learning all this and integrating this to my workflow. For your information, at the moment I normally use BossGM800 for Guitar to MIDI conversation with very satisfying results in both Poly and Mono mode. Looking forward to get a better hold of MG3. Good work. There is so much new stuff coming from MG2.
Welcome to Ableton Liveās world of messed-up MIDI nonsense.