MU.LAB 2 Test C

[MuTools]

1)
Big one: Multisampla doesn't remember loop points in a saved patch even though they're still there! I haven't a clue if this is a new bug or if I just stumbled on it tonight.
I saved a sliced drumloop and made a patch called "cool beat" out of it. Upon the next startup it loaded everything just fine, except it tells every key to start from "Start" and play to "Sample End" instead of "Start - 2", "2 -3" etc.

Can't repeat it here, saving multisamples works fine as well in musessions as in separate patch files.

Is it repeatable on your system? If yes, can you please give a step by step. Thanks.

I had some weirdness with "note stealing" connecting a "multi sample player" to an ADSR envelope in MUX (again with a sliced loop). overlapping two notes a little will bizarrely mute the first note in a kind of faux mono mode.

I still don't really "get" all the ADSR settings, let alone routing in MUX, so it may just be my thick head.

If it comes back, and you think it's a bug, then please let me know.

I also caused a crash in MUX couldn't repeat yet:
http://www.fileden.com/files/2007/5/13/ ... .crash.log

Thanks. Will research!

Whenever you got another crash, please send the crashlog, and include what you were doing at that time, as that's also important info.

[MuTools]

I'm having crash problems with MDA's E-Piano. Would have blamed it on the instrument but it never played up until Test C (possibly even Test C 2).

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

I DID download some new VSTs today (kunz.corrupt.ch), all of which work fine though. But that would be about the only thing I could have been doing to cchange the way MU.LAB behaves.

I can't check mda piano myself as i have an intel mac, and it's ppc only as far as i know

[MuTools]

opening the "choose program" window on a synth/effect could potentially get you in a dangerous situation because sometimes the window is tall enough for the little close-window thingy to be offscreen.

Ok, finetuned this a bit in Test D.

Want to add that i just don't get why osx does not offer any way to move the window in such case

You're pretty much left with clicking OK (ie choosing a program) when you may have decided that you don't want to open a program at all but stay with what sound you've tweaked yourself.
Maybe we could have a "cancel" button next to "OK".

When you click a program, you tell the vst plugin to change its program, and so it depends from vst plugin to vst plugin whether it will 'cancel' any previous edits or not.

So to add a 'Cancel' button would not be an option, a 'Close' or 'Done' button is, but in fact it's not different from 'OK', functional wise.

Anyway, the height issue is finetuned in Test D.

And you could also press Return or Escape to close that window.

[Bonteburg]

Hi Jo!

The multisampla problem is entirely repeatable here:

http://www.fileden.com/files/2007/5/13/ ... at.MuSynth

http://www.fileden.com/files/2007/5/13/ ... .MuSession

http://www.fileden.com/files/2007/5/13/ ... 20Loop.wav

http://www.fileden.com/files/2007/5/13/ ... /PATHS.TXT

Everything is saved OK with the session file but as soon as I click the name of my saved multisampla instrument in the white panel to the left, all the loop data is lost (ie sample plays from start instead of a locator).

>>>>Edit:
Jo, this is big news!
Opening the patch via the yellow folder thingies works fine! It's clicking on the white panel with the list of patches that does it.<<<<

----
Re: MDA E-Piano. I have a 2007 Mac Mini so I think I have a, intel Mac too? Anyway, E-piano hasn't crashed since. It's apparently rather a special bug. Nothing to lose sleep over I guess.


----
Thanks for the "esc" tip! (Closing window situation). Works very well!


Marco

[MuTools]

unless there is a hot-key for "split" you have to drop down a right-click menu to use this function.

Indeed, but it only takes 2 clicks to split a part, no modifiers or tool switching needed anymore!

But i do agree that a hot-key would be very nice too.

An advanced hot-key system is high on the whishlist, and in the making

Also the eraser tool is gone. While I personally rarely ever used the eraser tool, is there a different way to use this function?

Sure: If you want to delete a couple of parts, lasso select them and press [Delete] (or [Backspace])

The loop point are great. I love being able to drag them around instead of making a selection that was kind of quirky to operate. For instance - I was never able to trim my loop selection on either end. I had to reselect from the beginning of where I wanted the loop area to start. BIG IMPROVEMENT!

Glad you like it

Note that you can now also create as many locators as you want in the Composer!

These can be used to mark the 'Verse 1', 'Chorus', 'Break' etc... in your Composition.

And of course, Rewind and Forward jumping include these locator positions.

[MuTools]

I found that when I change a MIDI-sequence part's start point and hit undo, then the part start goes to the origin instead of where it was before - hitting redo doesn't help!:o - This behaviour doesn't occur on changing the part's length.

True, a bug, will be fixed, thanks!

[MuTools]

The multisampla problem is entirely repeatable here.

Everything is saved OK with the session file but as soon as I click the name of my saved multisampla instrument in the white panel to the left, all the loop data is lost (ie sample plays from start instead of a locator).

>>>>Edit:
Opening the patch via the yellow folder thingies works fine! It's clicking on the white panel with the list of patches that does it.<<<<

Ah, found the very problem:

It's when choosing such patch for the second time.

It has to do with the fact that MU.LAB tries to avoid to load the same sample multiple times into RAM.

Loading bug which will be fixed!

Thanks for reporting this.

Re: MDA E-Piano. I have a 2007 Mac Mini so I think I have a, intel Mac too?

See Apple menu -> About This Mac -> Processor

Anyway, E-piano hasn't crashed since. It's apparently rather a special bug. Nothing to lose sleep over I guess.

Ok, lets keep an eye on it.

[Bonteburg]

"1.66 GHz Intel Core Duo" but as you say, let's keep an eye on it. It doesn't seem to be a very big thing...

[Bonteburg]

I was able to recreate the MUX note-stealing situation:

http://www.fileden.com/files/2007/5/13/ ... .MuSession

The second sequence recreates what you'd do trying out a multisample as you create it - you play it but but with pretty loose timing.

When two notes overlap the second note seems to be cut off just when you release the first one, creating the voice stealing effect.

These are my first attempts to actually do something with MUX. It's entirely possible that I made a routing mistake or tweaked a few knobs the wrong way in the ADSR module.

I was going for a short release time and a no-frills "as-long-as-you-hold-it-down" decay.

[MuTools]

Thanks for the musession, makes it clear.

In fact everything is playing normal.

You have to understand that the MUX is an effect unit, not a synthesizer, which means it's not working with 'voices'.

So if you add an ADSR envelope in the MUX, all notes go to that 1 ADSR envelope.

If it would be a synth, then each note creates a new voice, and so each ADSR would follow its own note, so to say.

But so now in this case, all notes go to that 1 ADSR envelope, which means that any note on will retrigger the envelope, and any note off will push it into release stage, which explains what you're hearing.

I was going for a short release time and a no-frills "as-long-as-you-hold-it-down" decay

Just open the MultiSampla editor, click the Amplifier 'Env' tab, put the release down.

By default Sampla and MultiSampla use a release time of +- 1.2 seconds, which was a musical idea.

But have been chatting already about this and i think it's better to have a 'normal' default release time of +- 1 ms i.e. immediate stop without audio click.

[Bonteburg]

Ah... I was half expecting it was normal behavior! Thanks for clearing it up.

[MuTools]

Want to add that it is very OK to add an ADSR in the MUX, cfr the "Note-Gater" patch in the Mux Library.

It's just that there is a difference between using an ADSR in the Mux and using one in the MuSynth between voice in and out.

Cheers

[pljones]

Strange, in the musession you sent, the a.wav file is empty

The original sample was on another disk in another folder - I guess the reference to that didn't point anywhere useful on your system . I thought it might be handy to include the file in the archive, in case it was needed.

I'm can't repeat it here, mixdown works normal here.
That is with the K3 demo, as i don't have K2.

I'll grab the K3 demo...

What happens if you just plug in another vst in that project and do mixodwn?

Does it mixdown properly? If yes, i think it's a K2 issue.

Do you mean in addition to K2, playing another part? (I think I tried that previously and it made no difference but I'll try it again.)

[MuTools]

Do you mean in addition to K2, playing another part? (I think I tried that previously and it made no difference but I'll try it again.)

I mean instead of K2.

So:

Situation: Sequence X plays K2 -> Some mixdown problem

Then:

-> Plug in e.g. CM-101 in a new rack
-> Route sequence X to the new rack
-> Mixdown the part

Still the same mixdown problem?

If yes, then please save and send the musession to me, then i can try again to analyze the issue using the CM-101 which i also have here.

If no, i think it's a K2 problem in some way.

[pljones]

Is there a quick way to delete samples from a session?

The MuSession I'm about to upload has three racks containing synths: K2, a Sampla (SamplaAh Rack) and CM101. The mixdowns from these are also captured in Samplas. It's only K2 that has a problem. It's definitely a problem between MULAB and K2 (but, like I say, Reaper and K2 don't appear to disagree the same way ).

(Once I get the K3 demo, I'll try it. It might be worth £100 if the bug's fixed there.)