MU.LAB 2 Test C

[MuTools]

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

You'll be lucky...

Euh, how do you mean?

(not native english, so i may miss an obvious point)

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...

Can't find that K3 mixdown in it.

Thus the one with K3 playing the ramped ah sample with longer notes than before.

[pljones]

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

You'll be lucky...

Euh, how do you mean?
(not native english, so i may miss an obvious point)

Sorry, you do so well I forget!

I mean life is never that easy, is it! You'll see what I mean when you look at the K3RampLong file.

Can't find that K3 mixdown in it.

Nope, neither can I... try this:
http://www.drealm.info/mu.lab/K3RampLongs.7z
That really, really is short notes, then long notes, then repeat for four bars.

[eidenk]

Albeit I did not try it on a supported system, Windows ME actually, I have encountered one single problem with it only, I can't display vst plugins. I can load them, use them, change presets, but can't display their GUIs. No problem with the built-in effects and synth, and anything else for that matter apparently. Same problem exists on the non-beta version actually. Just in case you have five minutes sometimes for looking into it. Thanks.

[MuTools]

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

Thanks for the logs. There indeed seems to be a nasty bug somewhere.

At which exact point does it crash?

When the file browser is still open?
When you click another sample to preview?
When you click OK to load the selected sample?
Or ..?

Tried to find it myself but no luck yet.

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.

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).

What do you mean with reprogrammed: Deleted it and re-inserted it?

Of course, if you could make a musession that demonstrates this problem and send it to me, that could be very helpful.

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.

The reason is that MU.LAB uses a '32 bit float' for velocities.

But maybe it's confusing to show the decimals..?

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.

Indeed, when browsing for a sample, the sample automatically gets on the keyboard for previewing. When closing the file browser, the original sound gets back on the keyboard.

[MuTools]

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.

I think it's logical to add the new event at the end.

When loading a midi file, and a new midi file event is loaded, and then the event would come as the first event of all events on that time, then the event order of the midi file would be reversed, which could not be the intention.

But i know what you mean and it's a typical 'sequencer' issue, which is normally solved by setting the times a bit earlier for the events that must come first.

The fact that a new event is inserted last can still be used to sorten the events as you whish, i think. You just have to insert the first event first, which sounds ok, no?

But what about this idea: lets add a 'Priority' value to each event so that all events which are on the same time, are then sorted by priority.

The higher the priority value, the more it will be sorted 'in front' of all events on that same time.

Events with the same time AND the same priority will then continue to behave like now.

By default this priority value would be zero, but can be edited somewhere.
(event context menu i assume)

This would make it easier to handle this typical 'sorting' issue.

Still just an idea though.

[MuTools]

Try this:
http://www.drealm.info/mu.lab/K3RampLongs.7z
That really, really is short notes, then long notes, then repeat for four bars.

Woops, even more bizarre!!

And that's only with Kontakt in MU.LAB, right?

You wrote some time ago that you emailed NI about this. What did they reply?

[MuTools]

Albeit I did not try it on a supported system, Windows ME actually, I have encountered one single problem with it only, I can't display vst plugins. I can load them, use them, change presets, but can't display their GUIs. No problem with the built-in effects and synth, and anything else for that matter apparently. Same problem exists on the non-beta version actually. Just in case you have five minutes sometimes for looking into it. Thanks.

I'm sorry but Win ME is not supported anymore.

[eidenk]

Albeit I did not try it on a supported system, Windows ME actually, I have encountered one single problem with it only, I can't display vst plugins. I can load them, use them, change presets, but can't display their GUIs. No problem with the built-in effects and synth, and anything else for that matter apparently. Same problem exists on the non-beta version actually. Just in case you have five minutes sometimes for looking into it. Thanks.

I'm sorry but Win ME is not supported anymore.

OK thanks.

[The Kob]

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.

will do... may be a couple of days

[The Kob]

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.

or even just the ability to save a number of default racks?
ie. i always chorus Voc-one and compress Karnage...

could i just save those as a rack-choice?

[MachFront]

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.

or even just the ability to save a number of default racks?
ie. i always chorus Voc-one and compress Karnage...

could i just save those as a rack-choice?

Hmmm. Rack presets?!? That would be sweet!

[MuTools]

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.

or even just the ability to save a number of default racks?
ie. i always chorus Voc-one and compress Karnage...

could i just save those as a rack-choice?

Not yet per rack, but it's on the whishlist.

Related to this: Note that if you save a musession as New.musession in your mulab folder, that one is opened whenever you do "New".

[pljones]

And that's only with Kontakt in MU.LAB, right?
You wrote some time ago that you emailed NI about this. What did they reply?

Yes... Um, and now I dig out the mail archive, they said they'd fixed it..! I should have read my old notes first - sorry Jo! I'll re-raise with NI.

[Bonteburg]

At which exact point does it crash?

When the file browser is still open?
When you click another sample to preview?
When you click OK to load the selected sample?
Or ..?

As far as I remember it happens while the browser is open the second time you click on a sample but before you get the chance to click OK.
Instead of the prelisten there's the crash.

Tried to find it myself but no luck yet.

Yeah, I know, it seems to be rather an elusive bug. Pretty hard to pin it down, more so if you're a layman like moi...
Now it happens, now it don't.

[MuTools]

Bonte, if it happens again, please keep on sending me the details (=your last actions + crash report) as i assume there indeed is some bug there.

Hope we can localize and fix it!