Analogue-sequencer

Hi Colin,

I've just updated the firmware on my P3 to V 3.1004 from the much 
earlier version it shipped with - does the Bootloader V3.1-T89  in the 
Yahoo files section now also include the patch for Sequentix Sysex ID? 

Its just that I followed the proceedure in the readme's for each 
patch, but when I tried to load the Sequentix Sysex ID patch it just 
kept coming up "bad data". The bootloader and V3.1004 firmware loaded 
fine and  P3 works great and shows COLIN FRASER 18, #0000 V3.1004 on 
booting, and when I enter firmware update mode it shows Checksum=0936

BTW, Is it necessary to do a memory initialisation each time after 
updating firmware?  After the firmware update I had the lower four 
mode led's cascading when I pressed play, I did a memory 
initialisation and now it works as it did earlier.

thanks,
Allan

> The update includes the Sequentix ID patch, yes.

Many thanks Colin, that explains it......

> Not sure what you mean by cascading, but in the play mode the mode 
LEDs
> toggle though a number of different options
This was from first switching on and pressing play without touching 
mode buttons, bottom four leds flashed VU meter style - they don't 
now, not until I hit one of the mode buttons, which I assume is 
correct behaviour.

> I think it looks cool, YMMV ;-)
Absolutely, and I also keep looking for excuses to start the P3 for 
for the opening lightshow, but I know its just to test all of the 
LED's are working ok, right? ;-)

Allan 


--- In analogue-sequencer@yahoogroups.com, "Colin f" <colin@c...> 
wrote:
>  
> > I've just updated the firmware on my P3 to V 3.1004 from the 
much 
> > earlier version it shipped with - does the Bootloader 
> > V3.1-T89  in the 
> > Yahoo files section now also include the patch for Sequentix 
> > Sysex ID? 
> 
> The update includes the Sequentix ID patch, yes.
>  
> > Its just that I followed the proceedure in the readme's for each 
> > patch, but when I tried to load the Sequentix Sysex ID patch it 
just 
> > kept coming up "bad data".
> 
> That's because the patch image has the old ID, which the updated 
bootloader
> doesn't like.
> 
> > BTW, Is it necessary to do a memory initialisation each time 
after 
> > updating firmware?  After the firmware update I had the lower 
four 
> > mode led's cascading when I pressed play, I did a memory 
> > initialisation and now it works as it did earlier.
> 
> Generally speaking, it wont require an initialisation.
> I recommend doing a backup and restore as a good habit to get into 
in case I
> do change the memory layout, but I haven't done so for a long time.
> Not sure what you mean by cascading, but in the play mode the mode 
LEDs
> toggle though a number of different options - VU meter, global 
beat and
> binary global bar position. Sounds like you might have been 
watching binary

> gbar pos.
> I think it looks cool, YMMV ;-)
> 
> Cheers,
> Colin f

> I've just updated the firmware on my P3 to V 3.1004 from the much 
> earlier version it shipped with - does the Bootloader 
> V3.1-T89  in the 
> Yahoo files section now also include the patch for Sequentix 
> Sysex ID? 

The update includes the Sequentix ID patch, yes.
 
> Its just that I followed the proceedure in the readme's for each 
> patch, but when I tried to load the Sequentix Sysex ID patch it just 
> kept coming up "bad data".

That's because the patch image has the old ID, which the updated bootloader
doesn't like.

> BTW, Is it necessary to do a memory initialisation each time after 
> updating firmware?  After the firmware update I had the lower four 
> mode led's cascading when I pressed play, I did a memory 
> initialisation and now it works as it did earlier.

Generally speaking, it wont require an initialisation.
I recommend doing a backup and restore as a good habit to get into in case I
do change the memory layout, but I haven't done so for a long time.
Not sure what you mean by cascading, but in the play mode the mode LEDs
toggle though a number of different options - VU meter, global beat and
binary global bar position. Sounds like you might have been watching binary
gbar pos.
I think it looks cool, YMMV ;-)

Cheers,
Colin f

> Absolutely, and I also keep looking for excuses to start the P3 for 
> for the opening lightshow, but I know its just to test all of the 
> LED's are working ok, right? ;-)

Um, yeah - that's it !
If you ever get fed up with it, you can hold STOP at power-on to skip the
LED test.

Cheers,
Colin f

Folks,

I'm working on adding midi remote control to P3.
Obvious TBIs are bank select or program change messages to change P3 bank,
CCs for mute/unmute tracks, maybe also CCs for edit track 1 - 8, pattern
select, note input for PXPos, that sort of thing.
Seems like a good idea to discuss it before I implement stuff no-one wants
;-)
I've already added a framework to the current test build that diverts
incoming messages on a chosen remote control channel for this sort of thing,
so I just need to decide what should be possible, and what parts of the UI
should generate messages for a slave P3 if required.

Cheers,
Colin f

>> I'm working on adding midi remote control to P3. Obvious TBIs are
bank select or program change messages to change P3 bank, CCs for
mute/unmute tracks, maybe also CCs for edit track 1 - 8, pattern
select, note input for PXPos, that sort of thing. Seems like a good
idea to discuss it before I implement stuff no-one wants...<<

ah. ah-hah. so.... stuff that takes more than one button push would go
on my list... like dropping in & out of record, & selecting the track
to record into... is that what you meant by "cc's for edit"?

what about.... mapping some program changes onto a bunch of
user-defined macros? given that nothing's more than a few button
pushes away anyway, you wouldn't have to store very much. 

you'd put the p3 into "learn" on power-up, by holding down the tempo
knob & blowing in a southerly direction. paul does this anyway. then
push a step key to select a macro to edit. the display would say
something like: "whatever buttons you push now, I'm going to push the
same buttons in the same order when I receive the PC corresponding to
step whatever, on the global channel". with scope in there somehow for
a PC followed by a CC so you could do things like change the length or
timebase of a pattern.....
yikes.
could it stand that much switching on & off?

(I deleted a load of thinking-out-loud, you'll be glad to know...)

d/r.m.i.

--- In analogue-sequencer@yahoogroups.com, "ferrograph632" 
<ferrograph@a...> wrote:
> >> I'm working on adding midi remote control to P3. Obvious TBIs are
> bank select or program change messages to change P3 bank, CCs for
> mute/unmute tracks, maybe also CCs for edit track 1 - 8, pattern
> select, note input for PXPos, that sort of thing. Seems like a good
> idea to discuss it before I implement stuff no-one wants...<<
> 
> ah. ah-hah. so.... stuff that takes more than one button push would 
go
> on my list... like dropping in & out of record, & selecting the 
track
> to record into... is that what you meant by "cc's for edit"?
> 
> what about.... mapping some program changes onto a bunch of
> user-defined macros? given that nothing's more than a few button
> pushes away anyway, you wouldn't have to store very much. 
> 
> you'd put the p3 into "learn" on power-up, by holding down the tempo
> knob & blowing in a southerly direction. paul does this anyway. then
> push a step key to select a macro to edit. the display would say
> something like: "whatever buttons you push now, I'm going to push 
the
> same buttons in the same order when I receive the PC corresponding 
to
> step whatever, on the global channel". with scope in there somehow 
for
> a PC followed by a CC so you could do things like change the length 
or
> timebase of a pattern.....
> yikes.
> could it stand that much switching on & off?
> 
> (I deleted a load of thinking-out-loud, you'll be glad to know...)
> 
> d/r.m.i.

I'm going to think out loud Colin ....

Duncan's learn idea is really neat (I assume its you Duncan). But am 
I right in assuming that ram space is as critical as ever?

The Bank Select and Pattern select stuff I assume speaks for itself, 
but have you thought about this ...

What if you implement something similar to the Packed NRPN feature on 
Novation Supernovas, Novas etc. The Novation kit have an NRPN or CC 
for every knob tweak, every button press, and every single user menu 
option that is possible, which makes them 100% remote controllable. 
They happen to have a massive number of tweakable options, but have 
managed to squeeze it all in to the limited number of CC's and NRPN's 
by using the Packed NRPN feature. I suggest you download the novation 
manual pdf's if you need to check it out. 

You could adapt the Packed NRPN concept and have a couple of Packed 
CC's to allow setting of things like the P3 User Config options, Midi 
channel setups and all that stuff.

This should move the bias from ram to rom because this would all be 
coded as rom based lookup tables and jump tables I suppose.

Like I said ... Thinking aloud (and probably whackily)

One question though Colin. Do you intend to transmit the same CC's 
that you receive?


Dave

I resisted so well...

I'd like the ability for the master P3 to send scale selection to the
slave on each part selection. That way two people with two P3s could
gig confident that they could both work freely and never be out of
key. 

I reckon that part selection, track selection, track arming for record
and track record would be ace. And Part transpose AND part root note
selection. 

On top of that an aux event for "redirect to remote P3" that worked
similar to redirect to track. 

And remote knob control. My wife asked for this. She wants an off
control for me. 

And coffee. That nice French one from Sainsbury's with the chicory. 

And possibly a way to transcend space and time, or to manufacture ice
cream.

It's Friday!

Paul
---
Paul Nagle / Soft Room Music
 www.softroom.co.uk
 www.BogusFocus.com

** Binar's Project Poltergeist and Headshock's MFPE available direct from the Bogus site NOW. **

> ah. ah-hah. so.... stuff that takes more than one button push would go
> on my list... like dropping in & out of record, & selecting the track
> to record into... is that what you meant by "cc's for edit"?

Yes - there could be a CC for 'edit track' that would take a value of the
track to be edited.
Then a midi switch box could have 8 dedicated 'edit track n' and 8 dedicated
'record track n' buttons if you wanted.
Would this be an improvement on sticky keys though ?
If you haven't come across sticky keys, they are modifier keys with a
timeout or toggle action, so pressing REC would display 'Select REC track',
and then you'd press a track key on it's own to activate record. Similar
thing for PLAY/EDIT and possibly FUNC.
This replaces two-key combinations with 2 key sequences - easier if you only
have one hand free.
 
> what about.... mapping some program changes onto a bunch of
> user-defined macros? given that nothing's more than a few button
> pushes away anyway, you wouldn't have to store very much. 

Yikes. My scope creep alarm just went off ;-)

Cheers,
Colin f

> Nice ideas! If popular I'd suggest the Access solution over Novation -
> supplementing CCs with add poly aftertouch events rather than NRPNs.
> They're shorter.
> 
I have no experience of the Access method, but from the way you 
described it, if the Packed NRPN concept was applied straight to a CC 
rather than an NRPN, that would be shorter than the Access method as 
well wouldn't it ?

For example if CC 120 had the P3 user config options "packed" into it, 
that would be half the size of an NRPN and I assume shorter than a CC + 
poly aftertouch.

Or is my understanding of the Access method basically wrong ?

Dave

On Fri, 27 May 2005 21:01:08 +0100, "Colin f" <colin@colinfraser.com>
wrote:

>If you haven't come across sticky keys, 

.... would they *be* sticky in that case?

Paul

---
Paul Nagle / Soft Room Music
 www.softroom.co.uk
 www.BogusFocus.com

** Binar's Project Poltergeist and Headshock's MFPE available direct from the Bogus site NOW. **

On Fri, 27 May 2005 20:47:10 -0000, "em_dkj" <david@davekj.f2s.com>
wrote:

>What if you implement something similar to the Packed NRPN feature on 
>Novation Supernovas, Novas etc. The Novation kit have an NRPN or CC 
>for every knob tweak, every button press, and every single user menu 
>option that is possible, which makes them 100% remote controllable. 
>They happen to have a massive number of tweakable options, but have 
>managed to squeeze it all in to the limited number of CC's and NRPN's 
>by using the Packed NRPN feature. I suggest you download the novation 
>manual pdf's if you need to check it out. 

Nice ideas! If popular I'd suggest the Access solution over Novation -
supplementing CCs with add poly aftertouch events rather than NRPNs.
They're shorter.

Paul
---
Paul Nagle / Soft Room Music
 www.softroom.co.uk
 www.BogusFocus.com

** Binar's Project Poltergeist and Headshock's MFPE available direct from the Bogus site NOW. **

On Fri, 27 May 2005 22:01:32 -0000, "em_dkj" <david@davekj.f2s.com>
wrote:

>For example if CC 120 had the P3 user config options "packed" into it, 
>that would be half the size of an NRPN and I assume shorter than a CC + 
>poly aftertouch.
>
>Or is my understanding of the Access method basically wrong ?

Yeah, I explained it badly...

Access use MIDI CCs for all the common functions. For the others they
use poly aftertouch. There's no mixing of CCs and poly AT for any
function.

It's Friday; I'm odd on Fridays... 8)

Paul
---
Paul Nagle / Soft Room Music
 www.softroom.co.uk
 www.BogusFocus.com

** Binar's Project Poltergeist and Headshock's MFPE available direct from the Bogus site NOW. **

--- In analogue-sequencer@yahoogroups.com, "Colin f" <colin@c...> 
wrote:
> Folks,
> 
> I'm working on adding midi remote control to P3.
> Obvious TBIs are bank select or program change messages to change 
P3 bank,
> CCs for mute/unmute tracks, maybe also CCs for edit track 1 - 8, 
pattern
> select, note input for PXPos, that sort of thing.
> Seems like a good idea to discuss it before I implement stuff no-
one wants
> ;-)
> I've already added a framework to the current test build that 
diverts
> incoming messages on a chosen remote control channel for this sort 
of thing,
> so I just need to decide what should be possible, and what parts of 
the UI
> should generate messages for a slave P3 if required.
> Cheers,
> Colin f

Bonjour,
i am in demand for that;
As i am a guitarist, i use footswitch like FCB1010
with my midi device. i also use synchro and recording
change with my main sequencer on computer.
Others may like to remote functions they can't access directly
with one button push.

So basicaly : play, rec, stop
              select bank, part
              track mute.
              
Some of synths can transmit any editing by their 
midi output. It will allow another 
way to "program" P3.

Further, some parameters, like the limit of an accumulator
or the value of an auxiliary event, and, the tempo.

Salutations, cyrille.

Yes! We want remote control!

I'd like track mutes, part change and an easy way to drop into (and 
out of) record on a selectable track, oh and the transpose stuff too 
please.

I think most of that's been asked for already and it's way too early 
on a sunday morning for me to make any suggestions as to how this 
should be implemented, although "simply" comes to mind. :-)

Did I ask for a MIDI synced herb grinder (with a filter to pick out 
the occasional seed) and spliff roller that will cope with Rizlas 
thinnest papers?

There, that's my unhelpful contribution to the debate.

Phil