MU.LAB beta A

[pljones]

(The "Save" option on WFT Osc worked okay, by the way.)

Did i miss a post? Wasn't it working first?

I wasn't sure which of the "Load/Save xxx File" items should be working. I thought you'd said only MUX and MuSynth? (I wonder whether the Load/Save on the metronome is as useful as it is on other plugs... So far, I think only Racks don't have the option!) I guess as the docs come together, things like this will become clear.

[jens]

The F1-2-3 window commands are also accessible via the Edit menu.

So it's also available via easy mouse clicking.

Extra buttons would also add extra gui clutter.

Yes, I see your point - however if F3 is a maximized MPA there's no file menu - but anyway: these are minor issues...



now to something diffferent:

I must congratulate and salute you - the modular concept of MU.LAB is exceptional - it goes way beyond eXT - it kind of combines eXT-functionality with Reaktor-functionality which is novel and unique.

[Caleb]

Hmmmm - Mux, MPA and MuZynth are all slightly confusing to me.
Looks pretty deep though.

I get crashes sometimes if I put a rack in the Mux and add a VSTi to
the rack - should I be able to do that?

I understand that I'm not supposed to use the "Voice In" etc.. in MUX - however, if I put a MuZynth in MUX I can use voice in for MuZynth? Bit confused here.

I'm sometimes getting one of those extremely painful unkillable process problems when exiting MUTOOLs here and there - the one where you can't kill the process in Windows if your life depends on it. Even got an automatic reboot and "Windows has recovered from a serious error". Oh my!

I just didn't have enough time to play around with things tonight - I never do have much time come to think of it.

Maybe if I get a chance tomorrow I can play further - maybe even find out why I got those particularly nasty crash things happening.

Regards
Caleb

[Caleb]

now to something diffferent:

I must congratulate and salute you - the modular concept of MU.LAB is exceptional - it goes way beyond eXT - it kind of combines eXT-functionality with Reaktor-functionality which is novel and unique.

I agree. It looks quite exciting and flexible.
Bit confusing to me first up - but if I get time I hope to start seeing the potential of it a little better.

Regards
Caleb

[Caleb]

Hmmm - what does the harmonise function do on the WTF Oscillator? It seems to just give me sine waves of various amplitudes regardless of what wave is in there before I select the function. Also you can't see the input control fully when you select this function. You don't know what you're even typing in there.

Do you think the AIPS modulation control should alter the appearence of the wave file? Give you visual feedback on what you're doing?

Regards
Caleb

[jens]

Hmmmm - Mux, MPA and MuZynth are all slightly confusing to me.
Looks pretty deep though.

MPA is like XT2's 'comps'-area - Mux and Musynth are both more like Reaktor in that you use them to create new plugins - they both basically share the same functionality, but Mux is meant for effects and Musynth is meant for instruments.






edit: typos

[jens]

Hmmm - what does the harmonise function do on the WTF Oscillator? It seems to just give me sine waves of various amplitudes regardless of what wave is in there before I select the function.

yes, this confused me as well - I guess it must be a bug?

[muzycian]

(The "Save" option on WFT Osc worked okay, by the way.)

Did i miss a post? Wasn't it working first?

I wasn't sure which of the "Load/Save xxx File" items should be working. I thought you'd said only MUX and MuSynth? (I wonder whether the Load/Save on the metronome is as useful as it is on other plugs... So far, I think only Racks don't have the option!) I guess as the docs come together, things like this will become clear.

Yes, for now use only musynth and mux load/save please.

Normally the others won't crash, but they are not relevant at this point, so they'll be removed.

I'll try to get beta B ready asap, that will already clear things up.

To get it ready sooner, maybe beta B will not yet have *all* discussed items.

[Caleb]

Another one on the WFT Oscillator (so close to WTF).

What does this oscillator do exactly when you load in a wave file? It is synthesising the wave file into a small looped sample for playback? I'm interested in what it's doing there.

Is there plans on including more flexible wave file import into MuZynth? Like in Muzys3?

Regards
Caleb

[ApBTranCer]

wow im very impressed with what you have done so far

heres a couple of bugs ive found:
1: osx sound doesnt play on the first opening..... or the second or third.... 4th time worked like a charm
2: adding a MuVerb to my MuSynth somehow blocks the sound from the output
3: after having trouble with #2, i tryed adding the Muverb to the rack that the Musynth was on, and the same thing happened. Although, reseting the track target to the musynth somehow fixed this problem, but not #2s problem. I also tryed adding a VST effect instead of the muverb to the rack, and it had the same problem, so it might not be a problem with Muverb itself.

now a couple hours later, i tried using the stereo splitter and combiner, same problem, cuts off the audio output.

I cant wait for a stable release!! Im finally starting to see why i would use this host over other hosts

ok, i might have just fixed my problem... I was adding the muverb before the Voice Out..... now i added it after and it works fine... still doesnt explain the rack effects problem

Please try to repeat it in the rack situation, then email me the musession file.

Maybe the rack problem was related with the reverb-within-voice problem?

I havn't been able to recreate the rack problem yet.. and i didnt save the first session that had the "bugs" (shame on me), but i'l look into it more tomorrow... If this was a mistake on my end (which most of it obviously is ), then maybe mulab should not allow users to add effects before the voice out.. Before i ran into this problem, i read the documentation, looked over the demo and everything.. but sometimes we need pop-up reminders/blockers within the program that prevent us from making stupid mistakes

Tomorrow Il play around with rack effects and the musynth some more, and see what happens

_____

also, i was aware that the OSX version had a first time sound bug, i just thought id let you know that it happened "3" times before it worked, whether that makes a difference or not

_____


One more thing.. I wasnt able to change patches in one of my VST effect plugins since the VST effect didnt supply this feature in it's UI, and neither does Mulab

[Caleb]

MPA is like XT2's 'comps'-area - Mux and Musynth are both more like Reaktor in that you use them to create new plugins - they both basically share the same functionality, but Mux is meant for effects and Musynth is meant for instruments.

Yep this in concept is easy enough, it's the ability to dump MuZynths in MUX and vice versa that's a little confusing to me given their supposed different purposes.

Actually MUX in MuZynth probably makes sense - it's just the other way around that's confusing.

Regards
Caleb

[muzycian]

The F1-2-3 window commands are also accessible via the Edit menu.

So it's also available via easy mouse clicking.

Extra buttons would also add extra gui clutter.

Yes, I see your point - however if F3 is a maximized MPA there's no file menu -

Great preciseness jens!

but anyway: these are minor issues...

Yes, at this point i push this a bit forward. Taken notice of it.

now to something diffferent:

I must congratulate and salute you - the modular concept of MU.LAB is exceptional - it goes way beyond eXT - it kind of combines eXT-functionality with Reaktor-functionality which is novel and unique.

Thanks jens!

Yes, it's very powerful.

And i've got several ideas to push this even much further. Without complicating things. At the contrary.

But step by step.

First we really need to get this step of technology rock-solid!

[Caleb]

Grrr - stoopid me can't find the post about assigning labels to parameters in MUX etc...

You can assign via that middle window - but the label only appears when you are actually manipulating/clicking on the parameter control. As there are 16 knobs, clicking on them to remember what they're for doesn't seem ideal.

Would it be possible in a future update to be able to label the knobs themselves for easy overview?

Regards
Caleb

[Caleb]

Jo - are you supposed to be able to dump a Rack plug-in into MuZynth, put a synth plug-in in one of the slots and use it as an additional oscillator?

When I do it I seem to stuff up by ASIO connection or something - ie no more sound - even when I delete the rack instance.

Regards
Caleb

[muzycian]

Hmmmm - Mux, MPA and MuZynth are all slightly confusing to me.
Looks pretty deep though.

It's as superficial or as deep as you want.

I get crashes sometimes if I put a rack in the Mux and add a VSTi to
the rack - should I be able to do that?

Yes, that should work.

Can you please make a repeatable crash pattern.

I understand that I'm not supposed to use the "Voice In" etc.. in MUX

Indeed, it doesn't make sense.
They'll be removed from the MUX plugin menu to avoid the confusion.

So Voice In/Out are only for use in MuSynth.

- however, if I put a MuZynth in MUX I can use voice in for MuZynth? Bit confused here.

First, sorry to be bitfucker (or how do you say that in english) but can you please call it the MuSynth. Thanks! Want to avoid any confusion with..

Yes, you can use the MuSynth in the MUX. But then it only uses 1 voice! So in fact it's used as a kind of effect.

But that's very useful. Cfr my example of yesterday (earlier in this thread) with a MuSynth in the MUX modulating a ring-modulator: http://www.mutools.com/mulab/example.mp3

First 2 bars is straight ring mod, musynth get no notes, last 2 bars is musynth receiving notes from sequence.

I'm sometimes getting one of those extremely painful unkillable process problems when exiting MUTOOLs here and there - the one where you can't kill the process in Windows if your life depends on it. Even got an automatic reboot and "Windows has recovered from a serious error". Oh my!

I can only suspect an asio driver issue.

MU.LAB uses the same straightforward asio approach recommended by steinberg in their asio sdk.

Of course, if you could find a repeatable pattern, or find more pieces of the puzzle, we may find the reason.

I just didn't have enough time to play around with things tonight - I never do have much time come to think of it.

Know the feeling.

But then, you just have to rationalize i.e. prioritize what you really want to do in your life.

Oops, sorry man, i'm talking too much.

Maybe if I get a chance tomorrow I can play further - maybe even find out why I got those particularly nasty crash things happening.

If i can help, i'll certainly do.

Does anyone else have asio problems with mulab?