Timestretch in new version

[shamann]

Really like some of the changes in 1.45.

A question regarding timestretch: is it possible to save timestretch parameters in a host project? Currently for me, the timestretch info is completely lost on reloading a project (tried in Audiomulch, Bidule, eXT).

Also a slightly less pressing question, but what was the reason for moving the x to delete slices from the right to the left-hand side? I have no real objections, although it's going to take some time to mentally adjust, just wondering if there are benefits to the switch I'm unaware of.

[DarkStar]

FThe reason for moving the [x] was this:
BR 045 Overlapping events
When a short event starts and ends within another longer event you do not get the delete [x] icon in the top-right corner for the longer event
and
BR 052 - Disappearing [x] button in overlapping events
When two events overlap you cannot delete the first one by clicking on its [x] button.
- when you hover over the first (non-overlapping) part of the first event you can see the [x] but when you move over it (i.e. in the overlapping area) it disappears.

[ohm]

Really like some of the changes in 1.45.

A question regarding timestretch: is it possible to save timestretch parameters in a host project? Currently for me, the timestretch info is completely lost on reloading a project (tried in Audiomulch, Bidule, eXT).

Did we really overlook this in the testing? Can anybody verify this? I'm away from my development computer today, but I'll look at it tomorrow so we'll get it fixed.

[Juanjo]

Actually yeah, I just reproduced the issue in eXT, timestretching settings are not saved either in projects or in fxbs.

[ohm]

ok, it'll be a quick fix - I was expecting a 1.46 update anyways - it's impossible not to overlook the little details in a huge update like 1.45. I'll release it in a couple of days.

[Juanjo]

That's cool, there's certainly a ton of cool stuff in the new update anyway, thanks ohm.

[shamann]

The reason for moving the [x] was this:
BR 045 Overlapping events
When a short event starts and ends within another longer event you do not get the delete [x] icon in the top-right corner for the longer event
and
BR 052 - Disappearing [x] button in overlapping events
When two events overlap you cannot delete the first one by clicking on its [x] button.
- when you hover over the first (non-overlapping) part of the first event you can see the [x] but when you move over it (i.e. in the overlapping area) it disappears.

Understandable. I'll just have to train myself to move the mouse the opposite direction, which shouldn't take long.

[ohm]

Stretching parameters (liveslice 1.46) are still not saved when saving my project in cubase sx3 :S

damn... that's one illusive little bug. I'll look at it again.

[GilJ]

There's also an "old" DarkStar's BR which is still present in LS v1.46:

- BR 092 waveforms remain in Slicer when loop is deleted
v145 rc1 - when I delete a loop from the loops section (by middle-click or Ctrl+right-click) the loop waveform graphics remain in the Slicer for that loop slot.

[DarkStar]

who you calling old?

[ohm]

Stretching parameters (liveslice 1.46) are still not saved when saving my project in cubase sx3 :S

fixed

[ohm]

There's also an "old" DarkStar's BR which is still present in LS v1.46:

- BR 092 waveforms remain in Slicer when loop is deleted
v145 rc1 - when I delete a loop from the loops section (by middle-click or Ctrl+right-click) the loop waveform graphics remain in the Slicer for that loop slot.

fixed

[GilJ]

who you calling old?

Sorry, I should have written "an old bug reported by DarkStar"
The good news is that it has now been fixed
Thanks Ohm!

[ohm]

who you calling old?

fixed

[GilJ]