Q- Overlapping and Replacing Events

Official support for: livelab.dk
Locked New Topic
RELATED
PRODUCTS

Post

Q - Problems with inserting an overlapping event
After a slice is selected, Ctrl+click in a track can be used to insert the event at the desired position, ignoring the Snap setting, and overlapping any existing event

- with [snap] On, if you Ctrl+LMB within the first snap length of an existing event, the event is replaced, the overlapping does not work
- with [snap] On, if you Ctrl+LMB beyond the first snap length of an existing event it is kept and the new event overlaps it
- with [snap] Off if you Ctrl+LMB anywhere within an existing event it is replaced

Am I misunderstanding or doing this wrong? Or is it a bug (BR036)?

This screenshot show the effect of pasting in various overlapping positions:
Image

Big pic: http://img217.imageshack.us/img217/2162 ... lapjz8.png


Q - Parameters values when Events are replaced
Is this right?

- - when you replace an Event, if no parameter is selected, the new event takes the parameters values of the replaced event

- - when you replace an Event, if a parameter is selected, the new event sets the selected parameter value according to the vertical position of the mouse when clicked, and takes the other parameters values from the replaced event

If so, is this the desired action or is it a bug (BR037)?
Perhaps the new event always take its parameter values from the replaced event?

[Edit: to make BR numbers unique]
Last edited by DarkStar on Mon Jan 08, 2007 9:45 pm, edited 1 time in total.
DarkStar, ... Interesting, if true
Inspired by ...

Post

Bump.

Anyone?
DarkStar, ... Interesting, if true
Inspired by ...

Post

I'll get back to you in a couple of days when I've had the time to test myself. Others are more than welcome to verify in the mean time of course :-)
http://www.livelab.dk - slice up your life

Post

thank you
DarkStar, ... Interesting, if true
Inspired by ...

Post

DarkStar wrote:Q - Problems with inserting an overlapping event
...
- with [snap] On, if you Ctrl+LMB within the first snap length of an existing event, the event is replaced, the overlapping does not work
...
Cannot reproduce this. Regardless if I Ctrl+LMB within or beyond the first snap length of an existing event, I always get the same behaviour (new event overlaps old one as expected). Weirdly enough, if the end of a new overlapping event occurs before the end of the old overlapped event, then the old event only displays its full length while you click on it or on the new event. Otherwise it appears truncated at the point where the new event ends, although it does play back its full length correctly (?).
DarkStar wrote:Q - Parameters values when Events are replaced
Is this right?
...
- - when you replace an Event, if a parameter is selected, the new event sets the selected parameter value according to the vertical position of the mouse when clicked, and takes the other parameters values from the replaced event
...
Verified. This happens only if you replace by clicking on the desired event in the Slicer and then clicking on the event to be replaced in the arranger. It doesn't happen if you click+drag the desired event from the slicer into the arranger.

(eXT latest beta, LS 1.44)
The mind boggles.

Post

Juanjo,
thanks for #2

Re #1 - try it with a "long" event, a slice that covers several snap lengths in the arrangement - you'll see in my screenshots that the original events covered 2 snap lengths in the arrangement tracks

HTH
DarkStar, ... Interesting, if true
Inspired by ...

Post

DarkStar wrote:Re #1 - try it with a "long" event, a slice that covers several snap lengths in the arrangement - you'll see in my screenshots that the original events covered 2 snap lengths in the arrangement tracks
Yeah, I was trying with "long" events... but I was clicking and ctrl+dragging instead of clicking and ctrl+clicking, sorry about that... :oops:

So, #1 verified as well.

Btw, I think the following still applies:
Juanjo wrote:Weirdly enough, if the end of a new overlapping event occurs before the end of the old overlapped event, then the old event only displays its full length while you click on it or on the new event. Otherwise it appears truncated at the point where the new event ends, although it does play back its full length correctly (?).
Which might be a bug... any confirmation or am I seeing things?
The mind boggles.

Post

New Year's bump
DarkStar, ... Interesting, if true
Inspired by ...

Post

Happy New Year (bug fixed)

I've tried displaying all events at their exact length, instead of cutting them off at the beginning of the next event - once the next beta is out, I'll collect opinions on how this works. Perhaps if I can find a way to draw semitransparent events - it'll work even better
http://www.livelab.dk - slice up your life

Post

DarkStar wrote:Q - Problems with inserting an overlapping event
After a slice is selected, Ctrl+click in a track can be used to insert the event at the desired position, ignoring the Snap setting, and overlapping any existing event

- with [snap] On, if you Ctrl+LMB within the first snap length of an existing event, the event is replaced, the overlapping does not work
- with [snap] On, if you Ctrl+LMB beyond the first snap length of an existing event it is kept and the new event overlaps it
- with [snap] Off if you Ctrl+LMB anywhere within an existing event it is replaced

Am I misunderstanding or doing this wrong? Or is it a bug (BR030)?

This screenshot show the effect of pasting in various overlapping positions:
Image

Big pic: http://img217.imageshack.us/img217/2162 ... lapjz8.png
-> Confirmed
DarkStar wrote: Q - Parameters values when Events are replaced
Is this right?

- - when you replace an Event, if no parameter is selected, the new event takes the parameters values of the replaced event

- - when you replace an Event, if a parameter is selected, the new event sets the selected parameter value according to the vertical position of the mouse when clicked, and takes the other parameters values from the replaced event

If so, is this the desired action or is it a bug (BR031)?
Perhaps the new event always take its parameter values from the replaced event?
-> Confirmed

GilJ.

Post

we have semitransparent events - Doesn't seem to affect performance drastically on my system.
Fixed the (maybe) BR with event parameters on replacing - I agree it seems more logical to keep parameters of the replaced event.
http://www.livelab.dk - slice up your life

Locked

Return to “Livelab.dk”