M3 Tests

[MuTools]

If each MuLab device has its own little Icon
AND each preset stored in the Preset folder shows the ICON of the synth

Sounds like a good idea. Added on the future whishlist for further evaluation.

<edited> It not true that it's enough just to know that a Preset is a Bass, it is really important to know which Plug-in has created that sound for obvious reasons.

Which obvious reasons?

[sunhome]

Moved ....http://www.kvraudio.com/forum/viewtopic ... 19#3947419

[liquidsound]

If each MuLab device has its own little Icon
AND each preset stored in the Preset folder shows the ICON of the synth

Sounds like a good idea. Added on the future whishlist for further evaluation.

<edited> It not true that it's enough just to know that a Preset is a Bass, it is really important to know which Plug-in has created that sound for obvious reasons.

Which obvious reasons?

Thank you for considering the Icons

Each Synth has character, color, individual structure for further development of the sound etc.
For example when I need a Bass I may go with Albino or BLUE.

If I had just a short list of presets I may have enough memory to remember the preset' sound and synth, and in the case of a MUX, what kind of third party VST it contains.

But if the library really grows, then I will find myself looking at the list and if I need a Bass made by the MUX because I need to add Albino in it, well... how do I do it from the Preset List?

And this goes for a sample sound etc. Knowing the Synth it gives me total control over my choices for a preset.

[Nielzie]

If each MuLab device has its own little Icon

AND

each preset stored in the Preset folder shows the ICON of the synth

THEN

we can choose by Category and By Synth

Great idea!

Why didn't I think of that

[theorize]

Thanks Jo for being open to helping with the Rhino thing, admittedly I don't know much about the debugging process I'm not a programmer just an end user.

BTW I had a chance to try out the portability of Mu and it is awesome

About to go to work now but I have tomorrow off I think I'll spend the day with M3

I must say the program is getting WIKKED COOL I haven't been this stoked about a host for a long time.

[pljones]

I guess I'm with Jo on not taking it further. If I want "bass", I don't think "what synth created it?" - I couldn't care: I want a cool-sounding bass and I'll scroll presets (yes, that is the right word, isn't it ) until I find one. I don't want to spend my life learning that a particular synth is meant to sound better for certain types of sound.

-edit-
Oh, and I guess that means I feel "it's wrong to think that way"! ... As no one's saying I couldn't work "my" way maybe I shouldn't object -- I guess I just don't want Jo working on other people's interests!

[sorohanro]

There are "tweakers" who like to make their own sounds and there are people that are used to specific devices. For those is more useful to have the device/ synth is more important than have the presets. Some people like to sample stuff and use their own sounds (me, by example), others like synth programming & tweaking, you just can't put all of those away.


BTW, I love the new synth presets, so many and so good...

[liquidsound]

I guess I'm with Jo on not taking it further. If I want "bass", I don't think "what synth created it?" - I couldn't care: I want a cool-sounding bass and I'll scroll presets (yes, that is the right word, isn't it ) until I find one. I don't want to spend my life learning that a particular synth is meant to sound better for certain types of sound.

-edit-
Oh, and I guess that means I feel "it's wrong to think that way"! ... As no one's saying I couldn't work "my" way maybe I shouldn't object -- I guess I just don't want Jo working on other people's interests!

How do you think we got from M3.xx to M3.0.10?
I certainly agree with you on "Jo working on everyone's wishes" but this is the nature of the beast.
And in this case MuLab is going to be the BEAST!
I spent my professional life designing solutions to accommodate clients not near the so many cool people here.
I know what it means. I have a great respect for Jo and I also like to push the envelope. It makes steel out of ordinary iron.

I read your posts and I wish I knew as much as you do on technical issue but then... I would drive Jo crazy! (Which I will in order to learn this DAW to the bare bones).
My main concern is Work-Flow and MuLab is going to lead the pack.

Can't wait for this to be over. But then again....M4

[MuTools]

The MU.LAB 3.0.11 test version is available for download:

http://www.mutools.com/mulab/azalea

You need to re-install the full package as the patch library folder structure has changed.

But if you don't want to resetup MU.LAB, then copy all files in the previous Mulab/Settings folder to the new Mulab/Settings folder before running the new MU.LAB.

About this release: Not yet all items on the M3 whishlist are implemented, still a handful things to do, but the most important ones are done, cfr the change list.

I hope this already is a very usable version, which tends to be a prerelease candidate. Please lets focus on getting this version as stable as possible, i.e. lets concentrate on bug fixing. Thanks.

Cheers!

[pquenin]

Thank you for the 3.0.11, the presets thing is far better.
I have a question : when you put your mouse at the beginning of a part the arrow changes into a pen but if you use the pen to extend the part to the left, nothing happen. The same thing for a note is OK : the note is extended to the right. It's OK also in the multisaple editor.
So it must be a bug he he !

[pquenin]

Maybe another bug :
You say that when a parent track is muted, it affects all its subtracks too... Well maybe, but the little icon on the subtrack not reflect this..

[Nielzie]

Thank you for the 3.0.11, the presets thing is far better.
I have a question : when you put your mouse at the beginning of a part the arrow changes into a pen but if you use the pen to extend the part to the left, nothing happen. The same thing for a note is OK : the note is extended to the right. It's OK also in the multisaple editor.
So it must be a bug he he !

Just tried. Confirmed! Only thing is I wonder why I should use this as I can't seem to think of a reason to "extend" the sequence with empty space at the beginning..

[gemada]

Gui Bug: Rewind and Forward buttons doesn't change appearence in "down state" (when pressed)

[gemada]

Bug:
Copy--Paste a sequence, sometimes it does exactly in the cursor position (this is the right thing) but sometimes it pastes somewhere ahead or before the cursor position...

Another thing...Paste sequence: it will always open a "position window" (Paste Part At) and you have to confirm or change position.
It should just paste in cursor position and do not ask that...IMHO it would be more pratical.

Jo, MU.LAB 3.0.11 test version has better workflow but i confirm all the bugs described in this forum about this latest test version.

[bpblog]

a bug:
make a send from rack b to rack a. now make a send from rack a to rack b. this results in a short freeze followed by a crash.

another small one:
in the mixer, when you select a new rack output, the gui doesn't update. you have to select another rack and then the first one again to see the updated info.

EDIT 1:
another thing concerning rack outputs. when you select rack b as the output for rack a for example, it is still possible to select rack a as the output for rack b. there's no crash involved until you press F2 to check out the MPA. this is a nasty one, it freezed my pc completely, so have that in mind when reproducing.

EDIT 2:
i preferred how M2 had sequence names aligned to top-left. it looked way more neat, especially when you have a bunch of sequences of different length piled up on the screen. i'm not sure though if there is an advantage in having them centered that i'm not aware of.