1.4 beta and development thread

[DarkStar]

testing of v141 beta 1

BR - when copying text from the color text box on the setting page and then clicking in another app
All Ok here (copy and pasting to and from MS Word.

Spuddle's BR about GUI slowdown
- seems to be better
- but if I have2 LS open and move one of them around quickly, it is a bit jerky
- handling the short sample (8 KB) is better but still very weird

= == = = = = = = =
Also, for my earlier BRs

FR 01 -- done in v141 beta 1
in the Slicer, the selected slice is shaded blue (in the same way as events are shaded blue when you select them)

BR 01 - outstanding
Inserted Events jump around
Here's a way to reproduce it
- an 8-beat track, insert the same slice at beats 1, 3, 5, and 7
- change the pitches so you can distinguish them
- copy the all to a new track (ctrl+a works !)
- insert another slice at beat 2
- then click at beat 4, the new event jumps from beat 2 to beat 4
- then click at beat 6, the new event stays at beat 4, and one of the other events jumps to beat 6 (the significances is that this is the third click)

It looks like the "last touched" event remains linked to the mouse, then things start going wrong. THe link is a screen-shot showing what happens (hope it makes sense)


Big pic: http://img485.imageshack.us/img485/4758/lsjump6pz.png

BR 02 - partially fixed in v141 beta 1
Moving Event by LMB
In the Arranger, with Snap=16, for an event that is 2 or more 16ths long:
- with Snap on, if you LMB in the second 16th of the event, it will Snap to the second 16th position; I think it should just be selected.
- with Snap off, if you LMB in the second 16th of the event, it does not move, it is just selected; fixed in v141 beta 1

BR 03 locating slices- fixed in v141 beta 1

RAW BR 3 - not fixed in v141 beta 1
- dragging a slice to overwrite an event
- the dragged slice is placed at the position of the "last touched" event (or the last empty place where an event was deleted), not replacing the event at the current mouse position

RAW BR 5 - fixed in v141 beta 1
- when [locate] is on, and you select a parameter, [locate] is deactivated automatically


BR 013 (new)
- when you insert an Event it takes the parameters values of the preceding event.
- I think they should all be at their default values

BR 014 (new)- I loaded the same sample into v140 and v141 beta 1 and got different results. See below:


BIgger pic: http://img463.imageshack.us/img463/8915/lsclaves0tb.png

- and on playback the highlighting in the Arranger did not always get removed.

[GilJ]

BR 013 (new)
- when you insert an Event it takes the parameters values of the preceding event.
- I think they should all be at their default values

DarkStar, I think that the current behavior is not really a BR. It can be interesting in that, if you have programmed a complex sequence in a track, you can easily change the 'sound' of that track by replacing events and keeping the same parameters (volume, pitch, pan etc.)
Hence, you'll keep the same 'melody' on the track (a little bit like a workstation where you can, for the same sequence, change the instrument being played without changing the sequence)

Don't you agree with me?

[GilJ]

[LiveSlice v141b1]

BR1/ Event's white box display problem (Keyboard shortcuts)
1 - Load a loop
2 - Lock to loop
3 - Pitch up any event of the Track with LMB (I.E. +48 )
4 - Use the keyboard down arrow (shortcut) to pitch down the event
The track's display is not being updated completely : the horizontal pitch 'marker' is being updated, whereas the "white box" of the event doesn't get expanded again


BR2/ Event selection box display problem (Keyboard shortcuts)
1 - Load a loop
2 - Lock at the beginning of the track only 1 event
3 - Select the event in order for the event to be highlighten (LMB)
4 - Pitch down the event of the Track with LMB (I.E. -48 )
5 - Use the keyboard up arrow (shortcut) to pitch up the event
The selection box of the event is not being updated (however it's OK with LMB)

BR3/ Changing reverse parameter (Keyboard shortcuts)
Keyshortcuts Up/Down arrows don't change the reverse parameter (yes/no) for events (may be it's the way it's meant to be?)

BR4/ Changing colors (LiveSlice.ini)
1 - Delete LiveSlice.ini
2 - Load LiveSlice
3 - Change color Presets (I.E.Black)
4 - Close / Reopen LiveSlice (the color of LiveSlice is now Black)
5 - Change color Presets again (I.E.Red)
6 - Close / Reopen LiveSlice
The color is not being saved the second time: LiveSlice is still in Black. I must delete the LiveSlice.ini file in order to apply a new color Preset

[DarkStar]

BR 013 (new)
- when you insert an Event it takes the parameters values of the preceding event.
- I think they should all be at their default values

DarkStar, I think that the current behavior is not really a BR. It can be interesting in that, if you have programmed a complex sequence in a track, you can easily change the 'sound' of that track by replacing events and keeping the same parameters (volume, pitch, pan etc.)
Hence, you'll keep the same 'melody' on the track (a little bit like a workstation where you can, for the same sequence, change the instrument being played without changing the sequence)

Don't you agree with me?

Hmmm, perhaps. Interesting discussion.

Ok, on replacing an event, I can see that you migh want to keep the parameters, (but perhaps not volume or pitch).

But this also happens when I insert a new Event (say a kick) and the preceding event is, say, a cymbal crash. I can't see many times when I would want to adopt the parameters from the crash. ut thta's what happens at the moment.

[R.A.W.]

sorry, i'm ultra-busy at work so i won't have time for deeply testing before sunday.. but at least i'll comment on some BRs.

[LiveSlice v141b1]

BR1/ Event's white box display problem (Keyboard shortcuts)

confirmed

BR2/ Event selection box display problem (Keyboard shortcuts)

if you mean the grid doesn't come back (overlayed by the highlight) then it's confirmed.

BR3/ Changing reverse parameter (Keyboard shortcuts)

confirmed .. might be because it's the only env with just on/off instead of 128 values

BR4/ Changing colors (LiveSlice.ini)

i cannot reproduce this behaviour here, color schemes are saved just fine. perhaps there's something different in your file-permissions or something.

But this also happens when I insert a new Event (say a kick) and the preceding event is, say, a cymbal crash. I can't see many times when I would want to adopt the parameters from the crash. ut thta's what happens at the moment.

this behaviour was like this from day one iirc, so it wasn't introduced by the new version.
well, most times i find it quite handy that LS takes the last parameters for a new inserted event but i can see why you think different.


my first own new BR

when events are pitched up, i switch to another env and use RMB on the reset button in order to reset all parameters the white boxes don't get expanded again.

[ohm]

hi,
apologies if this is known (or intentional), but:

the rec panel hides the undo button.

fixed

[ohm]

Here's a few things [from v1.4.0]:

FR010 the "locate missing loops" window
- can the right hand end of the file name be shown in the window?
- currently it shows the start of the path, from C:\ . . . onwards

good idea. I now show the filename first and the full path after, so you can widen the window to see the full path.

FR011 "Volume parameter values"
- can the Volume parameter values be shown in -dB

done - values should be dB - SPL, verification would be great

FR012 Copy selected events to a track in a different Arrangement
- currently, Copy and Paste only works within an Arrangement.

I'll add that in 1.5

Q001 "Snap to zero crossing re-enabled"
- I am not too sure about this, when does it happen?
- Is it only when you use the Sensitivity control to slice a loop?

there was a bug in the zero snapping, thanks for pointing it out - it works much better now. I also changed the behavior of the slicer so that dragging is faster (precision by holding down CTRL)

BR010 Colour is always saved
- the current colour setting is always saved in the LiveSlice.ini file whne you close LS

I thought that was what you'd expect, but I can easily change it so that the color setting is only saved in the project until you hit "save settings as default" - this would allow you to use different colors for different projects - that might be handy, a dark liveslice for darke pieces and so on

BR011 Ctrl+right-click an event no longer works?
- Ctrl+right-clicking an event used to remove the slice but keeps the empty event
- this no longer works
is this by design or a BR?

that would be a bug - fixed

BR012 Selecting an Event moves it
Previously I reported

BR 02? moving Event by LMB
In the Arrange, with Snap on, if you LMB within an event, it Snaps to that position.
- I think this is a reasonable action.

- I now think that this is not the desired action.
- if the event is not quantized, then you cannot select it without it moving
- you should be able to click anywhere on an event to select it
- if you want to move it, just drag it

================================
Any thoughts?

I agree. I changed the behavior so that events only start moving when you drag them two or more pixels - so even if your hands are shaking after too much coffee events won't snap unless you want them to.

[ohm]

1.41 beta 1
The only minor thing i noticed is when altering the pitch in lock mode, only the 1st slice, along with the play locater, respond visually to a "+" pitch range (where they divide in color 1/2 light and 1/2 dark). If i alter each slice indivdually, they visually respond fine.

yep, that's a bit annoying - fixed

BR1: If I stop playback & then resume, only the page up/down keyboard shortcuts work. In order to have key shortcuts for the envelopes to work, I have to click on an envelope with the mouse .

fixed

BR2: Actually, not sure if this is a bug or if something changed but i can no longer toggle arrangements with the mouse. I can only toggle via MIDI.

what do you mean by "toggle with the mouse" ?

One FR: Is it possible to implement an EXT feature for the settings page where CNTRL/LMB (or whatever) activates a MIDI learn for CC/Note settings? This beats scrolling through notes/cc numbers

that is on my list

[ohm]

thanks again for a nice and easy to read summary

BR 01 - outstanding
Inserted Events jump around

BR 02 - partially fixed in v141 beta 1
Moving Event by LMB
In the Arranger, with Snap=16, for an event that is 2 or more 16ths long:
- with Snap on, if you LMB in the second 16th of the event, it will Snap to the second 16th position; I think it should just be selected.
- with Snap off, if you LMB in the second 16th of the event, it does not move, it is just selected; fixed in v141 beta 1

outstanding bug indeed now it's fixed

RAW BR 3 - not fixed in v141 beta 1
- dragging a slice to overwrite an event
- the dragged slice is placed at the position of the "last touched" event (or the last empty place where an event was deleted), not replacing the event at the current mouse position

fixed

BR 013 (new)
- when you insert an Event it takes the parameters values of the preceding event.
- I think they should all be at their default values

still reading the discussion, but I like it the way it is. I will on the other hand add a shortcut to reset all parameters of a single slice to their default values - now let me see... what is available ... CTRL + Middle mouse it is.

BR 014 (new)- I loaded the same sample into v140 and v141 beta 1 and got different results.

that's because I changed the handling of very small wave files. In 1.4 I tried matchine the current tempo even when it meant auto selecting a loop duration of 0.00016 beats ! that's what caused the odd behavior for small wave files and "lock to loop". Should be better now but I'm still working on handling small single hit samples better.

- and on playback the highlighting in the Arranger did not always get removed.

I've noticed that too. It happens only if the events are very very close - I'll see what I can do.

[spuddle]

Nice to see you working hard and getting stuff done Jacob!

[DarkStar]

Jacob
Great responses,
many thanks

[ohm]

Jacob
Great responses,
many thanks

heh, yeah I've been on a coding rampage tonight Taking a week off and going to Italy this saturday, so I'd very much like a bug-free LiveSlice before that.

Oh, and it would be great if you could keep an eye on the forum for me, in case someone has any urgent questions.

Hopefully I'll be through the next BR posts by tomorrow night, and that will be the final 1.41 beta.

[DarkStar]

Sounds like we'll be on a playing/slicing rampage for a week or so.

Have a great break in Italy.

[ohm]

[LiveSlice v141b1]

BR1/ Event's white box display problem (Keyboard shortcuts)
BR2/ Event selection box display problem (Keyboard shortcuts)
BR3/ Changing reverse parameter (Keyboard shortcuts)

fixed

BR4/ Changing colors (LiveSlice.ini)

couldn't reproduce either. Strange. In the next beta I'll change the behavior of the color changing so that settings are only saved to the ini file when you click "save settings as default", then please test this again.

now I better call it a night

[spuddle]

Dont forget to pass the beta along to me please! Would like to test the GUI slow down issue here on my system.