Analogue-sequencer

Hi Stoffel,

> i got some strange midi-sync things going on.
[snip]
> When the P3 is running, and it receives a Stop it stops. When it then
> receives a continue, it's not running in Sync.

I have to admit, since I never use P3 synced to something else, never use a
PC sequencer, and never use continue, I checked the continue support worked
at the time it went in but haven't revisited it since. That was so long ago,
there are any number of changes to the sequencer engine that might have
caused the loss of sync you're getting. I'll take a look at it - hopefully
it'll be something obvious and easy to fix.

> Ok, I hope this describes the Sync-Problem enough, so that you know
> what's going on. Well at least I know now what's going on, for now I
> just have to make sure, that the P3 doesn't receive Continue, just
> Start, then everything is cool.

Cool. I guess I could just define the midi spec as only supporting start and
stop ;-)

> And once again, thanx a lot for the AUX events, I'm using them more
> and more, they are really great. On May 20th I have a little OpenAir
> Session, and now I bought a MiniDisk, so then I will make some
> recordings, so you guys can hear what I'm doing with the P3.

I'll look forward to hearing that.
The auxes to affect global parameters are in teh works, and should be fun.
These include events to let you mute and un-mute other tracks, and select
different parts and part chain lengths - which will allow some nice
structural modulation effects...

Cheers,
Colin f



________________________________________________
Message sent using UebiMiau 2.7.2

I tracked down the cause of the sync loss on continue, which was 
down to some tidying up of the sequencer status in the stop_sequence 
routine that was added to prevent problems if you selected a new 
part chain then stopped the sequencer before it became active.
I've posted a build with this fixed, but since I'm not really set up 
to check this thoroughly myself at the moment, it's definitely a 
beta.

Cheers,
Colin f

Hi Colin,

it is amazing how fast you react. I installed your beta version, but
it made just a little improvement. If the P3 receives a continue, now
it really continues, from where it stopped before, but sometimes it is
shifted by one click. But the Problem of Logic is, that it also sends
a continue, when it stops somewhere, and you rewind back to the first
beat of a bar (e.g. the second bar), the sends some Song position
pointer, and then starts but with the continue signal. And also if the
P3 was running and is stopped by hand and then receives a continue it
is not in sync. If it receives a start everything is cool. So my
suggestion is, just treat the continue as it were a start signal. I
find it more easy, to make sure that the master starts on a beginning
of a bar, as I really can't think of a situation where the P3 really
has to continue from the middle of where it was stopped. I think if
you stop the music, you can easily start with the first beat of any
bar. This makes even more sense as the P3 is Pattern orientated, and
has not so much a song structure, although it is of course possible.
For me it would be ok if the continue is just treated as a start, and
I think this would make things easier for you. What do the other P3
user say?
Sorry for this MidiSync Stuff, i really couldn't convince my friends
to give up their laptops, but I'm working on it. I'm really glad that
I don't have to starr on the screen anymore, moving around little squares.
Best wishes and happy weekend, now I'm going to an industrial noise
festival in Essen, just to widen my musical horizon a little bit
(never been to such things before). I hope I don't get an earache.

Stoffel

Op 1-mei-04 om 15:33 heeft Stoffel het volgende geschreven:

> k if the continue is just treated as a start, and
> I think this would make things easier for you. What do the other P3
> user say?
>
Sounds logic to me and easier for Colin to implement. I have no 
problems with that.

Boele

Hello everybody

I am very very stoned on lovely mushrooms.

bless


the P3 has done more amazing sequency things last night I thought you
should know.

Paul
---
Paul Nagle / Soft Room Music
Email: paul@softroom.co.uk www.softroom.co.uk
                           www.BogusFocus.com

> I am very very stoned on lovely mushrooms.
> 
> bless
> 
> 
> the P3 has done more amazing sequency things last night I thought you
> should know.

Can we expect to hear P3_Tripping01.mp3 sometime soon then ? ;-)

Cheers,
Colin f

> But the Problem of Logic is, that it also sends
> a continue, when it stops somewhere, and you rewind back to the first
> beat of a bar (e.g. the second bar), the sends some Song position
> pointer, and then starts but with the continue signal.

Weird. Is that how the midi spec intended ? Seems like that would be a
pain with any device that doesn't support SPP.
Do any other PC sequencers do this ?
I guess I could always add SPP support, and just divide it into the
global bar length.
The idea of making continue=play sounds a lot easier though.

Cheers,
Colin f

On Sat, 1 May 2004 17:14:26 +0100, "Colin f" <colin@colinfraser.com>
wrote:

>Can we expect to hear P3_Tripping01.mp3 sometime soon then ? ;-)

If I can gfind somewhere to sitck em

we have hours and hors and hours of stuff

of course


---
Paul Nagle / Soft Room Music
Email: paul@softroom.co.uk www.softroom.co.uk
                           www.BogusFocus.com

> The idea of making continue=play sounds a lot easier though.
> 

Something that I have found to be a PITA, is that when syncing the P3 to my Yamaha 
AW16G multitracker, I don't always want the P3 to start with each midi start or 
continue message, but they can't be selectively turned off from the DAW.

I've found that I need to filter out the start and continue messages using Midiox which 
works OK, but means I have to keep the PC fired up. 'twould be good if there was a 
user function which could set the P3 to ignore midi start and continue messages, 
then  the P3 could be kept in sync, but manually started when required.

I'm not familiar with software sequencers, so this might not be an issue for those 
users, but for us hardware only folk, this might be a useful little addition.

Unless anyone's got any better workarounds?

All the best

Andy

--
Andy Wilson
http://www.techman.synth.net
mailto:andy@techman.synth.net

> Something that I have found to be a PITA, is that when 
> syncing the P3 to my Yamaha 
> AW16G multitracker, I don't always want the P3 to start with 
> each midi start or 
> continue message, but they can't be selectively turned off 
> from the DAW.

Many moons ago, the sync source in P3 had to be manually set.
When I made it automatic, I was pretty sure it would be a problem for
some people.
A manual over-ride won't be too hard to do, I'll just need to find
somewhere to stick the options.
There's a clock_config byte that indicates whether the time source is
internal or midi, and whether to output din sync and/or midi clock.
I can add a user config option to block the auto-switching in about 2
minutes. I'll need to find a soft-key space somewhere to allow you to
then set the clock source, which will take a bit longer.
 
Cheers,
Colin f

Hi Colin,

> Many moons ago, the sync source in P3 had to be manually set.
> When I made it automatic, I was pretty sure it would be a problem 
for
> some people.
> A manual over-ride won't be too hard to do, I'll just need to find
> somewhere to stick the options.
> There's a clock_config byte that indicates whether the time source 
is
> internal or midi, 

OK, it's not the clock *source* I want to switch. Auto clock setting 
is OK for me. I do want the P3 to follow external midi clock when 
it's available, but what I *don't* want is for the P3 to 
automatically start or continue each time I start the recorder. I 
want to be able to start the P3 manually but in sync. Therefore what 
I need is for the 'Start' and 'Continue' system realtime messages to 
be filtered out, which I'm doing with Midiox at the moment.
If this could be made a user option, that would be V.cool.

All the best

Andy
---

Andy Wilson
http://www.techman.synth.net
andy@techman.synth.net