+- XOR Userforum (https://forum.xor.eu)
+-- Forum: Products (https://forum.xor.eu/forumdisplay.php?fid=3)
+--- Forum: NerdSEQ (https://forum.xor.eu/forumdisplay.php?fid=6)
+---- Forum: General Questions (https://forum.xor.eu/forumdisplay.php?fid=17)
+---- Thread: Q re best practise for gates on CV16 (/showthread.php?tid=981)
Q re best practise for gates on CV16 - mgd - 01-24-2021
Hi Forum,
what is the best practise for generating gates with the CV16?
Currently I've setup my CV16 such that all odd numbered outputs are set to -5V - +5V and used for notes and the even numbered outputs are set to 0V - +10V and used for gates/env (CV2 is gate/env for CV1, CV4 for CV3 and so on). At the moment I'm not doing anything fancy. The even numbered columns contain solely ^11 for gate/env and -16 for rests.
While that basically works for me I'm suspecting this might not be the smartest way to do things and would like to know what others do.
The reason I'm suspecting the above might not be best practise is, that I'm currently trying to sequence 9 concurrent melodylines on three CV16 tracks (3 note columns and 3 gate/env columns per track):
Track 1: CV1-6
Track 2: CV7-12
Track 3: CV13-16 + LOC CV6 + LOC MOD6
My first suprise was that ^11 and -16 aren't supported on LOC MODn tracks (why is that so?)
I then changed the Track 3 setup to:
CV13-16 + LOC CV5 + LOC CV6
When I now play Track 3 alone I basically hear all 3 voices albeit the gate/env on LOC CV6 behaves noticeably different from those on CV14 and CV16, namely -16 has no audible effect.
When I play all 3 tracks together (9 melodylines) LOC CV5 does not play any notes. However it emits a constant voltage resulting in a droning VCO (which is what you expect from a constant voltage).
Have I hit some sort of limit?
Am I doing something silly (and what)?
Any advice welcome,
kind regards,
Michael
RE: Q re best practise for gates on CV16 - XORadmin - 01-24-2021
Actually all CV16 modulations have only effect on the CV16 expander.
The CV16 got it's own envelopes and LFOs and are also only working on these (they are generated in the expander and not in the NerdSEQ).
They don't work on the local tracks (these got their own 'modulators').
About Local CV5, I don't know why that doesn't seem to play in your case. There should normally be no problems with that. Please check the general settings for the tracks. If that doesn't work I could check your project and test your sequence.
RE: Q re best practise for gates on CV16 - mgd - 01-25-2021
Thank you for your answer, especially the explanation w/r to the CV16 and it's own envelopes and LFOs. That clarifies a few things
I've carefully checked my project, setup and cabling and currently Local CV5 is playing the notes it should. I guess during my experiments yesterday I misconfigured something or had cables swapped or something in that realm (meaning: Usererror on my part).
What I have not yet been able to figure out though is how to have an envelope generated on Local Mod5 that is triggered by the notes sent out to Local CV5 from note column 5 on track 3 (setup as of my initial post except for Track 3: CV13-16 + LOC CV5 + LOC MOD5)
I've gone to the Envelope page (via Automator) and configured ENV1 Destination=MOD5. I set Source to either GATE3 (because I'm on Track 3) or GATE5 (because I put out notes through Local CV5) but neither produced an Envelope on Local Mod5.
How do I create my Envelope on Local Mod5 based on the notes that are being sent out via Local CV5?
Kind regards,
Michael
RE: Q re best practise for gates on CV16 - XORadmin - 01-25-2021
You would need to set a gate on this track then. The envelope is connected to the gate. If you only change notes then the envelope doesn't react.
So what you would have to do is to have 2 columns. One for the note and one for the gate of the track. I actually didn't test the envelope with that but I am pretty sure that would work. I think both Gates and Triggers should work depending on your envelope needs (Local ADSR envelope then).
RE: Q re best practise for gates on CV16 - mgd - 01-25-2021
I have two columns (setup as LOC CV5 + LOC MOD5). The LOC MOD5 column has ^11 wherever I want a gate to start and -16 wherever I want an explicit GATE OFF.
In one pattern I've changed all ^11 to TD1 and all -16 to TD0 and the Env is set to AD-SR. That basically works in so far as the Env is triggered with each note and stopped with each TD0. Using TD2 instead of TD1 on short notes gives even better results. Ok, I see light at the end of the tunnel
Now a "Global Change" function that does some form of "search and replace" for a column in a pattern, for a column or all columns for all patterns on a track and for all patterns in a project would come handy
Just out of curiosity and because I intend to get another CV16 anyway:
Would or will it be possible to have a track setup like this:
Track 1: CV1-6 of NSA1
Track 2: CV7-12 of NSA1
Track 3: CV13-16 of NSA1 + CV1-2 of NSA2
Thank you for your help,
kind regards,
Michael
RE: Q re best practise for gates on CV16 - XORadmin - 01-27-2021
(01-25-2021, 11:08 AM)mgd Wrote: I have two columns (setup as LOC CV5 + LOC MOD5). The LOC MOD5 column has ^11 wherever I want a gate to start and -16 wherever I want an explicit GATE OFF.
In one pattern I've changed all ^11 to TD1 and all -16 to TD0 and the Env is set to AD-SR. That basically works in so far as the Env is triggered with each note and stopped with each TD0. Using TD2 instead of TD1 on short notes gives even better results. Ok, I see light at the end of the tunnel
Now a "Global Change" function that does some form of "search and replace" for a column in a pattern, for a column or all columns for all patterns on a track and for all patterns in a project would come handy
Just out of curiosity and because I intend to get another CV16 anyway:
Would or will it be possible to have a track setup like this:
Track 1: CV1-6 of NSA1
Track 2: CV7-12 of NSA1
Track 3: CV13-16 of NSA1 + CV1-2 of NSA2
Thank you for your help,
kind regards,
Michael
Exactly: ^11 in a LOC xx column is not possible (I don't know what it does then out of my head right now).
TD1 is not triggering the envelope but gating it (Since it is in AD-SR mode and not one-shot). So it will stay in 'Sustain' until TD0 starts the release phase.
TD2 does a 10ms Trigger, so the Envelope is gated for 10ms and released then again. Both are for sure usefull depending on your needs.
Quote:Track 1: CV1-6 of NSA1
Track 2: CV7-12 of NSA1
Track 3: CV13-16 of NSA1 + CV1-2 of NSA2
Actually that is not possible for Track 3. You can dedicate a track only to 1 expander.
Global 'Search and Replace' .....man you are killing me :-)
RE: Q re best practise for gates on CV16 - mgd - 01-27-2021
Thank you, that clarified a couple of things.
Kind regards,
Michael