Analogue-sequencer

"How about displaying the actual, continuously updated data value in
brackets somewhere on the screen?"

I agree with Martin that something like that would be very helfpul - its
often impossible to get back to where you were on the P3

Richard

----- Original Message -----
From: "Martin Naef" <mnaef@acm.org>
To: <analogue-sequencer@yahoogroups.com>
Sent: Tuesday, February 14, 2006 9:35 AM
Subject: Re: [analogue-sequencer] Something else...


> Hi Colin
>
> Colin f wrote:
> >> Sculpt: Why don't I see the sculpt value immediately? Especially for
> >> slow patterns it's hit and miss when I try to set a specified value
> >> (e.g., I only see the current data value once I hit the next step)
> >
> > Sculpting is captured at the start of each beat.
> > If you pressed the sculpt key just before the start of a beat, then the
old
> > way, you would sculpt two steps.
> > The ideal implementation is probably to have a window for sculpt from
half a
> > beat before, to half a beat after, so you can easily pick out one step
to
> > sculpt.
>
> The window method is certainly a good idea. However, my issue is really
> about *visual* feedback. I need to see immediately where my data pot is,
> otherwise it's extremely difficult to hit a certain value. Try the
> following:
>
> I recently tried to add a set of AUX rel notes one octave below the main
> note. The track was running at timebase 4 (global Tempo 66), so rather
> slow. I only knew where my knob was at the start of each step, so it
> took more than one full track length just to adjust the data knob to
> -12. Now I had to keep pressing the sculpt key for another eternity
> until the track actually run through all steps. Of course, I slightly
> moved my left hand, so at some time I started writing -13. The result: I
> had to go through all steps again... In retrospective, it would have
> been faster to use the individual pots instead of sculpt.
>
> If the screen represented the data value at all times, it would have
> taken me one second to get to -12, and there's a good chance I would
> have spotted the change to -13 before it was written.
>
> How about displaying the actual, continuously updated data value in
> brackets somewhere on the screen?
>
> > I didn't start out doing it that way. The transpose knobs in playlist
edit
> > still have zero in the middle.
> > But there isn't enough resolution to add a dead zone and still have the
full
> > range of values.
> > I got fed up hunting for a mid-point zero on bi-polar knobs, and decided
> > just to make zero fully anticlockwise.
> > I think once you accept that's the way it works, it can make life
easier.
>
> Agreed. If the dead-zone can't be implemented, having the 0 at full left
> makes sense.
>
> Bye
> Martin
>
>
>
>
> Yahoo! Groups Links
>
>
>
>
>
>
>