MU.LAB 2 Test C

[MuTools]

Indeed, strange, will look into it, thanks!

[ApBTranCer]

the splash screen appears for me every time

I spent a few hours last night playing with mulab, and i didnt find any new bugs, but I found a few things that could possibly be improved. I found it slightly annoying that I couldn't access my VST presets from the the VST window, unless it was built in to the plugin. I think this was brought up before (I think you were having gui problems or something?), so sorry for repeating this, but the preset selection should really be right there with the instrument. Also, maybe a dry/wet knob somewhere in that region. I loved that in Muzys

I would also really like to be able to place VSTs in the musynth modular editor. Please bring that feature back! This whole modular workspace thing has opened some new doors for me, and im feeling kinda cut short knowing that VSTs COULD be used here, but you would rather not have them used here.


keep up the good work

[MuTools]

the splash screen appears for me every time

Yes, indeed, splash does come every time.

But if you did not yet choose another session after first run, then the next run will still auto load the demo.musession, and as MU.LAB has a very fast startup, the splash does not get the time to appear in that case.

I've tuned it so that the splash screen appears even faster, be it for a fraction of a second.

I found it slightly annoying that I couldn't access my VST presets from the the VST window, unless it was built in to the plugin. I think this was brought up before (I think you were having gui problems or something?), so sorry for repeating this, but the preset selection should really be right there with the instrument. Also, maybe a dry/wet knob somewhere in that region. I loved that in Muzys

I know about this and it's high on the whishlist, have been researching this more already but could not yet get it ready in 2.0.

And i couldn't postpone 2.0 forever... so had to push it to a next version.

I would also really like to be able to place VSTs in the musynth modular editor. Please bring that feature back!

No, i won't do, sorry. (but don't worry, there is a neat solution )

The main reason is because i really want that every Musynth patch is exchangable.

When using vst plugs, the patch becomes dependent on what's installed on the system.

But you can easily get what you want by putting that Musynth patch into a Mux, and then add the vst plugs you want to that Mux patch.

Then the Mux patch = Musynth + vsts

[pljones]

I'll try to create a very simple Session with K2.

Hmm... Well, I've created a four-bar sequence triggering a single-sample instrument in K2. And the problem occurs.

http://www.drealm.info/mu.lab/AhAhAh.exe (2Mb self-extracting 7-Zip)

<edit>(I'm not quite sure what I needed to included. I think everything is there now.)

Track one is the sequence, targetting K2.
Track two is the Sampla output that I got as a result of doing a mixdown. You get to hear the attack portion of the notes but not the release.

There's also a Sampla in there that approximates what the K2 set up is. I've not tried doing a mixdown with that, actually...
</edit>

[pljones]

1. How do I create a folder when saving a Session?

2. Why do I suddenly not get offered my last session when I start up? Weird... Oh, and no splash screen.

<edit>3. And why is it working again now?</edit>

[joshua19]

Another personal note:
I prefer putting the master track / rack all the way to the left. This way when you add racks to your project the MASTER rack is always to the far left. (Because you can only add tracks to the right.) If you could rearrange the location of the racks, that would be a cool option. That way if you're doing some sketching you can go back later and arrange the layout in a more grouped kind of way. ie. |MASTER||Compressor(Send)||Reverb(Send)||Kick||Snare||Perc||Bass||and so on.....

With that said, the way a new project is already setup to have 4 tracks routed to a master is really cool. Again, I just wish you could move the positioning around after adding new racks. Im so excited about this piece of software!

[Bonteburg]

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.

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



I also caused a crash in MUX couldn't repeat yet:

http://www.fileden.com/files/2007/5/13/ ... .crash.log

Look for August 1st, 23:14.

Could be pure randomness and nothing to worry about.

MU.LAB Test C 2


Marco

[Bonteburg]

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.

OSX 10.4.11

[Bonteburg]

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

I realize this is somewhat academic. Has anyone run into trouble/lost a potential killer patch yet because of excess VST program window size?

edit: jst noticed that you don't lose your settings when opening the "choose program" window because whatever tweaks you make will stay with the patch you started from ... unless you change the program AND then click OK you're save.

laalalala...

[joshua19]

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

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

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!

[Oxygenee]

Hi!

I think that zoom levels should be free (not restricted in range). - But, to have better control over the strength of zooming during '+' or '-' button press, you could add a numerical (text field) sensitivity field with the default at '1' so that if you leave it at default it will zoom just normal, when set to values greater than '1' it will zoom faster on '+' or '-' button press and with values smaller than '1', it will zoom slower than normal. - A small zoom-reset (also zoom sensitivity reset) button would be handy then.

What do you think?

Have a nice day!

[Oxygenee]

Hi!

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.

See you!

[MuTools]

Well, I've created a four-bar sequence triggering a single-sample instrument in K2. And the problem occurs.

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

Track two is the Sampla output that I got as a result of doing a mixdown. You get to hear the attack portion of the notes but not the release.

I'm can't repeat it here, mixdown works normal here.

That is with the K3 demo, as i don't have K2.

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.

[MuTools]

1. How do I create a folder when saving a Session?

Not yet in there.

Why do I suddenly not get offered my last session when I start up? Weird... Oh, and no splash screen.

<edit>3. And why is it working again now?</edit>

Bonte also wrote something similar, forgot what it was, will keep an eye on it.

[MuTools]

Another personal note:
I prefer putting the master track / rack all the way to the left. This way when you add racks to your project the MASTER rack is always to the far left.

Good idea.

Atoh: People will intuitively start plugging in synths/effects in the first rack, which is then the master rack, and when plugging in a synth in there it will block the audio from racks A-D, which will cause confusion. So not sure about it.

If you could rearrange the location of the racks, that would be a cool option.

Shift+click on the rack name + drag left/right