Welcome, Guest
You have to register before you can post on our site.

Username
  

Password
  





Search Forums

(Advanced Search)

Forum Statistics
» Members: 1.812
» Latest member: snkyfkr
» Forum threads: 2.067
» Forum posts: 12.140

Full Statistics

Online Users
There are currently 55 online users.
» 0 Member(s) | 52 Guest(s)
Baidu, Facebook, Google

Latest Threads
FW Update of VEX does not...
Forum: Beauty and less important bugs/glitches
Last Post: mgd
11-02-2026, 03:39 PM
» Replies: 0
» Views: 29
Feature Request: Mapping ...
Forum: Feature requests
Last Post: XORadmin
11-02-2026, 12:51 PM
» Replies: 1
» Views: 69
One Time Trig
Forum: NerdSEQ
Last Post: XORadmin
11-02-2026, 12:42 PM
» Replies: 1
» Views: 47
Broken Redirect Links?
Forum: Website issues
Last Post: fossilizeme
11-02-2026, 03:26 AM
» Replies: 0
» Views: 44
Random choices
Forum: General Questions
Last Post: joesh
10-29-2026, 10:35 PM
» Replies: 2
» Views: 77
Release Candidate Firmwar...
Forum: Firmware / Manual
Last Post: XORadmin
10-29-2026, 08:35 PM
» Replies: 20
» Views: 2.597
Ratchet Randomly or Just ...
Forum: General Questions
Last Post: dangerBreak
10-29-2026, 08:00 PM
» Replies: 6
» Views: 185
Output a clock divider on...
Forum: General Questions
Last Post: XORadmin
10-28-2026, 10:34 PM
» Replies: 2
» Views: 101
Hallucinatory MIDI CC com...
Forum: Beauty and less important bugs/glitches
Last Post: XORadmin
10-28-2026, 10:02 PM
» Replies: 7
» Views: 1.388
Option to set Range on Ra...
Forum: Feature requests
Last Post: XORadmin
10-28-2026, 10:01 PM
» Replies: 2
» Views: 122

 
  [FIXED] Midi/I2C track forgets drum matrix page as default
Posted by: yrn1 - 01-12-2024, 08:37 PM - Forum: Beauty and less important bugs/glitches - No Replies

I have a Midi/I2C track on track 8. I use it only with the drum matrix view. But when I switch to a pattern on another track and then back to the one on track 8, doesn’t show the drum matrix page. Instead it shows the first page. If I remember correctly, with the trigger expander (which I no longer have), a pattern remembered the fact that it was on the drum matrix, right?

Print this item

  Activate screensaver while sequencer is running
Posted by: robinrabauke - 01-10-2024, 02:02 PM - Forum: General Questions - No Replies

Hi,


I wanted to ask if there is an option to activate the screensaver while
* the sequencer is in "playing"-state AND
* there has not been a clock-trigger for N seconds/minutes.

(or similar).


I use another module as my main clock and I like to keep the nerdseq on "play" while I patch other things with my main-clock stopped. Sometimes for hours because I get interrupted  or carried away Angel

Thanks!




https://forum.xor.eu/showthread.php?tid=...creensaver
Quote:mostly because the graphics part is eating up all processor time and the sequence itself would have a very poor stability.


I guess this explains why it won't be able to turn on while in "play"-state, even without receiving a clock.

I'm happy to be told otherwise  Big Grin

Print this item

  Optionally start first row on project load
Posted by: sems - 01-08-2024, 01:22 PM - Forum: Feature requests - Replies (1)

As I posted in the facebook group, it would be great if it was possible to optionally automatically start a project when loaded, for smoother transitions between songs. This could either be a per-project setting or a global setting.

This doesn't matter if there's a split second where the clock is stopped, what's important is that when this setting is on and the user clicks on load, it waits for the 0-cross of the main clock, loads the project, and starts the first row of the sequencer.

Print this item

  Read first!
Posted by: XORadmin - 01-07-2024, 12:23 PM - Forum: Mappings - No Replies

Mapping files are placed in the project folder.

Mappings can be imported in the mapping screen. Press SHIFT+NERD to get into the Nerd Menu and from there you can choose to import and export mapings.
It will overwrite all your mapping rows. Also variables are included in the mapping exports.
Please be sure that your NerdSEQ firmware version uses at least the mentioned firmware version for the mapping or newer.

If you post your mapping, it might be nice to add some little information like made with Firmware xx, maybe some info about the variables so people know directly which varibales are worth to manipulate. Also maybe also all in and outputs.

A tool is coming up which lets you export a mapping also into a readable format which could be pasted here easily (and much more planned). No one expects you to explain every line and what it does, but it would be very welcome if you would do. I try also to explain as much as possible so more and more people understand the power and make their own mappings and share them!

Print this item

  Probability on FX columns
Posted by: SB-SIX - 01-06-2024, 10:15 PM - Forum: General Questions - Replies (2)

I was wondering if this is a bug or expected behaviour...
Let's say I want to have the first note in my pattern (at position 00) to go an octave up, 50% of the time. 
- I'll set the basenote to 00C in fx1 column (one octave up)
- set PRF1 to 032 in fx2 column (50% probability)

And then on the next note
- set basenote to 000 and PRF1 to 064 (reset basenote and probability)

It seems that the probability will only work when it is set on a row BEFORE the note is triggered. So in this case I'll have to set the 50% probability in the last row of the pattern. Is that the correct way?

Print this item

  Turing Machine V1
Posted by: XORadmin - 01-06-2024, 09:40 PM - Forum: Mappings - Replies (11)

The Turing Machine V1.  Works with V2.0C

.map   TURING1.MAP (Size: 1,47 KB / Downloads: 84)  

This V1 got only the left shift option. Sounds best with any global scale enabled.
It uses the CV Input as 'switches' where 0 Volt means switch OFF another value means switch ON.
CV Input 1 : Set bit 0
CV Input 2 : Reset bit 0
CV Input 3 : Invert bit 0
CV Input 4 : Random bit 0
Of course you can replace the CV inputs with any other source easily.
If you got a trigger expander then you can see the turing parts nicely on Triggers 1-12.
You can use variables C, G and H to change some turing settings (see variables below)

The turing machine is connected to the sequencer and starts if the sequencer is started.
Var A: Switch/CV Input threshold (Initialized)
Var B: Type of trigger (Initialized w Trigger E1)
Var C: Amount of used turing bits
Var D: Helper variable for calculation (Initialized)
Var E: Used for program flow
Var F: Variable to hold the turing bits
Var G: Multiplicator for turing output (if less bits are used to get the full range anyways)
Var H: Pitch Offset

Code:
| 00 | GLOB | CLKO | ---- |>| ---- | ---- | ---- |  Use clock output as a 'clock source'
| 01 | CALC | CNT  | 00=0 |>| ---- | ---- | ---- |  Count on raising row 00
| 02 | ---- | ---- | ---- |>| ---- | ---- | ---- | 
| 03 | CALC | IF > | 01=1 |>| SETV | RW01 | RST  |  If row 01 is bigger than 1 then reset row 01
| 04 | SKIP | 03 > | 01=0 |>| ---- | ---- | ---- |  Skip the next 3 rows if row 01 is bigger than constant 0
| 05 | SKIP | 02 = | 09=0 |>| ---- | ---- | ---- |  Skip the next 2 rows if row 09 is 0
| 06 | CALC | SHTL | VFVC |>| SETV | V  F | SRC  |  Leftshift Var F, Use Var C for the amount of shifts. Store back in Var F
| 07 | VAR  | V  E | #001 |>| ---- | ---- | ---- |  Set Var E to constant 1
| 08 | ---- | ---- | ---- |>| ---- | ---- | ---- |
| 09 | GLOB | SRUN | ---- |>| ---- | ---- | ---- |  Use the state 'Sequencer started'
| 0A | CALC | DINV | 09=0 |>| SETV | RW01 | RST  |  (digital) Invert row 09 and reset row 01 if the invert result is true
| 0B | ---- | ---- | ---- |>| ---- | ---- | ---- |
| 0C | CV   | IN 1 | ---- |>| ---- | ---- | ---- |  Use CV Input 1
| 0D | SKIP | 01 < | 0CVA |>| ---- | ---- | ---- |  Skip the next row if row 0C is smaller than Var A (VA is a threshold)
| 0E | CALC | B OR | VF=1 |>| SETV | V  F | SRC  |  Bitwise OR of Var F and the constant 1 (which means always set LSB)  Store back in Var F
| 0F | ---- | ---- | ---- |>| ---- | ---- | ---- |
| 10 | CV   | IN 2 | ---- |>| ---- | ---- | ---- |  Use CV Input 2
| 11 | SKIP | 01 < | 10VA |>| ---- | ---- | ---- |  Skip the next row if row 10 is smaller than Var A (VA is a threshold)
| 12 | CALC | BAND | VFVD |>| SETV | V  F | SRC  |  Bitwise AND of Var F with Var D (which is initialized to FFE)-> always clear LSB, Store in VF
| 13 | ---- | ---- | ---- |>| ---- | ---- | ---- |
| 14 | CV   | IN 3 | ---- |>| ---- | ---- | ---- |  Use CV Input 3
| 15 | SKIP | 02 < | 14VA |>| ---- | ---- | ---- |  Skip the next 2 rows if row 14 is smaller than Var A (VA is a threshold)
| 16 | SKIP | 01 = | VE=0 |>| ---- | ---- | ---- |  Skip the next row if Var E is 0
| 17 | CALC | BXOR | VF=1 |>| SETV | V  F | SRC  |  Bitwise XOR of Var F with 1 (flip LSB of Var F) Store back in Var F
| 18 | ---- | ---- | ---- |>| ---- | ---- | ---- |
| 19 | SKIP | 04 = | VE=0 |>| ---- | ---- | ---- |  Skip the next 4 rows if Var E is 0
| 1A | CALC | MUL  | VFVG |>| ---- | ---- | ---- |  Multiply Var F with Var G  (widen the range of the turing bits so the notes are more spread)
| 1B | CALC | ADD  | 1AVH |>| ---- | ---- | ---- |  ADD row 1A with Var H (add note offset so the pitches are a bit higher)
| 1C | CALC | P2NT | 1B=0 |>| CV   | NOTE | CV 1 |  Convert Pitchvalues (in row 1B) to Notenumbers and output notes on CV1
| 1D | VAR  | V  B | SRC  |>| TRIG | VAL* | TR 1 |  Use the value of Var B as the trigger type (E1) and output on Trigger 1
| 1E | ---- | ---- | ---- |>| ---- | ---- | ---- |
| 1F | SKIP | 06 = | VE=0 |>| ---- | ---- | ---- |  Skip the next 6 rows if Var E is 0
| 20 | CV   | IN 4 | ---- |>| ---- | ---- | ---- |  Use CV Input 4
| 21 | SKIP | 04 < | 20VA |>| ---- | ---- | ---- |  Skip the next 4 rows if row 20 is smaller than Var A (threshold)
| 22 | GLOB | RAND | ---- |>| ---- | ---- | ---- |  Generate random value
| 23 | CALC | BAND | 22=1 |>| ---- | ---- | ---- |  Bitwise AND row 22 with 1 (results in only the LSB)
| 24 | CALC | BAND | VFVD |>| SETV | V  F | SRC  |  Bitwise AND Var F with Var D and store in Var F
| 25 | CALC | B OR | VF23 |>| SETV | V  F | SRC  |  Bitwise OR Var F with row 23 and store in Var F
| 26 | ---- | ---- | ---- |>| ---- | ---- | ---- |
| 27 | VAR  | V  E | #000 |>| ---- | ---- | ---- |  Reset Var E to 0
| 28 | ---- | ---- | ---- |>| ---- | ---- | ---- |
| 29 | CALC | BAND | VF=1 |>| TRIG | GATE | 1- 1 |  Bitwise AND of Var F with 1 (bit 0)and output on Trigger16 #1
| 2A | CALC | BAND | VF=2 |>| TRIG | GATE | 1- 2 |  Bitwise AND of Var F with 2(bit 1) and output on Trigger16 #2
| 2B | CALC | BAND | VF=4 |>| TRIG | GATE | 1- 3 |  Bitwise AND of Var F with 4(bit 2) and output on Trigger16 #3
| 2C | CALC | BAND | VF=8 |>| TRIG | GATE | 1- 4 |  Bitwise AND of Var F with 8(bit 3) and output on Trigger16 #4
| 2D | CALC | RSFT | VF=4 |>| ---- | ---- | ---- |  Rightshift Var F with 4 bits (do not store in Var F)
| 2E | CALC | BAND | 2D=1 |>| TRIG | GATE | 1- 5 |  Bitwise AND of row 2D with 1(2nd bit) and output on Trigger16 #5
| 2F | CALC | BAND | 2D=2 |>| TRIG | GATE | 1- 6 |  Bitwise AND of row 2D with 2(2nd bit) and output on Trigger16 #6
| 30 | CALC | BAND | 2D=4 |>| TRIG | GATE | 1- 7 |  Bitwise AND of row 2D with 4(2nd bit) and output on Trigger16 #7
| 31 | CALC | BAND | 2D=8 |>| TRIG | GATE | 1- 8 |  Bitwise AND of row 2D with 8(2nd bit) and output on Trigger16 #8
| 32 | CALC | RSFT | 2D=4 |>| ---- | ---- | ---- |  Rightshift row 2D with 4 bits 
| 33 | CALC | BAND | 32=1 |>| TRIG | GATE | 1- 9 |  Bitwise AND of row 32 with 1(2nd bit) and output on Trigger16 #9
| 34 | CALC | BAND | 32=2 |>| TRIG | GATE | 1-10 |  Bitwise AND of row 32 with 2(2nd bit) and output on Trigger16 #10
| 35 | CALC | BAND | 32=4 |>| TRIG | GATE | 1-11 |  Bitwise AND of row 32 with 4(2nd bit) and output on Trigger16 #11
| 36 | CALC | BAND | 32=8 |>| TRIG | GATE | 1-12 |  Bitwise AND of row 32 with 8(2nd bit) and output on Trigger16 #12

So how does it work. In general it is a turing machine which uses the 4 CV inputs. If Input 1 is on (high) then turing bits (on the LSB) are set.
If Input 2 is on (high) then turing bits on the LSB are reset. If Input 3 is on (high) then the LSB of the turing value is being inverted. If Input 4 is on (high) then the LSB of the turing value with randomly be set or reset.
Rows 00 to 0A will use the Clock output and on a raising edge (and running sequencer) then the turing value will be shifted. Var E will be set then as well (if sequencer is running AND a raising edge) which is being used in later checks then (like if Var E is set then other commands following can be executed). 
Row 0C to 0E do the check for the first input and will set the turing LSB if the input was high.
Row 10 to 12 do the check for the second input and will reset the turing LSB if the input was high.
Row 14 to 17 do the check for the third input and will invert the LSB if the input was high. Checking Var E is taking care that the LSB is not inverting all the time but only once on each raising edge of the clock.

Row 19 to 1D will check if Var E is set and then it will output the current turing value to output CV1 and generates a trigger. The value is optimized via multiplication and an offset so it is audibly more interresting.
Row 1F to 25 will check Input 4 and will randomly set or reset the LSB of the turing value if the input was high.
Note: the block row19-1D and row 1F-25 could/should be swapped for the better readability but it doesn't really matter for the result as always Variable F is being used for the output.

Row does reset Variable E again which takes care that all the important stuff up there is always only being executed once when the raising clock with a started sequencer happened.

Row 29-36 does generally a bitwise check of all the turing bits and outputs the bit states on the Trigger 16 Expander (NSA1) outputs 1-12. This gives a nice visual feedback of the turing value.

Print this item

  Bouncing Ball V1
Posted by: XORadmin - 01-06-2024, 09:27 PM - Forum: Mappings - No Replies

Here is the bouncing ball. Started by executing Row 01 (SHIFT+OK on 01) or the XMAP FX. Works with V2.0C

.map   BOUNCE1.MAP (Size: 1,47 KB / Downloads: 49)

Variable A: Width = Amount of notes
Variable B: Helpcounter to create the 'timebase'
Variable C: Tempo
Variable D: Note Offset
Variable E: Helpcounter
Variable F: Type of Trigger

Code:
00 SKIP     01 =     =0=0     >                            //always skip 1 row
01 VAR      #  A     #025     >                            //set variable A to 25 (amount of notes)
02 --              //upper part is to allow the start of the bouncing ball only from the XMAP FX command
03 CALC     INC      VBVB     >     SETV     V  B     SRC  //Increment Variable B  (B=B+1)
04 SKIP     02 >     VCVB     >                            //SKIP 2 rows if Variable C is bigger than Variable B
05 VAR      #  B     #000     >                            //Reset Variable B
06 CALC     INC      VEVE     >     SETV     V  E     SRC  //Increment Variable E (E=E+1)
07 --              //upper part generates a timebase/ tempo defined by variable C
08 SKIP     05 >     =1VA     >                            //Skip the next 5 rows if Variable A is 0 (or Var A < 1)
09 SKIP     04 <     VEVA     >                            //Skip the next 4 rows is Variable E is smaller then Variable A
0A VAR      #  E     #000     >                            //Reset Variable E again.
0B CALC     DEC      VAVA     >     SETV     V  A     SRC  //Decrement Variable A  (A=A-1)
0C VAR      #  F     #0E1     >     TRIG     VAL*     TR 1 // Generate a Trigger E1 on Trigger 1
0D CALC     ADD      VAVD     >     CV       NOTE     CV 1 // VA holds a note number, added offset defined by Variable D
                                                           //Output the Note on CV 1

So generally, 03 - 06 is a simple timebase and decrements E.
08 Skips always if A hasn't been 'executed / initialized'.
09 Skips until E reaches A and gets reset again on 0A
On 0B Var A is decremented. That repeats and gets faster as A is getting smaller and E reaches it faster until A is 0 and 08 will skip it again.
And VA is also being used to play a note and because it is getting smaller each time it will also play each time a lower note. D is just an offset to the Note you can add to have it in a range you like.

Print this item

  [FIXED] Scale name doesn’t update when changed with mapping
Posted by: yrn1 - 01-04-2024, 07:36 AM - Forum: Beauty and less important bugs/glitches - Replies (1)

OK, this is super-minor: when changing the scale with a mapping (e.g. by using a CV input for this), then in the name of the scale doesn’t update in the ‘project’ page nor in the ‘project -> scale’ page. It does update when moving the cursor in the project -> scale page, but not otherwise.

Print this item

  Issue with real time recording on 7&8 with Korg SQ1
Posted by: Renzki - 12-30-2023, 11:03 PM - Forum: General Questions - Replies (1)

Hi,

Not sure if this function was available in v1.27 but it really worked at considerably improving my workflow with v2.0. I am from an old school method of composition, and my experience using an external controller to record triggers and cv was basically cubase, which, to the best of my recollection, required you to change the midi channel number on the controller in order to record on the adequate Cubase track. It was not much of an issue, but this time I'm using the Korg SQ1. This controller requires to be turned off in order to change the midi channel. And going to that global mode also changes other internal presets and this is not really an option.

This is when I stumbled onto the midi in > record selected channel. This really changed the game with my rigg, I can now write very fast.

https://photos.app.goo.gl/Zd9S1meX6zKqhXbR6

Thing is, it does not work the same way with track 7 and 8. I have multiple one shot drum samples on them, and aware that they have 2 patterns in each. What happened is that it doesn't want to play anything at all. It seems that instead of notes, we have note off info and everything will be set to 0, even though it's recording.

Is there a part of the manual where this is examined clearly? My gates via midi from SQ1 are positive, and CV are -5v/+5v

I also have another question, is there a way to stop the record mode from the sequencer screen with a shortcut? I think not.. As this routing is somehow dangerous if you have dancers.

Many thanks

Print this item

  [FIXED] Midi note from mapping not quantized correctly
Posted by: yrn1 - 12-30-2023, 05:35 PM - Forum: Beauty and less important bugs/glitches - Replies (3)

When outputting MIDI notes from a mapping with

AUTM  SLT1  ---  >  MIDI  TC 4  NOTE

and a global or track-local scale applied, it does not quantize the notes correctly according to the scale. I does 'something', i.e. it doesn't play all the notes from the chromatic scale, but not correctly.
When doing the same, but with CV out (e.g. CV  NOTE  CV 1), the quantization is correct.

I attached a project (slow LFO into MIDI channel 4)



Attached Files
.nrd   MIDISCAL.NRD (Size: 438,5 KB / Downloads: 1)
Print this item