The Key tracking in the mod matrix is not working for me in Dune2.
I just compared it to Dune1 where it does work and it's not working.
It seems no different than if I used the Const- setting.
This is on mac os, 10.6.8
This is only when setting keytrack in the matrix section.
I wonder if the same problem happens with the freqtrack.
I'll check that now.
DUNE2 key tracking in matrix not working.Moderators: Christophe, Mark
8 posts
• Page 1 of 1
Re: DUNE2 key tracking in matrix not working.2 diff things....it used to be note# (i think....sure i read it somewhere)
Windows 11 Home - 12th Gen Intel(R) Core(TM) i5-12400 2.50 GHz -32GB RAM
250GB SSD - 1TB HDD | M-Audio Oxygen 25 V
Re: DUNE2 key tracking in matrix not working.
in the manual ? Yamaha CS-30, Roland SH-1, Roland MKS70, Focusrite Scarlett 18i6, Yamaha FS1R, Oberheim Matrix 1000, Novation Remote 37SL, Korg Legacy, Alesis M1Active 520, Novation Launchpad Pro, Push2, Intel i7-7700HQ
Re: DUNE2 key tracking in matrix not working.You must be joking
Windows 11 Home - 12th Gen Intel(R) Core(TM) i5-12400 2.50 GHz -32GB RAM
250GB SSD - 1TB HDD | M-Audio Oxygen 25 V
Re: DUNE2 key tracking in matrix not working.yes
Yamaha CS-30, Roland SH-1, Roland MKS70, Focusrite Scarlett 18i6, Yamaha FS1R, Oberheim Matrix 1000, Novation Remote 37SL, Korg Legacy, Alesis M1Active 520, Novation Launchpad Pro, Push2, Intel i7-7700HQ
Re: DUNE2 key tracking in matrix not working.Keytrack is working fine here in Logic Pro X, OS X 10.9.3. Which DAW are you using?
The effect seems to be a little more noticeable for certain Destinations than others in the Mod Matrix. Try this: Start with the Init Patch In the Mod Matrix, select Keytrack for the Source, set the AMT to +100, and the Destination to Filter Cutoff Set the Lowpass Filter Cutoff to 20% Now start playing from C0 to all the way up your keyboard and you should hear the filter opening up as you do (The manual says "the MIDI Note number becomes the source of modulation, relative to C0." Therefore if your only playing within one octave, say C3, you won't be hearing much of a difference in the filter cutoff.) Also try switching the Destination to Reverb Time with the Time set to 0, the note C0 will sound as if it's in a small room and the space will get bigger the higher the note you play. Kriminal is right about it being Note# in DUNE 1.
Re: DUNE2 key tracking in matrix not working.It's not that it isn't working. It's that it isn't working like it did in Dune1.
So now if my patch doesn't have enough bass in the lower bass keys, and the upper bass keys have too much low end tone. I can't use keytracking to adjust for that anyore in Dune2. Yet in Dune1 I used it all the time. I've already been informed as to why this has changed. It's not a good thing imo...in fact it's a very bad thing. specially when you want to shift more bass to the lower keys, and less bass to the upper keys. You can't do this anymore. EDIT: Okay, I get it now. The changes with the key tracking between versions requires a different approach, but thanks to Richard's explanation I understand it now. For most sounds now, setting the keytracking to about -50/ -60 thereabouts, and then you'll have to adjust the main output level to compensate for the lower output level that happens from the keytracking. So all is good.
Re: DUNE2 key tracking in matrix not working.
Yea I think that it was note# but I was too lazy to look it up. I'm still too lazy even now. I'm pretty sure I'll be too lazy tomorrow as well. Maybe next week.
8 posts
• Page 1 of 1
Who is onlineUsers browsing this forum: No registered users and 149 guests |
© 2017 Synapse Audio Software. All Rights Reserved. |