1.35 Beta thread

[ohm]

This thread is for discussion and stuff, related to the (closed) 1.35 beta.

edit: added list of new stuff:

• Spline interpolation = better quality when changing pitch.
• Improved tolerance for erroneous wav files
• display was not updated on end recording - fixed
• snap function now sets the pitch envelope value (within +- 1 octave), and is saved with the song
• freeze when randomizing two events bug fixed
• skipping slices in ACID fixed

[JamminFool]

so far the beta is working well for me. i will, of course, continue to use it and report any problems, if encountered.

in the meantime, i have some feature requests, if that's appropriate:

1) perhaps i'm missing something here, but why is SHIFT+selection necessary to place the same slice multiple times? shouldn't this be the default? right now, if i LMB in the arranger after LMB in the slicer, the slice is moved to the new location. why would i not use MOVE (LMB+drag) for this instead, if i want to try it in different positions?

so i would like this to be changed to: LMB in slicer to select slice. LMB in arranger to paste slice. repeated LMB in arranger continues to paste last slice. drop SHIFT+select in slicer, as not needed.

2) a value display for the current parameter in the arranger. this would make it easy to set parameters non-contiguous events to the same value.

3) UNDO. makes experimenting easier. and this tool is all about experimenting!

4) is there a way to clear an arrangement? i tried MMB and rather than clearing the arrangement, it selected it. in fact, this caused multiple arrangements to be selected. i thought at first that this would allow multiple arrangements to play at once, but not so. what exactly is the intent of multiple arangement selection?
<*EDIT*> never mind, see later post.

5) an option to allow sample directories to be searched deeper than 1 level of sub-directory. i have my loops organized in a sub-directory structure much deeper than 1 level. i would love to be able to point my LiveSlice Browser at the root of my loops folders and browse/search from there.

comments?

[rn99]

working rock solid in audio mulch so far (and also inside energyxt within mulch)...no more freezing when randomising 2 events...sound quality on altering pitch is very good - but if you are thinknig of increasing it further i agree it would be a good idea to make it an optional feature for those occasions when cpu/memory is tight...another feature i would like to see would be a multiplication of the maximum pitch range - something like a 2x, 4x checkbox to increase max range 2 or 4 fold. thiswould be particularly useful for granulation type fx...is there any possiblity that you could introduce an undo function?

[JamminFool]

4) is there a way to clear an arrangement? i tried MMB and rather than clearing the arrangement, it selected it. in fact, this caused multiple arrangements to be selected. i thought at first that this would allow multiple arrangements to play at once, but not so. what exactly is the intent of multiple arangement selection?

ok. never mind. i figured this out.

use the clear button at the top to clear single/multple arrangements.

[JamminFool]

has anyone tried LS in MiniHost?

a 16 slice loop in the arranger only appears to play slices 2-9 as it loops.

[Maniah]

working rock solid in audio mulch so far (and also inside energyxt within mulch)

I was afraid it may have something to do with my system. LS keeps crashing after about 5 minutes of use when using Ext SA (dec. 23 beta). I for the life of me cannot figure what's doing it but i have been having problems with XT lately. Chainer, Dr fusion and now LS crash. I'm getting my laptop back tomorrow or the next so i will try it there and see what happens using it within Live.

[JamminFool]

I was afraid it may have something to do with my system. LS keeps crashing after about 5 minutes of use when using Ext SA (dec. 23 beta). I for the life of me cannot figure what's doing it but i have been having problems with XT lately. Chainer, Dr fusion and now LS crash. I'm getting my laptop back tomorrow or the next so i will try it there and see what happens using it within Live.

hmmm...i just ran an arrangement for bout 20 minutes in eXT using the play button in LS w/o any problems.

are you using the play button, or triggering arrangements from a midi track in eXT?

is it a complex arrangement or a simple single loop?

does it do it with all loops or just a particular loop/arrangement?

[R.A.W.]

something like a 2x, 4x checkbox to increase max range 2 or 4 fold.

you should try RMB on the range-box - that switches between defaults of 2, 12, 24, 36 and 48 seminotes.. it's not what you asked for but comes close.

has anyone tried LS in MiniHost?

a 16 slice loop in the arranger only appears to play slices 2-9 as it loops.

that's a prob of minihost as it loops only 1 bar (and not accurate as it seems as sometimes it starts playing from the 2nd event ). it's not LS's fault.

[JamminFool]

has anyone tried LS in MiniHost?

a 16 slice loop in the arranger only appears to play slices 2-9 as it loops.

that's a prob of minihost as it loops only 1 bar (and not accurate as it seems as sometimes it starts playing from the 2nd event ). it's not LS's fault.

ok. so this is a known issue.
thanks R.A.W.

[R.A.W.]

ok. so this is a known issue.

hmm, yes, known by me - and now by you all
it was never officially listed in any way though, but i used minihost quite a lot for quickchecking plugs b4 i got eXT.. and that was when i discovered that problem and it only appears in minihost. and it is minihost's problem for sure as also other plugs with internal sequencers loop after one bar.

if you need a free little host for quickchecking i'd now recommend VSTHost or SAVIHost because of that issue in minihost.

[JamminFool]

man...we have to get tobybear to fix that.

i love minihost. i don't want to switch.

btw: i also use SONAR and eXT, but still love to use MH for quickchecks and just playing instruments in stand-alone mode.

[ohm]

Former Pharaoh: These crashes do they occur with 1.30 too or just with the beta? Please try starting a new project and load only LiveSlice, then see if it still crashes. Try both 1.3 and a.35 beta please.
Finally: zip and email me your liveslice.ini file, then back it up and delete it - this has been known to cure some crashes - it's important that you email the original .ini file to me first so I can prevent the problem from occuring again.

I'll comment on the FR's later - actually I'll comment on the FR's in a week, because I'll be away on a short vacation
You can continue discussing FR's without me though, then I can get a picture of what seems most urgent (undo I guess ?) - it's probably better to start a new thread for each FR, or each set of related FR's - to keep it simple.

[opia]

My credit card is kicking to come out and play with this one,but I have to wait until santa is paid up.

In the meantime I've been playing with the demo,which is great, except for that one little thing JamminFool mentioned

1) perhaps i'm missing something here, but why is SHIFT+selection necessary to place the same slice multiple times? shouldn't this be the default? right now, if i LMB in the arranger after LMB in the slicer, the slice is moved to the new location. why would i not use MOVE (LMB+drag) for this instead, if i want to try it in different positions?

I second that

[ohm]

why is SHIFT+selection necessary to place the same slice multiple times?

If you are using a mouse pad or a trackpoint (on a laptop) it's a bit inconvenient to drag stuff around, this is why I chose this implementation.
I can definately see your point though, so I'll try it out and see how it works. I'm worried about one thing though: some users may not have noticed that a slice is selected and be surprised that a slice is inserted when they try and manipulate the "pan" parameter.
The good thing about the SHIFT-LMB combo is that you don't hit it by accident.

[JamminFool]

why is SHIFT+selection necessary to place the same slice multiple times?

If you are using a mouse pad or a trackpoint (on a laptop) it's a bit inconvenient to drag stuff around, this is why I chose this implementation.
I can definately see your point though, so I'll try it out and see how it works. I'm worried about one thing though: some users may not have noticed that a slice is selected and be surprised that a slice is inserted when they try and manipulate the "pan" parameter.
The good thing about the SHIFT-LMB combo is that you don't hit it by accident.

good point. but that same problem exists now once you have used SHIFT+LMB (even if less prone to occur due to not being the default).

so it occurs to me that selecting a param button in the arranger (or clicking anywhere except on a slice in the slicer) should clear the current slice in the paste buffer (ie. denotes start of new action), regardless of whether SHIFT+LMB is used in the future.

UNDO should help with the case where you accidentally paste a slice...

just my initial thoughts.