M4 Test

[MuTools]

Oh and btw there's a windowing problem you haven't adressed yet (not sure if you didn't see it because you were quoting me on just about everything else:

-I'm having trouble moving the MU.LAB window across the screen. Most notably it refuses to move up unless I'm really pussyfooting. The same thing applies to windows inside MULAB.

Sorry, i see what you mean and will research further.

[Bonteburg]

I am currently using an instance of Musampler.

I put a Lowpass Filter on Effect Slot 1 of the MuSampler and dragged it onto an empty track to create a target. Tried to draw a sequence and MU.LAB pops up a white Window asking me if I want to place an audio file or a sequence. I click 'Sequence' but no sequence is created.

Edit: I Recorded a piece of automation with said lowpass filter ant it worked, BUT: It doesn't play back the automation.

MU.LAB feels very stable otherwise. All of my VST plugs got accepted (except for one).

[Bonteburg]

When I open a new session without having closed the previous session first, MU.LAB will sometimes (maybe always, don't know yet) focus on a player in the previous session, even though the new session is in the foreground ("Eh, I'm hearing a piano, but there's no piano in the current session! Ah OK, have to close previous session.")


Multisamples in the MuSynth weirdly seem to default to 'muted'. This happens when you create them. Not sure what happens if you load an existing one.


There's a slight chance of multisamples in MuSynth not sounding until you create a sequence playing them. However I need to give it more testing and it may well turn out to be the 'muted' phenomenon (see above) causing some confusion.

[Bonteburg]

Is the Sample Player in MuSynth (Multisample slot) as affected by Filter Section 3 as Oscillators 1 and 2 are by Filter sections 1 and 2? I seem to be able to completely obliterate the oscillators, but on the Multisample Player, the dry sound is always audible.

[pljones]

Having selecting a track highlight the target precisely would be great!

[janamdo]

When I open a new session without having closed the previous session first, MU.LAB will sometimes (maybe always, don't know yet) focus on a player in the previous session, even though the new session is in the foreground ("Eh, I'm hearing a piano, but there's no piano in the current session! Ah OK, have to close previous session.")

There is a new session and there is a new sessionfile in Mulab
new ( session) ..opens a new session in one Mulab program
new session.. opens a whole new second Mulab program( if you have already opened one mulab session via "new" than a Mulab opens with a second Mulab program)

Is this perhaps the cause of confusion of your setup?

Note:
Perhaps better is to chance the name "new session" in "new multisession" ?

[MuTools]

I am currently using an instance of Musampler.

I put a Lowpass Filter on Effect Slot 1 of the MuSampler and dragged it onto an empty track to create a target. Tried to draw a sequence and MU.LAB pops up a white Window asking me if I want to place an audio file or a sequence. I click 'Sequence' but no sequence is created.

Indeed a bug. Will be fixed in the next version. Next version expected later today.

Edit: I Recorded a piece of automation with said lowpass filter ant it worked, BUT: It doesn't play back the automation.

I assume you mean that no new part is created, right?
That's what i see here, when recording parameters from a MuSampla slot.
That bug is fixed in the next version.

MU.LAB feels very stable otherwise. All of my VST plugs got accepted (except for one).

And is that the same result as in M3?

[MuTools]

When I open a new session without having closed the previous session first, MU.LAB will sometimes (maybe always, don't know yet) focus on a player in the previous session, even though the new session is in the foreground ("Eh, I'm hearing a piano, but there's no piano in the current session! Ah OK, have to close previous session.")

Will research.

Multisamples in the MuSynth weirdly seem to default to 'muted'. This happens when you create them. Not sure what happens if you load an existing one.

There's a slight chance of multisamples in MuSynth not sounding until you create a sequence playing them. However I need to give it more testing and it may well turn out to be the 'muted' phenomenon (see above) causing some confusion.

The MuSynth has routing buttons to tell how the signal must flow.
See the little buttons in the filter sections and amplifier.
"O1" = Osc 1, ... "SP" = Sample Player.
The MuSynth patch in [Devices] is set up for Osc 1.
Hope you see what i mean, else please let me know.

[MuTools]

When I open a new session without having closed the previous session first, MU.LAB will sometimes (maybe always, don't know yet) focus on a player in the previous session, even though the new session is in the foreground ("Eh, I'm hearing a piano, but there's no piano in the current session! Ah OK, have to close previous session.")

Indeed the focussed module stays the same until you click a track/part/module to change it. Switching session windows has no influence on that.

[MuTools]

When I open a new session without having closed the previous session first, MU.LAB will sometimes (maybe always, don't know yet) focus on a player in the previous session, even though the new session is in the foreground ("Eh, I'm hearing a piano, but there's no piano in the current session! Ah OK, have to close previous session.")

Indeed the focussed module stays the same until you click a track/part/module to change it. Switching session windows has no influence on that.

Finetuned in the next version:Switching to another session window now also shifts the MIDI focus.

[Bonteburg]

I Recorded a piece of automation with said lowpass filter ant it worked, BUT: It doesn't play back the automation.

I assume you mean that no new part is created, right?

No it did create a part and the automation was visible but it didn't do anything.

As for creating an automation part from scratch on a track with the Lowpass module as its target: it was then that it gave me the choice of audio and sequence, but my pencil wouldn't draw the part.

All of my VST plugs got accepted (except for one).

And is that the same result as in M3?

Oops, indeed! I wasn't even aware that the plugin existed anymore. Just tried to get M3 to accept it.

I will give the MuSynth routing another go. It's kind of complex. Bear with me.

I also could do with a little MuDrum tutorial. Nielzie, was that you?? I tried downloading a pdf from earlier in the thread but the link is now defunct.

[MuTools]

I Recorded a piece of automation with said lowpass filter ant it worked, BUT: It doesn't play back the automation.

I assume you mean that no new part is created, right?

No it did create a part and the automation was visible but it didn't do anything.

That's odd. Can you please do that again in a simple session and email me that session. Thanks.

As for creating an automation part from scratch on a track with the Lowpass module as its target: it was then that it gave me the choice of audio and sequence, but my pencil wouldn't draw the part.

Yes that's a bug, sorry, fixed in the coming version.

I will give the MuSynth routing another go. It's kind of complex.

Mmm, really? It's just about the little routing buttons on the filters and the amplifier. They're logical, no. Similar concept found on many VSTs too.

I also could do with a little MuDrum tutorial. Nielzie, was that you?? I tried downloading a pdf from earlier in the thread but the link is now defunct.

I've uploaded that pdf in the cedar webfolder, where you also find the M4 download. So you can grab it there

[Nielzie]

I also could do with a little MuDrum tutorial. Nielzie, was that you?? I tried downloading a pdf from earlier in the thread but the link is now defunct.

No that pdf document was uploaded by Trancit. I've just searched on my pc but can't find it anymore.. Perhaps Trancit could upload it again?

However it didn't take me long to understand MuDrum better, after I tried to load some samples in and put some effects on them. The slots are automatically linked to the midi keys. I record my drums now by playing them in by hand and in overdubs and of course with quantization on

[janamdo]

I will give the MuSynth routing another go. It's kind of complex. Bear with me.

It seems to me that the audiopath in Mysynth is:

( osc1+Osc2+sampler) + (filter1+ filter2 filter3) + amplifier(+A-env).... => + effects

Besides the audiopath there are the modulations knobs and you can route a oscillator(or..osc2,sampler) to a serial/parallel filter or one filter connected with a amplifier.

Routing in Mulab should be handier if there is a small routing diagrams on the module to consult

[Bonteburg]

I've uploaded that pdf in the cedar webfolder, where you also find the M4 download. So you can grab it there

Cool, thanks!