Feature Requests

[dj ray]

Automap 3 Mixer Control!

[tomica]

I think there's nothing wrong with the way MIDI is recorded in that situation, but it would be good to get an option when you press stop after recording, if you recorded some MIDI longer than the loop setting, whether you want to merge or expand the recorded MIDI data.

well yes, i never said something was wrong, this wasnt a bug report, but a future request. ^^

anyway, you summed it up even better. there should be the option to either expand the recorded midi, or layer it all on top of itself. wow, would that be nice!

[pljones]

I see three things you could want:
1) Part long enough to hold entire sequence
2) Part holding entire sequence, wrapped at current loop points
3) Part holding "latest take" (i.e. last recording between current loop points)
I guess just a popup menu when you stop recording would do?

(Notice for 1 I wouldn't want anything else done - no other parts unrolled / repeated / extended to match.)

[tomica]

wow. yes! it would make things much easier.

[pljones]

Ideally, I'd like the multiple takes to remain available to be picked through, too... It might have be the first of seventeen takes that sounded best...

[pascalb]

for LFO, a sine wave, a noise and a sample & hold for all the waveforms

[MuTools]

for LFO, a sine wave, a noise and a sample & hold for all the waveforms

A 'noise lfo' can be done by using the Wobble Generator

[Gianluca13_2]

The two major lack I see in Mulab at the moment are:
A) the impossibility to control transport bar via MIDI message Play, Stop, Rewind, Record, and not less important Loop, should be
controllable by a master keyboard or remote controller.
B) The possibility to recall all session via a MIDI message like a program change.

Both this function are very very important for a live use.

Cheers,

Gianluca

[MuTools]

A) the impossibility to control transport bar via MIDI message Play, Stop, Rewind, Record, and not less important Loop, should be
controllable by a master keyboard or remote controller.

Fyi: Will be possible in MU.LAB 3.

B) The possibility to recall all session via a MIDI message like a program change.

Why do you really need to open a session via program change?

I mean, loading a session can take some time, depending on what's used in the session (which vst plugins, which samples, etc...). So it won't be a big time gain i think.

Or maybe you want to be able to do so for easiness?

Just hit a preprogrammed program change on your midi controller and the session is being loaded, even if it would take some time to load.

Is it for that reason?

[pljones]

I could second that -- hitting patch change to bring in a new set of virtual instruments. (But I'd see support for multi-channel MIDI routing from multiple MIDI In ports as more important).

[NBV]

Could you please consider the option of bundled saving for mu.lab projects? It makes things very easy when you have to recover a project from a backup copy.


Thank you in advance.

[MuTools]

About bundled saves:

There are 3 aspects about this:

1) Vst plugins
2) Samples
3) Audio files

1) It is not possible to bundle the used vst plugins within the session file. Not only impossible for technical reasons but also for legal reasons.

2) Samples can already be embedded in the MuSession file.
Use Edit menu -> Sample Manager -> Embed All

3) Indeed this aspect should be improved.
Embedding audio files within the MuSession file is not the way i would go as that could make too large files.
Solution here is to support relative audio file paths which are relative to the MuSession file path. This is on the Whishlist.

Or do you see other aspects besides the above?

[NBV]

Hello Jo, I was indeed referring to audio bundled saving. I think your solution of supporting relative audio paths is *a lot* better than bundling audio files. Hope we could see it in Mulab 3. Thanks.