Mapping Discussion

[XORadmin]

Okay, thanks for the suggestions, I'll give them a try. It also looks like even with the CALC workaround (from earlier in the thread), the CV outputs remain in a single octave.

 
What exactly? I think the calc functions should work and I don’t know why the CV should be only within one octave. Maybe you can point me to what you mean.

[zeitkunst]

Okay, thanks for the suggestions, I'll give them a try. It also looks like even with the CALC workaround (from earlier in the thread), the CV outputs remain in a single octave.

 
What exactly? I think the calc functions should work and I don’t know why the CV should be only within one octave. Maybe you can point me to what you mean.

Oh, what I meant was that when using the previously mentioned workaround (CALC PASS 00=1 > TRK TRK1 TICK) the CV output (for, say, pitch) only remains in one octave (C1 and C2 output the same pitch).

[XORadmin]

Okay, thanks for the suggestions, I'll give them a try. It also looks like even with the CALC workaround (from earlier in the thread), the CV outputs remain in a single octave.

 
What exactly? I think the calc functions should work and I don’t know why the CV should be only within one octave. Maybe you can point me to what you mean.

Oh, what I meant was that when using the previously mentioned workaround (CALC PASS 00=1 > TRK TRK1 TICK) the CV output (for, say, pitch) only remains in one octave (C1 and C2 output the same pitch).

Still don't know what you mean   Where do you send the pitch and what do you send. And still the tick function doesn't work as expected until the maintenance release.

[yrn1]

I've been trying to create an arpeggiator with mappings for some time now. One way I sorta get there (but not really) is reprogramming the scales to the sets of notes I want to arpeggiate and then change the scales with a CV IN. But what I would really want is to simply hit some notes on a midi keyboard and arpeggiate those, you know, like a normal arpeggiator would do. But, no such luck so far. Any ideas how this could be achieved?

[Labrioche]

Hello,

just updated to FW 2.0C and still don't manage to trigger Track Clock tick correctly.

I was thinking the bugfix: 
- fixed player functions if a track is externally 'clocked' by mappings
Correct the behavior

Track 1 clock source is set to: 
- MAPPNG
Mapping screen is: 
- CV IN 1 -> TRCK TRK1 TICK 

Each Trigger advance the track by at least 20 steps, I've tried with very small trigger or longer gate but same behavior. 
Not sure what's expected here, I would like the Track advance by 1 step every trigger detected

[XORadmin]

Hello,

just updated to FW 2.0C and still don't manage to trigger Track Clock tick correctly.

I was thinking the bugfix: 
- fixed player functions if a track is externally 'clocked' by mappings
Correct the behavior

Track 1 clock source is set to: 
- MAPPNG
Mapping screen is: 
- CV IN 1 -> TRCK TRK1 TICK 

Each Trigger advance the track by at least 20 steps, I've tried with very small trigger or longer gate but same behavior. 
Not sure what's expected here, I would like the Track advance by 1 step every trigger detected

No it works well. Your map literally adds the read CV value as trigger ticks and which is surely not what you want.
Use either the pass function or one of the other possibilities to check if the CV value is zero vs it got a value and let it add 1 or more ticks.

Example:

Code:

00 CV       IN 1
01 CALC     PASS     00=6  >  TRCK      TRK1      TICK

This generates 6 ticks if the CV input changes from zero to any value. This works if the CV signal is clean and the CV input is calibrated properly. Else you would need to add a threshold like this:

Code:

00 CV       IN 1
01 CALC     IF >     00VA
02 CALC     PASS     01=6  >  TRCK      TRK1      TICK

And you would set VA before to a higher value which defines the threshold. If CV In goes higher than VA then row 02 will generate 6 ticks.

[Raymond19990802]

Hey Dear XOR

Is there a expression for overrule the original output from cv/gate/mod?

I wish I could have a seq for cv1, another seq for mod1, then use map to calculate them together to have a complex seq interact within each other. At last, using this new complex seq to overrule (maybe cv1),maybe another calculation style to generate a new seq to overrule mod1, and output them. I don't know if it is possible, because it will be such a waste if cv1&mod1 are only treat as a source and not using them at all.

Thanks! happy new year!

[XORadmin]

Hey Dear XOR

Is there a expression for overrule the original output from cv/gate/mod?

I wish I could have a seq for cv1, another seq for mod1, then use map to calculate them together to have a complex seq interact within each other. At last, using this new complex seq to overrule (maybe cv1),maybe another calculation style to generate a new seq to overrule mod1, and output them. I don't know if it is possible, because it will be such a waste if cv1&mod1 are only treat as a source and not using them at all.

Thanks! happy new year!

If I understand it right, then you want to avoid the regular sequencing to output on the CV outputs but use the sequenced value as a source for the mapping?

It is not possible currently. You would need to output these in the first place and then can use the signals for the mappings and output the result on another CV/MOD output.

[zeitkunst]

Okay, thanks for the suggestions, I'll give them a try. It also looks like even with the CALC workaround (from earlier in the thread), the CV outputs remain in a single octave.

 
What exactly? I think the calc functions should work and I don’t know why the CV should be only within one octave. Maybe you can point me to what you mean.

Oh, what I meant was that when using the previously mentioned workaround (CALC PASS 00=1 > TRK TRK1 TICK) the CV output (for, say, pitch) only remains in one octave (C1 and C2 output the same pitch).

Still don't know what you mean   Where do you send the pitch and what do you send. And still the tick function doesn't work as expected until the maintenance release.

Just getting back to this as I was traveling for the holidays. So I'll try and give more details about my issue, which is still in there with the v2.00C release. And then I have another question about the CALC function and triggers

Here is my setup: external trigger coming in to CV in 1. I setup my mapping as follows:

* 00  CV  IN1  
* 01 CALC PASS 00=6 > TRK TRK1 TICK

In Track 1 I create a pattern, set the track clock to mapping. The trigger comes in (5V trigger), the steps in the pattern advance on track 1.

I have two issues now, one of which is the previous one that I will try and explain better!

* First, I set the note value in the pattern to be something like, C-4. I then put a C-5 on a different step in the pattern. No matter what octave I put for the note, the voltage remains between 0 and 1V. And, it seems as if the voltage output is not being output correctly between 0 and 1V, as changes between various half steps are not audible, and there is no voltage change on my multimeter. I haven't had a chance to map out the discrepancies exactly (for example, I don't hear or see any difference between C-4 and C#-4), but the main issue is: voltage remains between 0 and 1V, no matter the octave, and all of the voltage steps are not being outputted. I will try and map things out in the coming days.
* The second issue is that the voltage output seems to be delayed by some amount compared to my incoming trigger. Of course this is to be expected, given that a calculation is occurring. But the delay is enough to cause the voltage output (for my oscillator) to be offset from the incoming trigger enough to cause an audible slur to be heard. Is there a way to know the delay between the incoming trigger on, in my case, CV1, and the voltage output in the sequencer? Or, is it better to just use the trigger output from the sequencer itself to trigger downstream modules?

Thanks so much for your help on this!

[XORadmin]

....
* First, I set the note value in the pattern to be something like, C-4. I then put a C-5 on a different step in the pattern. No matter what octave I put for the note, the voltage remains between 0 and 1V. And, it seems as if the voltage output is not being output correctly between 0 and 1V, as changes between various half steps are not audible, and there is no voltage change on my multimeter. I haven't had a chance to map out the discrepancies exactly (for example, I don't hear or see any difference between C-4 and C#-4), but the main issue is: voltage remains between 0 and 1V, no matter the octave, and all of the voltage steps are not being outputted. I will try and map things out in the coming days.

Thanks so much for your help on this!

Offset switch to the right? No other modulators on the CV signal running? Transpose on in any way? CV In to out enabled somehow...outputs calibrated well? Maybe add your project where this happens so I can check whats going on.

* The second issue is that the voltage output seems to be delayed by some amount compared to my incoming trigger. Of course this is to be expected, given that a calculation is occurring. But the delay is enough to cause the voltage output (for my oscillator) to be offset from the incoming trigger enough to cause an audible slur to be heard. Is there a way to know the delay between the incoming trigger on, in my case, CV1, and the voltage output in the sequencer? Or, is it better to just use the trigger output from the sequencer itself to trigger downstream modules?

There can be a delay of max 1 ms until the execution of the mapping row. And then it depends on the next sequencer tick of the running sequencer until it is being executed from the pattern. The lower the BPM the higher the chance of a little delay.
The fact that it executes with the next internal sequencer tick can't be avoided as it wouldn't act together with the start/stop/launch part.
I would suggest to not use the incoming trigger as the one that works with the CV's but to generate the triggers from the sequence as that would match again.