BR - My problems with Slice triggers [mostly a dodgy sample]

[DarkStar]

(LiveSlice, v1.2.1, full)
LS is set up as a comp in energyXT (v1.3.6).

I thought I would explore the individual slice triggering today, but I ran into some issues:

(1) The slice triggers (C4 to G8 ) seem to trigger the last loop loaded in the loops section, not the currently-selected loop.

- - - - - - - - - - -
(2) Also some slices are a lot quieter
Triggering some slices plays them back very differently from:
- right-clicking the slice itself (by 16db or so)
- playing an arrangement of events using the slice

[I have all my trigger keys C1, D1, C5 to B5, set to velocity 127]

Stop press - here's some more info:
- it might be only the first slice that is affected (but I did not try all the others)
- and I could can get the same (reduced) level in an arrangement by setting Attack to 100ms or so.

I tried another loop (the EthnoPercB one, ohm, if that helps)
- this time triggering the first slice played it at the right volume
- (3) but the trigger key was D4 not C4

I tried a third loop:
- again t was only the first slice that is affected (but I did not try all the others)
- and I could can get the same (reduced) level in an arrangement by setting Attack to 100ms or so.

- - - - - - - - -
[FR] When you select an arrangement to trigger the slices of its first track, the Play button is tagged "individual", but it is no longer active. I think it would help if it were still active.

HTH

[EDIT: to clarify the title, the dodgy sample causes the second and third problems mentioned]

[R.A.W.]

The slice triggers (C4 to G8 ) seem to trigger the last loop loaded in the loops section, not the currently-selected loop.

i can confirm that, everything else works normal here. i tried several loops and any slice played with the correct volume.

[ohm]

I'll look into it, thanks for the report.

As for your FR - it was much simpler implementing it this way - I know it's a bit annoying, so I'll probably do it the hard way in another update

[DarkStar]

ohm, RAW
If it helps, the low volume and triggering starting at D4 problems can been heard using the EthnoPercB loop (this is the one that also shows 28 in the slice value, but only 25 slices in the Slicer view)

[ohm]

ok, thanks. Will check it out soon.

[R.A.W.]

I tried another loop (the EthnoPercB one, ohm, if that helps)
- this time triggering the first slice played it at the right volume
- but the trigger key was D4 not C4

ok, checked the loop now on my system.. it's the same issue, there are 2 "invisible" slices at the beginning of that loop. like i said before in another thread, the loop seems to have invalid slice-marks, this leads to the behaviour that the first slice you see is infact the 3rd, therefore mapped to D4 (with the default settings of course ).
so it's not a LS bug, it's just the invalid loop.

[DarkStar]

RAW,
Yep I remember you said about the "invisible" slices. I thought I had got rid of them by dragging the Sensitivity slider right and left to get the slices value to be 25 slices. But i think the weirdness was still there.

I'll explore more later on.

Thank you for the reminder, though.

[R.A.W.]

Thank you for the reminder, though.

np

now that you can save the acid-info with liveslice, you can easily get rid of those strange marks.

[ohm]

I found the problem - I was looking in the wrong place before, because that loop you sent me contained the slices as cuepoints, not as ACID info, and I wasn't checking for errors in cuepoints. The file contained three extra slices in the beginning of the loop, now I check that all slices are at least 50 ms. apart, and ignore them otherwise. A new beta will be out before the weekend.

[ohm]

The slice triggers (C4 to G8 ) seem to trigger the last loop loaded in the loops section, not the currently-selected loop.

- fixed

took care of the volume problem as well.

[DarkStar]

great news - I need to learn more about cuepoints and ACID info, any good links?

[ohm]

don't have any links, but cue points are what some audio editors call markers. They simply describe a sample value and can contain a textual description as well.
ACID info is not really made to describe slices, but contain detailed information about the transients of the individual hits, as well as tempo info, that can be "translated" into slices.