Analogue-sequencer

Folks,

I've uploaded the latest beta to Yahoo files.
This one is v3.1.006b38.

I am listening to your aux event suggestions, but they will have to 
wait until after the final 3.1.006 version, as I really need to get 
a release build out so I can get the manual done.

This build has one significant change - "aux note abs" event values 
are *not compatible* with your existing patterns.
For reasons that made sense at the time, the old aux note abs event 
was limited to a range of 64 notes, from MIDI note 24 to 87.
The event now takes the full range of notes, but this means existing 
data is now wrong.
Dave has a build of P3 Tools that will fix this, hopefully to be 
posted soon.
I could add a pattern macro to update individual patterns, if it 
proves a major problem.

Other than that change, this build has updated Sculpt and Randomize 
functions that act only at the start of each step. i.e. you need to 
be holding the softkey as P3 moves into the step to be sculpted or 
randomized. The modified step value will take effect immediately.

Also there is the pattern macro function I described earlier.
In pattern edit, press FUNC+UPPER MODE, then select a macro with the 
DATA knob and press F1 to apply.
This makes setting up poly patterns much slicker.
I can add other things here too.

Last change in this build is the addition of a live/ready recrd 
option to pattern edit record mode. It defaults to live, so will 
behave as now if you don't press the key. But if you want 
to 'rehearse' what you're about to record in pattern edit, you can 
do that now.

Best regards,
Colin Fraser
Sequentix Music Systems Ltd
http://www.sequentix.com

Hey Colin,

sounds cool will try this beta directly here....thet change to aux  
note abs is no huge problem to me as I quickly erase much patters as  
soon as played them into logic...

cheers,
henry


Am 17.01.2006 um 21:41 schrieb colinfraser_com:

> Folks,
>
> I've uploaded the latest beta to Yahoo files.
> This one is v3.1.006b38.
>
> I am listening to your aux event suggestions, but they will have to
> wait until after the final 3.1.006 version, as I really need to get
> a release build out so I can get the manual done.
>
> This build has one significant change - "aux note abs" event values
> are *not compatible* with your existing patterns.
> For reasons that made sense at the time, the old aux note abs event
> was limited to a range of 64 notes, from MIDI note 24 to 87.
> The event now takes the full range of notes, but this means existing
> data is now wrong.
> Dave has a build of P3 Tools that will fix this, hopefully to be
> posted soon.
> I could add a pattern macro to update individual patterns, if it
> proves a major problem.
>
> Other than that change, this build has updated Sculpt and Randomize
> functions that act only at the start of each step. i.e. you need to
> be holding the softkey as P3 moves into the step to be sculpted or
> randomized. The modified step value will take effect immediately.
>
> Also there is the pattern macro function I described earlier.
> In pattern edit, press FUNC+UPPER MODE, then select a macro with the
> DATA knob and press F1 to apply.
> This makes setting up poly patterns much slicker.
> I can add other things here too.
>
> Last change in this build is the addition of a live/ready recrd
> option to pattern edit record mode. It defaults to live, so will
> behave as now if you don't press the key. But if you want
> to 'rehearse' what you're about to record in pattern edit, you can
> do that now.
>
> Best regards,
> Colin Fraser
> Sequentix Music Systems Ltd
> http://www.sequentix.com
>
>
>
>
>
>
>
> SPONSORED LINKS
> Sampler	Electronic instrument	Synthesizer
> Synthesizer music	Electronic music	Midi sequencer
>
> YAHOO! GROUPS LINKS
>
>  Visit your group "analogue-sequencer" on the web.
>
>  To unsubscribe from this group, send an email to:
>  analogue-sequencer-unsubscribe@yahoogroups.com
>
>  Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
>
>

------------------------------------------------------------------------ 
-----------
Who is general failure? And what is he doing on my harddisc?




[Non-text portions of this message have been removed]

colinfraser_com wrote:

>Last change in this build is the addition of a live/ready recrd 
>option to pattern edit record mode. It defaults to live, so will 
>behave as now if you don't press the key. But if you want 
>to 'rehearse' what you're about to record in pattern edit, you can 
>do that now.
>  
>
Awesome - thanks dude. Will make my drum pattern programming so much easier!

Paul

---
Paul Nagle / Soft Room Music / Bogus Focus Records / Binar / Headshock / The Joint Intelligence Committee
        www.softroom.co.uk / www.BogusFocus.com / www.JointIntelligenceCommittee.com

On Tue, 17 Jan 2006, colinfraser_com wrote:

> Other than that change, this build has updated Sculpt and Randomize
> functions that act only at the start of each step. i.e. you need to
> be holding the softkey as P3 moves into the step to be sculpted or
> randomized. The modified step value will take effect immediately.

Excellent... thanks, Colin!

bleep.
out.

---
http://leichenfeld.iuma.com
http://thirdwavecollective.com

Paul Nagle wrote:
> colinfraser_com wrote:
> 
> 
>>Last change in this build is the addition of a live/ready recrd 
>>option to pattern edit record mode. It defaults to live, so will 
>>behave as now if you don't press the key. But if you want 
>>to 'rehearse' what you're about to record in pattern edit, you can 
>>do that now.
>> 
>>
> 
> Awesome - thanks dude. Will make my drum pattern programming so much easier!
> 
Yep, this combined with the 8 Aux note on a track option definitely has
definitely opened up the P3 in regards to Drum as well as Keyboard
programming.



Thx..!!!


Dave

> But drum programming on the P3 seems a bit ungainly unless
> there is way to isolate only the 8 midi notes I need - but 
> then how to have
> a snare and bass drum on the same beat - auxes? - could there 
> be a slick way
> to use
> the P3 for drums that I'm missing?

It is still quite ungainly for step time entry of drum patterns.
With a pattern set for 5 note poly, it's quite simple to play in a
percussion pattern using realtime record, and get up to 5 notes on the same
beat, but then it's not so easy to follow what you've entered in step time.

One of the big limitations with aux notes for step time drum programming is
the fact that the main gate setting applies to all aux notes.
I have a notion that I might add 'aux note ind' events that would be similar
to 'aux note abs', except that the aux notes would be gated by their own
status bits, and therefore be independent of the main gate.
By adding a pattern macro that would set the note on every step for the main
note and all four auxes to some predefined values, you could then use the
gate and 4 aux flags as a sort of grid drum editor.

Best regards,
Colin Fraser
Sequentix Music Systems Ltd
http://www.sequentix.com

So you do drum programming on the P3 Paul? Just using one track or using
several? In my pieces I only use 6 melody parts (Akai vx600 having only six
voices...) and one for extra modulation so I have one free to play with...

BTW I followed your advice and picked up a korg electribe ER1 which I
mistakenly
had filed under the "stupid DJ toy" catagory. How wrong I was - its a little
beastie!! I like its rather plastic "Berlin" sound a lot  - I so much prefer
it to the Machinedrum

However, being a gear junky with an eye for a bargain that didn't stop me
picking up a used Vermona DRM1 this week - the best drumsynth I've ever
heard and fantastic controlled from the Electribe.

But drum programming on the P3 seems a bit ungainly unless
there is way to isolate only the 8 midi notes I need - but then how to have
a snare and bass drum on the same beat - auxes? - could there be a slick way
to use
the P3 for drums that I'm missing?

Richard

----- Original Message -----
From: "Paul Nagle" <softroom@btinternet.com>
To: <analogue-sequencer@yahoogroups.com>
Sent: Tuesday, January 17, 2006 1:37 PM
Subject: Re: [analogue-sequencer] New beta...


> colinfraser_com wrote:
>
> >Last change in this build is the addition of a live/ready recrd
> >option to pattern edit record mode. It defaults to live, so will
> >behave as now if you don't press the key. But if you want
> >to 'rehearse' what you're about to record in pattern edit, you can
> >do that now.
> >
> >
> Awesome - thanks dude. Will make my drum pattern programming so much
easier!
>
> Paul
>
> ---
> Paul Nagle / Soft Room Music / Bogus Focus Records / Binar / Headshock /
The Joint Intelligence Committee
>         www.softroom.co.uk / www.BogusFocus.com /
www.JointIntelligenceCommittee.com

>
>
>
>
> Yahoo! Groups Links
>
>
>
>
>
>
>

Colin f wrote:

> I have a notion that I might add 'aux note ind' events that would be similar
> to 'aux note abs', except that the aux notes would be gated by their own
> status bits, and therefore be independent of the main gate.
> By adding a pattern macro that would set the note on every step for the main
> note and all four auxes to some predefined values, you could then use the
> gate and 4 aux flags as a sort of grid drum editor.


I definitely like this idea.  Would be a great asset to the machine.


Dave

On Tue, 17 Jan 2006 15:14:50 -0800, "Richard"
<richardscott@btconnect.com> wrote:

>So you do drum programming on the P3 Paul? Just using one track or using
>several? In my pieces I only use 6 melody parts (Akai vx600 having only six
>voices...) and one for extra modulation so I have one free to play with...

Well, I have two P3s <g>
But I tend to use two tracks of P3(2) for percussion, usually playing
two different kits on my Proteus 2000. As I have three electribes
running as well (!), I tend to add a few simple drums only and use
playlists to run patterns with slight variations in sequence. I
program the knobs so that turning them makes the pattern more complex,
'reveals' additional percussion fills or adds note repeats - the
repeat with pitch transposition is a brilliant feature for drums.

>BTW I followed your advice and picked up a korg electribe ER1 which I
>mistakenly
>had filed under the "stupid DJ toy" catagory. How wrong I was - its a little
>beastie!! I like its rather plastic "Berlin" sound a lot  - I so much prefer
>it to the Machinedrum

Hehe, I like mine too - it spends much of its time going through a
Xone VF-1 filter that adds analogue distortion as well as filter
sweeps. A perfect source of electronic kicks, plinky noises and simple
high hat patterns.

>However, being a gear junky with an eye for a bargain that didn't stop me
>picking up a used Vermona DRM1 this week - the best drumsynth I've ever
>heard and fantastic controlled from the Electribe.

Yeah, I'd love one. I have a Perfourmer and that is a superb thing to
sequence with the P3 despite its primitive MIDI spec. 

>But drum programming on the P3 seems a bit ungainly unless
>there is way to isolate only the 8 midi notes I need - but then how to have
>a snare and bass drum on the same beat - auxes? - could there be a slick way
>to use
>the P3 for drums that I'm missing?

I just play them in polyphonically as best I can - not too bothered
about editing, just delete and start again if necessary. But needless
to say I've offered Colin a few suggestions... 

You know, some evenings, when it's quiet and the wind is in the right
direction, I swear I can hear the sound of distant thudding from the
north. I think it might be the sound of a scotsman beating himself
over the head and weeping, presumably with the sheer joy of receiving
another great idea from me... :)

Paul
---
Paul Nagle - Joint Intelligence Committee - www.JointIntelligenceCommittee.com
                           SoftRoom Music - www.softroom.co.uk

--- In analogue-sequencer@yahoogroups.com, Paul Nagle <softroom@b...> 
wrote:
>
> Well, I have two P3s <g>
> But I tend to use two tracks of P3(2) for percussion, usually playing
> two different kits on my Proteus 2000. As I have three electribes
> running as well (!), I tend to add a few simple drums only and use
> playlists to run patterns with slight variations in sequence. I
> program the knobs so that turning them makes the pattern more complex,
> 'reveals' additional percussion fills or adds note repeats - the
> repeat with pitch transposition is a brilliant feature for drums.
> 


Maybe Colin can be persuaded to build a drum sequencer unit, something 
that looks slightly reminiscent of the old EKO ComputeRhythm that had 6 
rows of 16 flashing lite-up buttons, but have 8 rows instead of 6, 
although the idea was done by Simmons for the SDS6, often wonder why no-
one has ever went back to making a matrix-sequencer ?

Ah well you can't have everything can you :(

A1k

I was just remembering that ages ago there was talk of a drum machine version of the P3 
code. Has this ever come to fruition? Is it still planned? 

I also found the message below from Colin back in Jan 06. Are these 'aux note ind' events 
included in the new code? It's been a while since i've updated.

Tommy





--- In analogue-sequencer@yahoogroups.com, David Bate <dave@...> wrote:

>
> Colin f wrote:
> 
> > I have a notion that I might add 'aux note ind' events that would be similar
> > to 'aux note abs', except that the aux notes would be gated by their own
> > status bits, and therefore be independent of the main gate.
> > By adding a pattern macro that would set the note on every step for the main
> > note and all four auxes to some predefined values, you could then use the
> > gate and 4 aux flags as a sort of grid drum editor.
> 
> 
> I definitely like this idea.  Would be a great asset to the machine.
> 
> 
> Dave
>

> I was just remembering that ages ago there was talk of a drum 
> machine version of the P3 
> code. Has this ever come to fruition? Is it still planned? 
> 
> I also found the message below from Colin back in Jan 06. Are 
> these 'aux note ind' events 
> included in the new code? It's been a while since i've updated.

'Aux note ind' events are still on my TBI list. Architectural changes to the
P3 code since I last thought about it would make them a lot easier to do, so
thanks for reminding me...
And I would really like a good percussion sequencer for my own use.
But one thing that I thought was essential for a pairing of P3 and a drum
sequencer would be to have some meaningful way of managing pattern storage
across both units.
At the moment I use my P3 with a 909, and it's a real pain trying to
remember which drum patterns I've used with which bank on the P3 - I usually
end up just using the same patterns too often.
A percussion sequencer specifically designed to work with a P3 needs a
'matching' memory layout, ideally with remote sync of banks and so on, so
that the two units would work as a whole.
One of my intentions for the P3 replacement was to include percussion
patterns natively, so a single box could do both jobs.
But the P4 design process has got a bit bogged down. I have a target
platform that could be awesomely powerful, but the development timescale is
looking very long, and I started to worry that it will take me too long to
ever actually get it finished - there's no money coming in while I'm not
selling anything...
So I've been working on something else - a re-worked version of P3.
I've taken the final P3 OS as a starting point, and re-written large parts
of it to eliminate things that I think are conceptually awkward, or
limiting.
It has no playlists, a fixed 16 bank memory structure, patterns up to 16
bars in length (editable with Electribe-style access to all bars) and
dynamic allocation of pattern storage.
This OS will most likely be released as an update for P3, but may also
appear on a new product.
The revised memory model in the new OS would also lend itself very well to a
compatible percussion sequencer, so I will be looking into it...

Best regards,
Colin Fraser
Sequentix Music Systems Ltd
http://www.sequentix.com

Colin wrote

So I've been working on something else - a re-worked version of P3. I've
taken the final P3 OS as a starting point, and re-written large parts of it
to eliminate things that I think are conceptually awkward, or limiting.
It has no playlists, a fixed 16 bank memory structure, patterns up to 16
bars in length (editable with Electribe-style access to all bars) and
dynamic allocation of pattern storage. This OS will most likely be released
as an update for P3, but may also appear on a new product. The revised
memory model in the new OS would also lend itself very well to a compatible
percussion sequencer, so I will be looking into it...


Colin,
Is there any chance that the new OS will have a memory buffer for a whole
bank rather than for an individual track?
Cheers
Jez


[Non-text portions of this message have been removed]

On 1 Apr 2007, at 13:15, Colin Fraser wrote:

> This OS will most likely be released as an update for P3, but may also
> appear on a new product.

 From your description, this sounds like a fork of the existing P3  
OS. What would be the story regarding updates/fixes to the current OS?

(I actually like playlists...)

	-- N.

colin,

would it be possible to include a feature then where you play in some  
notes into a memory buffer (i.e played.from an ext. keyboard)
and then insert notes from this buffer into sequentially every step  
activated? its a bit like the old roland MC sequencers have worked.
you play in a small melody, you create rhythm and lenght afterwords...

best,
henry


Am 01.04.2007 um 14:15 schrieb Colin Fraser:

>
> > I was just remembering that ages ago there was talk of a drum
> > machine version of the P3
> > code. Has this ever come to fruition? Is it still planned?
> >
> > I also found the message below from Colin back in Jan 06. Are
> > these 'aux note ind' events
> > included in the new code? It's been a while since i've updated.
>
> 'Aux note ind' events are still on my TBI list. Architectural  
> changes to the
> P3 code since I last thought about it would make them a lot easier  
> to do, so
> thanks for reminding me...
> And I would really like a good percussion sequencer for my own use.
> But one thing that I thought was essential for a pairing of P3 and  
> a drum
> sequencer would be to have some meaningful way of managing pattern  
> storage
> across both units.
> At the moment I use my P3 with a 909, and it's a real pain trying to
> remember which drum patterns I've used with which bank on the P3 -  
> I usually
> end up just using the same patterns too often.
> A percussion sequencer specifically designed to work with a P3 needs a
> 'matching' memory layout, ideally with remote sync of banks and so  
> on, so
> that the two units would work as a whole.
> One of my intentions for the P3 replacement was to include percussion
> patterns natively, so a single box could do both jobs.
> But the P4 design process has got a bit bogged down. I have a target
> platform that could be awesomely powerful, but the development  
> timescale is
> looking very long, and I started to worry that it will take me too  
> long to
> ever actually get it finished - there's no money coming in while  
> I'm not
> selling anything...
> So I've been working on something else - a re-worked version of P3.
> I've taken the final P3 OS as a starting point, and re-written  
> large parts
> of it to eliminate things that I think are conceptually awkward, or
> limiting.
> It has no playlists, a fixed 16 bank memory structure, patterns up  
> to 16
> bars in length (editable with Electribe-style access to all bars) and
> dynamic allocation of pattern storage.
> This OS will most likely be released as an update for P3, but may also
> appear on a new product.
> The revised memory model in the new OS would also lend itself very  
> well to a
> compatible percussion sequencer, so I will be looking into it...
>
> Best regards,
> Colin Fraser
> Sequentix Music Systems Ltd
> http://www.sequentix.com
>
>
> 

cheers,
henry





[Non-text portions of this message have been removed]

> Is there any chance that the new OS will have a memory buffer 
> for a whole
> bank rather than for an individual track?

It might do, but it depends on how much code it would take to manage it.
When you go into edit mode, however many bars are used by the pattern being
edited are allocated to the edit buffer, and the original pattern copied
into it. Edits are then performed on the data held in the edit buffer.
When you exit edit mode, the edit buffer bars are copied back into the
source pattern, or assigned to a different target pattern, or lost.
In theory, there could be an undo buffer that tracked all changes to a bank
since it was selected.
But that would use a lot of storage.
A simpler solution would be a bank copy option, that would let you copy a
'starting point' bank to another bank.
Then you could make whatever edits you like, but still have the starting
point to recall later.
With 16 banks on hand, you'd have space for at least 4 bank copies before
you had fewer banks to play with than on P3.
It just depends on how many bars are allocated whether you'd have the space
to do it.

>  From your description, this sounds like a fork of the existing P3  
> OS. What would be the story regarding updates/fixes to the current OS?
> 
> (I actually like playlists...)

It is a fork of the current OS.
Whether I continue to update the original OS much beyond it's current
position will depend on how popular the revised version is.
No-one else has used it yet, though it will be ready for limited beta
testing soon.
To a large extent, playlist functionality is replicated in the new OS.
Each bar in a pattern will have tranpose, repeat and sync options, just like
the steps in a playlist.
You wont be able to re-use the same 'bar' at multiple points in one pattern,
but to replicate a playlist where you have the same pattern on multiple
steps, you would just need to copy the bar you want to repeat to other
positions in the pattern.
Storage space permitting, it will be possible to replicate any given P3 bank
under the new OS.

Best regards,
Colin Fraser
Sequentix Music Systems Ltd
http://www.sequentix.com

oh man im getting all excited ;-D

On 4/1/07, Colin Fraser <colin@sequentix.com> wrote:
>
>
> > Is there any chance that the new OS will have a memory buffer
> > for a whole
> > bank rather than for an individual track?
>
> It might do, but it depends on how much code it would take to manage it.
> When you go into edit mode, however many bars are used by the pattern
> being
> edited are allocated to the edit buffer, and the original pattern copied
> into it. Edits are then performed on the data held in the edit buffer.
> When you exit edit mode, the edit buffer bars are copied back into the
> source pattern, or assigned to a different target pattern, or lost.
> In theory, there could be an undo buffer that tracked all changes to a
> bank
> since it was selected.
> But that would use a lot of storage.
> A simpler solution would be a bank copy option, that would let you copy a
> 'starting point' bank to another bank.
> Then you could make whatever edits you like, but still have the starting
> point to recall later.
> With 16 banks on hand, you'd have space for at least 4 bank copies before
> you had fewer banks to play with than on P3.
> It just depends on how many bars are allocated whether you'd have the
> space
> to do it.
>
> > From your description, this sounds like a fork of the existing P3
> > OS. What would be the story regarding updates/fixes to the current OS?
> >
> > (I actually like playlists...)
>
> It is a fork of the current OS.
> Whether I continue to update the original OS much beyond it's current
> position will depend on how popular the revised version is.
> No-one else has used it yet, though it will be ready for limited beta
> testing soon.
> To a large extent, playlist functionality is replicated in the new OS.
> Each bar in a pattern will have tranpose, repeat and sync options, just
> like
> the steps in a playlist.
> You wont be able to re-use the same 'bar' at multiple points in one
> pattern,
> but to replicate a playlist where you have the same pattern on multiple
> steps, you would just need to copy the bar you want to repeat to other
> positions in the pattern.
> Storage space permitting, it will be possible to replicate any given P3
> bank
> under the new OS.
>
> Best regards,
> Colin Fraser
> Sequentix Music Systems Ltd
> http://www.sequentix.com
>
>  
>


[Non-text portions of this message have been removed]

On 1 Apr 2007, at 18:09, Colin Fraser wrote:

> You wont be able to re-use the same 'bar' at multiple points in one  
> pattern,
> but to replicate a playlist where you have the same pattern on  
> multiple
> steps, you would just need to copy the bar you want to repeat to other
> positions in the pattern.

Ah - OK. It sounds like the main difference is bar inclusion rather  
than pattern reference.

Would be interesting to have a play with it and see how it contrasts  
with the current "workflow".

	-- N.