MOTM

Need to see what the uSeq soon-to-be owners think about how to implement a certain operational
mode.

There is a mode called Gated Play. This is *currently* how the firmware is written:

a) Apply Gate/LFO signal to the GATE IN jack.

b) Without having to touch any uSeq controls, when GATE is high (greater than +2.5V), the uSeq
plays the sequence, starting at the fist note, at the specified tempo.

c) When GATE goes low, the uSeq *immediately* stops playing, de-asserts the GATE outs, and resets
the sequence to the beginning. When the GATE goes high again, back to (b).

d) If the user presses the STOP panel button while GATE is high, the uSeq *immediately* stops and
resets.

There is an additional 'constraint' I am pondering. If case (d) occurs, does the firmware
*require* the user to press PLAY in order to 'arm' the uSeq, and then when a GATE happens, it
operates as before.

The 'Pro' of the current firmware is that the uSeq becomes "hands free", meaning you can
start/stop it "remotely".

The 'Con' is that there is no way to "kill it" with physically killing the GATE (pulling patch
cord out/ceasing the GATE source).

Comments?

Paul S.

IMHO, the first commandment of modular synths is that everything 
should be voltage controllable at all times, 24/7, manual 
intervention is just an extra. With that in mind, pressing STOP 
causes the thing to stop regardless of the GATE input. It should not 
start up again until the GATE input goes low and then high again. We 
shoudn't have to press PLAY again.

At 12:56 PM -0500 2003/05/29, Paul Schreiber wrote:

>Need to see what the uSeq soon-to-be owners think about how to 
>implement a certain operational
>mode.
>
>There is a mode called Gated Play. This is *currently* how the 
>firmware is written:
>
>a) Apply Gate/LFO signal to the GATE IN jack.
>
>b) Without having to touch any uSeq controls, when GATE is high 
>(greater than +2.5V), the uSeq
>plays the sequence, starting at the fist note, at the specified tempo.
>
>c) When GATE goes low, the uSeq *immediately* stops playing, 
>de-asserts the GATE outs, and resets
>the sequence to the beginning. When the GATE goes high again, back to (b).
>
>d) If the user presses the STOP panel button while GATE is high, the 
>uSeq *immediately* stops and
>resets.
>
>There is an additional 'constraint' I am pondering. If case (d) 
>occurs, does the firmware
>*require* the user to press PLAY in order to 'arm' the uSeq, and 
>then when a GATE happens, it
>operates as before.
>
>The 'Pro' of the current firmware is that the uSeq becomes "hands 
>free", meaning you can
>start/stop it "remotely".
>
>The 'Con' is that there is no way to "kill it" with physically 
>killing the GATE (pulling patch
>cord out/ceasing the GATE source).
>

You are already requiring the user to press 'Stop', so it's no longer 
hands-free.  Having the user press 'Start' again is preferred, rather 
than pulling the patch cord, IMO.

Mike

--- In motm@yahoogroups.com, "Paul Schreiber" <synth1@a...> wrote:
> Need to see what the uSeq soon-to-be owners think about how to 
implement a certain operational
> mode.
> 
> There is a mode called Gated Play. This is *currently* how the 
firmware is written:
> 
> a) Apply Gate/LFO signal to the GATE IN jack.
> 
> b) Without having to touch any uSeq controls, when GATE is high 
(greater than +2.5V), the uSeq
> plays the sequence, starting at the fist note, at the specified 
tempo.
> 
> c) When GATE goes low, the uSeq *immediately* stops playing, de-
asserts the GATE outs, and resets
> the sequence to the beginning. When the GATE goes high again, back 
to (b).
> 
> d) If the user presses the STOP panel button while GATE is high, 
the uSeq *immediately* stops and
> resets.
> 
> There is an additional 'constraint' I am pondering. If case (d) 
occurs, does the firmware
> *require* the user to press PLAY in order to 'arm' the uSeq, and 
then when a GATE happens, it
> operates as before.
> 
> The 'Pro' of the current firmware is that the uSeq becomes "hands 
free", meaning you can
> start/stop it "remotely".
> 
> The 'Con' is that there is no way to "kill it" with physically 
killing the GATE (pulling patch

> cord out/ceasing the GATE source).
> 
> Comments?
> 
> Paul S.

Seems to me that Mike is correct. If you do not hit 'Stop', the 
starting and stopping is fully remote via the gate signal.

If you do hit 'Stop', well, you're already at the panel and you can 
easily hit 'Start' to rearm it.

What I'd like to see added is an option to choose whether the 
sequence resets to the beginning or plays from the current location 
with each successive gate onset.

Moe

--- In motm@yahoogroups.com, "Mike Marsh" <mmarsh@w...> wrote:
> You are already requiring the user to press 'Stop', so it's no 
longer 
> hands-free.  Having the user press 'Start' again is preferred, 
rather 

> than pulling the patch cord, IMO.
> 
> Mike
>

Yes! I just did not have the guts to suggest it, but having the 
option to 'ply thru' instead of restart would be very helpful.

Mike

--- In motm@yahoogroups.com, "mate_stubb" <mate_stubb@y...> wrote:
.
.
.
> What I'd like to see added is an option to choose whether the 
> sequence resets to the beginning or plays from the current location 
> with each successive gate onset.
> 
> Moe
.
.
.

> What I'd like to see added is an option to choose whether the
> sequence resets to the beginning or plays from the current location
> with each successive gate onset.

It's already there. See section 6.3 of the spec.

--Adam

Cool.  I guess I understood from Paul's description that it was 
restart only...

--- In motm@yahoogroups.com, Adam Schabtach <adam@s...> wrote:
> 
> > What I'd like to see added is an option to choose whether the
> > sequence resets to the beginning or plays from the current 
location

> > with each successive gate onset.
> 
> It's already there. See section 6.3 of the spec.
> 
> --Adam

I'm also of the mind that one should press start/play for the sequence 
to resume.

S.
---------------------------------------------------------
Paul Schreiber wrote:

> Need to see what the uSeq soon-to-be owners think about how to implement a certain operational
> mode.
> 
> There is a mode called Gated Play. This is *currently* how the firmware is written:
> 
> a) Apply Gate/LFO signal to the GATE IN jack.
> 
> b) Without having to touch any uSeq controls, when GATE is high (greater than +2.5V), the uSeq
> plays the sequence, starting at the fist note, at the specified tempo.
> 
> c) When GATE goes low, the uSeq *immediately* stops playing, de-asserts the GATE outs, and resets
> the sequence to the beginning. When the GATE goes high again, back to (b).
> 
> d) If the user presses the STOP panel button while GATE is high, the uSeq *immediately* stops and
> resets.
> 
> There is an additional 'constraint' I am pondering. If case (d) occurs, does the firmware
> *require* the user to press PLAY in order to 'arm' the uSeq, and then when a GATE happens, it
> operates as before.
> 
> The 'Pro' of the current firmware is that the uSeq becomes "hands free", meaning you can
> start/stop it "remotely".
> 
> The 'Con' is that there is no way to "kill it" with physically killing the GATE (pulling patch
> cord out/ceasing the GATE source).
> 
> Comments?
> 
> Paul S.
> 
> 
> 
>  
> 
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/ 
> 
> 
>

I'm of the opinion that one should have to hit "play" in this situation.

-Russell

> 
> The 'Con' is that there is no way to "kill it" with physically killing the GATE (pulling 
patch

> cord out/ceasing the GATE source).
> 
> Comments?
> 
> Paul S.

> The 'Pro' of the current firmware is that the uSeq becomes "hands free", meaning you can
> start/stop it "remotely".
>
> The 'Con' is that there is no way to "kill it" with physically killing the GATE (pulling patch
> cord out/ceasing the GATE source).
>
Seems like I'm already in the minority, but I would prefer the "hands
free" option, if there is only one option to choose.  I'd prefer having
to cease a gate operation (e.g., run the gate through an attenuator), and
the 'remote' operation allows a lot more flexibility.
Jeff

I agree that hands free should be possible.  So, it can be started and
stopped remotely using the gate in.  I think the idea of having to pull the
cable is very bad.  Could it operate like this?

1.  complete remote start and stop, no intervention on the panel required.
Or, "as the gates flow."
2.  "Stop" on the panel overrides all remote gate start / stop function, so
when you hit stop in the "gated play "mode, it stops and stays stopped no
matter how many gates it receives.
3.  "Start" on the panel cancels the "stop" function and allows the restart
once gate input action resumes.

Seems like in the "gated play" mode start and stop could support that
function but would not actually be required use.  They would be almost like
"arm" and "disarm" buttons for the gate signals.

Larry H

----- Original Message -----
From: Jeffrey Pontius <jpont@...>
Seems like I'm already in the minority, but I would prefer the "hands
free" option, if there is only one option to choose.  I'd prefer having
to cease a gate operation (e.g., run the gate through an attenuator), and
the 'remote' operation allows a lot more flexibility.
Jeff