LiveSlice 1.47 beta thread

[DonJenaro]

How to get this 1.47 beta? On the site is just a commercial release 1.46.

[Architeuthis]

I know why LiveSlice Effect doesn't show up in Cubase... well I don't know really, but I have a clue:

I moved my VST files around and now LiveSlice effect shows up and LiveSlice VST does not show up. That means it has something to do with the two files conflicting. I LOVE THE RECORD FEATURE! I just discovered how easy it is to glitch things up.

[shamann]

Presumably that means they share the same VSTID.

[shamann]

Just checked with version 1.45 with VSTSpy, both use JCLS as their identifier. The effect version also doesn't show up in Bidule (which also scans based on ID).

[ohm]

sounds like an easy fix, just change the ID Next build of liveslice effect will have the ID JCLF instead... JCLE was taken.

[ohm]

new beta is ready, and will be sent out shortly.

fixed:
- crash when setting arrangement to zero duration
- crash when loading banks in ableton live
- better tolerance for erroneous Acid tempo information
- attempted fixes for unverified access violation bugs
- locate slice button fixed
- better window refresh when expanding the gui (no more black areas) - tested in energy xt, traction and live.
- rex sample rate conversion bug fixed (I overlooked that the rex library converted everything to 44100 unless instructed specifically to keep the original sample rate, so 96k loops were a bit high pitched)

I could not reproduce the error with rapid file browsing.

regarding weird tempo reports on rex files: LiveSlice will display the original tempo of the loop - this is different from the one defined in recycle, usually a bit slower.
Also: if the slices are stretched in recycle, the duration of the loop will be longer, hence the tempo a bit slower. I can't really change this easily, because liveslice does not store each slice separately but rather has all sample data arranged in a linear fashion. This might change, and then I'll get back to this little detail. It will complicate moving slice points, as I beleive I already explained in a different post, so for now, I'll keep the present data format.

[DarkStar]

Good Oh!

I hope that playing the "overlapping" slices in a RX2 loop is now OK.

[ohm]

Good Oh!

I hope that playing the "overlapping" slices in a RX2 loop is now OK.

hmmm speaking of overlapping slices.... could you send me one of those problematic rx2 files? I can't find those you sent me before...

[DarkStar]

Same one will be on its way!

[ohm]

Same one will be on its way!

got the files
fixed the bug
beta email sent

[spuddle]

Can anyone replicate this bug?

In latest version of REAPER (2104), open LiveSlice 1.47 beta 3 in a track, then load a bank using REAPER's native patch loading function. The first bank loads flawlessly. But when trying to load another bank in same LiveSlice, it crashes REAPER.

Is this REAPER or LiveSlice at fault?

[ohm]

Can anyone replicate this bug?

In latest version of REAPER (2104), open LiveSlice 1.47 beta 3 in a track, then load a bank using REAPER's native patch loading function. The first bank loads flawlessly. But when trying to load another bank in same LiveSlice, it crashes REAPER.

Is this REAPER or LiveSlice at fault?

I'd like to try and reproduce this, but none of the liveslice banks I have crashes reaper. I did find a bug related to bank loading, that would prevent playback if a loop was missing.

perhaps you can email me one of the banks that crashes reaper?

[audio_dude]

Hi ohm,


it seems there's some kind of "bad memory access" bug in 1.47 when you trigger slices from a host as DarkStar explained here http://www.kvraudio.com/forum/viewtopic ... 54&start=0 .

I use LiveSlice 1.47 in FL (latest stable FL7 + latest FL8 beta), and each time I configure LiveSlice in order to trigger the slices from MIDI notes in FL, it quickly crashes FL or display a "Access Violation" window.

I think it's actually a problem with LiveSlice because I tried the same thing with other VSTs and it worked with absolutely no problem (with other VSTs, it doesn't crash FL or display a "Access Violation" window).

So it could be really interesting if other users could try this thing (with FL or other hosts).

Thanks !

Keep up the good work, ohm ! LiveSlice's great !


EDIT / MORE INFO : the bug doesn't appear if you just configure LiveSlice as described above, and, then, leave it as it is, making your music without going back to LiveSlice, BUT as soon as you re-open LiveSlice's GUI, the "Access Violation" bug appears. Hope this helps.

[ohm]

thanks - I'll try reproducing the bug tonight.

[ohm]

thanks - I'll try reproducing the bug tonight.

Couldn't reproduce. Are you sure you are using the latest beta? it says "beta 3" in the liveslice gui.

Are you using the effect or the instrument version? What exactly do you do?

thanks for helping me solve this.

- Jacob