Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Release Candidate Firmware V2.03 RC1
#11
Really appreciating your effort. I just purchased the dualchord and am looking very much forward to check out the new features.
Reply
#12
(04-01-2025, 02:58 PM)XORadmin Wrote:
(04-01-2025, 02:55 PM)Dissonant Waves Wrote: Totally new here and new to the NerdSeq.  Should I go ahead and install 2.03RCI?  Im on 2.02A right now.  Like i said, I'm learning how to use the NerdSeq so I feel useless on reporting bugs ATM.

Only use the stable versions which is V2.02A currently.
• I 

i Hi Thomas

Today i found a possible conflict between CV4 and the MODs in the “Automator”. For example, activating MOD5 also affects CV4.


• When mapping a MIDI signal through the Automator (Autom-Slot2 > MIDICC-CH1-#1), if I change the source and send an external MIDI signal instead (MIDCC-TCH1-#70 > MIDICC-CH1-#1), it still remains active on the previous source “Automator”. This happened to me on the 4th project output.

• If I use the Automator to send a signal to a modulation output via mapping (Autom-Slot2 > CV-Pitch-MOD4), when I stop the Automator, the MOD output sends a medium-level signal instead of resetting to zero.

• Imported pattern does not work


Hope this helps
Reply
#13
(04-11-2025, 12:39 AM)Jas1x Wrote: i Hi Thomas
Hi Smile
Quote:When mapping a MIDI signal through the Automator (Autom-Slot2 > MIDICC-CH1-#1), if I change the source and send an external MIDI signal instead (MIDCC-TCH1-#70 > MIDICC-CH1-#1), it still remains active on the previous source “Automator”. This happened to me on the 4th project output.

I got to check that but it should normally be fine. The first Midi CC input signal should change the destination after you changed the source.
Maybe you can show a little video about it showing the mapping screen. Also keep in mind that too much data can overflow the Midi bandwidth.

Quote:If I use the Automator to send a signal to a modulation output via mapping (Autom-Slot2 > CV-Pitch-MOD4), when I stop the Automator, the MOD output sends a medium-level signal instead of resetting to zero.

That is correct. Automators do work bipolar and zero is the neutral position. The mapping values are only positive and so the automators are mapped unipolar and the zero position of the automator is the middle position of the mapping.
The question is why do you use the mapping to send an automator to a CV output. The direct modulation matrix of the automator itself is much better for it and it works indeed 'bipolar'.


Quote:Imported pattern does not work

Is the version you use this release candidate? Did you export the pattern with an earlier version? Can you maybe attach the pattern here so I can check?


Also, this release candidate is not supported anymore. A new version which is in the making will replace this. I suggest to only use the stable version for now.
PLEASE use the search function if something have been asked or discussed before.
Every (unnessesary) forum support means less time to develop! But of course, i am here to help!  Smile
Reply
#14
after quite some time of absence i installed this firmware today and so far i was able to jam without an issue. but surely, i just scratched the surface and didn't dive any deeper than a few lfo and fx commands. everything i used ran smoothly
Reply
#15
(03-22-2025, 10:04 AM)XORadmin Wrote: I think I will skip that release.

They were not many downloads and nearly no feedback (thanks for the ones who did). Nothing at all about the new (requested) functionality.
The idea for release candidates is to get feedback if things are ok or if some of the new stuff needs some finetuning.

By now I am already working on something else and I don't think it's worth to get back in the codebase to make a release.

Of course the question comes up in me if there is much interrest in new releases. The latest firmwares showed much less downloads than earlier ones even though many cool features have been added.

I really appreciate all your hard work!

Personally I am more invested in running the nerdseq *bare* without any extra modules or midi, so I won't be jumping on anything that has to do with expanders or MIDI etc.

My only request for the Nerdseq at this point are the few things that could make it faster to move around and work in, as I've mentioned before (and as you DID add in the last update, which was amazing - thank you!).

I got an M8 recently and I feel a lot faster with it, despite the nerdseq having more buttons. These aren't in competition, but it's difficult not to compare interfaces.
What I'm missing on the Nerdseq that the M8 has is only pressing OK to always paste the previously touched value for that column, or cycling through marking cell, column, row or the whole pattern (by pressing the sequencer button while already being in mark mode?) or being able to rotate marked parts with a shortcut (what's currently in the nerd menu).

I'm very content with all the available features Smile
Feature-wise this is a complete product for me. Ofc you can always add more lol.



And I don't know about everyone else, but for me eurorack is a seasonal/cyclical thing - I jam a lot on it for a couple of months, then I don't mess with it for a while, then I'm back on - so I'll def be back on shortly!
Again, appreciate all your hard work, I'm so happy with my nerdseq.
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)