Firmware V1.28 Test Version - Printable Version

Firmware V1.28 Test Version - Printable Version

+- 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: Firmware / Manual (https://forum.xor.eu/forumdisplay.php?fid=11)
+---- Thread: Firmware V1.28 Test Version (/showthread.php?tid=1604)

Pages: 1 2 3 4 5 6 7 8 9 10 11 12 13

RE: Firmware V1.28 Test Version - st3rk - 08-02-2023

(08-02-2023, 11:02 AM)XORadmin Wrote: It is a play-around version and there is much to play around already and yes surely not everything is working 100% correctly = not everything has been tested fully. There is also the chance that some functions only work for Modular tracks at the moment. Still it is totally worth to keep on playing with it. I got to check the probabilities though, I remember I had them working but also changed something here.

As for the glides, if you use a fader for example it doesn’t make any sense to use the too high values as your glide would be already too long with the smallest movement. I reduced that a bit to working values.

By the way, I will turn off notifications for this in the next days so I can relax a bit

Sure, not complaining, just giving feedback Smile

RE: Firmware V1.28 Test Version - XORadmin - 08-02-2023

(08-02-2023, 11:25 AM)st3rk Wrote:
(08-02-2023, 11:02 AM)XORadmin Wrote: It is a play-around version and there is much to play around already and yes surely not everything is working 100% correctly = not everything has been tested fully. There is also the chance that some functions only work for Modular tracks at the moment. Still it is totally worth to keep on playing with it. I got to check the probabilities though, I remember I had them working but also changed something here.

As for the glides, if you use a fader for example it doesn’t make any sense to use the too high values as your glide would be already too long with the smallest movement. I reduced that a bit to working values.

By the way, I will turn off notifications for this in the next days so I can relax a bit

Sure, not complaining, just giving feedback

Oh no worries, I just wanted to make sure that you are not giving up already Big Grin

RE: Firmware V1.28 Test Version - Terekki - 08-03-2023

Thanks looks great, have a great break...
My expectation with the Scales functionality was that the user would select a scale in settings, then in a pattern selecting notes would be limited to only notes in the scale - from what I can see in the beta - all notes can still be selected (and displayed) in a pattern and they are shifted to their closest note in the selected scale (up/down/coin toss) when triggered. This is counterintuitive when you come back to a pattern - as the notes displayed in the pattern are not actually being played - can't see the value in that (other than just randomly lashing in notes and 'hoping' something comes out nice when those notes are shifted to the scale). What's everyone's view on this? Thanks.

RE: Firmware V1.28 Test Version - XORadmin - 08-03-2023

(08-03-2023, 11:00 AM)Terekki Wrote: Thanks looks great, have a great break...
My expectation with the Scales functionality was that the user would select a scale in settings, then in a pattern selecting notes would be limited to only notes in the scale - from what I can see in the beta - all notes can still be selected (and displayed) in a pattern and they are shifted to their closest note in the selected scale (up/down/coin toss) when triggered. This is counterintuitive when you come back to a pattern - as the notes displayed in the pattern are not actually being played - can't see the value in that (other than just randomly lashing in notes and 'hoping' something comes out nice when those notes are shifted to the scale). What's everyone's view on this? Thanks.

See in the first post that it is not finished and they are the extra scale functions missing in this test version.
Check the scales thread here about my ideas about it. Yours is also in the pipeline for the release and the current functionality is also absolutely fine and covers what many users want to do already.

RE: Firmware V1.28 Test Version - Onosendai - 08-03-2023

On the matrix, try this

Glob Srun ... | Trig 1-1 Trig

I was expecting to generate a trig each time the seq was started or stopped, but the Trig out is always lit

It works with "Trig 1-1 Gate" (a gate stay on when play, then go off when stop)

RE: Firmware V1.28 Test Version - st3rk - 08-04-2023

Playing with the new mapping options, it's very useful to process logic directly inside the Nerdseq. Currently playing with two voices and the ADSR envelopes :
- LFO 1 value: modulates release time of envelopes 1 and 5 used for the VCA and filters of voice A
- FFF - LFO 1 value: modulates release time of envelopes 2 and 6 used for the VCA and filters of voice B
- LFO 2 value: adds an offset to envelope 1 used for the filter cutoff frequency of voice A
- 7D0 - LFO 2 value : adds an offset to envelope 2 used for the filter cutoff frequency of voice B

Adds cool movement, and replace two LFO, 2 offseting mixers and 2 attenuverters channels in the rack Smile

A cool bonus would be to have access to the CV16 envelopes parameters too, but there is maybe some hardware limitations? I see they are now available in the modulator screen, maybe is there a way to use that as a workaound.

Curious to know what creative use other have came up with! I've seen on an other thread the cool idea to "precision add" multiple track sequences and to map it on a CV output, have to try that. I guess the A-185-2 precision adder will leave my rack soon Smile

RE: Firmware V1.28 Test Version - mgd - 08-04-2023

Don't throw away your precicion adder prematurely. You still need it for everything not coming from the NerdSEQ Smile

RE: Firmware V1.28 Test Version - XORadmin - 08-04-2023

Ok, seeking for cool usage reports…

Here’s a little job:
Create a bouncing ball effect using trigger1 output. One shot firing the sequence from the sequencer.
Function created only via the mapping.

I’m sure it is possible with what is working right now.
Shoot!

RE: Firmware V1.28 Test Version - mgd - 08-05-2023

Here's a simple solution:
1) Create a pattern and put XMAP 001 in one of the FX columns (I have it in row 00)
2) Put the following code in the mapping settings:

Code:
00 SKIP 1  = VAVA > ---- ---- ----

01 CALC INC  VAVA > SETV V  A ----

02 SKIP 7  = VAVB > ---- ---- ----

03 VAR  #  C #032 > ---- ---- ----

04 VAR  #  D #1F4 > SETV V  E ----

05 VAR  #  F #0E1 > TRIG TR 1 TVAL

06 VAR  #  A #000 > SETV V  B ----

07 ---- ---- ---- > ---- ---- ----

08 ---- ---- ---- > ---- ---- ----

09 ---- ---- ---- > ---- ---- ----

0A CALC DEC  VEVA > SETV V  E ----

0B SKIP 3  > VEVB > ---- ---- ----

0C CALC SUB  VDVC > SETV V  D ----

0D VAR  #  D SRC  > SETV V  E ----

0E VAR  #  F SRC  > TRIG TR 1 TVAL

In a real world situation I would want to initialize the values for VAR #C (delay decrement) and VAR #D (initial delay) from some I2C connected slider...but I can't yet test that... Wink

Kind regards,
Michael

PS: It is rather educational to try to figure out what the above code is doing and why.

RE: Firmware V1.28 Test Version - mgd - 08-06-2023

Here's a list of caveats and things to remember/building blocks when dealing with the mapping screen [@Thomas: pls correct anything I got wrong]

0) First and foremost the whole mapping screen (all 70 [= hex 45] lines!) is executed/processed 100 or more times for each row in one of your patterns. E.g. when your song runs at 120 BPM (2 beats per second) the mapping screen is processed 125x for each row in any of your patterns.
This is great for reacting to external controls (e.g. faders connected via I2C) but requires extra means when you wish to do stuff in relation to the musical events in your pattern.

1) Synchronize processing of (some) mapping screen functionality with your sequence
This is achieved via the function XMAP <some mapping row> that you can place in the function part of a sequencer row. It will process exactly this one row of the mapping and nothing else [outside of the normal mapping processing].

The content of <some mapping row> is then processed and completely in sync with your sequence. Fine.
Now we need to make sure this line is excluded from normal mapping processing (remember, 125x per row, see above).

This is done by placing something like

Code:
SKIP 1  = VAVA

directly in front of row <some mapping row> (the one we process via XMAP <some mapping row> from our pattern).
The SKIP cmd conditionally skips 1 (or more - up to 8) following rows from processing. By choosing a condition that is always TRUE (like VA == VA - whatever the value of VA it will always be identical to itself) we can assure that this row is executed only when the pattern says so via XMAP.

2) The above works great for things that can be done in a single mapping row. However sometimes we may wish for more complicated processing. For this we can expand the trick we applied above:

Code:
SKIP 1  = VAVA

CALC INC  VAVA > SETV V  A

SKIP <n> = VAVB

<n> rows of mapping processing

...

The trick is that during normal processing the line

Code:
SKIP <n> = VAVB

will be TRUE (provided we made sure VA and VB started out the same) and the following <n> rows will normally not be processed. Only when we process

Code:
CALC INC  VAVA > SETV V  A

from our pattern (by means of XMAP <row # of that row>) it will be activated. To make sure it will be processed just once we have to reset the condition by something like

Code:
VAR  #  A #000 > SETV V  B

<n> can be up to 8 rows. If we need particularly complex processing we can repeat the above pattern like

Code:
SKIP <n> = VAVB

<n> rows of mapping processing

SKIP <n> = VAVB

another <n> rows of mapping processing

SKIP <n> = VAVB

yet another <n-1> rows of mapping processing

VAR  #  A #000 > SETV V  B

Be aware to put the last line (aka resetting the condition) into the last block of rows to process!

Kind regards,
Michael

PS: I will expand this as I come across other things I find useful as building blocks Smile

@Thomas
Wishes for extensions to the mapping processing:
1) SKIP cmd
It would be handy if the SKIP command would get at least a constant value of 0 as an additional second value, e.g. like:
SKIP 7 = VA#0
Comparing against 0 is so common that it seems a waste to always have a variable fixed to that value. It's probably possible to trick some row value (that implicitly is always 0), but that would create a debugging nightmare if for whatever reason that will change.

2) VAR cmd
Fast scrolling UP through the values works just fine. DOWN seems to stop when the first digit is 0 and from then on one needs to use slow scrolling to e.g. reach #000. Please ammend Smile

3) Copy and paste in mapping screen
I'm sure it is on your TODO list but I thought I'd mention it anyway Wink

When editing/developing more complicated processing I often need to insert rows. I'm not aware of a way to achieve that (other than to re-enter all the lines below).