MuLab 4 Released

[MuTools]

Here is my saved project with FM8:

http://dl.dropbox.com/u/5646041/MuSessi ... .MuSession

Thanks for the musession!

The composition contains 5 tracks (sub-tracks are also taken into account) so that's the reason.

If you delete one of these empty tracks, the voice will shut up.
(even i myself am happy if that *ssh*l* shuts up )

By the way, i see what you mean with the XY pad recording.
It's recorded as a parameter event sequence.
We need a function to translate such parameter event sequence into an automation part. Then you could further edit such recording using the breakpoint envelopes. Such function is on the wishlist.

[> DiGiT <]

were you gonna fine tune the task bar behavior? maybe make the modular section so you can hide it?

handsome program you got there.

[aMUSEd]

Here is my saved project with FM8:

http://dl.dropbox.com/u/5646041/MuSessi ... .MuSession

Thanks for the musession!

The composition contains 5 tracks (sub-tracks are also taken into account) so that's the reason.

If you delete one of these empty tracks, the voice will shut up.
(even i myself am happy if that *ssh*l* shuts up )

By the way, i see what you mean with the XY pad recording.
It's recorded as a parameter event sequence.
We need a function to translate such parameter event sequence into an automation part. Then you could further edit such recording using the breakpoint envelopes. Such function is on the wishlist.

I can only see a main track with midi and an automation track - where are the others and how did they get there?

I assumed any params being moved would be recorded as automation - that seems a pretty normal thing that happens in other hosts when you move a param - why not just have it record straight off as automation instead of having to convert it? It seems an unnecessary intermediate step.

[janamdo]

I can only see a main track with midi and an automation track - where are the others and how did they get there?

I assumed any params being moved would be recorded as automation - that seems a pretty normal thing that happens in other hosts when you move a param - why not just have it record straight off as automation instead of having to convert it? It seems an unnecessary intermediate step.

Say there is a midi track and you do want to automate a knob
- record and move the knob..a automation subtrack is added under the maintrack
- draw a automation..add a subtrack and drag the parameter to the subtrack

[pljones]

why not just have it record straight off as automation instead of having to convert it? It seems an unnecessary intermediate step.

Possibly that's what Jo meant. If you bind a MIDI control to a parameter, recording would directly record parameter changes. However, I can quite see why it would record the MIDI events. And what if you want to change what your expression pedal is controlling after recording? It might be better to have the events. Myself, I'm not sure which I'd prefer - perhaps I'd want a choice every time I set a binding up. Or be able to switch back-and-forth transparently between event and curve forms... (heavy maths, there, I guess...)

[DHR53]

New version... Yayy. Looking good. Have adjusted my template again. Questions, Questions, features....

When I create a blank track, how does the connection default work? i.e. if I have a rack selected and create a new track does it go to that rack? And if I want just a blank track without a connection to anything do I need to deselect everything?

If I've created a blank track, selecting the track doesn't seem to affect the rack "selections." i.e. anything selected in the rack stays selected while selecting the new blank track? So the only way to add an instrument to the new "Blank" track is to click at the top of the screen the focused module panel and add a module or VST???


Thanks!

[> DiGiT <]

youre supposed to drag your module or rack to the track that will then be pointed to it

[DHR53]

So the procedure is to create a rack first, or can you drag from the VST/module window? Hmmm... I guess this process changed somewhat from version 3 to 4. Or I can't remember.

I'll check docs again. I'm still trying to figure out the dragging functionality thing.

[pljones]

Remember, you're not "adding an instrument to a track", you're setting the target for what the track is controlling - the inverse sense, if you see what I mean.

[janamdo]

So the procedure is to create a rack first, or can you drag from the VST/module window? Hmmm... I guess this process changed somewhat from version 3 to 4. Or I can't remember.

I'll check docs again. I'm still trying to figure out the dragging functionality thing.

In Mulab 3 there it was that you must "target" a rack with a track -
You choose a track and assign a rack,but this mechanism is removed in Mulab 4, because it was too difficult to see for a starter in Mulab.
Now this is replaced indeed by dragging a instrument in a rack to a track.

In mulab 4 it is easy.. you can work on 2 ways for creating a track with rack
Using the + button for
- add instrument Track --> you get colored tracks/tracks..this is the most userfriendly way and easy to do
- add Track --> here you can drag a instrument from a rackslot to a track(header)

[DHR53]

I still think it's a little confusing (as I thought in 3 as well) that tracks remain independent of racks, whether they're targeted or not. So naming is not carried over from the tracks to racks? I name a track and the rack doesn't reflect that... etc. I realize it lets you change the target for anything, but it would be easier if a target rack name would show up in the track? ...to avoid confusion. Maybe just me.

[aMUSEd]

I can only see a main track with midi and an automation track - where are the others and how did they get there?

I assumed any params being moved would be recorded as automation - that seems a pretty normal thing that happens in other hosts when you move a param - why not just have it record straight off as automation instead of having to convert it? It seems an unnecessary intermediate step.

Say there is a midi track and you do want to automate a knob
- record and move the knob..a automation subtrack is added under the maintrack

That's the bit that seems not to be happening though. If I have record on (including record events) and move a knob it is creating what I thought was an automation track but it seems it's actually something else and does not have nodes or curves - its a bit weird tbh

[pljones]

If you record MIDI data - i.e. what's coming in via a MIDI port - you get a sequence part recorded with MIDI events on it.

My foot controller controls the position of the hihat when I hit my hihat pad. When I record, I get a stream of foot controller messages and a hihat note. That's exactly what I'd expect. I can play that back to any sampler (etc) that understands foot controller and has hihat mapped to the same note(s) and get the same effect, so it's exactly what I'm after.

Alternatively, I have a nanoKontrol with knobs, sliders and buttons that I bind to various controls on plugins. When I record and move a knob, slider or button... exactly the same thing happens: the MIDI event gets recorded. I've done the same thing: sent a MIDI event. The problem comes when you think about the semantics. For a bound plugin control, it makes "no" sense to target those events at a different plugin - they should be treated the same as automation for that parameter.

It's this that is the "extra step" - understanding the semantics of the binding of an incoming MIDI event to a parameter and treating it differently when recording.

[MuTools]

I can only see a main track with midi and an automation track - where are the others and how did they get there?

Tracks are not parts. In the session you sent there are 5 tracks (triggering the voice) and 2 parts.

I assumed any params being moved would be recorded as automation - that seems a pretty normal thing that happens in other hosts when you move a param - why not just have it record straight off as automation instead of having to convert it? It seems an unnecessary intermediate step.

Alternatively, I have a nanoKontrol with knobs, sliders and buttons that I bind to various controls on plugins. When I record and move a knob, slider or button... exactly the same thing happens: the MIDI event gets recorded. I've done the same thing: sent a MIDI event. The problem comes when you think about the semantics. For a bound plugin control, it makes "no" sense to target those events at a different plugin - they should be treated the same as automation for that parameter.

Conclusion at this point:

Recording MIDI controllers results in a sequence part with MC events. That's how it works now, so OK. Recording plugin parameters should result in an automation part with breakpoint envelopes. Ideally there are conversion functions to convert a parameter automation part into a sequence part and vice versa.

Taken note.

[janamdo]

I still think it's a little confusing (as I thought in 3 as well) that tracks remain independent of racks, whether they're targeted or not. So naming is not carried over from the tracks to racks? I name a track and the rack doesn't reflect that... etc. I realize it lets you change the target for anything, but it would be easier if a target rack name would show up in the track? ...to avoid confusion. Maybe just me.

Standard opens Mulab with 4 racks.
It seems a little bit strange that you can add fifth track with the + button without a rack.
Is that confusing ?