MU.LAB Beta B

[fycfung]

I'm using a Dell Inspiron running XP SP2 with a Creative Audigy 2 ZS Notebook, ASIO4All (I think it's 2.4 but FL7 demo might have upgraded it to 2.7) and a Creative Prodikeys keyboard as MIDI input (input device 1 I believe). The keyboard seems to be working OK in, say, REAPER or other apps.

[muzycian]

Just tried with Rob Papen Blue also with a arpeggiator setting and the same happened there (See the Adventus post above for details).

Bug number 2:
If you delete a synth in the rack the window up in the right corner does still show the synth name (Not refreshed or cleared).

I have also played a bit with the Sequence loop option and i find to be a great feature

But i have one FR for it also:
It would be nice if it would be possible to enable loop from selection like you can do in the composer/Aranger view.

I just checked Rob Papen Blue in MU.LAB.

It works fine here, including the arpegiator.

Note however that if you're having long notes in a sequence, and you position the sequencer in the middle of such long notes, then click play, then these notes won't play yet, as you're beyond their start point, and thus the synth and the arpegiator won't be triggered yet.

If it's a looped sequence, the notes will play on the next loop cycle, and so the synth and its arpegiator will start making sound.

Does this explains the issue you had?

[D-Fusion]

Just tried with Rob Papen Blue also with a arpeggiator setting and the same happened there (See the Adventus post above for details).

Bug number 2:
If you delete a synth in the rack the window up in the right corner does still show the synth name (Not refreshed or cleared).

I have also played a bit with the Sequence loop option and i find to be a great feature

But i have one FR for it also:
It would be nice if it would be possible to enable loop from selection like you can do in the composer/Aranger view.

I just checked Rob Papen Blue in MU.LAB.

It works fine here, including the arpegiator.

Note however that if you're having long notes in a sequence, and you position the sequencer in the middle of such long notes, then click play, then these notes won't play yet, as you're beyond their start point, and thus the synth and the arpegiator won't be triggered yet.

If it's a looped sequence, the notes will play on the next loop cycle, and so the synth and its arpegiator will start making sound.

Does this explains the issue you had?

Hmm. it works fine now, but in Beta B it did some weird stuff (Might be that no selection of input and output option that caused it).

In Beta B2 it works normal

I also noticed that Adventus Vsti sometimes make Mulab Auto save when you click on the stop and play button a few times.

And when i close Mulab with adventus in it it crashes (On exit).

[muzycian]

Just tried with Rob Papen Blue also with a arpeggiator setting and the same happened there (See the Adventus post above for details).

Bug number 2:
If you delete a synth in the rack the window up in the right corner does still show the synth name (Not refreshed or cleared).

I have also played a bit with the Sequence loop option and i find to be a great feature

But i have one FR for it also:
It would be nice if it would be possible to enable loop from selection like you can do in the composer/Aranger view.

I just checked Rob Papen Blue in MU.LAB.

It works fine here, including the arpegiator.

Note however that if you're having long notes in a sequence, and you position the sequencer in the middle of such long notes, then click play, then these notes won't play yet, as you're beyond their start point, and thus the synth and the arpegiator won't be triggered yet.

If it's a looped sequence, the notes will play on the next loop cycle, and so the synth and its arpegiator will start making sound.

Does this explains the issue you had?

Hmm. it works fine now, but in Beta B it did some weird stuff (Might be that no selection of input and output option that caused it).

In Beta B2 it works normal

OK

I also noticed that Adventus Vsti sometimes make Mulab Auto save when you click on the stop and play button a few times.

This is not caused by Adventus.

MU.LAB auto saves every 15 minutes, but only on stopping the sequencer.

And when i close Mulab with adventus in it it crashes (On exit).

This is a known bug. Not Adventus specific. It's a possible crash bug on New Session, Revert Session or Quit. Resolved in beta C which is on the way

[D-Fusion]

Great to hear that you have solved it M8
Is there a way to turn of the autosave function?

[muzycian]

Great to hear that you have solved it M8
Is there a way to turn of the autosave function?

Why would you do that??

It's ALWAYS best to have an auto save.

And this applies to every software application!

Now for your info:

The Auto Save time is defined in your mulab/settings folder in mulab.txt.

Open it (when mulab is not up) and edit the line AutoSaveTimeOut=n
where n is the number of minutes between auto saves.

If you set it to 60, only once per hour there is an auto save, on stopping the sequencer.

But again, every 15 minutes is a good value.

[D-Fusion]

Ah ok
I save alot, but i am used to use to the save button since most of the autosave functions i have tried saves a bunch of different versions of the same file.

How does Mulab do this? does it create one copy of the file and use that or does it create a new file for each autosave?

I did also test the assign midi functions again and discovered the midi learn function that i asked for

Is there a shortcut for midi learn also so you can for example twiddle the cutoff knob and hit ctrl-l and then twiddle the knob on the controller?

I am also playing a little with the MuSynth to get the hang of it and i love how that resonance self oscillates

[muzycian]

Ah ok
I save alot, but i am used to use to the save button since most of the autosave functions i have tried saves a bunch of different versions of the same file.

How does Mulab do this? does it create one copy of the file and use that or does it create a new file for each autosave?

It always autosaves as "AutoSaved.MuSession" in your MU.LAB folder.

I did also test the assign midi functions again and discovered the midi learn function that i asked for

Is there a shortcut for midi learn also so you can for example twiddle the cutoff knob and hit ctrl-l and then twiddle the knob on the controller?

No, not yet, but it's on the whishlist.

[toxicoh]

Just to lt you know I've been able to run MuLab Beta b2 on my Acer Travelmate 3200. The Realtek AC'97 Audio card was not detected. Everything works ok after I installed ASIO4ALL 2.7.

Playing with the MUX seems to add extra delay (latency?) to long audio tracks. [Edit: I was trying to add echo to a vocal track recorded in Luna.]

Has anyone been working on extra presets for MUX and MuVerb?

[muzycian]

Just to lt you know I've been able to run MuLab Beta b2 on my Acer Travelmate 3200. The Realtek AC'97 Audio card was not detected. Everything works ok after I installed ASIO4ALL 2.7.

Playing with the MUX seems to add extra delay (latency?) to long audio tracks. [Edit: I was trying to add echo to a vocal track recorded in Luna.]

The "Echo" plugin indeed delays the original signal, this is exactly its goal.

The echo effect we're all used to uses a balanced mix between the original and the delayed signal.

So you need to add a Balancer in the MUX patch, and feed audio input 1 with the original and audio input 2 with the delayed signal. Then you can make a fine balance, and you'll hear the direct signal too

Has anyone been working on extra presets for MUX and MuVerb?

Until now the betas have not yet been very stable (although beta B2 is getting there), so i understand it was too early for building patches.

Beta C is almost ready and hopefully that is a nice stable version.

I will then start making patches myself too.

[muzycian]

Hi Jo,
Here's something I encountered. I tried to open Mu.Lab and do a MIDI recording.
So, 1. I can't seem to set it up so that the MIDI controller is playing through a certain rack without generating a sequence part.

Yes you can:

Just plug in a synth in a rack, and right-click it and choose focus.

This way the synth will get the midi focus.

In beta C, plugging in a synth in a rack automatically focusses the whole rack, so then it's plug and play

If I just click in the upper right where the rack selection is to occur, nothing happens.

If there is no part selected, you cannot do anything in the Part Property Panel.

The Part Property Panel displays/edits the properties of the first selected part.

Next: If I don't select a rack, then when I hit the record button, the record button lights up and so does the play button.

If I then hit my MIDI keys and then hit the record button again (presumably to stop recording), then it asks for a name for the recorded sequence, but then when I enter one and hit Enter, it just keeps playing and no sequence is persisted.

However, if I start the recording and then hit the play button to stop the playing, it asks for the name and then it persists the sequence.

Note, the second time I hit record to stop the recording, it seems to persist the sequence.

Edit: actually I am not quite sure what the trigger is. When I tried turning on a loop and then recording while it was looping, then I was able to get multiple parts to fail to appear (there was no rack selected but it was playing on the rack that was last used). Strangely, the parts were playing, they just didn't appear in the part view. Then the notes all hung and I had to reset the real-time engines.

I've been checking the midi recording functions and have finetuned some things.

For example: if you would have recorded something during countdown, there was a chance that the resulting recording contained long notes.

Please lets check out beta C first and see how it goes from there.

Another comment: I think that when you call 'Duplicate Sequence', it should automatically change the name of the sequence (e.g., if the original sequence was "foo", then the name of the duplicated sequence should be changed to "foo(1)" or something like that). Changing the color would be good too. That way it becomes clear that the duplicated sequence has been severed.

In beta C, there is an automatic name indexing system, you'll see.

I noticed that FL Studio 7 apparently has a way to "select all similar parts" which would, I suppose, automatically highlight all the parts that are copies of a given part (i.e., not duplicated).

Added on the whishlist.

Also, it does not seem to be possible to instantiate a sequence part directly from that drop-down box; rather, you have to be operating on an existing sequence part, right?

Correct. If you want a new part, use the pencil.

Further comment: on a short note in the MIDI editor, I can only get the "left" pencil to edit length to the left, rather than also getting the "right" pencil to edit to the right.

I checked this and everything seems to work ok.

Maybe you wanted to tweak the start or end of a note on a grid but the note was lareday but 1 grid distance long.
You cannot put the start of a note at the same point as the end (and vice versa).

Hope this helps.

[muzycian]

but i don't see a friendly way (=without using modifiers)

what about left click + right click?

Ok, i think i found something:

Shift + Click Pencil = Lasso select parts/events, extending the current selection!

Shift + Doubleclick Pencil = Select None

So you can start a new selection with the pencil tool by "Shift - clickclick - lasso"

So you can extend a selection with the pencil tool by "Shift - click - lasso"



Works in both the composer and the note editor.

Now the pencil tool can almost do everything:

New selection: hold shift, doubleclick and drag
Extend selection: hold shift, click and drag
Draw new part/event: click+drag in background
Change start or length: click+drag when pencil hovers start/end
Move: click with arrow in middle of part/event and drag around
Copy: same as move but hold control
Copy+duplicate: same as copy but also hold shift
Delete part/event: hold alt while pencil hovers start/end
Monitor event/key in note editor: hold alt while clicking (not when pencil hovers start/end <-> delete event)

(this info is copied to the docs)

Now you could ask: why is the arrow tool still there?

Well because the pencil tool is powerful but you need to know things before you can use all of it.

So for mu.lab newbies the arrow tool is a straightforward selection tool.

[jens]

Sounds great to me!

[muzycian]

Thanks for putting me on the rails 'bout this jens!