Korg Forums

I am currently running a Kronos to Mainstage 3 (via USB) using the Setlist feature of the Kronos to change patches in Mainstage. This part works fine. However, I just added Setlist Maker on my iPad to the mix. While I can get the iPad to change programs on my Kronos Setlist, the program changes do not go through to Mainstage unless I physically touch the pad on the Kronos. Any ideas on why this is happening and how I might fix it?

Thanks in advance for your thoughts.

Gear:
iPad running Setlist maker
Griffin MIDI dock for iPad running MIDI out to Kronos MIDI in
Kronos running USB MIDI to MacBook Pro with Mainstage 3

dckerley wrote:I am currently running a Kronos to Mainstage 3 (via USB) using the Setlist feature of the Kronos to change patches in Mainstage. This part works fine. However, I just added Setlist Maker on my iPad to the mix. While I can get the iPad to change programs on my Kronos Setlist, the program changes do not go through to Mainstage unless I physically touch the pad on the Kronos. Any ideas on why this is happening and how I might fix it?

Thanks in advance for your thoughts.

Gear:
iPad running Setlist maker
Griffin MIDI dock for iPad running MIDI out to Kronos MIDI in
Kronos running USB MIDI to MacBook Pro with Mainstage 3

when you say the pads, are you talking about the setlist slots on the kronos?

I have experimented using Setlist Maker with Kronos Setlist and Ableton live for my soft synths. So different workflow and not having to deal with that extra pad push you asked about. But thinking through your existing setup, 2 options come to mind.
1 Use SetList Maker as a song list database to select a page in Kronos Setlist that has all the sounds for a song. Whether they be mainstage or Kronos. Select sounds In K Setlist as you do now.
2 use Setlist maker as both song list database and to send midi commands separately to main stage and Kronos . You would select your sounds on Setlist maker as song progressed ,
Hope this makes sense. I think your other setup duplicates some process unnecessarily.

My idea or suggestion would have something to do with a midi out vs a thru...

MIDI out has to come from button pushes on that machine. So you have that part correct. When you push buttons on the Kronos is goes MIDI OUT to your mainstage. But when you select sounds etc on the iPad it only gets sent to the Kronos then it stops. This is because in order for the iPad button pushes to be seen by mainstage you would have to have midi thru (from Kronos to mainstage) so the iPad midi data goes THRU the Kronos to mainstage.

I hope that makes sense. It's the first thing that came to my mind, but I guess it could be wrong. Try it and let me know what you discover.

The magic may be to change the order USB vs MIDI.
iPAD Setlistmaker via USB to Kronos, Kronos MIDI to Mainstage.
Here is a link to a guy on the setlistmaker site who does it this way.

http://forum.arlomedia.com/index.php?topic=724.0

regards,

Rockitman

Rockitman wrote:The magic may be to change the order USB vs MIDI.
iPAD Setlistmaker via USB to Kronos, Kronos MIDI to Mainstage.
Here is a link to a guy on the setlistmaker site who does it this way.

http://forum.arlomedia.com/index.php?topic=724.0

regards,

Rockitman

Ha - that's me


Yea - my setup is a little bit different now, but basically I use SLM to send program changes to the Kronos (thru setlist mode). Every slot is mapped to a combi. I then use the combi timbres to send program changes to everything else.

Right now, my setup is (mostly) similar, except that I have the iPad plugged into an iConnectMIDI4+ interface and send the program change messages through that (the Kronos is hooked up via MIDI cables). This extra piece of hardware allows me to use the iPad app Midibridge to do realtime routing and CC translations/remaps to different gear - basically allowing me to control anything with anything. Wheras before I could control everything from the Kronos, but I was limited with what I could do with the other gear.