(12-11-2023, 12:18 AM)MatzeMillion Wrote: Starting multiple marked tracks at once is only working if the sequencer is stopped. Not sure if this is intended. It would make sense to have this function as well when the sequencer is running.
Stop works when the sequencer runs of course.

When I created 2 envelopes, both triggered by the same source, both with same attack time, but different attack peak, do not reach that peak at the same time. The one with the lower peak reaches it faster.

I'm not sure if this is a bug or I should post this in the new firmware 2.0 section? Anyhow, for some reason I notice that Auto Fill-In Trigger gives (on my NS) a value of E1. On all previous firmware it gave a value of 40 as stated in the manual.  

By the way, although this I'll put in the feature requests, it would be interesting (IMHO) if one could set their own auto fill-in value, and even better if that could be set per project.

Hi
My new launchpad mini das not work :-(  (can anybody give some help)
i updated the multi IO expander and and the host  after upgrading the nerdseq to 2.0
i set the midi expander to multi io
midi/i2c setup  - set to mini - Host

is there some setting in the launchpad i mis? last software is set.

Hi out there,

with the new firmware we all got the opportunity to write some individual skripts to fix modulation ideas and more.

While I am currently using mapping mostly for manipulation LFOs and Envelops via fader, I'd be super interested on your ways how to use mapping and specifically the scripting.

So, how about sharing your ideas and discuss what we all explore?

I am sure that there are some super Nerds ? that could help all of us to fully use the potential of f2.0 for better realzing our musical ideas.

On the Multi-IO is it possible for future runs to have 90 degree headers instead of the straight headers? I have an Intellijel 7u case and the Multi-IO cannot fit where I want it when I2C is plugged in. If the headers were 90 degree this would be alleviated.

Post all your mapping related questions here.

In the mapping would it be possible to get some kind of constant source value? I'm trying to do it with addition but it's not working. Generally I have some MIDI CC's that I want to set and I have no way to set them to a fixed value. I'm able to set row values but I can't seem to find away to just get a constant value.

Also is it possible to get the CC's to display in hex? I have a bunch of notes where I've written down hex values and I'll have to convert them all to decimal :/

It seems that this skip functionality is very common when needing to call mappings from other parts of the system:

'SKIP' '01 =' '=0=0'

Maybe another command could be added that support this specific use case? "SKIPX" All you supply is the number of rows to skip? It reminds me of a function call, maybe it could include a comment? Especially if you're going to skip a bunch and implement a large concept?

Lets start a new thread now it is out of Beta and available.

Note: All the basic stuff about connecting I2C and information you need is provided in the Installation Guide which came with the Multi-IO and in the currently Preliminary Manual for V2.0.

- You got to enable the Multi-IO in the NerdSEQ Setup Menu. SHIFT+SETUP -> MIDI Expander, change this to Multi-IO. Leave the menu. It might be possible that you got to restart the NerdSEQ once.
- The Front I2C Port and Backside port A are the same and it uses the same Pullup
- Mostly use the 3.3Volt pullup or none if the other gear got already a pullup installed. You can start always without and see if it works reliably or if at all.
- ALWAYS turn all power off before you connect any I2C gear. That applies for the front and backside port
- The 16n and derivates (eg F8R) do scan for any I2C gear 10 seconds after its startup if they are set to leader mode. And if it missed that scan then it won't work. It is possible that it didn't scan the Multi-IO if the I2C port on the Multi was not configured for it. In that case you would configure first and then give the 16n a power cycle. Rule to follow: Use 16n -> NS then the 16n got to be in leader mode, Address to 31hex. If the 16n is set to follower mode then the NerdSEQ got to be set to NS -> 16n 1-16, the address is not important for it.
- No, a 2nd Midi Interface (TRA-A or classic Midi-IO) won't provide an additional Midi Port to the NerdSEQ.
- The encoder is not a push-button