Firmware V1.20

[XORadmin]

second : i´m going nuts for two hours now , somebody figured out what PR does and how it works?

Haha....I know what it does!

Maybe you start a discussion thread for it...

[hardnut]

Thanks for this fantastic firmware update, Thomas. It's great!

[XORadmin]

People on MW were faster:

https://www.muffwiggler.com/forum/viewto...54#3149254

The secret or PR revealed

[spilthyfred]

Is there dedicated thread for Launchpad integration discussion?

[XORadmin]

Is there dedicated thread for Launchpad integration discussion?

Yep, here now:
https://xor-electronics.com/forum/showth...hp?tid=529

[Mat]

Woowwww, LFO/Modulation visual is crazy, wowwowow! <3

[pmarchitect]

Just updated and it's great.

But one problem:

I am getting stuck gates all the time from MIDI. After sending full stop signal it will trigger the first gate and then it's stuck again.

The only way to solve it is to reboot. I have had this issue with previous firmware but it was solved in 1.19. Now it's back again in 1.20

[XORadmin]

Just updated and it's great.

But one problem:

I am getting stuck gates all the time from MIDI. After sending full stop signal it will trigger the first gate and then it's stuck again.

The only way to solve it is to reboot. I have had this issue with previous firmware but it was solved in 1.19. Now it's back again in 1.20

Hey, oh that is not good.
The Midi implementation changed completely with the V1.20 and was tested quite a time. However there have been 2 reports of that but i asked for more information but never got any more feedback and it was impossible for me to reproduce it. I used several sources and tried to let it fail but it always worked well for me.
However, it seems to be there and maybe you can tell me some information about it.
What hardware do you use, how did you set up and can you reproduce it/how do you reproduce it?

[pmarchitect]

Just updated and it's great.

But one problem:

I am getting stuck gates all the time from MIDI. After sending full stop signal it will trigger the first gate and then it's stuck again.

The only way to solve it is to reboot. I have had this issue with previous firmware but it was solved in 1.19. Now it's back again in 1.20

Hey, oh that is not good.
The Midi implementation changed completely with the V1.20 and was tested quite a time. However there have been 2 reports of that but i asked for more information but never got any more feedback and it was impossible for me to reproduce it. I used several sources and tried to let it fail but it always worked well for me.
However, it seems to be there and maybe you can tell me some information about it.
What hardware do you use, how did you set up and can you reproduce it/how do you reproduce it?

Hi, I am using Digitakt as a little keyboard and to program simple beats / melodies into the modular as part of my workflow. So the Digitakt sends clock and midi notes / triggers to the 6 cv/gate tracks.

I don’t know if you remember me, but I had this issue before and you were testing with the Digitone, (which I also have), and you did a quick update which totally fixed the issue.

In terms of recreating it, it will happen within 5 minutes every time of having the Nerdseq on and working (which would involve a few times stopping and starting the sequencer).    

What happens is the gate gets stuck open, sending full stop turns the gate off. But after that, starting the sequencer it will be stuck open on the first gate received every time. I hope this helps. Apart from this issue everything else is looking really promising!

Happy New Year!

[XORadmin]

Just updated and it's great.

But one problem:

I am getting stuck gates all the time from MIDI. After sending full stop signal it will trigger the first gate and then it's stuck again.

The only way to solve it is to reboot. I have had this issue with previous firmware but it was solved in 1.19. Now it's back again in 1.20

Hey, oh that is not good.
The Midi implementation changed completely with the V1.20 and was tested quite a time. However there have been 2 reports of that but i asked for more information but never got any more feedback and it was impossible for me to reproduce it. I used several sources and tried to let it fail but it always worked well for me.
However, it seems to be there and maybe you can tell me some information about it.
What hardware do you use, how did you set up and can you reproduce it/how do you reproduce it?

Hi, I am using Digitakt as a little keyboard and to program simple beats / melodies into the modular as part of my workflow. So the Digitakt sends clock and midi notes / triggers to the 6 cv/gate tracks.

I don’t know if you remember me, but I had this issue before and you were testing with the Digitone, (which I also have), and you did a quick update which totally fixed the issue.

In terms of recreating it, it will happen within 5 minutes every time of having the Nerdseq on and working (which would involve a few times stopping and starting the sequencer).    

What happens is the gate gets stuck open, sending full stop turns the gate off. But after that, starting the sequencer it will be stuck open on the first gate received every time. I hope this helps. Apart from this issue everything else is looking really promising!

Happy New Year!

Ah ok i see. I remember i bought the digitone just for that (and rarely use it now, because i don't have time ).
I am sure the issue is a different one now. The main midi input changed completely from fixed to flexible, from monophonic to polyphonic notes. And i checked for the last issue already when implementing and again when i tried to reproduce.

I will copy this now to the bug reports and lets continue there. I will sent my questions there to hopefully be able to fix it soon!