i'm with ohm on the shift+lmb for permanently selecting slices, i'd rather see it not to be the default on lmb. now that drag'n'drop is implemented, it's fast enough to drag the same slice multiple times if you don't want to use shift+lmb.
1.35 Beta thread
-
- KVRian
- 1263 posts since 15 Jun, 2004 from hamburg
i checked out the beta today. seems to be rock solid and all reported bugs are fixed. you get my clearance 
i'm with ohm on the shift+lmb for permanently selecting slices, i'd rather see it not to be the default on lmb. now that drag'n'drop is implemented, it's fast enough to drag the same slice multiple times if you don't want to use shift+lmb.
i'm with ohm on the shift+lmb for permanently selecting slices, i'd rather see it not to be the default on lmb. now that drag'n'drop is implemented, it's fast enough to drag the same slice multiple times if you don't want to use shift+lmb.
-
- KVRian
- 540 posts since 31 Mar, 2005 from Tampere, Finland
Hi!
I didn't notice if anyone had reported this, but in VSTHost and energyXT at least (I only have those at home) when you right click a file multiple times in a row in _file browser_ to preview it, I get a crash. This does not happen if you've assigned the wav to loops already.
I didn't notice if anyone had reported this, but in VSTHost and energyXT at least (I only have those at home) when you right click a file multiple times in a row in _file browser_ to preview it, I get a crash. This does not happen if you've assigned the wav to loops already.
A guy with serious GAS and lots of unused VSTs. But if I someday need them...
-
- KVRian
- 1263 posts since 15 Jun, 2004 from hamburg
i can't confirm that.. i just tried to make it crash in eXT and previewed the same loop for about 1 minute while right-clicking it about 100 times and had no crash at all.DotNoir wrote:Hi!
I didn't notice if anyone had reported this, but in VSTHost and energyXT at least (I only have those at home) when you right click a file multiple times in a row in _file browser_ to preview it, I get a crash. This does not happen if you've assigned the wav to loops already.
but sometimes i got a glitchy loud peak as if the former played sample and the second triggered are mixed and clip badly for some milliseconds, perhaps that made your system crash. perhaps it's related to the loop you previewed or did it crash with several different samples?
-
- KVRian
- 540 posts since 31 Mar, 2005 from Tampere, Finland
I tried with four samples, they were on dvd and also on hdd. It was at home, didn't remember trying at studio where I have a better equipment. At home I only have an SB Live. I have no idea what might've caused the crash (I reproduced it on my machine for 7 time with 4 different samples)
A guy with serious GAS and lots of unused VSTs. But if I someday need them...
-
- KVRian
- 540 posts since 31 Mar, 2005 from Tampere, Finland
OK, now there's something weird... I can't reproduce this crash anymore. I have no idea what happened. Sorry for reporting, but it _did_ happen 
A guy with serious GAS and lots of unused VSTs. But if I someday need them...
-
- KVRAF
- 2202 posts since 16 Apr, 2004 from between my ears
actually there may be something here.DotNoir wrote:OK, now there's something weird... I can't reproduce this crash anymore. I have no idea what happened. Sorry for reporting, but it _did_ happen
when i tried with eXT (latest beta), it didn't crash, but it did lock up the audio L/R channel: mixer meter levels showed as overloaded, then no more signal.
upon trying to repeat, it overloaded just the right channel (in the stereo track), and the signal stopped on the right side, but continued on the left side.
this occurred with very fast right clicking to preview a loop.
fwiw.
-
- KVRAF
- Topic Starter
- 1511 posts since 2 Jul, 2004
Sounds like I need to take a closer look at the preview code - thanks for reporting this.
http://www.livelab.dk - slice up your life
-
- KVRAF
- Topic Starter
- 1511 posts since 2 Jul, 2004
I fixed a bug in the wave file preview code that is very likely to be responsible for the problems mentioned above. New beta soon.
http://www.livelab.dk - slice up your life
-
- KVRAF
- Topic Starter
- 1511 posts since 2 Jul, 2004
New beta out (beta 2):
- Fixed a bug in the wave file preview code
- Improved the track sequencer – please comment
- The background indicates the beats (whole notes)
- The grid is hidden if snap is de-activated
- The lines showing the start of each event is hidden if the grid is visible
- The grid is dimmed when drawn on top of an event
- The grid is always drawn with dotted lines
http://www.livelab.dk - slice up your life
-
- KVRAF
- 10366 posts since 2 Sep, 2003 from Surrey, UK
1.35 beta 2
- nice update, runs Ok here and the two-tone background colours are useful,
A couple of things that I noticed:
a) the note divisions for the triplets are not correct, e.g. 1/8T gives 4 notes in 3 beats, I reckon this should be 9 notes (3 per beat) - this is also in v130 (just checked). Or am I getting something wrong?
b) with Snap off, when I insert slices they are inserted at a position in front of where the mouse pointer is,
(Ohm, I have emailed you a screenshot of these)
Also (an FR?)
If a slice in the slice is selected (shift+LMB), and then a parameter is selected in the Arranger, dragging the mouse through the events does not set the parameter levels, instead it inserted the slice; perhaps the slice selection should be (temporarily) deselected when a parameter is clicked?
What does anyone think?
- nice update, runs Ok here and the two-tone background colours are useful,
A couple of things that I noticed:
a) the note divisions for the triplets are not correct, e.g. 1/8T gives 4 notes in 3 beats, I reckon this should be 9 notes (3 per beat) - this is also in v130 (just checked). Or am I getting something wrong?
b) with Snap off, when I insert slices they are inserted at a position in front of where the mouse pointer is,
(Ohm, I have emailed you a screenshot of these)
Also (an FR?)
If a slice in the slice is selected (shift+LMB), and then a parameter is selected in the Arranger, dragging the mouse through the events does not set the parameter levels, instead it inserted the slice; perhaps the slice selection should be (temporarily) deselected when a parameter is clicked?
What does anyone think?
-
- KVRAF
- 2202 posts since 16 Apr, 2004 from between my ears
i agree. parameter selection should terminate the current shift+LMB selection.DarkStar wrote:
Also (an FR?)
If a slice in the slice is selected (shift+LMB), and then a parameter is selected in the Arranger, dragging the mouse through the events does not set the parameter levels, instead it inserted the slice; perhaps the slice selection should be (temporarily) deselected when a parameter is clicked?
What does anyone think?
in fact, it seems that the only way to deselect the current selection when shift+LMB is used is to LMB a new slice and paste it into an arrangement.
or ?
-
- KVRAF
- 10366 posts since 2 Sep, 2003 from Surrey, UK
I just found out that Shift+LMB on the selected slice deselects it - but I am sure not to remember to do it when i want to change the paramters values.JamminFool wrote:in fact, it seems that the only way to deselect the current selection when shift+LMB is used is to LMB a new slice and paste it into an arrangement.
or ?
Another case for (at least) a single Undo, too.
-
- KVRAF
- 2202 posts since 16 Apr, 2004 from between my ears
oh. didn't know that. not that i would ever remember to do that either.
but i agree, UNDO wuld be most helpful in this and many other situations...
but i agree, UNDO wuld be most helpful in this and many other situations...
-
- KVRian
- 540 posts since 31 Mar, 2005 from Tampere, Finland
Another FR I have in mind is having an (optional?) confirmation of overwriting an already assingned loop (I mean, happened to me quite a few times that I was browsing for new samples and pushed LMB while having an old loop active, bye bye old loop). I had something else on my mind, but don't remember it now.
A guy with serious GAS and lots of unused VSTs. But if I someday need them...
-
- KVRian
- 1127 posts since 18 Mar, 2005
I can barely make out the grid. The lines are more white than blue. Same with the track deletion "x". Anyone else have this issue?
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
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.
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
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.
Give me freedom or give me television
