MU.LAB 2 Test C

Official support for: mutools.com
Post Reply New Topic
RELATED
PRODUCTS

Post

pljones wrote:The notes start at the right point, with the correct attack, hold, decay and sustain (if they get that far) and release - except they seem to get shortened.
Indeed the envelope itself seems right as you clearly see the attack section.

But what i meant was: i would like to check where in the sample Kontakt starts playing.

This is impossible to hear like the sample is now. But if we would apply a pitch ramp to the sample and mixdown with that version, it would be more clear where in the sample Kontakt starts playing.

I've applied such pitch ramp and you can get the resulting "Ah" sample here:

http://www.mutools.com/mulab/test20/AhS ... Ramped.wav

Could you please make a mixdown with this one and publish the result.

Thanks.
Top

Post

Curiouser and curiouser...
http://www.drealm.info/mu.lab/Ah2Ramp.7z (MuSession, hopefully with everything embedded)
http://www.drealm.info/mu.lab/pitchramp_a.nkm (in case the NKM doesn't survive)
http://www.drealm.info/mu.lab/Ah2Ramp-mixdowns.7z

The Sampla mixdown seems fine. The others are just weird... It plays just about okay when not rendering... but I did hear a glitch once. Could just have been a CPU spike...
Top

Post

FYI: In the last session you sent, there is a difference in octaves between Sampla and Kontakt.

Anyway, quick question: if you double the note lengths, then does the lengths in the mixdown follow relatively?
Top

Post

hi
just started music again after a long break, and after struggling with CuBase (too bloody awkward) and Psycle (unstable, and eventually failed to load) i am loving MuTools!! I have a couple of basic questions that i'll ask eslewhere but...
i have managed to crash the test-c version by dropping a note outside of the window (thinking it would just delete it!)
also
compared with the previous version it is a shame that you get the full vst list rather than the scanned and sorted list you get in ver 1.1. Will you be reinstating this?

cheers :)
wee have also sound-houses
Top

Post

Hi Jo :D

It is nice to see that V2 is finally here but i haven't had a chance to look at it until today.

While i was playing with it i noticed that there where still no Multicore support which i see as a very important feature these days :D

So when will Mulab get it?

Except for that i really like what i see and i really like the new improvements so far :tu:
Top

Post

The Kob wrote:hi
just started music again after a long break, and after struggling with CuBase (too bloody awkward) and Psycle (unstable, and eventually failed to load) i am loving MuTools!! I have a couple of basic questions that i'll ask eslewhere but...
i have managed to crash the test-c version by dropping a note outside of the window (thinking it would just delete it!)
Will research this.
also compared with the previous version it is a shame that you get the full vst list rather than the scanned and sorted list you get in ver 1.1. Will you be reinstating this?
I'm not sure if i understand.

Can you please send screenshots that illustrate what you mean.
Top

Post

D-Fusion wrote:While i was playing with it i noticed that there where still no Multicore support which i see as a very important feature these days :D

So when will Mulab get it?
As soon as possible.

Can't be more specific at the moment.

Optimizing/spreading cpu load is high on the whishlist though.
Top

Post

It would be good if, in the VST Plugin Manager, you could crtl-select and shift-select several plugins and put them in the same group at once.

In Vista, opening a MU.Lab session that was saved with the window maximized opens a stretched, but non-maximized window. This is not happening in winXP since Test C.
Top

Post

Branis wrote:It would be good if, in the VST Plugin Manager, you could crtl-select and shift-select several plugins and put them in the same group at once.
Added on the whishlist.
In Vista, opening a MU.Lab session that was saved with the window maximized opens a stretched, but non-maximized window. This is not happening in winXP since Test C.
Could you please post a screenshot illustrating this?
Top

Post

mutools wrote:Could you please post a screenshot illustrating this?
Sure :)

Image
Top

Post

Mmm, i'm still not yet sure if i understand the very prob.

But i should probably just try it on a vista machine, which i don't have in the neighbourhood...

Anyway, just fyi, note that the main window size is not remembered per session but per installation.
Top

Post

When you close Mulab with a maximized window it should open with a maximized window, right?
As you see from the screenshot (it's a full size screenshot, my monitor resolution is 1280x800px) Mulab isn't maximized, it's even a bit out of the desktop. It seems that the window size is right (1280x800 if you include the frame), it's just not maximized.
I tried this on winXP where Mulab opens fully maximized.
Top

Post

mutools wrote:Anyway, quick question: if you double the note lengths, then does the lengths in the mixdown follow relatively?
You'll be lucky...

http://www.drealm.info/mu.lab/RampLongs.7z (6MB)
Contents - the session, the nki and nkm files, plus mixdowns for Sampla and K3. If you look at the K3 mixdown waveform, it's just... plain weird. The first section, with the short notes, has more signal than the second section...

I was going to suggest turning note tracking off to see if it's note number related at all... but I can't see any pattern in what's there, so I can't imagine one appearing...
Top

Post

Evening!

The return of the Multisampla crash on opening a sample:

http://www.fileden.com/files/2007/5/13/ ... sampla.txt

http://www.fileden.com/files/2007/5/13/ ... pla_02.txt

My theory is that it happens when you choose the second file browsing a folder you haven't opened before. Needless to say it's little more than guesswork but maybe it's helpful. In both cases I had created 9 empty velocity layers before and it happened on setting up the second layer.
I tried to test my theory and sure enough, it didn't crash. Elusive little bastard!

---

I also noted a silent note on playing back a drumbeat when I had finished my kit. I couldn't find any gaps in my velocity layers (the ever popular reason) so I checked the list editor and aparently notes in MU.LAB can potentially have weird velocites with decimal points.

I'm not a MIDI expert but I hardly think this is necessary in the 0-127 system? If there's a good reason for it, ignore me. :D

It just strikes me as a likely cause for my silent note (oddly, it played OK once I had reprogrammed it to the same weird value in the list editor).

---

I also think I solved my "problem" with the keyboard that wouldn't play when creating a multisample - it simply doesn't play the multisample as you're browsing for samples. Consider it fixed. ;)
Intel Mac Mini
OSX 10.4.11

Marco :)
Top

Post

MuLab Beta 2.0C - Windows XP

When using the List Editor to edit a Midi part I would suggest a change to the way that MuLab inserts a new Event. If there are several events with the exact same time, MuLab inserts the new event at the end of all the events that have the same exact time. In imported Midi files, there are often a number of initialization events that are placed at the exact same time. When trying to re-arrange some events, particularly Bank select and Program Change events, you must change all of the surrounding event times to different event times in order to arrange events in order.

I would recommend that when editing list events, that the insert function just place the new event in front of the selected event and assign the exact time of the selected event as a default.

This practice is more intuitive and parallels similar insert functions found in other list editors.
Image
Top
Post Reply

Return to “MuTools”