Kronos Editor and DAW Midi (No plugin)

[tajna92]

Since we all know that Kronos editor is in 32 bit only and in order to get 64bit VST version, we need to buy Midi Quest Pro which costs almost as quarter of a Kronos itself, it's just not worth it...

I was trying to use my DAW (studio one) and Kronos Editor side by side (at the same time) and it did not work as it seems that the editor or the daw take exclusive control of midi ports.

Is there any workaround for this??

[Bitflipper]

I doubt this has to do with 32- vs. 64-bit code. The MIDI interface doesn't care about that. More likely, it's the interface driver that wants to be owned by one application at a time.

I'm stepping a little beyond my own expertise here, so much of this is speculation. But I do know that for audio ASIO cannot be shared by multiple programs. Because I am on Windows, I have WDM/KS and WASAPI as alternatives to ASIO so if I need audio from two applications (e.g. watching a YouTube tutorial while following along in my DAW) I can switch one of those drivers instead.

Given that the ASIO driver also handles MIDI I/O, I would surmise that the same limitation applies to MIDI data as well. Try going into S1 and change the driver model. Sorry, I am not a Studio One user so I can't tell you how to do that, but it's easy in my DAW of choice so I assume it's similarly easy in any other DAW.

[Bachus]

Since we all know that Kronos editor is in 32 bit only and in order to get 64bit VST version, we need to buy Midi Quest Pro which costs almost as quarter of a Kronos itself, it's just not worth it...

I was trying to use my DAW (studio one) and Kronos Editor side by side (at the same time) and it did not work as it seems that the editor or the daw take exclusive control of midi ports.

Is there any workaround for this??

There are wrappers that allow you to use a 32 bit vst in a 64 bit only daw.