Since the main topic is locked (!?) :
n0nx0x2 (2.11) seems to have issues when stopping the sequencer, be it standalone or midi-slaved. Sometimes it stops correctly, ie: editing is possible in write mode and dinsync stops correctly; but most of the time a note get stuck, editing is not possible and dinsync outputs random pulses and finally restarts. I need to restart/stop the clock several times to stop the sequencer correctly. Is there a setting to correct this ? I tried a reset but it didn't solve this problem.
Thanks
n0nx0x2 - Stop issues
Moderators: altitude, adafruit_support_bill, adafruit, phono, hamburgers
Please be positive and constructive with your questions and comments.
- gelabs
- Posts: 23
- Joined: Sun Jun 19, 2011 4:13 pm
Re: n0nx0x2 - Stop issues
If it can be of any help to diagnose the issue : when the problem appears the tempo LED stays lit.
- antto
- Posts: 1636
- Joined: Thu Apr 15, 2010 3:21 pm
Re: n0nx0x2 - Stop issues
wot?! o_Ogelabs wrote:Since the main topic is locked (!?)
a ton of threads are actually locked, in all of the x0xb0x subforums
based on the symptoms, i guess you mean stopping the master causes n0nx0x2 to freeze (tempo LED stops blinking)n0nx0x2 (2.11) seems to have issues when stopping the sequencer, be it standalone or midi-slaved. Sometimes it stops correctly, ie: editing is possible in write mode and dinsync stops correctly; but most of the time a note get stuck, editing is not possible and dinsync outputs random pulses and finally restarts. I need to restart/stop the clock several times to stop the sequencer correctly. Is there a setting to correct this ? I tried a reset but it didn't solve this problem.
Thanks
this would happen on what i call "lousy" masters which stop generating sync clock when stopped
- gelabs
- Posts: 23
- Joined: Sun Jun 19, 2011 4:13 pm
Re: n0nx0x2 - Stop issues
I think Zaquencer has a quite healthy implementation of midi clock and still generates the clock even when stopped. I'll have to check that this evening.
Could it be possible to alter the code in the firmware to react to a midistop message (even if the clock stops), and have it reset on step 1 of a pattern just like the other firmwares, for example ?
Could it be possible to alter the code in the firmware to react to a midistop message (even if the clock stops), and have it reset on step 1 of a pattern just like the other firmwares, for example ?
- gelabs
- Posts: 23
- Joined: Sun Jun 19, 2011 4:13 pm
Re: n0nx0x2 - Stop issues
So, it appears that Zaquencer does indeed stop generating midiclock when stopped ...
I modified my midi routing and put an x0xb0x as masterclock, less convenient but it works ...
I modified my midi routing and put an x0xb0x as masterclock, less convenient but it works ...
- gelabs
- Posts: 23
- Joined: Sun Jun 19, 2011 4:13 pm
Re: n0nx0x2 - Stop issues
Speaking of n0nx0x, antto, could you please publish the code on Github/Gitlab ?
- antto
- Posts: 1636
- Joined: Thu Apr 15, 2010 3:21 pm
Re: n0nx0x2 - Stop issues
it's on gitlab but not public.. for reasons
sync masters which stop the clock when not playing are dumb, they should at least send out one or a few additional clock ticks
or "All Notes Off" or something
sync masters which stop the clock when not playing are dumb, they should at least send out one or a few additional clock ticks
or "All Notes Off" or something
- gelabs
- Posts: 23
- Joined: Sun Jun 19, 2011 4:13 pm
Re: n0nx0x2 - Stop issues
Oh ok, whatever are those reasons I respect your choice.
I have posted a request on Zaquencer forum about the clock issue, we'll see ...
Thanks anyway.
I have posted a request on Zaquencer forum about the clock issue, we'll see ...
Thanks anyway.
Please be positive and constructive with your questions and comments.