Analogue-sequencer

Folks,

The P3 v3.1.005 release build and an updated user manual are now in 
the Yahoo files section.

Note that if you upgrade to v3.1.005, any patterns with GRAB or SWAP 
aux events assigned will need to have these events re-assigned for 
the new implementation of these events.
Other than that, there are no compatibility issues with existing 
pattern data.
You can automatically convert grab and swap events with the upcoming 
release of P3Tools, which I hope Dave will share with us shortly ;-)

New features in this release include:
 * 'grab', 'swap' and 'push' events
 * 'set tempo' event
 * sticky keys in play mode
 * remote control (currently only for part selection)
 * a 'tie' softkey in arpeggio capture for step-time entry of notes 
longer than one step (you need to have rong off to use this)

There are a few other tweaks and undocumented feature revisions 
(i.e. bugfixes).

Cheers,
Colin f

I have followed the FUNC+PAGE then power-on,
then F3 to begin update.

Then I try the new .syx update, but the P3 
always displays BAD DATA!

What's wrong?

Cheers
Analog1k



--- In analogue-sequencer@yahoogroups.com, "colinfraser_com" 
<colin@c...> wrote:
> Folks,
> 
> The P3 v3.1.005 release build and an updated user manual are now in 
> the Yahoo files section.
> 
> Note that if you upgrade to v3.1.005, any patterns with GRAB or 
SWAP 
> aux events assigned will need to have these events re-assigned for 
> the new implementation of these events.
> Other than that, there are no compatibility issues with existing 
> pattern data.
> You can automatically convert grab and swap events with the 
upcoming 

> release of P3Tools, which I hope Dave will share with us shortly ;-)
> 
> New features in this release include:
>  * 'grab', 'swap' and 'push' events
>  * 'set tempo' event
>  * sticky keys in play mode
>  * remote control (currently only for part selection)
>  * a 'tie' softkey in arpeggio capture for step-time entry of notes 
> longer than one step (you need to have rong off to use this)
> 
> There are a few other tweaks and undocumented feature revisions 
> (i.e. bugfixes).
> 
> Cheers,
> Colin f

--- In analogue-sequencer@yahoogroups.com, Robert van der Kamp 
<robnet@w...> wrote:
> On Wednesday 06 July 2005 16:01, analog1k wrote:
> > I have followed the FUNC+PAGE then power-on,
> > then F3 to begin update.
> >
> > Then I try the new .syx update, but the P3
> > always displays BAD DATA!
> 
> For what it's worth. I just successfully updated Boele's P3 
> with the latest .sys file. Worked like a charm. 
> 
> - Robert


Why are you posting in this thread ?

On Wednesday 06 July 2005 16:01, analog1k wrote:
> I have followed the FUNC+PAGE then power-on,
> then F3 to begin update.
>
> Then I try the new .syx update, but the P3
> always displays BAD DATA!

For what it's worth. I just successfully updated Boele's P3 
with the latest .sys file. Worked like a charm. 

- Robert

On Wednesday 06 July 2005 16:18, analog1k wrote:
> --- In analogue-sequencer@yahoogroups.com, Robert van der
> Kamp
>
> <robnet@w...> wrote:
> > On Wednesday 06 July 2005 16:01, analog1k wrote:
> > > I have followed the FUNC+PAGE then power-on,
> > > then F3 to begin update.
> > >
> > > Then I try the new .syx update, but the P3
> > > always displays BAD DATA!
> >
> > For what it's worth. I just successfully updated
> > Boele's P3 with the latest .sys file. Worked like a
> > charm.
> >
> > - Robert
>
> Why are you posting in this thread ?

To help you and Colin rule out the possibility that the .syx 
file that was posted on the web may have been bad.

Am I in the way?

On Wed, 6 Jul 2005, analog1k wrote:

> I have followed the FUNC+PAGE then power-on,
> then F3 to begin update.
>
> Then I try the new .syx update, but the P3
> always displays BAD DATA!

the same thing happened to me recently... try slowing down the MIDI-OX (or
whatever you're using) transmission time by increasing the time between
buffers. then pay attention to the P3's screen as it is loading... it
should give hex addresses and the message "OK" or something like that...
take note of whether you start to get the bad data message at the same hex
address. this was happening to me consistently, and colin had to send me a
new CPU to fix it. somehow my original one got corrupted or something.

bleep.
out.

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

> Then I try the new .syx update, but the P3 
> always displays BAD DATA!

It's possible yor P3 might need the sysex ID patch - what's the current
version of the firmware ?

Cheers,
Colin f

Cheers Colin,

I uploaded the sysex ID patch, then put in the new
firmware upgrade using midiox, I guess that's all
it was needing.  :-)

Analog1k


--- In analogue-sequencer@yahoogroups.com, "Colin f" <colin@c...> wrote:
>  
> > Then I try the new .syx update, but the P3 
> > always displays BAD DATA!
> 
> It's possible yor P3 might need the sysex ID patch - what's the 
current

> version of the firmware ?
> 
> Cheers,
> Colin f