great control ! is it available in kronos

[AMK]

http://youtu.be/bDJ29OnohlM

can we do the same with kronos? how?

1 using the numpad on kronos to change the daw varible like tempo or velocity etc…
2 using start stop or record to control cubase or protools or logic, start stop record command?

3 saving the tracks / instrument and effect from the daw to kronos. i.e if my first track is nylone guitar with delay effect both on kronos and I want to open the saved project later from cubase it automaticallt load the guitar and delay effect from the connected kronos for me

are any of those available?

[SanderXpander]

1. Don't think so
2. Yes
3. Yes, using the Kronos Editor VST inside a 32-bit DAW

[AMK]

thanks sander. but please can you share how to on 2?

and suggest 32 bit DAW cause I have a kronos but I fail to control it from cubase7 and slso fail to control cubase7 from kronos

Although, my many trys faield I only able to record MIDI and save the project in kronos and cubase seperatedly.

[SanderXpander]

Cubase exists as both 32 bit and 64 bit versions, I'm pretty sure. If you work with a lot of sample libraries you really should be using the 64 bit version (the main difference is it can "see" more than 4GB RAM), but that means you can't use the Kronos Editor VST. That's actually the most common complaint against it - it will only work in a 32-bit DAW. If you get most of your sounds out of hardware synths it's not such a big issue, and there is usually no problem installing both versions and using them alternatingly depending on the needs of the project. You can check which version you have now by going to help/about in the menu bar.

I can't really help you with 2 because I don't use Cubase so I don't know where to make the settings. I just know that Korg synths in general do transmit these button presses as sequencer control, I've used it in the past. Perhaps Qui can jump in?

[QuiRobinez]

Perhaps Qui can jump in?

sure

first of all, everything SanderXpander has said in this thread is correct, so there is no extra information on those issues.

Now the video you showed us, was the integration of the Motif with cubase, that integration was specially programmed by yamaha and goes quite far.

That doesn't mean that it isn't possible on the kronos, but you have to do this yourself by creating a generic remote map which maps the CC's to the corresponding functions you like (like transport, quick controls, mixer faders, etc.)

This is really easy to do in cubase and works the same for every midi controller
The best idea is to use the Kronos External Controller Mode. There is a button that you can press and then you can select the active controller page you want to use. You can set (or load a template for it) the external controller CC's by pressing the global button and then press the midi tab and then the external 1 tab. There you can set the CC's you want to assign (see page 777 of the kronos parameter guide). Of course you can also use the default RTC controls of the Kronos, those CC's can also be found in the Parameter guide. I prefer the External CC's because those have no influence on the kronos itself, only on the connected gear.

Now the work you have to do is in cubase:
- go to device setup
- create a new generic remote map
- assign the kronos midi channels to that map
- now map the features you want to control in cubase (you can use the learn button in the map and press or turn the kronos knob to map the CC number)
- save the generic remote as a kronos generic remote map.

in this video you will see a basic explanation how to do this for a midi controller, the procedure for the kronos is the same in cubase.
http://www.youtube.com/watch?v=DeNyL136b64


Now what my advice would be to set it up is to use the following mapping structure:
- first create a new Cubase template
- Create 8 subgroups channels in cubase in this template:
...Kick
...Hats
...Other Drums
...Bass
...Lead
...Other
...Pads
...Vocals
- save this new cubase project as your default template
- now create the generic remote
- the 8 kronos knobs you should assign to the Cubase Quick Controls 1-8
- The 8 kronos faders you should assign to the 8 subgroups
- the start, stop, rew and forward you should assign to the transport section
- save the generic remote as a kronos remote map (by naming it kronosremote)


Now the fun starts:
- start the kronos in combi mode (i prefer combi mode because that way i can save the timnbre setup from the kronos in a combi, which isn't possible in sequencer mode without loading the song again when you need it)
- assign the sounds you want
- assign a vst in cubase for instance NI Massive
- set the output of NI Massive to the bass subgroup
- In the track lane of NI Massive set the quick controls 1 to cutoff and quick control 2 to reso
- now press the Control Surface’s EXTERNAL knob on your kronos
- with fader 5 you control the volume of the bass sound (massive), with knobs 1 and 2 you control the cutoff and reso of massive

by using a setup like this you can control anything in cubase, since you can map the quick controls to whatever you like on a channel, for instance when you have a vocal sample with a reverb and delay on it, you could assign quick controls 1-4 to the reverb and controls 5-8 to the delay. By activating that lane you can program and automate! the things you want on that channel from your kronos.

Extremely powerful once you set it up. Now when you understand these basics you can go much further, you could create more pages in the Kronos external control section and expand your generic remote map in cubase, you could create pages for synth programming, mixing and mastering, quick control setups, showing editors and even basic midi functions.

You can also create a cubase device map for the kronos for the RTC functions for instance, if you do that and create a cubase external instrument with that device map you can also use the cubase quick controls to use automation for the kronos for the RTC functions (like kronos cutoff, reso, adsr, etc..) But that's a different area of expertise and falls outside the scope of the original question. But it is possible to do.

[AMK]

Many thanks for your help SanderXpander. I was confused why the Kronos vst not working well with my 64 bit cubase. now I can see why thanks for you.. I am happy with your reply

[AMK]

QuiRobinez !!! I can not stand my happiness! I really get a reply from you!!

I am a big fan of yor work and tutorials on youtube channal and for sure I already subscribed! but to get such a proffisional answer from you mean alot for me. I shall do those steps and get back here to post the results may be after tomorrow..

I am happy today in Korg Forums..

thank you all

[SanderXpander]

Qui certainly came through!
If you're really interested in getting the Kronos Editor to work in 64-bit Cubase, the only option currently is to upgrade to the full SoundQuest editor (the creators of the Kronos Editor). That one works in a 64-bit DAW supposedly but it's a lot of money if you only have the Kronos to work with (it's a general editor for many devices).

[AMK]

I guess I chose to work with cubase 86 bit not the 64 bit. and go back and forth with cubase 64. like you suggested.. however.. do you or QuiRobbins suggest a DAW other than cubase that is more friendly with Kronos

[SanderXpander]

They all have this same 32/64 bit issue, it has to do with the code base of the Kronos Editor. The rest is a matter of preference.
Qui has also made a really nice setup with Ableton using a similar technique to what he described, but Ableton is a bit "out there" compared to other DAWs. It's very nice for setting up ideas (and for working in a live environment, obviously) but it lacks a lot of the powerful editing you can find in most other modern DAWs, including Cubase.

[QuiRobinez]

but Ableton is a bit "out there" compared to other DAWs. It's very nice for setting up ideas (and for working in a live environment, obviously) but it lacks a lot of the powerful editing you can find in most other modern DAWs, including Cubase.

that was also my opinion at first hand but ableton live developed quite a bit in the midi area, ableton live 9 has quite some tricks up his sleeve for midi and the midi editing gap with for instance cubase is not that big anymore.

Also the hardware integration works flawlessly now in ableton live 9 (which was a big usp before that for cubase).

I think DAW choice is a matter of working method preference. If my working method is pattern based then ableton live 9 is much better then cubase 7.5, If my working method is song based then i prefer cubase.

In the audio area ableton live 9 is much more powerfull then cubase.

[SanderXpander]

Really? Sonar still beats Ableton in many ways (not all). And how about Cubase note expression?

EDIT: but yeah I agree completely about the pattern/song thing. That's the main reason I think Ableton is so good for setting up songs/ideas. It's just really easy to combine audio loops and midi parts and experiment.

Oh and with "out there" I meant more that Ableton takes a different approach to many things so while it is possible to arrive at the same conclusion, you'll probably feel lost in the beginning, coming from Sonar/Cubase/Logic/PT.

[QuiRobinez]

Really? Sonar still beats Ableton in many ways (not all). And how about Cubase note expression?

really, ableton live 9 is extremely improved compared to the 8 version. although i have to admit that you need the ableton live suite 9 version for that, because a lot of the default power stuff cubase can do is done by the M4L extension plugins. But when comparing both daws the suite is the only valid version to compare with and M4L is free and integrated with that version.

Note expression is a term that is interpreted differently amongst musicians. Some musicians refer to the controller data per note to add for instance vibrato to a flute in a vst3.5 plugin that supports that dynamic data. Other musicians refer to it as combining controller data to a note which copies and moves with it when modifying the note.

Ableton live controller data is clip based, so note expression is something that is not supported yet in ableton (although you can off course copy the notes and controller data by selecting it in ableton, but not as convenient as in cubase).

Also something that ableton doesn't have is score sheet display and editing.

So definitely cubase is still better in the midi editing area, but the most common functions that you need in daily live are now available in ableton live 9, like legato, quantize, multiple note values editing, randomizing position or velocity (for percussion or guitar parts for instance), etc... all those things are available now.

And then there are a huge amount of midi modifying plugins available in the M4L database, so there is much that can be done at the moment and it's definitely not a musical ideas scratchpad anymore

But i use both daws, as stated earlier, the work process defines which daw i use.

Oh and with "out there" I meant more that Ableton takes a different approach to many things so while it is possible to arrive at the same conclusion, you'll probably feel lost in the beginning, coming from Sonar/Cubase/Logic/PT.

very good point, since the whole workflow is pattern based with clips (although there is a song mode similar to the cubase project screen) you need to think differently when creating songs. In cubase i think of a song like, create the intro, verse, bridge, etc..
In ableton i just add lots of ideas in clips and then combine them in realtime to a song, it's a very different approach to music making.

[SanderXpander]

I have Live 9 Suite but have to admit I haven't dug into the M4L stuff yet. Thanks for the heads up!

I think mainly Ableton's screen layout and use of shortcuts sets it somewhat apart from "common" DAWs. Regular DAWs have things like a track view, a mixer view, a score view, piano roll view, etc.
Ableton does too but it's kinda all integrated (e.g. Mixer is clip/session view, piano roll and clip envelopes are inside the same box). Also, many features seem to not exist in the menu structure but are available using shortcuts. So basically "be prepared to rethink your workflow" if you want to switch to Ableton, is all I'm saying.
I think the only thing that really "sucks" is overdubbing, multitracking and comping.

Don't get me wrong, I love Ableton but I couldn't replace Sonar with it entirely. I also use Melodyne/ARA a lot and couldn't imagine going without that anymore.

[AMK]

so much things to try this weekend thanks for both of you.. should go buy some time! hey you tube! common show me this abilton as a start!!!

will get back after the result