liveslice 1.45 beta thread

[english]

Same thing in Cubase 4.02...fine at 44 but audio glitches at 88 and 96 when playing back in the seq.

eng

[english]

sorry to keep banging on about this but I thought I would just do some mp3 examples...

http://homepage.ntlworld.com/t.englefield/44.mp3
http://homepage.ntlworld.com/t.englefield/96.mp3

Its the exact same project, loop and tempo (tempo of project is same as actual loop tempo), the sample rate is the only thing thats changed. As you can hear there is quite bad audio glitches in the slice playback at higher sample rates. This happens in both Reaper and Cubase 4.02 and at samplerates 88 and 96 (and 48 in Reaper). It also doesnt matter what buffer size I set the soundcard to, even at 1024 these problems happen.

However, auditioning loops in LS even at the higher samplerates plays back them back perfectly fine with none of these problems.

You can obviously hear it more on some loops than others, but its still there. Can anyone else confirm this issue at a 88/96? (im using beta 6 btw)

Cheers,

eng

[kejkz]

Indeed, I must confirm there is something wrong abowe 48khz.
Podium crashed, reaper stutters, tracktion 1 reports problems with liveslice. Weird

update: it doesen't play slices correctly, it chops ends of them

[ohm]

I have identified and fixed the problem. It occured when lowering the pitch too - I made a miscalculation in the stretching algo, so it would kick in too early and cause glicthes.

[scuzzphut]

glicthes ?

good to know is fixed, ohm

[ohm]

sorry there was a ghlicht in my keyboard stream. I meant to type "gitlcehs" of course. Everything seems to wok now.... I think.

[english]

schweeeet !! thanks muchly

eng

[ohm]

good news for those of you using 24 and 32 bit samples: I fixed saving of 24 bit wav. files and added saving of 32 bit (PCM and float). All load / save functionality has been verified by comparing wave files before and after a save using a hex-compare utility.
Would be nice to add an option to specify the output format for recordings. At least it would probably be a good idea to use 32 bit float as the default format, because it's identical to the internal format used in VST plugins (guaranteed no clipping).

[parris]

Sounds like a good idea to me ohm, as i use 32bit float in cubase 4. Keep up the class job your doing on this update...........

[kejkz]

sorry there was a ghlicht in my keyboard stream. I meant to type "gitlcehs" of course. Everything seems to wok now.... I think.

Damn, i considered tha as a feature! Autoghiclht

[GilJ]

Thanks Ohm for the beta 7 version ( the new features AutoStretch/AutoPitch, option to turn off AlphaTransparency, slicedisplay zoom / scroll much faster etc.)

Here are some BR I've noticed so far (haven't spent too much time with the new 'time stretch implementation' yet )

[LiveSlice v145b7]
BR1/ Mouse's wheel (scroll down only) doesn't work on some parameters (I.E. Number of slices, number of beats, Number of stereo outputs, Number of visible tracks etc.)

BR2/ First slice in slicer not being deleted correctly
1- Load a loop
2- In the slicer, set the slices parameter to 0
3- CTRL+LMB in the slicer in order to add a 1st marker
4- CTRL+LMB in the slicer in order to add a 2nd marker (to the right of the first one)
5- Delete (MMB) just after the 1st marker in order to delete it
The default 'start marker' is being moved

BR3/ Display bug for the red \"playing\" marker
1- Click on Play in LS
2- Select (LMB) C3
3- Select (LMB) C#3
The 2 red \"playing\" markers are being displayed

BR4/ AutoPitch button
RMB Autostretch button=Autopitch
The button remains 'selected' (should not be a toggle button, should it?) and the range parameter is automatically set to 12...

BR5/ No pop up menu for Chan. parameter in settings > Other Midi Controller config

BR6/ Bad range for the pop up menu for Arr. (settings > Other Midi Controller config)
Arr. range=from C1 to C7, but C7 arrangement doesn't exist in LS

[EDIT, new BR added]
BR7/ Recording function of LiveSliceEffect works in eXT, but doesn't work in Ableton Live
When a LiveSliceEffect is inserted after a VSTi, it bypasses all the audio coming out from of the VSTi (in Live only, in eXT it's OK)

Cheers,
GilJ.

[ohm]

Thanks Ohm for the beta 7 version ( the new features AutoStretch/AutoPitch, option to turn off AlphaTransparency, slicedisplay zoom / scroll much faster etc.)

You're welcome - a question: does it make a difference if you turn off alpha? It doesn't on my system (geforce 7300) almost seems alpha rendering is faster.

Here are some BR I've noticed so far (haven't spent too much time with the new 'time stretch implementation' yet )

[LiveSlice v145b7]
BR1/ Mouse's wheel (scroll down only) doesn't work on some parameters (I.E. Number of slices, number of beats, Number of stereo outputs, Number of visible tracks etc.)

fixed

BR2/ First slice in slicer not being deleted correctly
1- Load a loop
2- In the slicer, set the slices parameter to 0
3- CTRL+LMB in the slicer in order to add a 1st marker
4- CTRL+LMB in the slicer in order to add a 2nd marker (to the right of the first one)
5- Delete (MMB) just after the 1st marker in order to delete it
The default 'start marker' is being moved

"but it's a feature not a bug" as they say. Ok so maybe a feature that needs some revision... The default 'start marker' IS the first slice. The reason for this is: In most cases you want the first slice right in the beginning of the loop so if there were two markers they'd overlap, and I'd need to add a "crop" button that had to be activated before the crop markers were even shown. I wanted to keep a simple as possible workflow.
I realize there are loops where the first slice is not at the beginning (drum loop packs with separate bd / snare loops) in that case you'll be forced to have a silent slice in the beginning - a bit clumsy.
Also you can argue it's bad gui design to have a slice that looks different than all the other slices, and to be honest: most people would never use the "crop" feature so it does make sense to keep it hidden behind a "crop" button, or similar. I've been considering an "edit" toolbar containing the crop + normalize buttons and would enable the loop point editing when I implement that.

BR3/ Display bug for the red "playing" marker
1- Click on Play in LS
2- Select (LMB) C3
3- Select (LMB) C#3
The 2 red "playing" markers are being displayed

odd. cannot reproduce this...

BR4/ AutoPitch button
RMB Autostretch button=Autopitch
The button remains 'selected' (should not be a toggle button, should it?) and the range parameter is automatically set to 12...

it's a toggle button because when it's activated and the project tempo changes - the stretch / pitch is ajusted automatically. The range is set to 12 because it hardly makes sense to stretch more than an octave to match tempo does it?

BR5/ No pop up menu for Chan. parameter in settings > Other Midi Controller config

fixed - also found a bug in the note param not being divided into columns (pretty long list)

BR6/ Bad range for the pop up menu for Arr. (settings > Other Midi Controller config)
Arr. range=from C1 to C7, but C7 arrangement doesn't exist in LS

fixed

[EDIT, new BR added]
BR7/ Recording function of LiveSliceEffect works in eXT, but doesn't work in Ableton Live
When a LiveSliceEffect is inserted after a VSTi, it bypasses all the audio coming out from of the VSTi (in Live only, in eXT it's OK)

fixed.

Cheers,
GilJ.

thanks

[ohm]

found and fixed a bug causeing the playback marker not to be erased if playback was very fast (faster than the update rate)

[GilJ]

Thanks Ohm for the beta 7 version ( the new features AutoStretch/AutoPitch, option to turn off AlphaTransparency, slicedisplay zoom / scroll much faster etc.)

You're welcome - a question: does it make a difference if you turn off alpha? It doesn't on my system (geforce 7300) almost seems alpha rendering is faster.

I wanted to ask you the question about the performance (CPU use) with alpha being turned on/off
It's just that I'm more used with the old version (=no alpha) I just need to get used to the AlphaTransparentcy events (specially if rendering is faster )

BR2/ First slice in slicer not being deleted correctly
1- Load a loop
2- In the slicer, set the slices parameter to 0
3- CTRL+LMB in the slicer in order to add a 1st marker
4- CTRL+LMB in the slicer in order to add a 2nd marker (to the right of the first one)
5- Delete (MMB) just after the 1st marker in order to delete it
The default 'start marker' is being moved

"but it's a feature not a bug" as they say. Ok so maybe a feature that needs some revision... The default 'start marker' IS the first slice. The reason for this is: In most cases you want the first slice right in the beginning of the loop so if there were two markers they'd overlap, and I'd need to add a "crop" button that had to be activated before the crop markers were even shown. I wanted to keep a simple as possible workflow.
I realize there are loops where the first slice is not at the beginning (drum loop packs with separate bd / snare loops) in that case you'll be forced to have a silent slice in the beginning - a bit clumsy.
Also you can argue it's bad gui design to have a slice that looks different than all the other slices, and to be honest: most people would never use the "crop" feature so it does make sense to keep it hidden behind a "crop" button, or similar. I've been considering an "edit" toolbar containing the crop + normalize buttons and would enable the loop point editing when I implement that.

I see what you mean, and that's rather a cool feature , but I still think there's something quite odd here:
If you have a loop with the default 'start marker' and 1 other marker (M1) only: if you MMB after M1, M1 is deleted and the 'start marker' isn't being moved (as expected)
However, if you have a loop with the default 'start marker' and 2 other markers (M1,M2): if you MMB after M1 (but before M2), M1 is deleted as expected, but the 'start marker' is being moved to M2...

BR3/ Display bug for the red "playing" marker
1- Click on Play in LS
2- Select (LMB) C3
3- Select (LMB) C#3
The 2 red "playing" markers are being displayed

odd. cannot reproduce this...

I had some problem to reproduce it too at first, but now it's always behaving like this. Here's how in eXT:
1- Load LS
2- Hit Play in eXT
3- Load a loop and lock to loop (C1 arrangement)
4- Click on play in LS
5- Select C#1 arrangement
C1 and C#1 arrangements both have the red "playing" markers

BR4/ AutoPitch button
RMB Autostretch button=Autopitch
The button remains 'selected' (should not be a toggle button, should it?) and the range parameter is automatically set to 12...

it's a toggle button because when it's activated and the project tempo changes - the stretch / pitch is ajusted automatically. The range is set to 12 because it hardly makes sense to stretch more than an octave to match tempo does it?

But if I activate AutoPitch (RMB on AutoStretch), when I change the tempo of my host, the pitch of the loop isn't being repitched (I need to RMB on the button again in order for the loop to be repitched)


Thanks again Ohm
GilJ.

[DarkStar]

And one more from me:

BR 071 - LS does not write the correct ACID info sometimes

I loaded a sample into LS, sliced it into 4 even slices and saved it 120_shika_68_4e.wav). This sliced sample was not OK and would not load into another slice player.

I loaded the sliced sample back into LS, changed one of the slices by dragging it and saved it again (120_shika_68_4e2.wav). This one was OK.

Attached is a screenshot showing the slice info part of the sample files. The corrupt sample has 2 sections with the text "acid" and "strc" in it, the good sample has 1 section. I think this might be relevant.



Big pic:
http://img106.imageshack.us/img106/4344/lsacid01gv7.png