1.35 Beta thread

[ohm]

Thanks for the comments and reports everyone - makes debugging so much easier.

the note divisions for the triplets are not correct

fixed

with Snap off, when I insert slices they are inserted at a position in front of where the mouse pointer is

fixed

parameter selection should terminate the current shift+LMB selection

I agree

I can barely make out the grid.

Made them darker

I'm a bit confused on the "snap" activate/de-activation.

Snap is activated by default - clicking the snap button will de-activate it. All LiveSlice buttons are blue when selected and white when they are not selected.

Also, when loading a file to the first empty loop slot, only the 1st two slices are visible in the slicer.
The issue with the LMB not working in the Midi Configurations Settings persists on both of my computers.

uh - I thought that was fixed long ago. I have "a few" questions that will help: How many instances of LiveSlice are you running? Does it happen with only one instance? Have you tried different hosts? Anybody else experience this?
Never heard about the hidden slices bug - can you email me a screenshot? Please include your system details as well - are you running a dual processor system perhaps?. Thanks.

[JamminFool]

playing around with LS in SONAR again, and i notice that the STOP button from SONAR is ignored in LS.

like if i have a midi track in SONAR triggering a slice in LS. when i push PLAY in SONAR, it plays as expected. however, when i push STOP in SONAR, LS keeps playing.

this works fine in eXT, so i'm guessing that SONAR doesn't send the standard message to indicate that the transport is stopped.

[Maniah]

uh - I thought that was fixed long ago. I have "a few" questions that will help: How many instances of LiveSlice are you running? Does it happen with only one instance? Have you tried different hosts? Anybody else experience this?
Never heard about the hidden slices bug - can you email me a screenshot? Please include your system details as well - are you running a dual processor system perhaps?. Thanks.

Just one instance of LS in latest beta of EXT. EXT is where I am coming across a lot of bugs. I tried in Live and it works fine. I also tried in the demo version of Orion Platinum and it works ok there as well.
I tried reproducing the missing slices upon loading on the 1st loop slot but it's not doing it anymore. Also, the grid is alot more prominent than it was when i first loaded the beta but it's good that you made it darker anyway cause they are still a little light.
So i guess that's all for now. If it happens again i'll be sure to take a snap of it.
As for the LMB not working in the MIdi Config settings, I seem to be the only one experiencing this so do you suppose it has something to do with my system?

My main computer for DAW recording is a Sony Vaio P4 2.8 with WinXP home SP1. It is configured strictly for audio. In fact, the only programs in it are Live 5.3, EXT (latest beta) and Bidule 0.9 (latest). All are licensed so there aren't any conflicts with "buggy" copies if you know what I mean.
I also do testing on my desktop which is a P4 2.4 Dell running XP Pro SP1. No dual processors. I have XT, and Bidule on this computer. Both experience the LMB issue.

[Maniah]

Snap is activated by default - clicking the snap button will de-activate it. All LiveSlice buttons are blue when selected and white when they are not selected.

Ok, so then it's backwards . With Snap activated by default, the grid does not show. When i De-activate it, the grid appears.

[R.A.W.]

I can barely make out the grid. The lines are more white than blue. [...]
I'm a bit confused on the "snap" activate/de-activation. If i press the snap button, i would assume that would activate Snap? Am i wrong with this? If I am right,The Grid should be visible when pressing the snap button but it's not visible. If I got this backwards then just let me know

what's changed now is that when snap is active you see the grid (dotted lines) instead of solid lines on the event-starts. so it's just right like it is now, we only have to get used to it.
tbh i'd prefer some kind of visual sign of event starts also when snap is active.

Same with the track deletion "x". Anyone else have this issue?

nothing changed here - it's like in all versions before.

Also, when loading a file to the first empty loop slot, only the 1st two slices are visible in the slicer.

i can't reproduce. is it with all your loops or just some? my testloops all loaded fine.

The issue with the LMB not working in the Midi Configurations Settings persists on both of my computers.

can you repeat what the problem was? as far as i can see everything works just fine here.


i just noticed something:
perhaps you know the situation, you click and hold the "X" of a window, then suddenly realize you don't want to close the window and drag the pointer out of the button range and then release the mouse.. the window stays up and you can continue to work in the program.
i thought the track's "X" would work like that but it doesn't.. i just had the situation, i wanted to delete the track at first, then had second thoughts and wanted to tweak more but already clicked the X but was still holding it. when i moved pointer outside the box the track still was removed though i didn't release the lmb before.

[R.A.W.]

Snap is activated by default - clicking the snap button will de-activate it. All LiveSlice buttons are blue when selected and white when they are not selected.

Ok, so then it's backwards . With Snap activated by default, the grid does not show. When i De-activate it, the grid appears.

nope.. read above, the grid makes the solid event-start-lines disappear in the latest beta, but with snap active the grid IS shown.

btw. i use eXT now for all my quick-checks of the betas and never had that much issues with it.. if it was only one of your systems i would blame them, but as you get problems on two of your computers i'm clueless.

[Maniah]

nope.. read above, the grid makes the solid event-start-lines disappear in the latest beta, but with snap active the grid IS shown. Wink

Right I know, I am reporting a bug. I sent an email to Jacob showing that with Snap activated, no lines are displaying (at least for me they aren't) But when i DE-ACTIVATE snap, they do show. It's backwards

nothing changed here Wink - it's like in all versions before

I'm refering to their prominence. They look the same but i could barely see them. Same with the scroll bar in the arranger. It's better now then when i first tested it but it still appears less prominent.

can you repeat what the problem was? as far as i can see everything works just fine here.

When attempting to make settings in the MIdi Configurations, the paramaters do not respond to my LMB. This happens sporadically but often.

i just noticed something:
perhaps you know the situation, you click and hold the "X" of a window, then suddenly realize you don't want to close the window and drag the pointer out of the button range and then release the mouse.. the window stays up and you can continue to work in the program.
i thought the track's "X" would work like that but it doesn't.. i just had the situation, i wanted to delete the track at first, then had second thoughts and wanted to tweak more but already clicked the X but was still holding it. when i moved pointer outside the box the track still was removed though i didn't release the lmb before.

I can confirm this for any track below the first track. The first track works like how you would expect it but the subsequent tracks delete regardless if you move the pointer out of the way while still holding the LMB.

[R.A.W.]

the first track can't be removed at all (it's not a bug, it's a feature ), that's why it reacts different.

btw i get a feeling that you have something special set up in your systems that gives you those probs noone else seems to have.. the only thing i can think of right now are the regional or language settings or something else that might differ from most users but which you use on both machines. perhaps a process running in the background like some special helper tool might cause this.

[DarkStar]

re: the first track:
- you can delete it if there is another track below it,
- if it is the only track you cannot,
- if you have >1 track , click the [x] on the first track and drag the mouse pointer off it, it will be deleted.

I have not seen the "parameters fail to respond to LMB" here - in eXT or Tracktion

[kejkz]

Hi to all in the thread!

I just tried to reproduce bug with snap, but I don't see it as a bug. When you deactivate snap, you see the slices starts, and not dotted grid. It's perfect from my standpoint: when you want snapping, you see grid, when you want shuffling, you need starting points of slices. Maybe Jacob can make solid lines instead of dotted when snap is on, and dotted when snap is of. Maybe in other color (darker)too.
What do you people think about color themes for Liveslice? Maybe that way we can avoid coloring problems.

[ohm]

I fixed the delete button behavior so it works as a standard windows button - ie. if you release the mouse button outside the button area, nothing happens.

I will continue the grid color experiments a bit to see if I can find any way of showing both grid and event start lines simultaniously without creating a mess. Before you really couldn't tell them apart so it was hard to see what was grid and what was events.

[DarkStar]

Hmm, I like it how it is now, almost:
- the snap grid is always dotted,
- when snap is off the event start is shown by a thin darker blue line,
- but when snap is on this line disappears, perhaps it should remain even when snap is on
- when you mouse over an event the start changes to a thicker dark blue line with Snap on or off.


As another idea:
show the start positions of the events by a small triangle at the top of the grid (as done in the Slicer). These would not change the waveform colours or the white areas.

Finally, re the overall colour:
It is (fairly) easy to have Hue, Sat and Lum contols to affect all the areas that are blue. Three controls in total (like in SampleTank2).

[ohm]

Thanks Darkstar - as usual your ideas are good, well explained and well thought out

- I've made the grid lines on whole beats solid
- I've stopped making the line thicker on mouse over (more accurate)
- I've tried to things to enable the event start lines to be visible at all times:
a) Draw them using a darker line (steals focus)
b) Draw the little triangles only, and then draw a thin line on mouse over

I like the b) solution better as it can look real messy with both grid lines and start lines at the same time.

I'll take a look at the midi assign box bug and then send out a new beta.

re the overall color: Yes, it's actually fairly simple with the current implementation to change the basic color, and then have LiveSlice re-calculate all the gradients.

[M'Snah]

My problem with loading too many loops has been solved now, I tried with different loops in 20+ slots, and all worked fine, incl. the preview.

The checkbox to include audio files in the (eXT-) project still can only be switched on, not switched off - the audio remains captured in the project file after it has been switched on once. However this is not really an issue for me, I'll just stay away from that checkbox.

When I had the slots filled with loops and closed and opened LiveSlice, re-opening still had the issue I mentioned earlier: First a small white/grey square is displayed, I assume during the initialisation of the loops or something, after that the display of LiveSlice is normal. (This is also not really a problem).

[ohm]

When I had the slots filled with loops and closed and opened LiveSlice, re-opening still had the issue I mentioned earlier: First a small white/grey square is displayed, I assume during the initialisation of the loops or something

Thanks, It looks like the coloured waveforms are initialized every time you re-open the gui. Completely unnecessary waste of system ressources and it looks silly. I've fixed this now.

The checkbox to include audio files in the (eXT-) project still can only be switched on, not switched off

You are right - there was a problem I overlooked - fixed.