Yes, it's time again for another update. Also this time, plenty of new features are added (some you would expect and some you didn't expect) and known (and unknown) bugs are fixed.
First, thanks for all the Release Candidate tests, they really helped to fix some hidden bugs. The good thing is that it all has been only minor stuff (also from V1.19 and earlier).
Some important information before you update:
- make a backup of your SD Card and especially of your projects - Old Projects can simply be loaded with the new version (also the projects from the Release Candidates should work). - Firmware updates always work, if it doesn't, then you did something wrong. Check the Firmware update FAQ for some infos. - No worries, in case of any issues you can always go back to your earlier version!
Also note: Since this version the update will look a bit different around the end of updating. For most people the Progressbar will go back to 0 and some percent. That is totally fine and as long as it says 'Updating Succeed', then everything is fine.
So here are the long awaited new features and fixes:
- Added live animation for automator screen
- Added Euclidean Rhythm input for Trigger16 expander
- Added Shift UP/DOWN of drum matrix column for Trigger16 expander. Shifts Up/Down the sequence in a drum matrix column (and inserts on carry)
- Fixed: Trigger16 drummatrix and the 8 normal Trigger16 columns overrule on swapped tracks
- Added functionality that cursor gets back to drummatrix when it was on drummatrix at latest
- Added missing probability on drummatrix in double pairs on first or 2nd 8 drumtriggers
- Added Launchpad Integration for Launchpad Pro, MK2 and Mini. You can only use the Pro for now as it has regular Midi In/Out. (Beta)
- Added decimal view in transpose, if decimal is on
- Added Version number in Setup screen
- Fixed possible hanging Midi notes on CV recording
- Added Mute and Solo for Trigger16 expander
- Added Speedup/Slowdown (Nudge) for finenudging and ticks (Project -> Tempo)
- Added 'Enter pattern screen on OK' function (if enabled). Enters pattern screen or creates a new pattern (if the spot was empty)
- Added 1.2V/Oct as alternative note-scaling (buchla)
- Added Hz/Volt note scaling
- Added Note transpose of marked values from sequencer screen
- Added MOD note transpose
- Fixed possible 'stop track now' and 'stop sequencer now' issues
- Added function to change global transpose on a zero transition or when pressing OK directly (Project screen->Transpose)
- Added track transpose to sequencer screen Nerd menu
- Fixed loading issue of older projects < V1.19 where the automator settings could be wrong
- Added pre-listening also for Midi tracks
- Fixed Page Up/Down in sequencer screen when marked
- Fixed possibility when creating a new (last) pattern that the sequencer could overwrite table fields
- Added Page Up/Down in calibrate screen to direct reach the needed part
- Added Note to the Trigger16 FX, so notes (with or without trigger) can be played on the regular CV/Gate output
- Added additional delay setting for the trigger column. Trigger delay settings for cv/gate setup screen, so triggers can be delayed more compared to the CV outputs.
- Update: If a trigger is filled in in the trigger column, then it always overrules the note auto-gate regardless of probabilities
- Added: User Interface menu and screen to change font (5 new fonts) and screen colours
- Added: Midi recording with flexible input routing, added polyphonic recording (Notes, CC, aftertouch, pitchbend etc) into midi tracks, recording and playing into Trigger tracks, Midi pitchbend into CV tracks, Midi to transpose tracks and transpose all
- Fixed: When marking, SHIFT+DOWN marks all now also for Midi and Trigger16 screens.
- Added: Delete while recording: Deletes if recording and in pattern screen and pressing the table button for parameters that are selected to record
- Added recording into the current cursor position for CV input and Midi (Note input into patterns through CV inputs or Midi with or without running sequencer)
- Major CV recording update, Flexible input routing, Live CV input for transpose, manipulations, Sample playing, sample pitch, slot and gate recording, XY Sequencer Move, Input->Output quantization
- Added manual CV calibration
- Added: PR
- Added: Pre-listening for MOD values and not only notes
- Fixed: Unwanted BRK0009 insertion in sample screen on first parameter
- Fixed Midi mark values for FX columns
- Added per track transpose including settings to allow or avoid track transpose or global transpose for the track (track settings and special FX)
- Added All Sound off function (midi controller78)
- Fixed Midi basenote FX
And many minor small things that came along the way or needed to be done...
The new firmware is attached here, download it, put it in your firmware folder and update following the usual firmware update instructions.
Also to be sure that you don't miss any feature or to know how it works, check the manual.
The new manual version V1.0.7 is available in this thread: https://forum.xor.eu/showthread.php?tid=523
Don't forget to spread the word, make videos, because that is what's needed to continue adding new features!!
Can I just check please... for modular tracks you can edit the triggers directly with the launchpad, but this doesn't work with sample tracks.
Presumably this isn't supported yet rather than a bug with my launchpad?
Also, in Brandon Logic's video https://www.youtube.com/watch?v=FLoKOoYwuRM he is using note input on the launchpad. Was that using a different version of the firmware than the current version with launchpad integration? In your release notes you don't mention note input so I expect this feature is not in this build, but again double-checking to make sure my launchpad doesn't have a fault or needs a firmware update itself.
In simple terms I'd like to have a kind of "MI Branches" function between the sample tracks.
It could be great for a stereo usage
Running the same sequence in both sample tracks but the effective output would be randomly choosen.
And even between the 2 tracks included inside one sample track !
And even between the "regular tracks" !
Clocking MI Grids from a trigger output, and sending a reset from another trigger output to Grids at specific times results in grids getting slightly out of time or double triggering.
Grids needs 24ppqn so I write a pattern with triggers filled in on every step and the groove set to 1.
I've tested this sending triggers from my computer (Renoise/logic/ableton) and the problem is not there.
Is there a chance the triggers are sent out at very slightly different times?
I get plenty of questions from all channels asking the same things over and over again. So read this first before asking!!
I just received my NerdSEQ and used it for 2 days. Can you please add feature X, Y and Z together with changing A, B and C and that feature that the other sequencer has?
Short answer: NO. Please learn the NerdSEQ first to find out what you really need. After 2 days I don't think that you dived deep enough to know all the possibilities (and probably why your request doesn't make sense or doesn't fit to the workflow). I am not really interrested of what other sequencers do and I don't want to copy any functionality. The NerdSEQ is its' own thing and other sequencers are their own thing. I am interrested in implementing nice and cool, maybe sometimes a bit weird and unexpected features. Only copying mainstream features is boring and doesn't really inpire me to keep on adding features to the NerdSEQ.
There is help on this forum to get things running as you want it and all the common stuff have been answered multiple times. And more important, look into the manual if the functionality you want is not already there. And 2nd, look into the forum if something similar has not been requested already.
Will it also work with Ableton Push, Push 2 etc or only with the Launchpad?
No, it will not work with the Ableton Push controllers. These always need a computer to work. Also i am not planning to support other controllers for now, except for the case you donate one to me and if these make sense to use (same kind of buttons available) and if i got time left.
This doesn't have anything to do with CC Midi controllers though, they can be of course used to insert Midi Data.
I want these contitional triggers that elektron has. Can you implement it?
No, that is not possible in that way, it would need much more memory to keep count of every pattern cell (for each track). You can get similar (and more advanced) functionality with smart arrangement of your patterns/loops and the use of the mappings.
The manual says that 4 expanders can be connected to the NerdSEQ. Does that include also one of the Midi Expanders?
No, the Midi expanders got their own connector. So it is 4 Expanders + one of the Midi Expanders.
What happened to the Cartridge expanders and Synth Cartridges?
Currently nothing yet. They are still planned and will be there at some point for sure.
What happened to the Matrix expander i saw? Will it ever be made?
The Matrix expander was just an idea with a 'Proof of concept' prototype. When i made the Launchpad integration it went obsolete. Mostly because I can't produce something for a good price with RGB LED inside and a 8x8 button matrix + 16 extra buttons which would fit into the rack. And if, it would cost like 4 times more than a launchpad. It's just not worth the effort to make it in the end, so i stopped developing it.
Will function X will be in the next release?
No! You will mostly see in the release candidates and teasers what the next release will bring. My 2do list is long and everytime someone keeps asking for feature X then it will automatically scroll down in my 2DO list Many things will be added, some not and the list frequently changes with every function. Sometimes when I am busy with one part, it makes sense to add another part.
I am disappointed that function X is not in the new release. Why didn't you add it but instead added other stuff i don't need?
I can imagine that you are disappointed. But keep in mind that I am doing this all on my own and I can only do one thing at a time. Some functions need much work while others are very fast implemented. Some things are more urgent while others are not. Features that can be done already in other ways have mostly a lower priority. All the free updates contain always many new features and I can never please everyone. Also one important thing is that i sometimes add stuff directly when it comes in my mind and i think it is cool. This is also where i get motivation for myself from it. Because I am using it myself and want to have fun with it. This brought you already many cool unusual features that you don't know from other sequencers. I will keep doing that and at some point maybe also your long awaited feature is implemented. I keep track on the feature requests at all times.
Can you please add a shortcut for function X?
Generally my philosophy is to not add any weird button shortcuts. I want to keep the button functions clean from that. Nearly all navigation is available with the button or shift+button. They are only very little ones where it really makes sense to have more buttons used (Copy Paste or delete with moving, Mute/Solo). I will try to avoid more combos except for if they are well thought of and are for that killer feature which really is needed to be on top of control. If i would start over again with the NerdSEQ i would have added more buttons and some encoders. But now we got to stuck with the current hardware.
Will i get more tracks when i add a expander?
No, there will never be more tracks. Expanders can be integrated in the current tracks and add more features. And you still keep the functions of the local outputs. So you don't lose anything but only get more. Another thing is that i want to keep all tracks visible and usable on the sequencer screen and there is no space to fit more tracks. NerdSEQ will always stay with 8 tracks.
Why are they only 6 or 8 Columns for the Trigger16 or CV16 accessible per track and not 16 columns for the 16 outputs?
Unfournately, the amount of columns is limited per track and can't be enhanced because there is not more memory available to do that. However, you can still access always all outputs through the FX, patches, mappings etc. And you can use one expander on multiple tracks. Also it is always assignable which outputs should be directly available per track. The Trigger16 can additionally use all 16 trigger outputs directly through the drum-matrix. The CV16 can also be flexible programmed. And to be honest, I don't think it's too bad for a hardware sequencer having 9 voices (and more) directly available per track while on the other outputs lfo's are running....
My automator LFO is broken and it outputs only the positive waveform but the negative waveform cuts off. Is this a firmware bug?
No, this is no bug but it is the intended function and only got set it up correctly. You got to know two things: 1.The automators (LFO) are bipolar and generate positive and negative values. 2. If you route them to the CV or MOD outputs then they are added (or subtracted) to the output. So on the positive wave-phase the LFO will be added to the output and on the negative phase it will be subtracted. Now if your output is playing on the lowest pitch (like a note C-0 or 000) then the negative wave of the LFO can't be more subtracted as the output is on it's lowest possible value already.
What you need to do is either to set the output to a higher value (Like C-5 / 800) and then the full LFO range will add and subtract around that 5 volt. One usecase would be to have a vibrato around your note. Another option is to change the offset of the automator LFO so the output voltage would shift up (or down).
So this in an intended functionality and you only got to keep in mind to set up your output together with an automator. In any way, a LFO can be used with it's full range of 10 Volt on an output.
I was wondering it would be difficult to create a mini midi I/O expander? I have a pretty tight case and I don't have need for the sega controller input. Has anybody requested this or made their own?
Many things will be added, some not and the list frequently changes with every function. Sometimes when I am busy with one part, it makes sense to add another part.