I just emailed it to you. I remember recently changing your email address, but I don't remember you requested to be on the beta list. Anyways, now you are. I recently made some changes to the way I send out the beta's so it's finally very easy to managespuddle wrote:Where can I get the latest RC from?
liveslice 1.45 beta thread
-
- KVRAF
- Topic Starter
- 1511 posts since 2 Jul, 2004
http://www.livelab.dk - slice up your life
-
- KVRian
- 1214 posts since 10 Aug, 2005
I may have requested to be on the beta list but quite a while ago, so no matter anyway.
Got the new beta today when I woke up. Thanks Jacob
Got the new beta today when I woke up. Thanks Jacob
- KVRian
- 508 posts since 8 Dec, 2004 from Belgrade
Do you guys have a problem that song created with liveslice become corrupted when trying to reload them? I'm using it in Tracktion and Podium (CM) lately, and the strange thing is that, somehow, waves from other sessions are loading in session you are working with right now. Podium says that plugin Liveslice is causing illegal operation... and no wavs are saved in song...
so strange
so strange
-
- KVRAF
- 10366 posts since 2 Sep, 2003 from Surrey, UK
v145 rc1 - here's my test report:
The following bugs have been fixed:
BR085 - Different MIDI Note Config in different hosts
BR084 - [Reset] sets wrong [D] value
BR083 - Events triggered by too many MIDI notes
BR082 - [H] mode setting affects inserted events
BR081 - Changing [H] scale to [Absolute] messes up [Autostretch]
BR080 - Open LS GUI uses up much CPU
BR079 - Slow arrows keys for selecting next/previous event
BR077 - Blocky graphics in Arranger
BR076 - Decreasing [A] does not increase [H]
BR067 - Changing Absolute scale changes parameter values
=========================================
I have seen a couple of new ones:
BR087 - When I Reverse an Event I get some has some initial graphics glitch
BR086 - When I change the Middle C MIDI number it is not saved when I return to the main LS page and then back to Settings, or when I click "Save all settings as default"
===========================================
For completeness there's just a few of my BRs that are outstanding:
BR078 - Zoomed-in scroll speed
When zoomed right-in, dragging the scroll bar to scroll is quick.
But at lower zoom levels (e.g. so that half the loop is displayed), there is a noticeable lag when dragging the scroll bar.
BR 052 - slices in middle of sounds
When doing automatic slicing using [Sensitivity], LS inserts slices in the middle of sounds and misses other slice points. Can the slice-detection algorithm be improved to avoid this?
- see the attached screenshot for some examples

Big pic:
http://img180.imageshack.us/img180/8885/br052byd0.png
BR 048 - wrong cursors - is back
I get the wrong cursor at various times, e.g. the text editing cursor is kept _after_ I have completed editing a loop name, or the double-headed arrow <-->-is kept after I had done some slicing and moved over the function buttons.
I've found out (by accident) how to get the wrong cursor at various times, e.g. the double-headed arrow. Overlay the LS GUI window with an energyXT MIDI Part, hover over the MIDI Part and move the mouse slowly onto the LS window - the mouse cursor will be "inherited" from energyXT.
BR 037 - 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.
Surely the new event should _always_ take its parameter values from the replaced event?
BR 032 - cancelling the [Autostretch] button
- [Autostretch] does not unhighlight when you [Clear] the track
BR 025 - [Play] still plays selected Arrangement even after Bank change
- select an Arrangement in Bank 1
- select [Bank 3]
- click [Play]
=> the "hidden" Arrangement in Bank 1 plays,
- in this circumstance, I think that perhaps, no arrangement should play.
BR 023 - Short folder name corrupts path display in Browser
One of the folder levels in the path to some loops is "FX". When I select this path in the browser, the path name displayed is corrupted.
I think it is because the folder name is only 2 characters (works Ok if I change the folder name to be 4 or more characters)
HTH
PS I've got "a few" FRs - would you like to see them soon?
The following bugs have been fixed:
BR085 - Different MIDI Note Config in different hosts
BR084 - [Reset] sets wrong [D] value
BR083 - Events triggered by too many MIDI notes
BR082 - [H] mode setting affects inserted events
BR081 - Changing [H] scale to [Absolute] messes up [Autostretch]
BR080 - Open LS GUI uses up much CPU
BR079 - Slow arrows keys for selecting next/previous event
BR077 - Blocky graphics in Arranger
BR076 - Decreasing [A] does not increase [H]
BR067 - Changing Absolute scale changes parameter values
=========================================
I have seen a couple of new ones:
BR087 - When I Reverse an Event I get some has some initial graphics glitch
BR086 - When I change the Middle C MIDI number it is not saved when I return to the main LS page and then back to Settings, or when I click "Save all settings as default"
===========================================
For completeness there's just a few of my BRs that are outstanding:
BR078 - Zoomed-in scroll speed
When zoomed right-in, dragging the scroll bar to scroll is quick.
But at lower zoom levels (e.g. so that half the loop is displayed), there is a noticeable lag when dragging the scroll bar.
BR 052 - slices in middle of sounds
When doing automatic slicing using [Sensitivity], LS inserts slices in the middle of sounds and misses other slice points. Can the slice-detection algorithm be improved to avoid this?
- see the attached screenshot for some examples

Big pic:
http://img180.imageshack.us/img180/8885/br052byd0.png
BR 048 - wrong cursors - is back
I get the wrong cursor at various times, e.g. the text editing cursor is kept _after_ I have completed editing a loop name, or the double-headed arrow <-->-is kept after I had done some slicing and moved over the function buttons.
I've found out (by accident) how to get the wrong cursor at various times, e.g. the double-headed arrow. Overlay the LS GUI window with an energyXT MIDI Part, hover over the MIDI Part and move the mouse slowly onto the LS window - the mouse cursor will be "inherited" from energyXT.
BR 037 - 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.
Surely the new event should _always_ take its parameter values from the replaced event?
BR 032 - cancelling the [Autostretch] button
- [Autostretch] does not unhighlight when you [Clear] the track
BR 025 - [Play] still plays selected Arrangement even after Bank change
- select an Arrangement in Bank 1
- select [Bank 3]
- click [Play]
=> the "hidden" Arrangement in Bank 1 plays,
- in this circumstance, I think that perhaps, no arrangement should play.
BR 023 - Short folder name corrupts path display in Browser
One of the folder levels in the path to some loops is "FX". When I select this path in the browser, the path name displayed is corrupted.
I think it is because the folder name is only 2 characters (works Ok if I change the folder name to be 4 or more characters)
HTH
PS I've got "a few" FRs - would you like to see them soon?
-
- KVRAF
- Topic Starter
- 1511 posts since 2 Jul, 2004
Thanks.kejkz wrote:Do you guys have a problem that song created with liveslice become corrupted when trying to reload them? I'm using it in Tracktion and Podium (CM) lately, and the strange thing is that, somehow, waves from other sessions are loading in session you are working with right now. Podium says that plugin Liveslice is causing illegal operation... and no wavs are saved in song...
so strange
There was a bug in the routine for saving the new parameters (Darkstars BR086) this can lead to crashes on rare occations. The bug has now been fixed.
http://www.livelab.dk - slice up your life
- KVRian
- 508 posts since 8 Dec, 2004 from Belgrade
No problem Ohm, i'm here to help
and there is another one, at least for here on my computer: Liveslice again skips slices in random manner. Sometimes it sounds cool, but.... I will try to repeat this in different hosts, it's maybe a Buzz "thing"...
Confirmed, like it's drawing a starting peak of next sliceDarkStar wrote:BR087
I see what you mean, but it's not so slow on my computer..DarkStar wrote:BR078
It seems that pauses in your loops are problem for liveslice, i have just tried detection on some classic drum loops, and all seems fine...DarkStar wrote:BR 052
hm, I can't reproduce this one...but then again, I don't use energy xtDarkStar wrote:BR 048
I think this is the way it works long time... you have to deselect parameter to change the slice without changing parameterDarkStar wrote:BR 037
Confirmed, and also doesen't unstretch or unpitch trackDarkStar wrote:BR 032
confirmed!DarkStar wrote:BR 025 - [Play] still plays selected Arrangement even after Bank change
Confirmed alsoDarkStar wrote:BR 023
and there is another one, at least for here on my computer: Liveslice again skips slices in random manner. Sometimes it sounds cool, but.... I will try to repeat this in different hosts, it's maybe a Buzz "thing"...
-
- KVRist
- 282 posts since 16 Mar, 2005
Hi,
Thanks Ohm for this nice update
(I haven't tested the previous BRs I reported, but I think that they have been fixed by you so far
)
Here are some BRs I noticed while playing with this new version:
[LiveSlice v145rc1]
BR1/ LiveSliceEffect doesn't monitor audio (tested with Live v6)
1- Load LiveSliceEffect on a track with audio playing on the track
Even if the 'mon' button is activated, I can't here any audio passing through LiveSliceEffect (however I can still record audio, even if I'm not not hearing what's being recorded)
BR2/ Once clicked, Autostretch button stays highlighted for all arrangements
1- LMB on Autostretch button
2- Select another Arrangement
The Autostretch button stays highlighted on all the other arrangements, although it is not actually active on these arrangements
I think that this bug can be the same one described by DarkStar's with his BR 032
1- Load a loop in LS
2- In the slicer, move the 'end marker' to the left
3- Click on 'crop'
The bpm is not being calculated again (unless I change the beats number)
BR4/ Inserting a new event on the end of a 'long event' doesn't overlap to the closest grid, but entirely replaces the 'long event'
Don't konw if this one is a bug or a change in behavior Ohm implemented?
In LS v1.44, when inserting a slice on the end of an existing event, the new slice was 'snapped' to the closest grid; on the latests versions of LS, the slice replaces the event.
I.E. With this new behavior, if you have an event which takes nearly all the track in size, you can't insert a new event on the half end of the long event- unless using CTRL+LMB, but in this case, the event isn't being snapped to the grid...
Personally I find the previous behavior more interesting
And you guys ?
Cheers,
GilJ.
Thanks Ohm for this nice update
Here are some BRs I noticed while playing with this new version:
[LiveSlice v145rc1]
BR1/ LiveSliceEffect doesn't monitor audio (tested with Live v6)
1- Load LiveSliceEffect on a track with audio playing on the track
BR2/ Once clicked, Autostretch button stays highlighted for all arrangements
1- LMB on Autostretch button
2- Select another Arrangement
I think that this bug can be the same one described by DarkStar's with his BR 032
BR3/ Bpm not being refreshed when croppingDarkStar wrote: BR 032 - cancelling the [Autostretch] button
- [Autostretch] does not unhighlight when you [Clear] the track
1- Load a loop in LS
2- In the slicer, move the 'end marker' to the left
3- Click on 'crop'
BR4/ Inserting a new event on the end of a 'long event' doesn't overlap to the closest grid, but entirely replaces the 'long event'
Don't konw if this one is a bug or a change in behavior Ohm implemented?
In LS v1.44, when inserting a slice on the end of an existing event, the new slice was 'snapped' to the closest grid; on the latests versions of LS, the slice replaces the event.
I.E. With this new behavior, if you have an event which takes nearly all the track in size, you can't insert a new event on the half end of the long event- unless using CTRL+LMB, but in this case, the event isn't being snapped to the grid...
Personally I find the previous behavior more interesting
And you guys ?
Cheers,
GilJ.
-
- KVRAF
- Topic Starter
- 1511 posts since 2 Jul, 2004
I got rid of Darkstars BR 023, BR 032 and BR 087 too. I'll look at BR 25 too, and then if no other bugs show up, I'll send out RC 2 
Edit: I wrote this before reading GilJ's post - i'll fix those bugs soon, and aim for a release of RC 2 around wednesday.
Edit: I wrote this before reading GilJ's post - i'll fix those bugs soon, and aim for a release of RC 2 around wednesday.
http://www.livelab.dk - slice up your life
-
- KVRAF
- 10366 posts since 2 Sep, 2003 from Surrey, UK
ohm, good work 
Take your time, Wednesday will be fine for me
Take your time, Wednesday will be fine for me
-
- KVRAF
- Topic Starter
- 1511 posts since 2 Jul, 2004
fixed GilJ's BR's 1,2 and 3. #4 coming up. It doesn't happen when using drag'n'drop so I never noticed (I always d'n'd), thanks.
http://www.livelab.dk - slice up your life
-
- KVRAF
- 10366 posts since 2 Sep, 2003 from Surrey, UK
-
- KVRAF
- Topic Starter
- 1511 posts since 2 Jul, 2004
just elmiinated GilJ's #4 and Darkstars 25 and 37. getting very close to a bugfree release. If only I could find an elegant solution to that "!¤" cursor issue. As far as I can see that's the only outstanding bug. Darkstarts BR52 and 78 are really feature requests in desguise: more efficient scrolling and better slice detection
they are still noted as such though, I have plenty of ideas for improving the slice detection, the strongest being implementing multi-band transient detection. Wait... I'll call it "psycho acoustic transient detection" and get a patent
that'll be good for business.
http://www.livelab.dk - slice up your life

