Kirk Hunter Studios FAQs, Tips and Peer2Peer Info Sharing Thread
-
- KVRian
- 645 posts since 22 Jun, 2003 from Germany
-
- KVRer
- 23 posts since 23 Jul, 2009 from Germany
concert strings II - all keys one octave lower
I was trying to build expression maps for Cubase6 today and stumbled over the key mapping. Everything is mapped an octave lower than it should be. Like smooth articulation on c#0 as instead of c#1 ... in the beginning I thought it was just the keyswitches but the lowest starting note of the violins were a G2, violas C2. I have no midi modifiers or whatsoever activated ? That just seems weird. (Kontakt 5.0.1)
I was trying to build expression maps for Cubase6 today and stumbled over the key mapping. Everything is mapped an octave lower than it should be. Like smooth articulation on c#0 as instead of c#1 ... in the beginning I thought it was just the keyswitches but the lowest starting note of the violins were a G2, violas C2. I have no midi modifiers or whatsoever activated ? That just seems weird. (Kontakt 5.0.1)
-
- KVRist
- Topic Starter
- 443 posts since 20 Nov, 2010 from stuck in transition
you can set the keyswitches to whatever midi note you want (above or below the instruments range, of course) in the SETTINGS menuanterroir wrote:concert strings II - all keys one octave lower
I was trying to build expression maps for Cubase6 today and stumbled over the key mapping. Everything is mapped an octave lower than it should be. Like smooth articulation on c#0 as instead of c#1 ... in the beginning I thought it was just the keyswitches but the lowest starting note of the violins were a G2, violas C2. I have no midi modifiers or whatsoever activated ? That just seems weird. (Kontakt 5.0.1)
it's all relative what the octave is named. the two DAWS i own have middle C named differently
-
- KVRAF
- 10366 posts since 2 Sep, 2003 from Surrey, UK
@anterroir,
Are you saying that all the "note names", for key-switches and playable notes, are one octave adrift? If so, then you might consider setting the Preference / Option in your host (Cubase, I guess) to offset the names.
Or that the Smooth articulation is showing up as C#0 in your host but the playable key ranges are OK?
I have seen different hosts refer to "middle C2 (MID note # 60) as C3, C4 and C5.
Looking at the Frequency Range chart in the Miroslav User Manual,
-- violins are shown as G2 - A6
-- violas are shown as C2 - A5
Are you saying that all the "note names", for key-switches and playable notes, are one octave adrift? If so, then you might consider setting the Preference / Option in your host (Cubase, I guess) to offset the names.
Or that the Smooth articulation is showing up as C#0 in your host but the playable key ranges are OK?
I have seen different hosts refer to "middle C2 (MID note # 60) as C3, C4 and C5.
Looking at the Frequency Range chart in the Miroslav User Manual,
-- violins are shown as G2 - A6
-- violas are shown as C2 - A5
-
- KVRAF
- 10366 posts since 2 Sep, 2003 from Surrey, UK
I think that whatever it is set to, it will be named on a different octave in Concert Strings. offsetting the names in the host is the answer, I believe (as the note naming convention is fixed within the Concert Strings scripts).kcisANDderit wrote:you can set the keyswitches to whatever midi note you want (above or below the instruments range, of course) in the SETTINGS menu
Last edited by DarkStar on Tue Jan 03, 2012 4:23 pm, edited 1 time in total.
-
- KVRer
- 23 posts since 23 Jul, 2009 from Germany
I know they are relative and yes I know about the settings menu.
Let say say I change a keyswitch manually to C2 in the settings menu I still have to play a C1 on the keyboard to trigger it. And thats plain weird as I have no transpose options triggered nor any input transformers active.
---
*edit
yes they are all adrift, it's not a big bummer but maybe other Cubase users can look into that, confirm it and you can state that in the manual
Let say say I change a keyswitch manually to C2 in the settings menu I still have to play a C1 on the keyboard to trigger it. And thats plain weird as I have no transpose options triggered nor any input transformers active.
---
*edit
yes they are all adrift, it's not a big bummer but maybe other Cubase users can look into that, confirm it and you can state that in the manual
Last edited by anterroir on Tue Jan 03, 2012 4:26 pm, edited 1 time in total.
-
- KVRAF
- 10366 posts since 2 Sep, 2003 from Surrey, UK
^^^^
What is the MIDI note name range (from MIDI note #0 to #127) in your host? THat, I believe, is what needs adjusting.
What is the MIDI note name range (from MIDI note #0 to #127) in your host? THat, I believe, is what needs adjusting.
-
- KVRer
- 23 posts since 23 Jul, 2009 from Germany
C-2DarkStar wrote:^^^^
What is the MIDI note name range (from MIDI note #0 to #127) in your host? THat, I believe, is what needs adjusting.
Last edited by anterroir on Tue Jan 03, 2012 4:32 pm, edited 1 time in total.
-
- KVRAF
- 10366 posts since 2 Sep, 2003 from Surrey, UK
Set it to -C1 (or C-1) and the names will match up in the host and in Concert Strings.
That's what I've done here (in Reaper)
That's what I've done here (in Reaper)
-
- KVRer
- 23 posts since 23 Jul, 2009 from Germany
*edit* transposing doesn't solve the number problem
Thanks at all
Thanks at all
Last edited by anterroir on Tue Jan 03, 2012 5:13 pm, edited 4 times in total.
-
- KVRist
- 117 posts since 20 Nov, 2011 from Mao, Balears
As stated already midi note names is a convention and every developer (be it sampler dev, daw and alike) choose the offset he likes; what is standard and never change is the note number. In this way, for instance, note number 45 is the same note, the same key switch and the same key command for whatever software you are using 
-
- KVRAF
- 10366 posts since 2 Sep, 2003 from Surrey, UK
The problem is: there are several standards.anterroir wrote:It isn't that easy in Cubase but it's working with the Midi Modifier inserted in every track set to transpose one octave. (Shouldn't there be a standard about this)
Thanks at all
-
- KVRer
- 23 posts since 23 Jul, 2009 from Germany
But then it doesn't make sense to show the hardscripted key names in your plugin <- as in Cubase key number 25 is a C0 opposed to a C1 the KH Kontakt script is showing. That gives you two options - name that in the manual or add a function in the script to change the root note as in it's current state it shows wrong names for some people/daws.EdC wrote:As stated already midi note names is a convention and every developer (be it sampler dev, daw and alike) choose the offset he likes; what is standard and never change is the note number. In this way, for instance, note number 45 is the same note, the same key switch and the same key command for whatever software you are using
Don't get me wrong here - I don't really want to nitpick but thats the first time in 10 years I stumbled over that matter and it was just confusing at first.
Last edited by anterroir on Tue Jan 03, 2012 5:16 pm, edited 1 time in total.
-
- KVRist
- 117 posts since 20 Nov, 2011 from Mao, Balears
Hi Anterroir,
I understand your issue and I agree than this can seem confusing but the problem is not from Kirk but for rules concerning MIDI standards.
If you like you can find a better explanation here
http://tomscarff.110mb.com/midi_analyse ... ctaves.htm
cheers
I understand your issue and I agree than this can seem confusing but the problem is not from Kirk but for rules concerning MIDI standards.
If you like you can find a better explanation here
http://tomscarff.110mb.com/midi_analyse ... ctaves.htm
cheers
-
- KVRer
- 23 posts since 23 Jul, 2009 from Germany
It's okay, I wrapped my head around all that.
So it would be nice if Kirk can add an option to change the displayed notes according to the root note of the daw - like midi note 0 = insert root here or if that ain't possible just note in the "manual" it that a c#1 displayed is a c#0 in Cubase.
Saves trouble for other Cubase people asking the same question.
So it would be nice if Kirk can add an option to change the displayed notes according to the root note of the daw - like midi note 0 = insert root here or if that ain't possible just note in the "manual" it that a c#1 displayed is a c#0 in Cubase.
Saves trouble for other Cubase people asking the same question.
