Multiclient MIDI drivers still no go ?

[valis]

Imho the 'real' solution for the time being is to hang the hardare you need to address off of an interface that has multiclient midi support. Midi Yoke solutions are really not that hard either and if you have a multicore PC that isn't being pushed to 98% of its usage for your music it's likely the overhead for midi yoke is minimal (meaning you'll get a few ms delay from the size of the buffers, but the delay shouldn't change/swim/have jitter like it would back in the earlier p3/p4 days.)

I do agree that it's a proper request to send to Sonic|Core, but until such time as they've updated it you're going to have to do one workaround or another, no?

I personally only use the Scope midi ports for things that are scope related (like a set of faders or knobs used for scope stuff or to connect Scope to my 'primary' DAW machine for control) as the cpu-bound midi processing seems to have some bandwidth issues, *especially* with MidiQuest/Sounddiver type apps which will want to recieve and send a large amount of sysex/nrpn data. Sounddiver used to be just as effective at BSOD'ing my Scope rig (during the P4 era) as leaving Active Sensing running on a connected keyboard was.

[maky325]

You asked, i answered.Midi yoke will work for this..its free,it doesnt take more then 5 mins to understand and it will work perfekt.You can now go on and post how our solutions are worthless and we dont get what you are saying or you grab your balls squeeze em and get to work using the solutions posted.Or you maybe arent understanding the solutions.Seriously when you post for help keep your ego calm or you do look like an ass.
Oh and btw...midiquest is the problem here..or sounddiver.They do take the midi ports alone in standalone.You can load midiquest as a vst plugin to fix that.

Fluxpod i appreciate your input and i don't have problem with my ego. But last time i was reading this forum it was all about Scope. Somehow i was thinking that i don't need to write idiosyncratic instructions in which i am making detailed points that i am asking "what to do with multiclient midi issue WITHIN scope".

Now truly for the fact i know that you still don't know what the hell you are talking about. I already told you that i am not weekend user. I already said i did every possible combination. Now i know you have no experience at all IN THIS because in other way you would never said "Oh and btw...midiquest is the problem here..or sounddiver.They do take the midi ports alone in standalone.You can load midiquest as a vst plugin to fix that."

Helloooo!!! I am aware of that possibility but even so - YOU CAN'T MAKE ANY USE OF MIDI QUEST VST MODUL - YES EVEN VST SINCE YOUR HOST IS ALREADY USING THAT PORT TO SEND ACTUAL NOTES TO ACTUAL HARDWARE - MIDIQUEST WILL SAY THAT PORT IS ALREADY USED EVEN VST ONE - HELLOOOOO!!!!! Do you realize what nonsense you are speaking? Is it too much to say that this is happening only with Scope MIDI port?

While at the same time every other possible port CAN BE USED WITH MORE application at the same time. Yes, even that on my e-mu xboard 49, even that on my Edirol UM550, UM-880, Motu. Guys am i really forced to give that simple explanations?

I said that i am ready to learn if someone have advice on how to do it inside Scope. I am aware that my english is hilarious but somehow i see that even first time Alaska visitor here could understand that.

I even told (surprise) not to join if one does not know what the heck is MIDI multiclient driver. It's so simple! Instead of that i have ton or response from people which are completely missing my point and which are not having a clue on what they talk about. Not because they are dumb or something but because (i am guessing) of lack of experience. Just look at that. Only person which obviously see (i am guessing that he actually have hardware) what is all about is Valis. Thank you Valis for reasonable response(sounddiver working fine here). Everything rest is worthless (again, because of lack of experience)

Look at that list:

One advice is to buy another usb port exclusively for editor (while at the same time i don't know for any synth device in history which will accept 2X midi in but anyway - Gary is well known for positivity and for giving any kind of help)

One respone is midi Yoke. This seems that it could do the trick but from what i can see this is not confirmed. Even so i stated that i don't want to install additional software to make something to work.

Another one is telling me that my clients are wrong because they "can't distinguish what's coming down the pipe" - now that was complete flop - because if you read again this thread is all about Multiclient MIDI port. For Christ sake google for that before you make fool from your self. FYI same thing is happening inside Reaper, FL Studio, Cubase 5 and Cubase Studio 5. From my memory i can confirm it's the same thing inside Ableton and SX3. Oh wait...they are complete crap..Thanks man..

Look a this: "Scope's ports are not multiclient like MOTU's infernal antiquated approach" - Dude this is not Motu infernal antiquated approach. What the hell you are talking about? Why are you posting here in this thread? Multiclient MIDI ability is common thing for musicians. This is so common thing that brand names even don't advert it anymore. It is supposed to be like that. I am truly shocked with this response!

Guys I am not trying to be smartass but some of you obviously never used more then 2x or 3x dev. in MIDI rig. I am really amazed by the lack of experience and complete miss of my point. You know there are people which want to use software combined with hardware.

I am also positively surprised by number of people willing to help. That is fine but most of you (not all) have one big problem. You tend to be fanboys. That is fine and romantic but on the long run this could be a problem. Now when product is out and when there are some quirks, instead of reporting this to developers and pushing things in a nice way(supporting people) we have army of people which are participating in threads in which they don't know what they talk about, giving ridiculous advices at the same time. Above is clear example of this.

Scope platform have irreplaceable tools, one can not deny that, but it does have a lot of quirks still from the past. By being fanboy and silently denying/overlooking these problems you are shooting yourself in a head. This is not help to community and won't be anything helpful for sleepy staff at SC.

We have good people leaving from here, genuine developers leaving this place(and complete Scope platform)...i wonder are some aspects of this forum cause for this..

I am giving you quick instant solution. We should kidnap at least one SC employee and then we should burn it with flame thrower. We will have instant SC focus....ok that was a black joke...

Still..i am out of this thread. (i will post here if SC make some response)

[maky325]

my bad, i just thought you wanted it to work.

i don't know if such a driver is possible on this system or not. actually, i've have midi work both in samplitude and cubase at the same time, so i'm not sure exacly what makes the trouble. it seems like your editor should be able to choose which midi driver to use, so if the sequencer was holding on to one, the editor should be able to hold onto the other.

Gary this is a bit offtopic but care to elaborate how the hell you are running two application at the same time on Scope ASIO? I would like to know how can you do that.

[garyb]

i'm not running both apps on Scope asio.

i'm not against you getting what you want either. i wouldn't expect it to happen this week though, if it does. i'm just sayin'...reality....

but maybe it's a simple thing that S/C was never asked for before or thought about before or knew that they weren't multiclient before, and they'll just change a couple of characters of code and viola! an instant update in 15 minutes! i suppose it's possible.

i surely misunderstood the problem, but as to needing multiple inputs on a hardware synth if a seperate midi interface is used for the editor, a merge box would solve that. that's why such products are made. how about a patchbay? they can merge as well. i realize these things are work-arounds, but hey, it's a minor problem and nothing's every perfect in this world. if you have clients that can afford to care, they can afford to finance those minor expenses. an additional midi interface would be best for heavy sysex anyway. i'm not being dismissive or making light of your frustration, but i don't see that you have any choice but to do it one of the ways it will work(if any way does work) for right now.

[maky325]

i'm not running both apps on Scope asio.

i'm not against you getting what you want either. i wouldn't expect it to happen this week though, if it does. i'm just sayin'...reality....

but maybe it's a simple thing that S/C was never asked for before or thought about before or knew that they weren't multiclient before, and they'll just change a couple of characters of code and viola! an instant update in 15 minutes! i suppose it's possible.

i surely misunderstood the problem, but as to needing multiple inputs on a hardware synth if a seperate midi interface is used for the editor, a merge box would solve that. that's why such products are made. how about a patchbay? they can merge as well. i realize these things are work-arounds, but hey, it's a minor problem and nothing's every perfect in this world. if you have clients that can afford to care, they can afford to finance those minor expenses. an additional midi interface would be best for heavy sysex anyway. i'm not being dismissive or making light of your frustration, but i don't see that you have any choice but to do it one of the ways it will work(if any way does work) for right now.

Gary i am not saying you have anything against me. I was asking because i was interested is there such thing - working asio mode with two app at the same time. Since you said it in response above, i was thinking that you may know something(now i am wondering why you said it in the first place). Take my apology for cynical and not so easy understandable attitude.

Regarding Midi thing - Look it does have nothing with investing in another midi merge box or whatever. And i already have a patchbay(i said that few times) Look i'll try to explain one more time.

case 1:
Xite/Scope midi port - connected with (example) Roland d-550 - open your sound editor, pick up that same xite midi port, tweak sounds inside editor(or librarian), fine...Fire up any god damn sequencer in the world and it will say that scope/xite port can not be used (for sending notes if you like) since it is already used (by editor/librarian). Thus NOT Multiclient. Simple!

case 2:
Every other midi port i can think of (edirol, e-mu, motu, terratec, midex, even soundblaster audigy) - connected to Roland d-550, open editor/librarian,pick up that same XY port, tweak sound - working, now open sequencer - WORKING!

No any kind of error about already used port by another application. I can actually play my instrument via sequencer and at the same time i can tweak sound on hardware. Two app. (can be even more) are using same midi port to send various midi data such as cc,sysex etc. Really no big deal. This is called MIDI multiclient feature. However i would be truly shocked to know that i am the first one in Scope history to ask for such rudimentary feature in audio world. I doubt that i am the first one trying to truly utilize simple MIDI port in combination of SW-HW setup. Even so i am amazed that you guys are so calm about not having this in 1000 EUR price range gear (pointing to Scope pro but xite have same issue).

Maybe it's all about 15 lines of code fixed in 15 minutes (i doubt), i am not claiming anything. And i am not ditching SC either. I am amazed by some aspects of this forum.

This thread would be funny but it is sad before that..(this is not pointed to you).

[Fluxpod]

Have fun waiting forever on a fix.Pointless....

When you are tired of waiting go here.http://www.hitsquad.com/smm/programs/MIDIYoke_NT-XP/

[dawman]

Nice educational thread....
I was trying to figure out the advantages of having multiclient and since I have the MX8 for merging and filtering, the MIDI Solutions F8 for pedal assignments and SysEx strings to all of my hardware, and Wolf MIDI Tool Box and SpaceF's CC devices I don't see a need for this. I also have my KS88 Editor/Librarian ready to use, but I would have to re route to use the Editor, but I only need that to add more Performance presets.
Fortunately, I change all 8 templates manually that I use and have no need for MultiClient MIDI Drivers, but I think it would be a nice added feature for external patch editor/libraries.

It's too bad the D550 doesn't have the RGB ports that the S700 series sampler had. I had the D50/D70 for quite a while and I can see the advantage of MMD's for those.
Mpodrug you must understand that MMD features only are of use to keyboard guys, and not very many to be honest, that's why these engineer heavy guys here don't see the use.
And like Greg mentioned, I use a hardware sequencer and JLCooper MLC w/ PAR lamps and a dimmer pack occassionally and don't even need MMD's for that either.

Please keep us posted on your pregress with this.
But try to be a little more diplomatic w/ Holger. He is only trying to fix someone else's mess, and in no way is obligated, although he feels responsible at times.

[siriusbliss]

FYI... I'm using MIDIquest as a plugin in Ableton and Samplitude (JV1080, etc.) with no issues - IF you'd just TRY to load up multiple MIDI ports and/or TRY MIDI-OX to handle your configuration until S/C decides yes or no on multiclient.

But calling us dumbasses for not googling multiclient (when I already did - to confirm MOTU's UART issues that forced development of this in the first place way back when multiple MIDI I/O was not as popular), is just lame - since you refuse to try using the resources that are already there.

And I'm tired of guys that call us fanboys for merely recommending using what Scope has already available. SOME of us are pushing S/C behind the scenes to get things in this Release Candidate sorted out, rather than belabor the issue and complain and talk down to us for not fulfilling every possible feature request - as though we are responsible.

MIDI-OX does work, but you refuse to test it. Multiple ports DO work (if you can configure it properly), but you haven't tried it.

So, as I said, you're left either waiting on S/C, or getting it to work with what you already have available in Scope.

Greg

[garyb]

i'm still confused, and defininitely not trying to antagonize but,
why not just use say sequencer midi source and dest #2 or #3 for the sequencer in case 1 above? the data from sequencer midi source 1 and 2 and 3 and 27 can be merged in Scope if it needs to be. you can have 75 midi source and dest modules if you want and the software will see them all as individual interfaces. doesn't that work?

[Tau]

mpo, I have a DSI Evolver, which uses an editor, a Korg Z1, which uses an editor, a Wavestation SR, which uses an editor, an SY77 which uses an editor, and a few others too. I have a very basic USB 8 port ESI interface, which is not multiclient, and I use Live for sequencing. And Scope. I know what MIDI multiclient drivers are, and I have tried Midiquest, Sounddiver and a few Vyzex-based editors.

I have always had the same problem you have with the MIDI ports: can't use the same port for the editor and the sequencer, because the MIDI driver is not multiclient. Now, for the past, I don't know, 10 years or so, I have been using MIDIOx and MIDIyoke with absolute success. I can have Live sending notes to the DSI and have its editor open in another window and tweak the sounds in realtime. It seems to me that's what you want, and I'm pretty sure it's the best advice anyone here could give you.

As for Scope MIDI, the solution posted by Janni (and Gary, just above) is an elegant solution that doesn't require any tweaking in your sequencer, or any other app: one Seq MIDI source for the sequencer, another seq MIDI source for the editor, a Merger and a MIDI out to the Jomox which carries both signals. A SeqMID destination for the sequencer, another SeqMIDI dest for the editor, and a Merger before them to send the Jomox data to both apps. Each application can then grab its own Scope MIDI port.

This is as far as any user can go in providing a solution for the problem you posted here. What exactly were you expecting from us? You yourself know that Scope drivers aren't multiclient, so what were you expecting?

"Here, I have compiled this multi-client driver for Scope, feel free to use it" or "Oh my, oh my, WHY are there no multiclient drivers for Scope? WHY? WHY?".

Just take it easy, and try not to be so rude. People take time out of their lives to write and take pictures just to help you with a problem, and even if you're not willing to admit it, a few positive solutions have been provided. Now work with it, call S|C and wait a little until they can build new drivers. It's good if they do, but I really don't think it'll happen tomorrow.

As for the ASIO thing, don't you know that some ASIO drivers are multiclient? Haven't you seen the thread about the ASIO multiclient wrapper from Steinberg? It's been discussed recently, even though it's not a new thread. And that's how one could have two ASIO apps using the same Scope ASIO driver. Could, not can, I haven't tried it, and don't know anyone who has.

Cheers,

T

[dawman]

I like being called fanboy, but as the Brotha's would say......." Ya better watch dat boy shit."
Yes, Political Correctness demands the term " Fanman..".....
I must confess though I really miss the 3 x cards and 3 MIDI Source Modules + Dest.
I have work arounds though.
What I would love to see is OSC. Assaf has mentioned incorporating that in Scope would be awesome, which makes me think his new app might have it. Once S|C see's it's value we could possibly get MIDI in parallel with OSC which I would die for.
Even adding the MIDI 2 Specs would give us a huge dynamic benefit w/ velocity curves in audio and MIDI.
So this thread has served as a reminder for me to send an email after the next update, as I know they are in crunch time everyday.....

[siriusbliss]

OSC has huge potential. I'd love to see it happen.

So, how long has it been since the MIDI spec. was updated?

Greg

[siriusbliss]

...

As for Scope MIDI, the solution posted by Janni (and Gary, just above) is an elegant solution that doesn't require any tweaking in your sequencer, or any other app: one Seq MIDI source for the sequencer, another seq MIDI source for the editor, a Merger and a MIDI out to the Jomox which carries both signals. A SeqMID destination for the sequencer, another SeqMIDI dest for the editor, and a Merger before them to send the Jomox data to both apps. Each application can then grab its own Scope MIDI port.

This is as far as any user can go in providing a solution for the problem you posted here. What exactly were you expecting from us? You yourself know that Scope drivers aren't multiclient, so what were you expecting?...

+1
As stated....plenty of workable solutions already available...

Greg

[maky325]

Nice educational thread....
I was trying to figure out the advantages of having multiclient and since I have the MX8 for merging and filtering, the MIDI Solutions F8 for pedal assignments and SysEx strings to all of my hardware, and Wolf MIDI Tool Box and SpaceF's CC devices I don't see a need for this. I also have my KS88 Editor/Librarian ready to use, but I would have to re route to use the Editor, but I only need that to add more Performance presets.
Fortunately, I change all 8 templates manually that I use and have no need for MultiClient MIDI Drivers, but I think it would be a nice added feature for external patch editor/libraries.

It's too bad the D550 doesn't have the RGB ports that the S700 series sampler had. I had the D50/D70 for quite a while and I can see the advantage of MMD's for those.
Mpodrug you must understand that MMD features only are of use to keyboard guys, and not very many to be honest, that's why these engineer heavy guys here don't see the use.
And like Greg mentioned, I use a hardware sequencer and JLCooper MLC w/ PAR lamps and a dimmer pack occassionally and don't even need MMD's for that either.

Please keep us posted on your pregress with this.
But try to be a little more diplomatic w/ Holger. He is only trying to fix someone else's mess, and in no way is obligated, although he feels responsible at times.

Jimmy MMD is standar thing. D-550 was just an example but D-550 is rack synth anyway. No keyboard there. D-50 is the one with keys. But anyway front panel is tedious to use plus unit is far away from desk. MMD is used to control synths, samplers, FX, enything midi related. Really nothing keyboard only. Here is real world example:

Oberheim Matrix 1000 - there is no any kind of tweaking ability on the unit. You must use some kind of editor, plus take in account that i am not having all devices in front of me(just as in every other studio, you can't have anything at your fingertips). Matrix is few meters away in rack, connected with midi and standard I/O audio cables. To tweak sound one must use editor. Obviously scope can't make any use of this since it's not multiclient(please read explanation above). You see my point?

I am sure you have your own kung fu in your setup but you must realize that MMD is really rudimentary thing, available for even decade.

You can be sure that i'll post my findings with SC. I really don't have to be more or less polite with Holger. I know him and beside that i am not saying this is some major show stopper. I am sure it can be worked out. I am revolted and cynical by (still coming i see) large amount of really worthless response from people which are clearly and obviously lacking some experience in controlling outboard gear within standard studio MIDI setup. It's their shame anyway.

See you.

[dawman]

Well I kind of figured the D50 had keys. But we all needed our Librarian/Editors back then because the GUI's were minature LCD's and a real PITA. Roland had the best idea ever by using RGB connectors for CRT's etc. The Yamaha card I used for a while had MultiMIDI and was necessary if I wanted to use the TX816 properly. I use to have the QX-1 controlling all of that stuff before the cards were available.
I will send an email and see how much effort is needed to add/fix this,and also inquire about OSC. But in all honesty, I believe they are tackling some bigger issues, but it doesn't hurt to try.

Cheers.

[maky325]

mpo, I have a DSI Evolver, which uses an editor, a Korg Z1, which uses an editor, a Wavestation SR, which uses an editor, an SY77 which uses an editor, and a few others too. I have a very basic USB 8 port ESI interface, which is not multiclient, and I use Live for sequencing. And Scope. I know what MIDI multiclient drivers are, and I have tried Midiquest, Sounddiver and a few Vyzex-based editors.

I have always had the same problem you have with the MIDI ports: can't use the same port for the editor and the sequencer, because the MIDI driver is not multiclient. Now, for the past, I don't know, 10 years or so, I have been using MIDIOx and MIDIyoke with absolute success. I can have Live sending notes to the DSI and have its editor open in another window and tweak the sounds in realtime. It seems to me that's what you want, and I'm pretty sure it's the best advice anyone here could give you.

As for Scope MIDI, the solution posted by Janni (and Gary, just above) is an elegant solution that doesn't require any tweaking in your sequencer, or any other app: one Seq MIDI source for the sequencer, another seq MIDI source for the editor, a Merger and a MIDI out to the Jomox which carries both signals. A SeqMID destination for the sequencer, another SeqMIDI dest for the editor, and a Merger before them to send the Jomox data to both apps. Each application can then grab its own Scope MIDI port.

This is as far as any user can go in providing a solution for the problem you posted here. What exactly were you expecting from us? You yourself know that Scope drivers aren't multiclient, so what were you expecting?

"Here, I have compiled this multi-client driver for Scope, feel free to use it" or "Oh my, oh my, WHY are there no multiclient drivers for Scope? WHY? WHY?".

Just take it easy, and try not to be so rude. People take time out of their lives to write and take pictures just to help you with a problem, and even if you're not willing to admit it, a few positive solutions have been provided. Now work with it, call S|C and wait a little until they can build new drivers. It's good if they do, but I really don't think it'll happen tomorrow.

As for the ASIO thing, don't you know that some ASIO drivers are multiclient? Haven't you seen the thread about the ASIO multiclient wrapper from Steinberg? It's been discussed recently, even though it's not a new thread. And that's how one could have two ASIO apps using the same Scope ASIO driver. Could, not can, I haven't tried it, and don't know anyone who has.

Cheers,

T

Hi Tau! Thanks for your input! I'll try some of these solutions and if i stuck in some problems i will PM you for detailed help. Regarding ASIO I've never heard for such thing. Could you please point where did you hear that because i never heard for real multiclient ASIO wrapper from Steinberg. I am browsing their website right now and it's not even in their knowledgebase, not a word. I know for Asio4all but that is not anything Steinberg related plus it is buggy sometimes and still it's not anything about running two application at the same time. It is wrapper which will wrapp around your current windows driver, providing you with some sort of ASIO functionality. Pretty neat for notebooks with built in cards without asio driver but...

I've never been able to run two application at the same time, sharing one ASIO driver. Not with Scope, RME, Terratec or E-MU (yep, i changed a lot of cards). What do you mean on ASIO being multiclient? Can you elaborate because it could be pretty useful if it's true..

Thanks

[voidar]

http://forums.planetz.com/viewtopic.php?f=19&t=25685

[Tau]

mpo, feel free to ask. MIDIYoke and MIDIOx have been around for a long time, I had them in Win98, and was still using them in XP, after I moved my Scope cards to another computer. I am currently installing and tweaking the XITE, and most of my hardware is disconnected, so I can troubleshoot without having too many variables. I expect it all to be working again before the end of the year, and be able to help you more by then.

When I had Scope in the main computer, I did exactly what Janni posted and showed you in the first page of the thread: just create separate MIDI Seq modules for each editor you use, and merge their outputs with the MIDI seq modules used for the sequencer, before Scope HW MIDI destination. Disable those ports in the Sequencer, so that the editor can grab them, and it will work.

In practice, you won't be able to select the exact same port for the sequencer and the editor. Let's say you have Seq MIDI source 1 as your Sequencer MIDI port, and by choosing that, you can output notes to the Jomox (via SeqMIDI Src-> Hw MIDI dest). You create another SeqMIDI source (2), and have the editor use that, just as if it was a different MIDI driver. Then, you merge both Seq MIDI Src and send the output to the HwMIDI dest. This way, you can have the one MIDI port outputting both apps data. Do the same for Seq MIDI dest, connect the Hw MIDI source to both Seq MIDI destinations (no need to merge, as one out can feed any number of ins), and use SeqMIDI dest 1 for the sequencer (recording MIDI output from the Jomox), and SeqMIDI dest 2 for the Editor (feeding back Sysex). To make things even neater, insert a MIDI filter before SeqMIDI source1 to stop Sysex data from going to the Sequencer.

It may sound and read a little confusing, but in practice it's not that complicated. It worked here, and It'll work there. Just take a good look at Janni's picture.

I tried the Midiquest thing with the VST inserts, but it never seemed to work as well as using the individual editors, which is a shame, because it is a very good idea. But I don't need any more frustration, and after a couple of weeks of trying, I just gave up. MIDIyoke and MIDIOx are a lot simpler than that, believe me...

The MC ASIO thread is indicated in the above reply. I still haven't tried it.

Cheers,

T

[maky325]

mpo, feel free to ask. MIDIYoke and MIDIOx have been around for a long time, I had them in Win98, and was still using them in XP, after I moved my Scope cards to another computer. I am currently installing and tweaking the XITE, and most of my hardware is disconnected, so I can troubleshoot without having too many variables. I expect it all to be working again before the end of the year, and be able to help you more by then.

When I had Scope in the main computer, I did exactly what Janni posted and showed you in the first page of the thread: just create separate MIDI Seq modules for each editor you use, and merge their outputs with the MIDI seq modules used for the sequencer, before Scope HW MIDI destination. Disable those ports in the Sequencer, so that the editor can grab them, and it will work.

In practice, you won't be able to select the exact same port for the sequencer and the editor. Let's say you have Seq MIDI source 1 as your Sequencer MIDI port, and by choosing that, you can output notes to the Jomox (via SeqMIDI Src-> Hw MIDI dest). You create another SeqMIDI source (2), and have the editor use that, just as if it was a different MIDI driver. Then, you merge both Seq MIDI Src and send the output to the HwMIDI dest. This way, you can have the one MIDI port outputting both apps data. Do the same for Seq MIDI dest, connect the Hw MIDI source to both Seq MIDI destinations (no need to merge, as one out can feed any number of ins), and use SeqMIDI dest 1 for the sequencer (recording MIDI output from the Jomox), and SeqMIDI dest 2 for the Editor (feeding back Sysex). To make things even neater, insert a MIDI filter before SeqMIDI source1 to stop Sysex data from going to the Sequencer.

It may sound and read a little confusing, but in practice it's not that complicated. It worked here, and It'll work there. Just take a good look at Janni's picture.

I tried the Midiquest thing with the VST inserts, but it never seemed to work as well as using the individual editors, which is a shame, because it is a very good idea. But I don't need any more frustration, and after a couple of weeks of trying, I just gave up. MIDIyoke and MIDIOx are a lot simpler than that, believe me...

The MC ASIO thread is indicated in the above reply. I still haven't tried it.

Cheers,

T

Thanks guys! Regarding Midiquest - i was experiencing same situation as you and i found a solution (not documented anywhere). The thing is that you must load one main Midiquest VST.dll with nothing at all. Empty shell. Then if you load second which is (for example) registered in Midiquest main app to your hardware (example) JD-990 - that Same Midiquest VST JD990.dll will work then. You will be able to record everything in your seq, including automation data, patch mangling etc..If you unload empty shell, somehow everything seems to stop

also take in account that midiquest works with some hardware superb, with some not so good (buggy...). For example i can control every god damn Roland synth but i could not make anything Oberheim related to work. It always worked partly. But you have Sounddiver for this. I agree it's a shame. Midiquest have nice potential on paper but in reality it is a lottery..

Thanks anyway

[siriusbliss]

mpo, feel free to ask. MIDIYoke and MIDIOx have been around for a long time, I had them in Win98, and was still using them in XP, after I moved my Scope cards to another computer. I am currently installing and tweaking the XITE, and most of my hardware is disconnected, so I can troubleshoot without having too many variables. I expect it all to be working again before the end of the year, and be able to help you more by then....

Yes, as stated...in the interim- until you hear from Holger re: multiclient... MIDI-OX and/or multi-MIDI port setups in Scope DO work when using editors in parallel.

MIDI-OX (very low overhead software) is also good for tricking your host or whatever to see USB ports as extra MIDI ports. I use this for padKontrol and also for Korg nanocontrol for emulating external media controllers in a theater setting.

Greg