Firmware V1.22A

[Nerdseq.532]

@XORadmin

You fukn kick ass!!!
Thank you!!!
Your hard work is much appreciated!!!

[T3t_one]

We're Not Worthy, We're Not Worthy, We're Scum!


 

[loik73]

Thank you!wonderful update!!!

[redrik]

FM is a killer  ...Even more powerful Nerdseq 

[SB-SIX]

Played around with it yesterday, what an amazing update! The tables have become so much more useful now. But it also raised a few questions/remarks for me

- the “random” table preset does not seem to do much. I would expect all kind of random data everywhere but I only get a random hop to 00.
- the double/triple presets clear existing note transpositions, correct? Would be nice to only fill the fx columns
- In the pattern screen, pressing ok on an existing table does not navigate to that table. It would be more consistent if it worked just like the sequencer, where ok navigates to the pattern
- Quantising notes to a scale/chord is only possible inside a table right? I thought I saw some global options in a beta video somewhere, or maybe I just dreamt it
- The row probability command is not near to the other probability commands when scrolling thru them in an fx column. Minor issue but it seems more logical to have those next to each other

At first I thought envelopes were not working when I connected them to a VCA, but then I realised the envs are bipolar and thus need an offset of 128 to function properly in a vca, duh maybe this saves someone else from a long puzzle... Love how the envelopes can give a slight lofi effect on oscs in a very pleasant way!

[XORadmin]

Played around with it yesterday, what an amazing update! The tables have become so much more useful now. But it also raised a few questions/remarks for me

- the “random” table preset does not seem to do much. I would expect all kind of random data everywhere but I only get a random hop to 00.
- the double/triple presets clear existing note transpositions, correct? Would be nice to only fill the fx columns
- In the pattern screen, pressing ok on an existing table does not navigate to that table. It would be more consistent if it worked just like the sequencer, where ok navigates to the pattern
- Quantising notes to a scale/chord  is only possible inside a table right? I thought I saw some global options in a beta video somewhere, or maybe I just dreamt it
- The row probability command is not near to the other probability commands when scrolling thru them in an fx column. Minor issue but it seems more logical to have those next to each other

At first I thought envelopes were not working when I connected them to a VCA, but then I realised the envs are bipolar and thus need an offset of 128 to function properly in a vca, duh maybe this saves someone else from a long puzzle... Love how the envelopes can give a slight lofi effect on oscs in a very pleasant way!

Hey thanks for the feedback, lets get into it:

- the “random” table preset does not seem to do much. I would expect all kind of random data everywhere but I only get a random hop to 00.
It works in combination with the random 'range' on the right of the screen.
- the double/triple presets clear existing note transpositions, correct? Would be nice to only fill the fx columns
Yes, correct, it fills in a preset and i don't think it makes too much sense to keep any notes, since also the 'speed' is changed so it matches a regular step.
- In the pattern screen, pressing ok on an existing table does not navigate to that table. It would be more consistent if it worked just like the sequencer, where ok navigates to the pattern
I will check it if there is nothing in the way to do that.
- Quantising notes to a scale/chord  is only possible inside a table right? I thought I saw some global options in a beta video somewhere, or maybe I just dreamt it
There is no scaling for patterns. However you can use the tables to get the same effect. Empty table running endless loop-> set quantise settings of the table to up or down and speed to 1. This will quantize/scale your main sequence to whatever the allowed notes are set to.
- The row probability command is not near to the other probability commands when scrolling thru them in an fx column. Minor issue but it seems more logical to have those next to each other
A new sort of the FX order needs a bigger refactoring. It's on my list together with another addition to that. For now, i only fill 'empty' spaces if i have new functions without a bigger impact of older projects.

The envelopes are not bi-polar. You set your offset switch to bi-polar which mostly only makes sense if you send out some LFO, but for notes and other modulations you mostly don't have them set to bipolar. I guess it looks also a bit weird if you always add the 128 offset? Not as it suppose to be :-)
Just an envelope (without the use of the automator) and full range should eliminate also the lo-fi effect...

[SB-SIX]

Cool thanks for the quick response! Quantising using a table is a great idea. And of course you were completely right about the random preset, setting the range was the key.
I’ll have a look at the envs with the switch to unipolar. Glad you’re willing to look at pressing ok to jump into the table. I’m running into that one alot!

[apeirophobe]

Wow, this looks like an incredible update! Can't wait to start exploring. Many thanks!!

[ipassenger]

Possible feature request, add to table clock sources the trig outs of normal or trig expansion outputs? Not sure if that is do-able and obviously you could do it externally by connecting from tirg out to CV In etc but just thought it might be quite cool to have it work internally.

[XORadmin]

Possible feature request, add to table clock sources the trig outs of normal or trig expansion outputs? Not sure if that is do-able and obviously you could do it externally by connecting from tirg out to CV In etc but just thought it might be quite cool to have it work internally.

Local triggers no problem, external triggers would be not easy and most probably a no go.
But there is also now the table tick from SPFX now which you could also use next to triggers to get the same effect.
Table ticks from triggers makes also sense and is noted.