Your MIDI setup is important in this situation. Let's say we have 2 hardware synths and a computer. And a heads up: you mentioned clock data - Mixcraft doesn't respond to external clock data.
Synth 1 is my master
Synth 2 is slave 1
Computer is slave 2
The goal is to do everything on the master and have the slave devices respond.
Master set to omni out all - data is sent on all MIDI channels
Slave 1 set to receive on Channel 1
Slave 2 set to receive on the rest of the channels or a dedicated channel
I would generally try and keep tight channel control so I know what data I'm expecting on what hardware device, but you can feel this out according to your situation and look at my suggestions as just that: suggestions
The cable connection is as follows:
Master --> MIDI out --> MIDI in Slave 1 --> MIDI thru --> MIDI in Slave 2
or more specific to your situation:
Casio --> MIDI out --> MIDI in roli49 --> MIDI thru --> MIDI in computer (Mixcraft)
Whatever you do on the Master going to channel 1 will be picked up on Slave 1 on channel 1. That means you can have Slave 1 play its own sounds if you want. Also pedal depresses CC changes etc. Turn off local playback to avoid having the sound generator play the sounds from Slave 1.
Whatever you do on the Master is passed through Slave 1 to Slave 2. I'm specifically talking about MIDI data and not audio.
So if you step on the sustain pedal on Master, both Slave 1 and Slave 2 will pick it up. However, this is a one direction operation from the Master. If Slave 1 doesn't have a MIDI thru (or the MIDI out can't be set to MIDI thru on the hardware itself) what you play on Master won't be passed to Slave 2.
Older and top end MIDI equipment had/has at least 3 dedicated ports IN OUT and THRU. Modern MIDI devices often only have a USB or a single MIDI IN and a combined OUT/THRU. With three port MIDI devices you might be able to have cables running in both directions but always ending on Slave 2 as the final MIDI thru. The problem there is you said you don't want to layer the sounds from both keyboards but to go in both directions, you'd have to have the local sound generator off for the particular synth you don't want to layer - so it gets complicated.
There are are other configurations but the most direct through hardware is Master > Slave > Slave like I listed above.
You can get complicated and use something like MIDI Ox and loopMIDI to create a series of virtual ports and then have certain events take place and only respond when the Pedal is depressed. It can get even deeper with SYSEX messages where you can identify the hardware and have MIDI ox only do certain things when specific hardware is transmitting. There are a lot of options.
Synth 1 is my master
Synth 2 is slave 1
Computer is slave 2
The goal is to do everything on the master and have the slave devices respond.
Master set to omni out all - data is sent on all MIDI channels
Slave 1 set to receive on Channel 1
Slave 2 set to receive on the rest of the channels or a dedicated channel
I would generally try and keep tight channel control so I know what data I'm expecting on what hardware device, but you can feel this out according to your situation and look at my suggestions as just that: suggestions
The cable connection is as follows:
Master --> MIDI out --> MIDI in Slave 1 --> MIDI thru --> MIDI in Slave 2
or more specific to your situation:
Casio --> MIDI out --> MIDI in roli49 --> MIDI thru --> MIDI in computer (Mixcraft)
Whatever you do on the Master going to channel 1 will be picked up on Slave 1 on channel 1. That means you can have Slave 1 play its own sounds if you want. Also pedal depresses CC changes etc. Turn off local playback to avoid having the sound generator play the sounds from Slave 1.
Whatever you do on the Master is passed through Slave 1 to Slave 2. I'm specifically talking about MIDI data and not audio.
So if you step on the sustain pedal on Master, both Slave 1 and Slave 2 will pick it up. However, this is a one direction operation from the Master. If Slave 1 doesn't have a MIDI thru (or the MIDI out can't be set to MIDI thru on the hardware itself) what you play on Master won't be passed to Slave 2.
Older and top end MIDI equipment had/has at least 3 dedicated ports IN OUT and THRU. Modern MIDI devices often only have a USB or a single MIDI IN and a combined OUT/THRU. With three port MIDI devices you might be able to have cables running in both directions but always ending on Slave 2 as the final MIDI thru. The problem there is you said you don't want to layer the sounds from both keyboards but to go in both directions, you'd have to have the local sound generator off for the particular synth you don't want to layer - so it gets complicated.
There are are other configurations but the most direct through hardware is Master > Slave > Slave like I listed above.
You can get complicated and use something like MIDI Ox and loopMIDI to create a series of virtual ports and then have certain events take place and only respond when the Pedal is depressed. It can get even deeper with SYSEX messages where you can identify the hardware and have MIDI ox only do certain things when specific hardware is transmitting. There are a lot of options.
Statistics: Posted by cactus-head — Mon Jan 08, 2024 5:00 pm