Firing rows, sample muted, cv glide

[septcercles]

Hi,
I'm Thomas, new player here.
I have to say I’m amazed by this workhorse. 
Thomas, It’s often that so many thanks goes from me to you when I discover new possibilities, I’m totally sticking to your spirit and how you bring it to life into your sequencer. I’m also absolutely craving for the new firmware and the new extension, the work you’ve done is amazing and so pertinent.

That said, I’ve been using the nerdseq for several month now, quite intensely, and i’ve got a few things making me scratch my head :

-        STSP and firing new row every tracks in sync : Many times I’ve got mixed of different pattern length in an island, and in between tracks, and I want to start a new row after the last  pattern of an island have been played, mostly to start tracks that where not playing yet or stopped. 
As the end of my islands are almost never just before a zero cross, it waits until the zero cross to start the row, while I want the whole row to be started right the STSP is fired.  Live queue point is set to 16, or whatever, but still it doesn’t fire the row even if it cross a Live queue point before the zero cross. In Normal or sync mode. 
What’s the quickest way to fire all the patterns of an entire row at the same time after a pattern is finished ? What I tried with the sync fx does not seems to help, but maybe it’s a matter of FX order ?
-        It’s not rare that the sample players got muted for unknowed reason. I have a keystep pro followed by a pyramid going in the midi input of the nerdseq. The keystep is knonwed to be buggy, and I often got the midi input stuck, mostly when I got arpegiator running wild into the nerdseq.  Is there a midi cc or something that mute and unmute the sample player, that I could try to block from entering the nerdseq unintentionally ?
-        The CV glide is quickly super slow since the very first digits, I tried playing with the step settings, but still not very convincing, how are you doing guys for subtle fast glide ? Is it possible to change the slope of the curve in the new firmware ?

 Thanks for your light

[XORadmin]

Hi,
I'm Thomas, new player here.
I have to say I’m amazed by this workhorse. 
Thomas, It’s often that so many thanks goes from me to you when I discover new possibilities, I’m totally sticking to your spirit and how you bring it to life into your sequencer. I’m also absolutely craving for the new firmware and the new extension, the work you’ve done is amazing and so pertinent.

That said, I’ve been using the nerdseq for several month now, quite intensely, and i’ve got a few things making me scratch my head :

-        STSP and firing new row every tracks in sync : Many times I’ve got mixed of different pattern length in an island, and in between tracks, and I want to start a new row after the last  pattern of an island have been played, mostly to start tracks that where not playing yet or stopped. 
As the end of my islands are almost never just before a zero cross, it waits until the zero cross to start the row, while I want the whole row to be started right the STSP is fired.  Live queue point is set to 16, or whatever, but still it doesn’t fire the row even if it cross a Live queue point before the zero cross. In Normal or sync mode. 
What’s the quickest way to fire all the patterns of an entire row at the same time after a pattern is finished ? What I tried with the sync fx does not seems to help, but maybe it’s a matter of FX order ?
-        It’s not rare that the sample players got muted for unknowed reason. I have a keystep pro followed by a pyramid going in the midi input of the nerdseq. The keystep is knonwed to be buggy, and I often got the midi input stuck, mostly when I got arpegiator running wild into the nerdseq.  Is there a midi cc or something that mute and unmute the sample player, that I could try to block from entering the nerdseq unintentionally ?
-        The CV glide is quickly super slow since the very first digits, I tried playing with the step settings, but still not very convincing, how are you doing guys for subtle fast glide ? Is it possible to change the slope of the curve in the new firmware ?

 Thanks for your light

Heya,

the main difficulty is here that the pattern from where you start the STSP is not a leading pattern, so the command to fire a new row is always based on the mainclock zero point or the cue points (Sync mode) or at the end of each pattern or cue point (normal mode).
The cue points are actually set when using the command twice (exactly as if you would press shift+start twice which is the same command).
I wouldn't know right now on how to get all synced at the same time based on a pattern. It might be possible with the upcoming version and triggering an internal delayed reset command, but I can't tell right now if that would be possible perfectly in sync or not.

-        It’s not rare that the sample players got muted for unknowed reason. I have a keystep pro followed by a pyramid going in the midi input of the nerdseq. The keystep is knonwed to be buggy, and I often got the midi input stuck, mostly when I got arpegiator running wild into the nerdseq.  Is there a midi cc or something that mute and unmute the sample player, that I could try to block from entering the nerdseq unintentionally ?

Are you using the latest version? There is no mute command from Midi in the current stable versions, so I guess there might be a different problem. Can you reproduce that easily (directly Keystep->NerdSEQ)?

-        The CV glide is quickly super slow since the very first digits, I tried playing with the step settings, but still not very convincing, how are you doing guys for subtle fast glide ? Is it possible to change the slope of the curve in the new firmware ?

Set the steps to a higher amount and the glide will be much faster and snappy. Values higher 9 and the glide itself to 1.