It's 2001 all over again with a much better computer. Something about that "Mu" school of do just clicks with me. Ideas happen effortlessly through play.
Many many thanks!
MU.LAB 2 Test B
-
- Hun #3
- 4265 posts since 25 Mar, 2002 from A quaint little village just south of Hamburg, Germany
BTW, thanks for this software Jo - I'm again lost in a creative nirvana building worlds from a handful of samples.
It's 2001 all over again with a much better computer. Something about that "Mu" school of do just clicks with me. Ideas happen effortlessly through play.
Many many thanks!
It's 2001 all over again with a much better computer. Something about that "Mu" school of do just clicks with me. Ideas happen effortlessly through play.
Many many thanks!
-
- KVRAF
- Topic Starter
- 13862 posts since 24 Jun, 2008 from Europe
-
- KVRAF
- Topic Starter
- 13862 posts since 24 Jun, 2008 from Europe
-
- Hun #3
- 4265 posts since 25 Mar, 2002 from A quaint little village just south of Hamburg, Germany
Hah! Here I was thinking it's maybe not really a bug at all.
Goes to show it's always better to talk about stuff...
Goes to show it's always better to talk about stuff...
-
- Hun #3
- 4265 posts since 25 Mar, 2002 from A quaint little village just south of Hamburg, Germany
Jo, here's a pretty big one!
I recorded a sequence and quantized the notes (1/16th). First note of the sequence is dropped. Unquantized sequenced plays ok, but obviously it's not quantized. Nudging offending note a little further into the sequence "fixes" this).
-Bizarre: Happens in all VST synths but in none of the MU.LAB synths.-
-Dropped note syndom persists after deleting the note and drawing a substitute.
Only copying the notes over to a new sequence fixes it.
-Sequences that are penciled to begin with don't suffer from this problem.
Also, I managed to crash MU.LAB, something which has become a rare occurence indeed! Could have been the synth though (audjoo helix):
http://www.fileden.com/files/2007/5/13/ ... txt%20.txt
I recorded a sequence and quantized the notes (1/16th). First note of the sequence is dropped. Unquantized sequenced plays ok, but obviously it's not quantized. Nudging offending note a little further into the sequence "fixes" this).
-Bizarre: Happens in all VST synths but in none of the MU.LAB synths.-
-Dropped note syndom persists after deleting the note and drawing a substitute.
Only copying the notes over to a new sequence fixes it.
-Sequences that are penciled to begin with don't suffer from this problem.
Also, I managed to crash MU.LAB, something which has become a rare occurence indeed! Could have been the synth though (audjoo helix):
http://www.fileden.com/files/2007/5/13/ ... txt%20.txt
-
- Hun #3
- 4265 posts since 25 Mar, 2002 from A quaint little village just south of Hamburg, Germany
Sampla/multisampla:
Wanted to create a loop multisample using locators.
I made a beat, mixed down to file, ."new session" to keep things tidy, re-import via sampla, "create locator" on sample level is broken (ie doesn't exist as an option, I only get "set locator" etc).
I quit MU.LAB, import the sample, go to the sample window, "create locator" works again.
Wanted to create a loop multisample using locators.
I made a beat, mixed down to file, ."new session" to keep things tidy, re-import via sampla, "create locator" on sample level is broken (ie doesn't exist as an option, I only get "set locator" etc).
I quit MU.LAB, import the sample, go to the sample window, "create locator" works again.
-
- KVRAF
- Topic Starter
- 13862 posts since 24 Jun, 2008 from Europe
I tried what you described but all fine here.Bonteburg wrote:I recorded a sequence and quantized the notes (1/16th). First note of the sequence is dropped. Unquantized sequenced plays ok, but obviously it's not quantized. Nudging offending note a little further into the sequence "fixes" this).
-Bizarre: Happens in all VST synths but in none of the MU.LAB synths.-
-Dropped note syndom persists after deleting the note and drawing a substitute.
Only copying the notes over to a new sequence fixes it.
-Sequences that are penciled to begin with don't suffer from this problem.
Could you please send the musession that demonstrates this problem.
Do you remember what you were doing at that moment?Also, I managed to crash MU.LAB, something which has become a rare occurence indeed! Could have been the synth though (audjoo helix):
http://www.fileden.com/files/2007/5/13/ ... txt%20.txt
Reading the crash info, it seems you had just clicked somewhere.
Is it repeatable?
-
- Hun #3
- 4265 posts since 25 Mar, 2002 from A quaint little village just south of Hamburg, Germany
Hey Jo!
I just quantized a sequence (Free Alpha VST), not a problem.
It didn't work in any VST a few hours ago. I haven't a clue what I / MU.LAB was doing right this time.
I'll look into this same time tomorrow - bedtime looms
I'll also try to repeat the crash.
I just quantized a sequence (Free Alpha VST), not a problem.
It didn't work in any VST a few hours ago. I haven't a clue what I / MU.LAB was doing right this time.
I'll look into this same time tomorrow - bedtime looms
I'll also try to repeat the crash.
-
- KVRAF
- Topic Starter
- 13862 posts since 24 Jun, 2008 from Europe
Oops, a bug.Bonteburg wrote:Sampla/multisampla:
Wanted to create a loop multisample using locators.
I made a beat, mixed down to file, ."new session" to keep things tidy, re-import via sampla, "create locator" on sample level is broken (ie doesn't exist as an option, I only get "set locator" etc).
I quit MU.LAB, import the sample, go to the sample window, "create locator" works again.
Most of the time "Create Locator" will be there, but sometimes it might not.
Indeed reloading the wave might bring the option back when it's not there.
Fixed in Test C.
Thanks!
-
- Hun #3
- 4265 posts since 25 Mar, 2002 from A quaint little village just south of Hamburg, Germany
I haven't a clue! 
it didn't work again just now (Cheeze machine drops first note).
My current guess is that you have to do exactly these things to get the bug:
1-record sequence
2-put recorded sequence on a muted track as a backup
3-copy / paste sequence
4-duplicate the pasted part and name it to "sequence xy quantize"
5-quantize notes "from the outside" ie, without opening the part
6-first note is dropped.
it didn't work again just now (Cheeze machine drops first note).
My current guess is that you have to do exactly these things to get the bug:
1-record sequence
2-put recorded sequence on a muted track as a backup
3-copy / paste sequence
4-duplicate the pasted part and name it to "sequence xy quantize"
5-quantize notes "from the outside" ie, without opening the part
6-first note is dropped.
-
- KVRAF
- Topic Starter
- 13862 posts since 24 Jun, 2008 from Europe
Tried that, all going fine here
Not that i don't believe you, but i can't yet repeat it here.
If the first note is dropped, then you save that session, then reload that session, then is the note still dropped?
If yes, then please send me that session so i can research what's wrong.
Thanks.
Not that i don't believe you, but i can't yet repeat it here.
If the first note is dropped, then you save that session, then reload that session, then is the note still dropped?
If yes, then please send me that session so i can research what's wrong.
Thanks.
-
- KVRist
- 146 posts since 28 May, 2005 from Brisbane, Australia
Here's a feature request. I was testing out the Piano Roll display of MIDI events.
I'm using a 1440x900 display setting. There are 7 (+)/(-) vertical zoom steps in Piano Roll display?
To my eyes, the very smallest value is way too small to be useful. Even removing the Rack Display only reveals the standard 88 keys (didn't count them....) with a lot of grey space unused above. If they expanded to fill the available window space with showing/removing Rack Display that would be cool.
The largest display is so large it shows only 2 keys!! I'm sure no one works like this. Would most drum programming need a good display much more than C1-C3? That would still look ok to use.
At present, the changes are too big in my useful range, so going one zoom click larger goes from C1-C6 to C1-C3 and a bit. This is a very big change in display of notes for 1 click IMHO.
Is it possible to have the 7 steps in Piano Roll size more in the useful range? Most of my MIDI files start about C1 for drums. Occasionally I'll go above C4 with keyboards. It would be nice to see them all at once without a lot of scrolling about.
Others might use a lot more notes I guess, but the extremes do seem very extreme. Does this make sense?
Would this affect people using older computers/monitors much? My guess is the larger sizes would become even more useless on those machines. So everyone would benefit from losing the largest 2 sizes, at least. Perhaps its useful to keep the whole tiny 88 keys for those who use cut/paste that way?
I'm using a 1440x900 display setting. There are 7 (+)/(-) vertical zoom steps in Piano Roll display?
To my eyes, the very smallest value is way too small to be useful. Even removing the Rack Display only reveals the standard 88 keys (didn't count them....) with a lot of grey space unused above. If they expanded to fill the available window space with showing/removing Rack Display that would be cool.
The largest display is so large it shows only 2 keys!! I'm sure no one works like this. Would most drum programming need a good display much more than C1-C3? That would still look ok to use.
At present, the changes are too big in my useful range, so going one zoom click larger goes from C1-C6 to C1-C3 and a bit. This is a very big change in display of notes for 1 click IMHO.
Is it possible to have the 7 steps in Piano Roll size more in the useful range? Most of my MIDI files start about C1 for drums. Occasionally I'll go above C4 with keyboards. It would be nice to see them all at once without a lot of scrolling about.
Others might use a lot more notes I guess, but the extremes do seem very extreme. Does this make sense?
Would this affect people using older computers/monitors much? My guess is the larger sizes would become even more useless on those machines. So everyone would benefit from losing the largest 2 sizes, at least. Perhaps its useful to keep the whole tiny 88 keys for those who use cut/paste that way?
iMac (21.5-inch, Late 2009), 3.06 GHz Intel Core 2 Duo, 8 GB RAM, OSX 10.12.6
-
- KVRAF
- Topic Starter
- 13862 posts since 24 Jun, 2008 from Europe
I see what you mean, and have done some tunings in Test C, for both Composer as Note Editor.
Anyway, what i don't understand is that if you don't like certain zoom ranges, then it's just a matter of not using them, right?
Anyway, what i don't understand is that if you don't like certain zoom ranges, then it's just a matter of not using them, right?
-
- KVRist
- 146 posts since 28 May, 2005 from Brisbane, Australia
Oh, what is there now is "good enough". A little optimization would make it a bit more "fantastic"!mutools wrote:I see what you mean, and have done some tunings in Test C, for both Composer as Note Editor.
Anyway, what i don't understand is that if you don't like certain zoom ranges, then it's just a matter of not using them, right?
What you have in Test C might be in the right direction.
iMac (21.5-inch, Late 2009), 3.06 GHz Intel Core 2 Duo, 8 GB RAM, OSX 10.12.6
-
- Hun #3
- 4265 posts since 25 Mar, 2002 from A quaint little village just south of Hamburg, Germany
I'm inclined to agree with toxicoh - I don't mind extreme zoom levels so much but MU.LAB seems to have the habit of going back to the less than comfortable ones as you move on during the creation of a song - may just be the way I use stuff though!
I will try to set up some repeatable examples of the dropped note syndrome for you tonight Jo!
I will try to set up some repeatable examples of the dropped note syndrome for you tonight Jo!