1.3 beta thread

[Maniah]

How about I keep the current "double mouse" to reset?

that wouldn't give me my 1 click
well, when i'm the only one thinking about that, do whatever is best for you to implement as other users don't seem to care. leave it like it's now, it's fine by me.

Actually, i'm with you one the one mouse click. Sorry Ohm......


Edit: actually, the double click wouldn't be so bad either just as long as no "keys" are utilized (like CNTRL etc.).

[kejkz]

I found a bug, or a "feature", i'm not shure. When you dont save wav to hd, Liveslice doesent save it inside itself. I don't recall that behaviour in previous version!
And yes,about reset, well, i don't mind using keyboard that much (and my midi contrloler also).

[ohm]

When you dont save wav to hd, Liveslice doesent save it inside itself.

I wouldn't call it a bug, but it's definately annoying to loose a recording on this account. I changed the behavior so that liveslice saves the data internally if it's not saved as a wave file already.
You have mail.

[Maniah]

so far so good using in Live 5.2.
I noticed though, i used the LS VST fx within Live, saved a .fxb file, opened up Energy XT and loaded the LS VST-i. When i tried to open the FXB file i saved within the VST fx version, it wouldn't work. I HAD to use the VST fx version to use that saved file.
It's no big deal really but i didn't know that it mattered.

[DarkStar]

Just to say that I'm am not keen on the double-mouse click (strictly one mouse hold and one click) - AFAIK it's not a common action and I am not that co-ordinated. I tried it here a few times and found myself automatically releasing the LMB when clicking the RMB.

It seems to me that now (or soon) would be a good time to pause for breath, have a look at all the actions available and re-define all the mouse and KB command combinations.

[R.A.W.]

It seems to me that now (or soon) would be a good time to pause for breath, have a look at all the actions available and re-define all the mouse and KB command combinations.

i think it's quite good organized right now, lmb is always used for inserting/setting, rmb is previewing, mmb/ctrl+rmb is clearing/deleting and so on.
that's why i thought of using mmb/ctrl+rmb for resetting envs, coz imo it is similar to clearing/deleting events as this also is some kind of resetting. (i can't help it, sorry )


i got a FR for the drag'n'drop (which is cool btw ): can you display a line on the drop position in the arranger track when we still hold lmb? that'll make navigation a lot better.
ideal would be, when snap is activated in the track that the line also snaps so we can see where the event is dropped if we would release the lmb on the current position.

[R.A.W.]

i just checked out the recording of audio and used only 4 beats for the slicer and recorded a 1 bar drumloop. sync and mix was not activated, but when i recorded longer than 1 bar, the input was added with every loop (resulting in very loud ond overdriven sounds).
i would expect it to do that only when mix is active and in the setting i used here that the buffer would be flushed when the end of the slicer is reached, overwrite insted of overdub?

[ohm]

Thanks for the good comments.

i used the LS VST fx within Live, saved a .fxb file, opened up Energy XT and loaded the LS VST-i. When i tried to open the FXB file i saved within the VST fx version, it wouldn't work.

The VST standard sets some limits there I'm afraid. In order to be able to use both the effect and intstuments versions they have to have different "ID's" at the same time though, in order to load a bank file it has to be saved with the same ID as the plugin I do have plans though to implement bank loading from within the LiveSlice browser, and then I can allow the effect version to load instrument banks and vice versa.

now (or soon) would be a good time to pause for breath, have a look at all the actions available and re-define all the mouse and KB command combinations

maybe, but as R.A.W points out they seem pretty consistent as they are. The problem is that the arranger has too many actions to get by without either using CTRL or define different actions sets depending on the envelope state.
With envelopes hidden the actions are as follows:
Left mouse click or left mouse drag: insert / replace event
Right mouse: preview
Middle mouse / CTRL + right mouse: delete or clear depending on where you click

Thinking about this again: perhaps middle mouse / ctrl + RMB can be envelope reset when envelopes are visible - I wouldn't really miss not being able to delete or clear events when I'm setting envelope params. I'm still worried though that it might be confusing for some users that mmb has two different actions, although clear and reset is almost the same action.

Darkstar: I'm very open to suggestions on improvememts in the mouse actions if you have concrete ideas. I noticed for instance that the new "double click to zoom / pan" is a bit awkward, but then again: I'd much rather use the mouse wheel / mouse pad to zoom anyways.

can you display a line on the drop position in the arranger track when we still hold lmb?

I could do that. I could even display the event as it would look when inserted (it's easier with a line though, and probably easier on the eyes)

[ohm]

i would expect it to do that only when mix is active and in the setting i used here that the buffer would be flushed when the end of the slicer is reached, overwrite insted of overdub?

hmm. I can see why you are confused. The mix actually means to blend the recording with the existing content of the loop (if you want to add a snare hit to an existing loop for instance). There is no way to set the recording to overwrite instead of overdub, other than using the "effect" button, but that does more than just do overwrite recording.
Any ideas how I can make the terminology clearer? I would like to have two buttons: one that toggles the recording mode (overwrite or mix) and another that toggles whether the recording replaces the current loop or is mixed with the current loop (this button is now called "mix" should I call it "replace" instead?)

[R.A.W.]

I would like to have two buttons: one that toggles the recording mode (overwrite or mix) and another that toggles whether the recording replaces the current loop or is mixed with the current loop (this button is now called "mix" should I call it "replace" instead?)

i don't think there need to be 2 buttons, it could be called "overdub" only. if activated it just mixes the current content with the new input and adds input as long as the recording is active (which with sync is only as long as the slicer isn't at the end).
when deactivated, it just clears the buffer when the recording starts respectively the slicer loops to the beginning again, regardless if sync is active or not.
you can still accomplish everything you want with that one button.

[ohm]

what if I wanted to record without overdubbing but still mix the recording with the existing content of the loop? Or record with overdub but replace the current content of the loop?
The latter can be acheived by deleting the loop prior to recording, but the first cannot (actually the effect button does that, so perhaps you are right). I'll reconsider - it would be nice to get by with one button, the less buttons the better IMO.

[R.A.W.]

what if I wanted to record without overdubbing but still mix the recording with the existing content of the loop?

as long as you want to mix a whole loop, that'd be accomplished by activating the sync, then it mixes the content but automatically stops at the slicer end.
when it's about single hits, you have to start/stop manually anyway, so just don't start/stop after the first recording.

[ohm]

hey - you are right, didn't think of that I just changed the behavior so it only overdubs when mix is activated to see how it worked, I'm sure I'll keep it that way. Thanks

[R.A.W.]

Thanks

you're welcome.

so far so good using in Live 5.2.
I noticed though, i used the LS VST fx within Live...

i just want to note that it's able to route audio to the instrument version in live as well, and it works perfect!

[Maniah]

Ohm,
I got that problem again with the MIDI configurations. It only happened once under Bidule and so far it hasn't happened again. It's weird, i'll go to the settings window and the paramaters do not respond to my LMB (only the paramaters that do not have a pull down menu). There's nothing wrong with my laptop's LMB as everything else that requires a LMB within LS works fine. If i delete LS and reload into my host, sometimes that will solve the problem, other times i have to restart my host. Today, i had to restart my host. I am using the latest beta version u sent.
I wish i could tell you more as to what might be causing the problem but again, it only happened once today and i thought i better mention it just in case.