Analogue-sequencer

Folks,

v3.97 is in the Yahoo files section now.
An updated manual is there too. Gosh ;-)

There are two main additions to this build.

I've had a couple of people mention recently that they were 
getting 'ghosting' on their pots. This hasn't been a problem on my 
unit, although I am always careful to keep the pot leads as short as 
possible, and not run them near the PLED leads.
Tony Allgood suggested software noise-reduction might fix it, which 
seemed like a very good idea, so it's added now.
If you have ghosting in your pots, let me know if this build clears 
it up, or not.
If there are any other niggling little problems like this you don't 
think are worth moaning about, please do let me know.

Also added in this build is enhanced 'paste' functionality.
You can now selectively paste notes, auxes, both notes and auxes, or 
aux and accumulator config only. Use the 'select' softkey in the 
paste display to choose what will be pasted.

Cheers,
Colin f

I haven't used the p3 for so long, so my views are not that valid, but, as you asked...

Using the recommended alpha pots, and...

Sometimes when a pot is right on the border between two (digital) values, you may be working on something else and the screen starts 'flickering' with data from the pot, as it does when you intentionally change a value.

I'm not smart enough to suggest a solution, but i just thought id mention it as you had asked for any contributions like that.

I'm not running the latest os either.  Still haven't ordered those extra dins from rapid, and so only have a midi out so far ; )

Cheers, Julian


  ----- Original Message ----- 

  If there are any other niggling little problems like this you don't 
  think are worth moaning about, please do let me know.




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

Hi Julian, 

> Using the recommended alpha pots, and...
> 
> Sometimes when a pot is right on the border between two 
> (digital) values, you may be working on something else and 
> the screen starts 'flickering' with data from the pot, as it 
> does when you intentionally change a value.

Er, that's what I meant by 'ghosting'. Sorry if that wasn't clear...

To give you a bit more background...
The analogue to digital convertor scanning the P3 pots has an 8 bit range,
but only 7 bits are needed at most for midi values.
So the original pot scan code prevented ghosting/flickering between adjacent
values by only flagging the pot as 'changed' if the 8 bit value moved by 2
steps or more. Once this was divided down to 7 bits, it meant the values can
still step by 1.
It seems that in some cases a little bit of extra noise pick up somewhere
might mean the pot moves enough to trigger a 'change' even though the pot
hasn't been moved physically.
The updated code now only flags a pot as 'changed' if the value is different
from the previous value for 2 scans.
This seems to eliminiate extraneous noise pickup.

Cheers,
Colin f

Hi Colin,

On 1 Sep 2004 at 22:32, colinfraser_com wrote:

> 
> v3.97 is in the Yahoo files section now.

> If you have ghosting in your pots, let me know if this build clears 

> it up, or not.

That's great. I have noticed this ghosting effect occasionally. 
Strangely, it seems to be more noticeable on some days than others!!

Dare I mention 'Suspend Start Mode' as discussed at the beginning of 
May?? Any chance?  eh?

Cheers

Andy
---

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

On Thu, 2 Sep 2004, Andy Wilson wrote:

> That's great. I have noticed this ghosting effect occasionally.
> Strangely, it seems to be more noticeable on some days than others!!

what'd i tell you colin? relative phases of neptune's five moons! see,
this is a special metaphysical aux feature of the P3 colin and paul have
come up with when in touch with "higher powers." heh... :)

> Dare I mention 'Suspend Start Mode' as discussed at the beginning of
> May?? Any chance?  eh?

or track volume? :) the knobs don't need to set it... it can just be a
parameter somewhere in the menus. if possible, it would be nice if FUNC +
knob could be a shortcut to a volume change, but this is not completely
necessary.

or maybe the "set ticks per step" aux event? not totally necessary either,
but it'd be damn cool...

or a new one i dreamed up this morning, mute mode... when i used to work
with the MMt-8, one of the things i liked about it was that muting and
unmuting tracks had an instantaneous, audio-like effect. if a note was
sustaining and i unmuted the track, it would start making noise. i have no
idea how it did this, but i expect it's a combination of note on/off
messages and MIDI volume CC messages. if we could have a mute mode option,
that would be great...

mode 1 would be MIDI, which would work as it currently does. mode 2 would
be AUDIO, which would work like this... scratch what i said above, it
should *only* be a MIDI CC#7 message... muting a track simply sends MIDI
CC#7=0 on the track's channel; unmuting sends MIDI
CC#7=<TrackVolumeValue>. so it ties into my desire for that track volume
parameter too, heh.

bleep.
out.

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

Hi,

>If there are any other niggling little problems like this you don't
>think are worth moaning about, please do let me know.

I have one ;)
Well, it's not a problem, more a tiny wish.

I would like to be able to change track/pattern without having to press 
"Save", "Back" or "Lose".
I know func+play+track is already used, but pretending it's not, some ways 
to do it would be:
- pressing func+play+3 would save the current pattern and change to pattern 
1 in track 3.
- pressing func+play+3+4 would save the current pattern and change to 
pattern 4 in track 3.

or track 9-16 could be used together with func+play, so that func+play+10 
changes to track 2, 11 to track 3 and so forth.

Not a big deal, but it would make changing tracks/patterns a bit easier if 
func+whatever+3+2 always changed to track 3 pattern 2. A global shortcut 
just like the track mute shortcut.

Jesper.

> I would like to be able to change track/pattern without 
> having to press 
> "Save", "Back" or "Lose".
> I know func+play+track is already used, but pretending it's 
> not, some ways 
> to do it would be:
> - pressing func+play+3 would save the current pattern and 
> change to pattern 
> 1 in track 3.
> - pressing func+play+3+4 would save the current pattern and change to 
> pattern 4 in track 3.

The way the pattern edit code is written at the moment, switching directly
to edit another pattern isn't possible.
It may need some re-working if/when I come to add the 'Save to another
track' option.
I'll have a look at this then. But no promises...
 
> or track 9-16 could be used together with func+play, so that 
> func+play+10 
> changes to track 2, 11 to track 3 and so forth.

Remember if the memory layout is set for 3 banks of 16 patterns, keys 9 to
16 are used for pattern selection too.

Cheers,
Colin f

> If you have ghosting in your pots, let me know if this build clears 
> it up, or not.

It works for me Colin..
Gawd bless yer cotton bobby socks!
Phil

>Remember if the memory layout is set for 3 banks of 16 patterns, keys 9 to
>16 are used for pattern selection too.

That's right, I forgot ;)
What about 16 tracks instead of 8, is that possible (with fever patterns of 
course)?

Jesper.

> That's right, I forgot ;)
> What about 16 tracks instead of 8, is that possible (with 
> fever patterns of 
> course)?

The track count is restricted to 8 by the UI hardware I think.
There is an easy way to get 16 tracks, but I'm out of stock at the moment
;-)

Cheers,
Colin f