Analogue-sequencer

Sorry for the late reply. Comments inline:

Colin f wrote:
>  
> 
>>   Is their any way of incorporateing any of these features into your
>>Poly Record?
> 
> 
> I've been doing more work as a result poly record (though the last week has
> been spent on the 'half day' task of moving to a new PC), but this has
> involved tidying up loose ends rather than adding new features.
> 
> One of the things that I spotted after adding poly record was that it was
> possible to lose notes when different primary and aux notes in a pattern
> were set to the same note values across tied steps.
> For example, if a primary note is C5, and an aux note G5, and they are tied
> to a step with a primary note of G5 and the aux note C5, you get a note-off
> for the two previous notes immediately after the note ons for the tied step.
> This cuts both notes off - the code is only checking for the same notes in
> the same position, so it doesn't see that pair of notes is the same but
> swapped round.
> 
> There was also the possiblity to send multiple instances of the same note on
> on a single step, by assigning the primary and aux notes the same note
> value. This isn't a problem for P3, but it can upset some synths.
> 
> So I've re-written the way the sequence engine handles multiple notes.
> It now supports up to 8 notes per track. You still only have one primary and
> 4 aux notes in a pattern, but you can redirect aux notes from other tracks
> up to a maximum of 8 on each track.

Yes, Yes, Yes! I would have liked this and suggested it, but didn't
think you'd be able to do it.


> Tied groups containing the same notes are handled correctly, and note-ons
> are thinned so there is never more than one note on sent for a given note
> number on any step.
> Next on my list is re-ordering recorded notes in ascending order so the
> primary note is the lowest, followed by UI to quickly set up auxes for
> notes.

Excellent, this will be great for live events (as well as quicker studio
action).

>  
> 
>>Is their a way that we could setup the Poly Record feature to not only
>>work in real time (which I love!), but also have a step input feature
>>like for example the JX3P does.
> 
> 
> That one has been suggested already, so it's on the wish list.
> Time is a factor...

Good, I expected as such, but thought I'd mention it to make sure.

> 
> 
>>Chord Memory
>>Is thier any way that we could have 8 or 16 slot chord memory, that
>>would memorize certain chords? Maybe some make an aux event for it, so
>>you can select which chord you want with the aux event and 
>>have the root
>>note for that chord be selected by the note knob?
> 
> 
> One advantage of the new multiple note handling is that it would be easy to
> have a single event set multiple aux notes in one go.

I guess I'd have to see how you implement the single event --> multiple
aux notes to see what you mean.

> But I'm not sure if it would be better to have preset chords to call up,
> rather than just banging them into a specific pattern.
> Presets = you end up using the same chords all the time.

I do understand, but as long as they were user changeable, i'd just
change them, but I was thinking originally more like the 64 that are
available on the Notron, but wasn't sure if the extra memory was
available (or justified for this use).  It would be nice for live shows,
for doing some improvisational stuff, but again, I'd guess I'll see how
you implement the single event --> multiple aux notes thing.   I can
always have a piece of paper with my aux note settings :)  Good old
analog presets...


Dave