Hi there,
I am bit lost when it comes to how to use the Kronos in my normal sequencing/VST environment. I am using Cubase and my dream would be able to use the Kronos as a VST plugin and have its audio transferred via USB into my sequencer.
However currently the only thing I have figured out is to record the analog audio output of the Kronos into my sequencer (cubase), so wondering if there is a more elegant way of integrating my Kronos into my sequencing environment.
Does anybody have any experience with this?
Help much appreciated!
Recording Kronos in your sequencer
Moderators: Sharp, X-Trade, Pepperpotty, karmathanever
-
- Posts: 31
- Joined: Sat Jan 15, 2011 9:53 am
Using the Kronos as a plugin should be possible when the editor is released. I hope this will happen in the next few weeks. If you use a Mac, then you can already use your Kronos as an audio interface without any additional drivers etc. If you use Windows, it might work by using Asio4All (just google) but I didn't thy this yet.
- jeebustrain
- Platinum Member
- Posts: 1284
- Joined: Mon Jan 24, 2011 10:08 pm
- Location: In a Roger Dean painting
asio4all works nothing better than OK - I can record stereo audio just fine with it, but when I try to use to, say, run a VST instrument on the audio interface, I get all kinds of pops, clicks, and distortion, plus is spikes the CPU on my netbook (whereas the USB Fast Track Pro runs the same soft synths perfectly).Knightshift wrote:Using the Kronos as a plugin should be possible when the editor is released. I hope this will happen in the next few weeks. If you use a Mac, then you can already use your Kronos as an audio interface without any additional drivers etc. If you use Windows, it might work by using Asio4All (just google) but I didn't thy this yet.
There have been a few threads about this (one of them started by me). Dan from Korg chimed in at one point to clarify that on Windows it's only supported as a WME interface - the thread kind of died though with several of us speculating that the upcoming plugin release might alleviate this.
::: Korg Kronos 88 ::: Alesis Fusion 8HD ::: Kurzweil PC361 ::: Roland V-Synth ::: DSI Prophet 12 ::: DSI OB-6 ::: Korg Prophecy ::: Moog Micromoog ::: Yamaha CP-30 ::: Alesis Andromeda ::: Moog Sub37 ::: Sequential Prophet 600 ::: Korg MS2000BR ::: GSI Burn :::
My Music
My Music
KLF has a Wiki on recording your Korg keyboard to a DAW.
The article is for M3, but it's the same for Kronos:
http://karma-lab.wikidot.com/korg-m3:re ... sequencers
The article is for M3, but it's the same for Kronos:
http://karma-lab.wikidot.com/korg-m3:re ... sequencers
Lou
-
- Posts: 5
- Joined: Mon Oct 31, 2011 12:32 pm
Thanks for the feedback gentlemen. I cannot really switch drivers, since all my other VSTs are using the drivers of my soundcard. So what I am trying to figure out is essentially:
1. How can I control Kronos from my sequencer (vst? plugin editor?)
2. How can I record Kronos into my sequencer (usb? analog?)
3. How can I use it as a multi-timbral unit in my sequencer and how can my sequencer remember the setup?
I am using Cubase 5.5 if that helps.
Deep appreciations for all the help - really useful.
1. How can I control Kronos from my sequencer (vst? plugin editor?)
2. How can I record Kronos into my sequencer (usb? analog?)
3. How can I use it as a multi-timbral unit in my sequencer and how can my sequencer remember the setup?
I am using Cubase 5.5 if that helps.
Deep appreciations for all the help - really useful.
why not do it the old fashioned way....record the Kronos as simple midi. Edit the midi until you have what you want. Then record the audio of Kronos while the midi is playing back. Mute the midi track (but save it in case you want to make an edit later in your project). Done.
I've done it this way for 20 years. Its fast, simple, and direct, and doesn't bog you down with too much work flow.
I've done it this way for 20 years. Its fast, simple, and direct, and doesn't bog you down with too much work flow.
http://soundcloud.com/ronf-3/sets/ronf-music
https://www.youtube.com/channel/UCr1zAK ... LQZrUYGPQA
Favorite Gear: Kronos 61, M3, Z1, Radias, KPro, KP3, Moog Voyager, Foogers, Virus TI, Jupiter 80, Integra7, GAIA, SPD-30, Kiwi 106, RE-201, MC808, RC505, MV8800, DSI P6 and OB6 and P12, Ensoniq SQ80, EMU MP-7, Eventide H7600, Eclipse, SPACE, Pitchfactor, Timefactor, Looperlative LP-1, Axe FX Ultra, Nord Modular, DSI Tetra, Tempest, PEK, JDXA, Eurorack Modular, Octatrack, MDUW, Monomachine, A4, RYTM, Waldorf Q Phoenix, MWXTk, Blofeld, TR8.
https://www.youtube.com/channel/UCr1zAK ... LQZrUYGPQA
Favorite Gear: Kronos 61, M3, Z1, Radias, KPro, KP3, Moog Voyager, Foogers, Virus TI, Jupiter 80, Integra7, GAIA, SPD-30, Kiwi 106, RE-201, MC808, RC505, MV8800, DSI P6 and OB6 and P12, Ensoniq SQ80, EMU MP-7, Eventide H7600, Eclipse, SPACE, Pitchfactor, Timefactor, Looperlative LP-1, Axe FX Ultra, Nord Modular, DSI Tetra, Tempest, PEK, JDXA, Eurorack Modular, Octatrack, MDUW, Monomachine, A4, RYTM, Waldorf Q Phoenix, MWXTk, Blofeld, TR8.
It would be nice to have a simple Cubase patch list.
I miss the days of Motu free midi having a database of about every hardware synth you might plug in.
The only benefit I see to the coming "plug in editor" is a little easier to patch edit while in combi multitimbral mode, and store those tweaks with the project rather than changing the patch permanently.
I could be wrong(all speculation at this pointi)...if it somehow makes an audio connection that allows audio rendering in the app over USB, that would be a pretty big workflow win, IMO. That's the trouble I run into with using my combination of hardware and software instruments.
I miss the days of Motu free midi having a database of about every hardware synth you might plug in.
The only benefit I see to the coming "plug in editor" is a little easier to patch edit while in combi multitimbral mode, and store those tweaks with the project rather than changing the patch permanently.
I could be wrong(all speculation at this pointi)...if it somehow makes an audio connection that allows audio rendering in the app over USB, that would be a pretty big workflow win, IMO. That's the trouble I run into with using my combination of hardware and software instruments.