LiveSlice 1.12 released

[ohm]

This update mainly:

1) enables the save function

2) makes arranging much easier (check the manual)

3) fixes a number of bugs and glitches.

4) has an updated manual

new features:

• Grid is now drawn on top of events
• Events can be moved past their neighbours
• Events can no longer be hidden behind other events - use tracks for layering events
• When snap is activated, new events are inserted at the nearest available snap interval, without needing to hold down control.
• Tracks have "snap" activated as default
• Snap now moves back instead of moving to the closest interval
• Manual updated

bugfixes:

• save function enabled (was disabled by mistake)
• fixed problem with very rapid pan changes
• corrupted ini file crashing liveslice fixed
  "
• grouping slices" problem solved
• buggy graphics driver workaround (eliminates
• waveform artifacts on high zoom levels on some graphics cards)
• Hand cursor shown when you can move events only
• Midi parameter "toggle" status shown correctly
• minor gui glitches fixed
• tons of other minor fixes

I'll keep an updated "coming next" list on the website.

[DarkStar]

WooHoo!

[porpoise]

HI

It's nice to see this program being fine tweaked - probably best done while the code is fresh in the dev's mind!

Porpoise.

[GilJ]

Thanks for the 1.12 update Ohm

Just wanted to add some comments (& have your opinions) and … report some minor bugs

Comments on the new feature Events can no longer be hidden behind other events - use tracks for layering events:
I do agree 100% with the use tracks for layering events feature, but what seems a little bit confused to me, is that events can no longer be hidden behind other events:

It’s no longer possible to drag an event onto another event just to ‘see how the track would sound like’, because it deletes the latter. (And as the undo function has not been implemented yet, we can't roll back to the previous state )

What do you think about my following suggestion guys: maybe LiveSlice could manage events a little bit like in an audio track in Cubase for example.
IE When an event is on top of another one, it is only the visible event which is being played, whereas the background of the event changes its color, so you know that there is another event under the visible one

Bug Reports (some BRs are not new to the 1.12 version)
I've done my tests on the full version of LiveSlice:

BR1:
1- Launch Live Slice (with default settings)
2- Set Number of visible tracks to 1
3- Browse to C:\WINDOWS
4- Scroll down to the Media folder
5- Select the Media folder
The path is not shown anymore in the file browser, you need to refresh the latter to see the path back again (either by scrolling down & up again, or closing & opening the GUI back etc.)
-----------------------------------------------------

BR2:
1- Launch Live Slice (with default settings)
2- Select C:\WINDOWS\Media\tada.wav for example
3- In the Slicer: Set slices to 4
4- Lock to loop
5- In the Arranger: Select event #2 and bring it back towards event #1
Slice #1 automatically lengthens to stick to event #2
-----------------------------------------------------

BR3:
1- Launch Live Slice
2- MMB on any empty slot
2 slots are selected together
-----------------------------------------------------

BR4:
1- Launch Live Slice
2- In the Arranger: Create an empty track with only 1 empty event
3- Click on Play
4- LMB the empty event and move it anywhere through the track, drop it, move it back again etc.
Sometimes the vertical grids are full, sometimes stays dotted
-----------------------------------------------------

BR5:
1- Launch Live Slice
2- In the Arranger: RMB on Clear button for the first track
3- Click on settings button, then settings again to come back to the mail window
The first track is not displayed correctly (you need to 'refresh' the GUI for it to work)
-----------------------------------------------------

Has anyone been able to reproduce these BRs?

Thanks,
Gil.

[ohm]

Thanks for the report Gil, very easy to work with these precise descriptions.
I'll look into the BR's, they look like minor issues, but still I give any bug priority over new features.

When an event is on top of another one, it is only the visible event which is being played, whereas the background of the event changes its color, so you know that there is another event under the visible one

This sounds like a good way of doing things, even with undo avaiable non destructive editing is definately nice to have. I might implement undo first though, as it seems more urgent.

[DarkStar]

And a few from me - nothing drastic

BR01
- when you click [reset] it does not reset the random range to its initial value,
- I think it should

BR02
- I deleted a loop (say, X) from the loops section.
- I could not select that file (X) again from the browser to put it in another loop slot until I had clicked on another file (say, Y) in the browser (and therefore loaded that one).
- Then I could select the loop I wanted to reload (X).
- I hope that's clear.

BR03
- After you delete a loop, the number of slices does not reset to 16

BR04 - number of presets (seen in energyXT)
- when you look at the preset list for LiveSlice (in energyXT) you can see "default 1" to "default 65.
- I think that this should be "Arr 01 to "Arr 24" to select the 24 arrangements.

BR06 (5) -calculation of tempo
- I loaded a loop of 124518 frames at 85 bpm (4 beats)
- LS calculated this to be 4 beats but only 84 bpm
- can the BPM value have decimal places too?

[R.A.W.]

And a few from me - nothing drastic

BR01
- when you click [reset] it does not reset the random range to its initial value,
- I think it should

that's actually no bug and i dare to disagree.
e.g. i tend to set the left range of "probability" to a higher value and don't want it to be reset every time.
reset should just reset the envelope values.

BR03
- After you delete a loop, the number of slices does not reset to 16

i believe that's related to the function to use one loop and replace it while leaving the groove of the first loop, therefore i'd think of it more as a feature as a bug .
it could reset the slices to default on ctrl+rmb/mmb in the loops-list though, while keeping this function only when loading a new loop without clearing the slot first.

BR04 - number of presets (seen in energyXT)
- when you look at the preset list for LiveSlice (in energyXT) you can see "default 1" to "default 65.
- I think that this should be "Arr 01 to "Arr 24" to select the 24 arrangements.

confirmed in all my other hosts as well. i might add that if you pick an arrangement >24 from the hosts dropdown everything you do is also saved to arranger 1 as long as it's not used yet.

BR06 (5) -calculation of tempo
- I loaded a loop of 124518 frames at 85 bpm (4 beats)
- LS calculated this to be 4 beats but only 84 bpm
- can the BPM value have decimal places too?

it could be displayed with decimals for sure, but right now it seems as if the decimals are just cut.
assuming your samplerate was 44,1kHz the loop has exactly 84.99976 bpm - i think it would be enough if the bpm display in LS would just round mathematical correct instead of cutting the decimals.

[ohm]

thanks for the report.

After you delete a loop, the number of slices does not reset to 16

I agree that on deleting a loop the slices should be reset

BR04 - number of presets (seen in energyXT)

Wouldn't it be better if you could access those "hidden" arrangements from the gui also? I plan to increase the total number of arrangements to 72, I just want to wait until I implement some kind of
"record what you hear to a new arrangement" feature (v. 2 or so).
In the meantime I can make sure the host only sees the first 24

calculation of tempo

I will make sure the bpm is properly rounded.

BR02

yes, I noticed, this is annoying - will fix.

[DarkStar]

"hidden arrangements" ?
WooHoo, yes, please

On the 84/85 tempo - I think that the sample's tempo might be something like 84.8 or so. I loaded it into energyXT and had to make a fine tune adjustment to get it to fit into exactly 4 bars.

Could I suggest theat the BPM has 1 or 2 decimal places?

[ohm]

Could I suggest that the BPM has 1 or 2 decimal places?

I think one decimal is enough, but yes, that change can be implemented faster than writing this post so, I guess I should get on with it

[riley4reason]

I'm really impressed with the people in this thread.. This is like a Perfect World where people work together to solve problems and support each other.
I may buy Liveslice just be associated with such high caliber people.
Sincerely, Riley

[ohm]

I'm really impressed with the people in this thread

I'm really impressed myself - It's great to have active users that want to contribute their thoughts, ideas, demobanks / mp3's / command guides / skins for popular hosts, you name it And it helps encourage development - you may have noticed that my update rate is quite high

So please: Join the club - the indtroduction offer ends on monday

[riley4reason]

I'm really impressed with the people in this thread

I'm really impressed myself - It's great to have active users that want to contribute their thoughts, ideas, demobanks / mp3's / command guides / skins for popular hosts, you name it And it helps encourage development - you may have noticed that my update rate is quite high

So please: Join the club - the indtroduction offer ends on monday

Done! I'm a new owner! I won't have time to dig in until tomorrow morning but I'm really looking forward to it. I like the work done on the wav samples and the flash presentation was great.

Thanks! Riley