Start your musical journey by discovering amazing songs and artists
Loading devices…
No output devices found. Use a supported browser (e.g. Chrome) for device selection.
Names may show as "Output 1", "Output 2" unless this site has microphone access.
Hi folks Litlle question... Does anybody uses the new Midi Quest XL yet & if so, how did you configured it on your system? Problem I have is 'known' I'd say... I can't use Midi Quest as a vsti in Cubase there my driver of my midi ports are allready in use by Cubase... I think the workaround is to configure it with the MidiYoke virtual patchcabel & Midi-OK to configure the routing... I was trying to get my Korg N1R to work via midiquest as a vsti in cubase, but I don't seem to get it configured right... The two programs independly ain't a problem... but both of them at once sure is... (Driver already in use...) I seem to have regurlay echo feedback, that is when the input & output is configurred to the same port, but it does this kinda on itself, I can't seem to configure it elsewise.. Googled it, found some directions, but they were al so vague.... Been screwing around yesterday for a couple of hours, but without any luck... Had it kind of working yesterday in Cubase, but I couldn't record any decent midi notes with my keyboard.... It screwed them all up... ANd there was some kind of delay... My keys are connected via usb, my Korg via midi i/o to my soundcard... I can acces & configure it independently, but not together with Cubase... I can give more info when needed... Thanks in advance for your help/tips/links...
i used it for my juno a while, also in cubase sx & its very tricky indeed to setup properly.From what i understand from your post midiquest works in standalone but not as vsti, right? My guess is that there could be 2 problems: 1: Your midi-interface cant handle the midi-yoke routing (wich would surprise me, but you never know )Have you updated the driver for your midi recently? 2: The problem lies with midiquest itself. Its a hassle to route the appropriate ins & outs as it is & the configuration for standalone mode is different than when used in cubase.I suggest building 2 "studio's" in midiquest; one with config for standalone, one to work in cubase. It also took me a while to get things running in cubase and lately i have been avoiding midiquest & am using mixmaps i found on the web for my hardware. Less fiddling around & also less (to zero) crashes when changing parameters as the song is playing
Good luck ;-)
Couple more hours of screwing around with it & still no luck... I think there's a bug in the version I have... At least, that's the only possibillity that stays over after my trial & elimination round with that program.. Even when I identify in one programme (midi quest) that it should take other drivers then my hdsp midi out, it keeps on giving the message that that driver is allready 'taken' while opening the Korg or MidiQuest vsti in cubase... Or there has to be some sort of programm that uses my main midi out channel... (Pluging e.g.) Disabled midi devices, & all things related, to be sure nothing could use the hdsp midi out driver... (Even routed my standard midi out in audio properties to a midi yoke channel, to look whichone Cubase would take when opening.... Always the hdsp midi out as standard port, cause I can't open a second one..) Things I can still do / have done:
Question(s):
I have / use a mixmap in cubase with/from my Korg N1R, BUT... It only always you to change presets, but I'd also would like to use the fx (& other settings) from my Korg in Cubase... (Unless there is a way?) I'm not that familiar experimenting with those mixmaps & midi devices... Thx for your reply Hecticc... I don't know if you still have midi quest installed with midiYoke? If so, I sure would like to see a screen shot of the routing you've done in midi-OX :) Just to be sure I have nothing to do with the problem ;) Grts!
Beta — data may be reset. Beta