Analogue-sequencer

Hi all,

Newbie here. I am using V4. I have been working with this killer
machine for a few months now (bought it used). I have 3 banks full.
Usually about 5 of the 8 tracks used, and all 8 parts. No aux. I use
the new bar function a lot. I do not have the memory upgrade.

I just started filling bank 4 and I get a No Space to EDIT message. I
tried the reinitialize function and reload just that bank and I get a
bad bank message from the P3 Software tool. Please advise. Is it
possible I already filled the memory?

Also - I have noticed that the length function doesn't seem to work.
With my drum machine, the kick seems to phase a bit as the pattern
plays even though the length, delay, and volume are all set the same.
My moog will either play a short note (length = 1) or a long held note
(length=2-13). I can not get the P3 to do anything in between. Any
advice appreciated. Thanks!

John

> Newbie here. I am using V4. I have been working with this killer
> machine for a few months now (bought it used). I have 3 banks full.
> Usually about 5 of the 8 tracks used, and all 8 parts. No aux. I use
> the new bar function a lot. I do not have the memory upgrade.
> 
> I just started filling bank 4 and I get a No Space to EDIT message. I
> tried the reinitialize function and reload just that bank and I get a
> bad bank message from the P3 Software tool. Please advise. Is it
> possible I already filled the memory?

'No space to edit' means all the available bars are assigned.
When you edit a pattern, the pattern is copied into an edit buffer.
The edit buffer has to be allocated the same number of bars as the pattern
to be edited, and those bars come from the bar pool.
Without memx installed, there are two pools of 192 bars - one pool for even
numbered banks, another for odd numbered banks.
If you have started with banks 1, 2 and 3, then you must have used all 192
bars up in banks 2 and 4.
If you have fewer bars used in banks 1 and 3, then you might find you will
have space to create more patterns in bank 5 rather than bank 4.
Hold FUNC and press a track key, and the free bars available will be shown
in the bottom corner of the display.
That number will be the same for all even numbered banks, and for all odd
numbered banks, because of the shared pools.
If you get a memx installed, you get 224 bars for every bank.
 
> Also - I have noticed that the length function doesn't seem to work.
> With my drum machine, the kick seems to phase a bit as the pattern
> plays even though the length, delay, and volume are all set the same.
> My moog will either play a short note (length = 1) or a long held note
> (length=2-13). I can not get the P3 to do anything in between. Any
> advice appreciated. Thanks!

Not sure what's going on there.
Have you tried with a different sound/synth ?

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

> 
> Also - I have noticed that the length function doesn't seem to work.
> With my drum machine, the kick seems to phase a bit as the pattern
> plays even though the length, delay, and volume are all set the same.
> My moog will either play a short note (length = 1) or a long held note
> (length=2-13). I can not get the P3 to do anything in between. Any
> advice appreciated. Thanks!

Do you have a Moog Voyager with operating system v3.4 ?
I've been getting this same problem. I think it's related to Moog
changing the release settings in the latest software revision.
I can confirm that patterns will play fine on my other synths but not
the Moog. 
Pressing stop on the P3 seems to switch off the release parameter on
the Voyager.
Is any one else with a Voyager v3.4 getting the same behaviour ?
I'll email Moog and see what there saying.



Laters,
Mitch

Corrected my dumb mistake of last year and repurchased a p3.

Perhaps I missed it - I didn't see this addressed in the list.

I see in the v4 beta update notes:
"20/09/08
Added user conf option to enable independent aux note test code"

What is that exactly?

Also - how do I tell what firmware I currently have installed?

Thanks, and sorry if this has all been addressed.

Gene

Of course, right after posting that, I found this:

"Yeah, I fixed that one...
I've just uploaded the current build, it has a few fixes in it.
I was hoping to have finished the independent aux notes thing by now,  
but
I've been too busy with other stuff.
Independent aux notes play if their status is enabled, regardless of  
whether
the main gate is enabled for a step.
I added some code to enable independent triggering, I haven't yet got  
normal
and independent aux note triggers working at the same time - there  
needs to
be new events for independent notes, but also some extra code to handle
them.
In the build, you can have all aux notes trigger independently using a  
'user
conf' option.
This may suit the way some people use aux notes, but not others.
Also in the new build is a screensaver user conf option, for those v4  
users
of you with LCD displays who panic when it goes blank.
And there's a 'bar cut' thing in bar edit mode."

Still can't remember how to tell what version I have (whether I have  
this latest one).

Thanks.
> Corrected my dumb mistake of last year and repurchased a p3.
>
> Perhaps I missed it - I didn't see this addressed in the list.
>
> I see in the v4 beta update notes:
> "20/09/08
> Added user conf option to enable independent aux note test code"
>
> What is that exactly?
>
> Also - how do I tell what firmware I currently have installed?
>
> Thanks, and sorry if this has all been addressed.
>
> Gene
>
> 



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

> 
> Also - how do I tell what firmware I currently have installed?
> 

The P3 screen displays the firmware number when you power up.

This just says 4.00b - is there any way of telling which specific  
revision I have?

>
> >
> > Also - how do I tell what firmware I currently have installed?
> >
>
> The P3 screen displays the firmware number when you power up.
>
>
> 



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

Thanks Colin. I think I was not using the bar function efficiently. I
used many tracks for each drum in a kit. I was breaking the bars up
for each of these tracks to match the chord changes in other tracks,
but I think I should have been using the bar repeat function for all
the drums with only one bar. Also I was using the active copy for all
parts because I was making small changes. And I guess I should have
bought one of those expansion boards ;-)

Regarding the length issue, no I have not tried it on another synth. I
will. The one I am having trouble with was a Little Phatty II and the
kick drum issue was triggering a Vermona MKII.

John

--- In analogue-sequencer@yahoogroups.com, "Colin Fraser" <colin@...>
wrote:
>
>  
> > Newbie here. I am using V4. I have been working with this killer
> > machine for a few months now (bought it used). I have 3 banks full.
> > Usually about 5 of the 8 tracks used, and all 8 parts. No aux. I use
> > the new bar function a lot. I do not have the memory upgrade.
> > 
> > I just started filling bank 4 and I get a No Space to EDIT message. I
> > tried the reinitialize function and reload just that bank and I get a
> > bad bank message from the P3 Software tool. Please advise. Is it
> > possible I already filled the memory?
> 
> 'No space to edit' means all the available bars are assigned.
> When you edit a pattern, the pattern is copied into an edit buffer.
> The edit buffer has to be allocated the same number of bars as the
pattern
> to be edited, and those bars come from the bar pool.
> Without memx installed, there are two pools of 192 bars - one pool
for even
> numbered banks, another for odd numbered banks.
> If you have started with banks 1, 2 and 3, then you must have used
all 192
> bars up in banks 2 and 4.
> If you have fewer bars used in banks 1 and 3, then you might find
you will
> have space to create more patterns in bank 5 rather than bank 4.
> Hold FUNC and press a track key, and the free bars available will be
shown
> in the bottom corner of the display.
> That number will be the same for all even numbered banks, and for
all odd

> numbered banks, because of the shared pools.
> If you get a memx installed, you get 224 bars for every bank.
>  
> > Also - I have noticed that the length function doesn't seem to work.
> > With my drum machine, the kick seems to phase a bit as the pattern
> > plays even though the length, delay, and volume are all set the same.
> > My moog will either play a short note (length = 1) or a long held note
> > (length=2-13). I can not get the P3 to do anything in between. Any
> > advice appreciated. Thanks!
> 
> Not sure what's going on there.
> Have you tried with a different sound/synth ?
> 
> Best regards,
> Colin Fraser
> Sequentix Music Systems Ltd
> http://www.sequentix.com
>

My issue is with a Little Phatty Stage II v2.005.

--- In analogue-sequencer@yahoogroups.com, "acidmitch" <acidmitch@...>
wrote:

>
> 
> 
> > 
> > Also - I have noticed that the length function doesn't seem to work.
> > With my drum machine, the kick seems to phase a bit as the pattern
> > plays even though the length, delay, and volume are all set the same.
> > My moog will either play a short note (length = 1) or a long held note
> > (length=2-13). I can not get the P3 to do anything in between. Any
> > advice appreciated. Thanks!
> 
> Do you have a Moog Voyager with operating system v3.4 ?
> I've been getting this same problem. I think it's related to Moog
> changing the release settings in the latest software revision.
> I can confirm that patterns will play fine on my other synths but not
> the Moog. 
> Pressing stop on the P3 seems to switch off the release parameter on
> the Voyager.
> Is any one else with a Voyager v3.4 getting the same behaviour ?
> I'll email Moog and see what there saying.
> 
> 
> 
> Laters,
> Mitch
>