Re: [LCtalk] Going to use te Lanbox again for next project

[Dennis Peeters]

On 2-mar-06 at 2:02, Fokko van Duin wrote:
> OK, I am lost again. If you do a Go previous cue (or step), it goes 
> back nice and smoothly (but maybe too slow for you), and the same is 
> true for Go next cue.
>
> So, if I understand it correctly, you only want another set of Go 
> previous cue, with a fixed 3 sec fade time (or maybe using the manual 
> fade time)?

Manual fadetime would be great so we theatertechies can choose whatever 
time we prefer, even 0sec if preferred.


> If other theatre customers have no objections, maybe we can change the 
> "Go previous cue" so it uses the manual fade time, unless it's off 
> (then it uses the scene step fade time as it is now).

Great!!!! (voor elk wat wils zoals we zeggen in het nederlands) < <this 
is dutch for something for everyone

> Would that solve your problem?

Yessssssssss!!!! (thank you lord)


> Question: what should happen when this previous cue is a split fade 
> one? Just going back one step with a normal cross fade of manual 
> speed, or change fade in and out both to manual speed?

I think a normal crossfade in manual speed, because the split fade has 
nothing to do with the cue I just landed in, example:
5 to 6 is splitfade, 6 to 7 is crossfade,  I made a mistake, so back to 
5 again, why should 7 to 6 be a splitfade?


> > Brings me to something else, that might be more logical to you, and 
> > could also solve my problem.
> > Maybe it comes down to the fact that the Lanbox uses the "crossfade 
> > time" of the previous cuestep it goes to,
>
> No, it uses the fade time of the cue you are Going to.

That's what I mean, I think its weird, because I think in a linear 
timeline, cue to cue , and you, my friend, think in loops;)


> > and I think it more logical to use the "crossfade time" of the 
> > cuestep i've just called.
> > Example: Cuestep 7 has a crossfade of 50s, it fades in smoothly, 
> > during the following scene I make a mistake and go (to soon) to 
> > cuestep 8 (for example, a blackout) which has a crossfadetime of 3s, 
> > the stage goes dark, I press back and it doesn't crossfade back in 3s 
> > but in 50s.
> > I ask you, when and why would I want that?
>
> A moving sweep e.g.: slowly (50sec) to the left, to the top (10sec), 
> fast (3sec) to the right, and now bounce back (so reverse the path).

I get that I might need it for that, but then I'd program it like that 
in a bounce chase
There's a slight difference between a programmed cue and an emergency 
U-turn, i think:)
But you get the point I think?


> > (but maybe the k is in the same spot then). Could you maybe delve 
> > into what the problem is? This would really help me.
>
> I'll have a look, but Ukelele looks very complicated to me.

It's not, really, even a dumb theatertechie like me can understand it, 
so you must have no problems. Just read the manual, the character 
pallette is in the Finder (it doesn't mention that, and my OS is in 
dutch to it was a bit hard to find, in Dutch it's under Wijzig>Speciale 
tekens).


> > But seriously, Logic has done it all along hasn't it, I never heard 
> > anyone complaining about that.
> > I think such a versatile tool as the Lanbox should be flexible to use 
> > for everyones needs and (especially in combination with isadora) its 
> > far ahead in that already.
>
> Again, it's -extremely- difficult to get full control on keys under 
> current OSes, unless you create your own user interface like games, 
> and Audio/video programs.

Maybe just adding the / and* as alternate options for the l and k in 
the programming isn't that difficult, but I understand it probably 
sounds easier than it is.


> > I really love the Lanbox and LCEdit, and I'd like to help make  it 
> > just that bit more theater friendly.
> >
> > Hope you'll support me in that
>
> Yes, but it takes time :-)

I understand, thanks for the support again, I'll be looking forward to 
new innovations.

GRTZ
Dennis