MU.LAB Beta C

[toxicoh]

Maybe, in the free version, there will come a maximum of 8 racks in a session again, still thinking on that.

I for one would appreciate this. Opening some older midi files wants one track per channel. This can be a problem if the midi file uses a track for eack drum instrument, for instance.

The old 8 rack limit was workable for free, but worth paying for extra racks feature. 4 VSTi is a reasonable limit for the free version, unless you want to get generous?

[oldguy]

Hi Jo,

Playing around with the demo session file, I started the recording events and began playing around with the Feedback parameter on the MUX on the highhats. Groovy sounds ensued, and are duplicated in the playback. On hitch - I cannot for the life of me find the actual event track? Any thoughts?

-Oldguy.

[muzycian]

Maybe, in the free version, there will come a maximum of 8 racks in a session again, still thinking on that.

I for one would appreciate this. Opening some older midi files wants one track per channel. This can be a problem if the midi file uses a track for eack drum instrument, for instance.

The old 8 rack limit was workable for free, but worth paying for extra racks feature. 4 VSTi is a reasonable limit for the free version, unless you want to get generous?

Euh, when i think about the 8 racks limit, it would be together with the 8 tracks limit, not as a replacer.

But i understand your midi file point.

Will continue to search for the right balance for the free version.

[muzycian]

Hi Jo,

Playing around with the demo session file, I started the recording events and began playing around with the Feedback parameter on the MUX on the highhats. Groovy sounds ensued, and are duplicated in the playback. On hitch - I cannot for the life of me find the actual event track? Any thoughts?

-Oldguy.

Did you save the session file?

If yes, can you please email it to me for research.

Thanks.

[pljones]

What about defining the paste position by the position of the mouse pointer?

I'm not keen on "at the mouse pointer"... doesn't feel right, somehow.

Mmm, I always try first "what would a text editor do", then "what would a spreadsheet do". Neither really fits here... Piano roll is more spreadsheet-like, though. But MU.LAB doesn't have an edit cursor as such, so there's nowhere that a paste is "naturally" anchored to.

I tend to work in four bar chunks, so moving stuff within the sequence is easy. If I worked with large sequences, then pasting always (relative) to the start of the sequence would be a pain.

If MU.LAB had the concept of an edit cursor, which would be set by a single pointer click, then pasting could always be relative to that. (Step-sequence entry would also be easier, as the edit cursor could auto-advance by the grid size after each note entry, with MIDI step note entry as an extra option.) Bit of a serious change to the design concept, though.

Another one: always paste relative to the last edit point (i.e. the start point of the last edited event)?

I'd just rather the point was anchored to something I'd actively clicked on, I guess...

[libero]

Hi,
would it be very difficult to implement a vst version of mulab, so that it would be possible to load it inside another environment as a vst plug-in?

The modular section is fabulous, and it would be great to use it also inside other daws.

Cannot answer this yet.

But stay tuned, i would say.

I will!

Ok, can you please give me all details again:

which plug(s)?
which version?
what is the exact problem?
is it repeatable on other systems? (if you have the possibility to check this)

Ok, maybe I found what's going on:
I just updated Guitar Rig to the version 2.2.2.002 but still the mouse doesn't work properly.
Left click apparently doesn't work. Right click opens MuLab menu.
If I click a preset on Guitar Rig, nothing happens. But if I ctrl-click and then esc to exit MuLab menu, the preset is activated, as well as the menu of Guitar Rig. It looks like a superposition of the mouse properties of MuLab and those of the NI plugin.
I don't know if it is repeatable on ohter systems. But it is the only plugin that I use that shows this behaviour.

Libero

[muzycian]

What about defining the paste position by the position of the mouse pointer?

I'm not keen on "at the mouse pointer"... doesn't feel right, somehow.

Mmm, I always try first "what would a text editor do", then "what would a spreadsheet do". Neither really fits here... Piano roll is more spreadsheet-like, though. But MU.LAB doesn't have an edit cursor as such, so there's nowhere that a paste is "naturally" anchored to.

I tend to work in four bar chunks, so moving stuff within the sequence is easy. If I worked with large sequences, then pasting always (relative) to the start of the sequence would be a pain.

If MU.LAB had the concept of an edit cursor, which would be set by a single pointer click, then pasting could always be relative to that. (Step-sequence entry would also be easier, as the edit cursor could auto-advance by the grid size after each note entry, with MIDI step note entry as an extra option.) Bit of a serious change to the design concept, though.

Another one: always paste relative to the last edit point (i.e. the start point of the last edited event)?

I'd just rather the point was anchored to something I'd actively clicked on, I guess...

The idea of having an edit cursor is interesting, will keep it in mind for later.

-- edit --

at the other hand, having an edit cursor in the editor all the time, also when you don't need it, clutters the gui, and may be even annoying, standing in the way. what do you think?

-- /edit --

For now: what about a popup dialog (cfr click the position in the transport) where you input the paste position?

[muzycian]

Ok, maybe I found what's going on:
I just updated Guitar Rig to the version 2.2.2.002 but still the mouse doesn't work properly.
Left click apparently doesn't work. Right click opens MuLab menu.
If I click a preset on Guitar Rig, nothing happens. But if I ctrl-click and then esc to exit MuLab menu, the preset is activated, as well as the menu of Guitar Rig. It looks like a superposition of the mouse properties of MuLab and those of the NI plugin.
I don't know if it is repeatable on ohter systems. But it is the only plugin that I use that shows this behaviour.

NI has a demo version of guitar rig so i'll check that one out.

[muzycian]

Hi Jo,

Playing around with the demo session file, I started the recording events and began playing around with the Feedback parameter on the MUX on the highhats. Groovy sounds ensued, and are duplicated in the playback. On hitch - I cannot for the life of me find the actual event track? Any thoughts?

-Oldguy.

Thanks for sending the musession file.

Now understand the situation.

Here is the explanation why you didn't see the recorded feedback parameters:

As well in the MuSynth as in the MUX, only the Meta Parameters at the top of the editors can be recorded into the sequencer, not the parameters on the individual modules themselves.

So if you want to automate e.g. that feedback, assign a Meta Parameter to it via Options -> Edit Parameter Map

There you can doubleclick an empty line or press Insert to add a new mapping.
Then doubleclick the new mapping (or rightclick and choose "Edit") to edit it.

So it's perfectly possible to map 1 MetaParameter to multiple targets

And automating a Meta Parameter will of course affect all of its targets.

In Beta D, also MIDI controller to Meta Parameter mapping is fully supported. (in beta C this is not yet working).

[muzycian]

Just downloaded Beta C and I'm still getting the crash when I re-enter the Audio Setup. Also, as with Beta B, when MU-LAB gets closed by windows after the crash, it is still listed in the processes list and can only be gotten rid of by rebooting the computer.
This seems to have started with MULAB beta B. I can go into and out of the audio setup in beta A with no problems.

Hey Fuzzbeard,

Thanks a lot again for your patient help in narrowing down the problem via email!

Glad that we could find the problem. Will be fixed in beta D

[D-Fusion]

One more thing regarding Automation

I noticed that if you click record and move a knob on a vst the Sequencer stops moving until you stop moving the knob.

This makes it hard too see where you add the automation in real time.

I will do some more testing later today (Right now i am moving all my samples to another partition and reinstalling windows).

[muzycian]

One more thing regarding Automation

I noticed that if you click record and move a knob on a vst the Sequencer stops moving until you stop moving the knob.

This makes it hard too see where you add the automation in real time.

Ok, will be fixed in beta D!

I will do some more testing later today (Right now i am moving all my samples to another partition and reinstalling windows).

Good luck! And thanks in advance!

[Sotiris]

Ok, maybe I found what's going on:
I just updated Guitar Rig to the version 2.2.2.002 but still the mouse doesn't work properly.
Left click apparently doesn't work. Right click opens MuLab menu.
If I click a preset on Guitar Rig, nothing happens. But if I ctrl-click and then esc to exit MuLab menu, the preset is activated, as well as the menu of Guitar Rig. It looks like a superposition of the mouse properties of MuLab and those of the NI plugin.
I don't know if it is repeatable on ohter systems. But it is the only plugin that I use that shows this behaviour.

NI has a demo version of guitar rig so i'll check that one out.

Guitar Rig 2 works fine on my HP Compaq NX7000 laptop running mulab beta b2 on WinXPproSP2.
Everything (editing, preset selection, saving, etc.) works fine.
I just received my Komplete 5 box yesterday so i'll give you a "official" report on Guitar Rig 3 soon...

P.S. where can i download beta C or D ?

[libero]

Guitar Rig 2 works fine on my HP Compaq NX7000 laptop running mulab beta b2 on WinXPproSP2.
Everything (editing, preset selection, saving, etc.) works fine.
I just received my Komplete 5 box yesterday so i'll give you a "official" report on Guitar Rig 3 soon...

P.S. where can i download beta C or D ?

Yes, the problem is related only to the Mac os x version of MuLab and all the komplete 4.

[muzycian]

P.S. where can i download beta C or D ?

I'll email you about this!