Firmware V1.19

[XORadmin]

You can simply transpose all from the project menu. Shift up/down as usual for an octave and left/right for a semi-note.
Though, this update is already several months old :-)

Thanks! That one I know, although it would be mighty handy if it would be possible to transpose per octave. Then a simple precision adder could be patched into any of the inputs, and this way it would be incredibly easy to manually transpose separate tracks one octave up/down.

I think you’d try the latest V1.20 release candidate then. Because with it you could do this i think.

Yesss, i did, and it's awesome . However, i was wondering if next to the option of live transposing tracks per semitone, there would be also the possibility of transposing octaves. But i couldn't find it, so i guess it's not (yet) implemented. Right now i'm using an O&C for that purpose, running the cv out of the Nerdseq into the O&C, and transpose octaves using channels 2 and three of MN Maths. Thought it might work to run that into the live input and look for an octave transpose in the Nerdseq, but couldn't find it

But octave transpose is easy just using 1(or more)  volt higher or lower. If you want to be one octave higher then you put 6 volt on the input...ir 2 octaves lower, then 3 volt. Or whats your idea about it?

[Mat]

You can simply transpose all from the project menu. Shift up/down as usual for an octave and left/right for a semi-note.
Though, this update is already several months old :-)

Thanks! That one I know, although it would be mighty handy if it would be possible to transpose per octave. Then a simple precision adder could be patched into any of the inputs, and this way it would be incredibly easy to manually transpose separate tracks one octave up/down.

I think you’d try the latest V1.20 release candidate then. Because with it you could do this i think.

Yesss, i did, and it's awesome . However, i was wondering if next to the option of live transposing tracks per semitone, there would be also the possibility of transposing octaves. But i couldn't find it, so i guess it's not (yet) implemented. Right now i'm using an O&C for that purpose, running the cv out of the Nerdseq into the O&C, and transpose octaves using channels 2 and three of MN Maths. Thought it might work to run that into the live input and look for an octave transpose in the Nerdseq, but couldn't find it

But octave transpose is easy just using 1(or more)  volt higher or lower. If you want to be one octave higher then you put 6 volt on the input...ir 2 octaves lower, then 3 volt. Or whats your idea about it?

Yes, i agree! But then you'd have to use a precision adder to achieve that. I thought it would be cool if somehow the voltages could be quantized within the Nerdseq, so that any CV could be used to do octave shifting, not only precision adders, but also lfo's, envelope generators.. fixed voltage generators or anything else really

[ehr]

I've been using the groove column for simple 2x and /2 clocked patterns...works great. I recently tried the new track clock command on the effect column to do what I'd been doing with groove and noticed that when using the clock command in the efx column to change the track clock the pattern has to play through once before the change takes effect. Is this something that is unavoidable? Maybe I'm missing something or doing it wrong....

[persi74]

A massive update just arrived. Adding some long awaited features, some unexpected stuff and fixes.
Also there is support for expanders included and the 'More Triggers 16' expander is available now, too. Check another thread here for that one.

Some important information before you update:
- make a backup of your SD Card and especially of your projects 
- Old Projects from V1.18C and older can simply be loaded with the new version. Projects are not full downward compatible. So they might be some oddities if for expample saved with V1.19 and loading it with an older version V1.18 or earlier.

Here is a list of all the changes:
- Added: Midi sequencing:
    - new pattern screen for 4 note polyphonic (+ Velocity) sequencing per track.
    - Midi track support Notes, Pitchbend, Program Change, Polyphonic and Channel Aftertouch, CC, NRPN, flexible assignment of tracks and midi channels
    - Midi notes can be played (cloned) on the local modular tracks (CV & Gate) if wanted.
    - Most Midi commands can also be controlled by the automators
    - Midi Probabilities: Note1, Note2, Note3, Note4, FX1, FX2, FX3
    - Flexible Limiter for automation to Midi to reduce Midi data
- Added: NSA (Nerd Sound Adapter) Expander support. Beside the Midi expander 4 additional expanders can be connected which are then integrated in the sequencer.
- Expanders can be assigned to one or multiple tracks.
- Firmware updates of the expanders simply possible via the NerdSEQ. So new features are also possible for the expanders. As reliable as NerdSEQ firmware updating.
- Trigger 16 Expander:
    - Provides 16 more Trigger/Gate outputs with all functions the local trigger outputs can do (eg. Trigger Length, Delayed Gate, Retriggering....)
    - Binary output to be able to create some cool dividers
    - Added Trigger 16 screens and sequencing + integration with all FX and Automators.
    - Added drummatrix to allow classic drum sequencing with a good overview
    - Square wave generation to trigger output from automator lfo
- Added Track Setup screen for all track types where Track specific settings can be done.
- Fixed: when pressing stop twice (or stop track from FX) could insert problems
- Fixed: Possible crash when starting the sequencer with an empty project from external clock
- Added: General Track Assign screen where tracks can be assigned to either Internal CV/Gate, Midi or to the available expanders.
- Added: FX command to start a pattern from the sequencer by position
- Fixed: Avoid Sample retriggering without a playing sample
- Added: SHIFT+DELETE on a Note column acts now as either 'Delete Note' or as 'Insert Note Off', no browsing down to lowest note needed anymore.
- Fixed: possible SEGA gamepad freeze situation after saving
- Fixed: Muting for sample patterns with odd groove settings
- Added: Start playing possible from all regular screens now
- Fixed: Compact pattern function with copy/paste clipboard
- Added: Copy paste between compatible pattern columns. Copy and paste can be from all notes to all notes, triggers to triggers, grooves to grooves from different pattern types. Content can now also be copied between the 2 sample parts.
- Added: Per track multiplier / divider. Dividers and Multipliers can be either live assigned to a track or via FX command.
    Dividers/Multipliers: /32,/16,/8, /7,/6,/5,/4,/3,/2, *2,*3,*4,*5,*6,*7,*8)
- Visual updates: Sequencer screen layout, divider settings are shown per track, introduced VU meters for the samples, main clock indicator update
- Added: Colors on sequencer screen. Change the colors of special parts for fast recognition
- Enhanced: Longer filenames support for sample loader
- Added Enabling/Disabling of Midi clock output

So get it, check it out. Make videos. Spread the word. Buy the expander ;-)
But most important, enjoy!!!

The new firmware is attached here. This time also as .zip, so you need to unpack it into the firmware folder te be able to use it.

The updated manual is available in this thread:
https://xor-electronics.com/forum/showth...hp?tid=370

Please check the firmware update thread as well and read in the manual in case of any update issues.

Yess....is amazing the abilty to set different functions to midi channel as well live input...now i experiment to transpose arpeggio from LP in scale mode ...rene use like voltage memory and plate keyboard ..i can't sto to play!!thank's ..I READ THE MANUAL!!

[XORadmin]

I've been using the groove column for simple 2x and /2 clocked patterns...works great.   I recently tried the new track clock command on the effect column to do what I'd been doing with groove and noticed that when using the clock command in the efx column to change the track clock the pattern has to play through once before the change takes effect.   Is this something that is unavoidable?   Maybe I'm missing something or doing it wrong....

The main reason is that this is the only way to stay in sync with everything else. So you can switch while playing to other (even) scales and it would stay synced with the possibility that you as well can switch back to normal clock. If you could do this on the fly, you would directly loose the synchronisation.
The same for the groove indeed, if you edited the groove and the sequencer is passing half waym then your chance it big that it would run out of sync (because thats what is programmed in then).

[ehr]

I've been using the groove column for simple 2x and /2 clocked patterns...works great.   I recently tried the new track clock command on the effect column to do what I'd been doing with groove and noticed that when using the clock command in the efx column to change the track clock the pattern has to play through once before the change takes effect.   Is this something that is unavoidable?   Maybe I'm missing something or doing it wrong....

The main reason is that this is the only way to stay in sync with everything else. So you can switch while playing to other (even) scales and it would stay synced with the possibility that you as well can switch back to normal clock. If you could do this on the fly, you would directly loose the synchronisation.
The same for the groove indeed, if you edited the groove and the sequencer is passing half waym then your chance it big that it would run out of sync (because thats what is programmed in then).

That makes sense. 

The way I've been using groove column is to double the ticks per step of all the steps in the patterns that I want to play at a /2 speed then press play.   I don't make changes while the pattern plays.   I just thought that putting one clock command on the first step of the pattern would be easier than changing all the groove steps of the pattern.   No worries using groove works good.

[XORadmin]

I've been using the groove column for simple 2x and /2 clocked patterns...works great.   I recently tried the new track clock command on the effect column to do what I'd been doing with groove and noticed that when using the clock command in the efx column to change the track clock the pattern has to play through once before the change takes effect.   Is this something that is unavoidable?   Maybe I'm missing something or doing it wrong....

The main reason is that this is the only way to stay in sync with everything else. So you can switch while playing to other (even) scales and it would stay synced with the possibility that you as well can switch back to normal clock. If you could do this on the fly, you would directly loose the synchronisation.
The same for the groove indeed, if you edited the groove and the sequencer is passing half waym then your chance it big that it would run out of sync (because thats what is programmed in then).

That makes sense. 

The way I've been using groove column is to double the ticks per step of all the steps in the patterns that I want to play at a /2 speed then press play.   I don't make changes while the pattern plays.   I just thought that putting one clock command on the first step of the pattern would be easier than changing all the groove steps of the pattern.   No worries using groove works good.

But when that track is not playing, the scale changing will take effect directly, pressing start then will start the pattern directly in the chosen scale.

[ehr]

I've been using the groove column for simple 2x and /2 clocked patterns...works great.   I recently tried the new track clock command on the effect column to do what I'd been doing with groove and noticed that when using the clock command in the efx column to change the track clock the pattern has to play through once before the change takes effect.   Is this something that is unavoidable?   Maybe I'm missing something or doing it wrong....

The main reason is that this is the only way to stay in sync with everything else. So you can switch while playing to other (even) scales and it would stay synced with the possibility that you as well can switch back to normal clock. If you could do this on the fly, you would directly loose the synchronisation.
The same for the groove indeed, if you edited the groove and the sequencer is passing half waym then your chance it big that it would run out of sync (because thats what is programmed in then).

That makes sense. 

The way I've been using groove column is to double the ticks per step of all the steps in the patterns that I want to play at a /2 speed then press play.   I don't make changes while the pattern plays.   I just thought that putting one clock command on the first step of the pattern would be easier than changing all the groove steps of the pattern.   No worries using groove works good.

But when that track is not playing, the scale changing will take effect directly, pressing start then will start the pattern directly in the chosen scale.

Goove works this way, but SCLK in the effects column doesn't.  It takes effect after the pattern loops around once or on the start of the next pattern if there is a pattern chained after it.

[XORadmin]

I've been using the groove column for simple 2x and /2 clocked patterns...works great.   I recently tried the new track clock command on the effect column to do what I'd been doing with groove and noticed that when using the clock command in the efx column to change the track clock the pattern has to play through once before the change takes effect.   Is this something that is unavoidable?   Maybe I'm missing something or doing it wrong....

The main reason is that this is the only way to stay in sync with everything else. So you can switch while playing to other (even) scales and it would stay synced with the possibility that you as well can switch back to normal clock. If you could do this on the fly, you would directly loose the synchronisation.
The same for the groove indeed, if you edited the groove and the sequencer is passing half waym then your chance it big that it would run out of sync (because thats what is programmed in then).

That makes sense. 

The way I've been using groove column is to double the ticks per step of all the steps in the patterns that I want to play at a /2 speed then press play.   I don't make changes while the pattern plays.   I just thought that putting one clock command on the first step of the pattern would be easier than changing all the groove steps of the pattern.   No worries using groove works good.

But when that track is not playing, the scale changing will take effect directly, pressing start then will start the pattern directly in the chosen scale.

Goove works this way, but SCLK in the effects column doesn't.  It takes effect after the pattern loops around once or on the start of the next pattern if there is a pattern chained after it.

Just to be sure: You can change a non playing track scale which will take effect immediately (using the Nerd button)

[ehr]

The main reason is that this is the only way to stay in sync with everything else. So you can switch while playing to other (even) scales and it would stay synced with the possibility that you as well can switch back to normal clock. If you could do this on the fly, you would directly loose the synchronisation.
The same for the groove indeed, if you edited the groove and the sequencer is passing half waym then your chance it big that it would run out of sync (because thats what is programmed in then).

That makes sense. 

The way I've been using groove column is to double the ticks per step of all the steps in the patterns that I want to play at a /2 speed then press play.   I don't make changes while the pattern plays.   I just thought that putting one clock command on the first step of the pattern would be easier than changing all the groove steps of the pattern.   No worries using groove works good.

But when that track is not playing, the scale changing will take effect directly, pressing start then will start the pattern directly in the chosen scale.

Goove works this way, but SCLK in the effects column doesn't.  It takes effect after the pattern loops around once or on the start of the next pattern if there is a pattern chained after it.

Just to be sure: You can change a non playing track scale which will take effect immediately (using the Nerd button)

Yes, but I like to use the groove column because I have multiple songs in each project and prefer to have the setting per song, with groove, and not have to change the track scale between songs.   Would you consider having SCLK command scale immediately like the Nerd button track setting if pressing Play from a stopped sequencer, and if the sequencer is running have SCLK function the way it does now?  Just a thought, not important...we have groove