MuLab 5.0.31 Test

[torgo]

Haven't checked in the new .28 yet, but have seen this in .27 (and in M4):

In audio setup, when selecting inputs or outputs, if your sound card has more ins/outs available than will fit on the screen, you're stuck. There's no scroll bar on the select input window, you can't get down to the ok/cancel buttons, and there's no way to close the window.

Even if you go to the desktop and resize the display, the select input window is still cropped - taking up less space on the screen, but still without the bottom in/out choices, the buttons, or any way to close the window.

A scroll bar on those windows would be quite helpful, so that you can always get down to the bottom to close the window no matter how many audio in/outs the system has.




And I'll repeat the earlier request for a section in the docs on time signatures and quantization - and probably also having the auto-quantize turned off as the default for new compositions. That way first-time users won't record a part with trills, fast runs or strummed chords and wonder why MuLab trashed it.

I know digit was only trying to be helpful with that earlier response, but I think it's important to make stuff like that as obvious as possible for beginners and new users.

[Crackbaby]

Am i supposed to have a key for mulab 5? (i bought 4 UL)
My mulab 4 keys are invalid .. naturally..

[MuTools]

MuLab 5 UL user keys will be distributed upon release. If you want it now already, send me an email

[MuTools]

In audio setup, when selecting inputs or outputs, if your sound card has more ins/outs available than will fit on the screen, you're stuck. There's no scroll bar on the select input window, you can't get down to the ok/cancel buttons, and there's no way to close the window.

You can alt-click the borders of a window so to move it. That way you can move it so you can see the top/bottom. This is a kind of SOS way in case a window is too big for the screen.

That said, i'll finetune the Audio Setup dialog so to anticipate on this situation.

And I'll repeat the earlier request for a section in the docs on time signatures and quantization

I've read your suggestion, thx.
Please read http://www.kvraudio.com/forum/viewtopic.php?t=357048

I'll also do my very best to make MuLab as self-explanatory as possible so the need for (boring) docs gets as low as possible. Docs are a necessary thing for sure but atoh only a minority of users read them.

[MuTools]

You can alt-click the borders of a window so to move it. That way you can move it so you can see the top/bottom. This is a kind of SOS way in case a window is too big for the screen.

Just noticed that you can't move a window above the top of the screen, tuned that in the next version.

[Trancit]

Bug:

Import Sample Loop...
Open the Sequence in the key editor...

What do you see??? No notes (except the velocity lines underneath) and a very short vertical scrollbar on the right...(only visible C4 and up)

If you zoom in by mousewheel or plus button, the vertical scrollbar gets updated and you can scroll down to the notes...

[Trancit]

Bug:

Import Sample Loop...
Open the Sequence in the key editor...

What do you see??? No notes (except the velocity lines underneath) and a very short vertical scrollbar on the right...(only visible C4 and up)

If you zoom in by mousewheel or plus button, the vertical scrollbar gets updated and you can scroll down to the notes...

Addition: after zooming in, you can scroll to the notes, but the keyboard (lefthand side) doesn't scroll too...

If zoom on the keyboard or open another sequence in the key editor and then go back to the loop sequence, everything is fine...

[Crackbaby]

I tried Ace beta in mulab 5 beta and switched on the multicore support in Ace. My system froze and forced me a physical reboot.

http://www.kvraudio.com/forum/viewtopic.php?t=365340

Same thing with Diva (when turning on multi-thread support in the UI)

That said, it seems like Mutools splits Diva over the four cores anyway? That's what my process manager says.

[torgo]

I'll also do my very best to make MuLab as self-explanatory as possible so the need for (boring) docs gets as low as possible. Docs are a necessary thing for sure but atoh only a minority of users read them.

Thanks. The other "instant" solution would be to have "no grid" as the standard default for new compositions. Those of us who want auto-quantize can easily turn it on and even save it as our own default in a template.

But for new users (particularly beginners, who might not even be aware that quantizing exists and wouldn't know the word to Google the docs), a "what you play is what you get" default setting would probably be best.

Just noticed that you can't move a window above the top of the screen, tuned that in the next version.

The other oddity along those lines is that changing screen resolution didn't help either. That was the one that surprised me. If you increase resolution, you get a clipped version of the window. You can move it anywhere you want, but the buttons aren't there, so you still can't close it.

The scroll bar will be a huge help. Thanks. (I tried running M5 on a system with three Delta 1010s. The audio input configuration screen essentially killed it since there was no way to close that window.)

[AndreasD]

I tried Ace beta in mulab 5 beta and switched on the multicore support in Ace. My system froze and forced me a physical reboot.

Same thing with Diva (when turning on multi-thread support in the UI)

That said, it seems like Mutools splits Diva over the four cores anyway? That's what my process manager says.

I can confirm that. Might be a conflict between two multicore implementations. At least the Mulab multicore plays multiple ACE (multicore off) much better than the single core version. So, having ACE/Diva with MC off, works fine with me.

[Stephan326]

Is there a way to easily define the MuClip per note transients. Most of the loops I drag in have clicks and pops because of where the samples have been automatically defined.

[sl23]

Thanks. The other "instant" solution would be to have "no grid" as the standard default for new compositions. Those of us who want auto-quantize can easily turn it on and even save it as our own default in a template.

But for new users (particularly beginners, who might not even be aware that quantizing exists and wouldn't know the word to Google the docs), a "what you play is what you get" default setting would probably be best.

I disagree. When I bought my first keyboard, an XP-60, I knew nothing about making music, and I do mean NOTHING. I switched Quantise off as I thought it'd be more 'natural' but I quickly learned it's a necessary tool, for beginners especially.

It would be easier for advanced users to create a template than a beginner.

[Trancit]

Is there a way to easily define the MuClip per note transients. Most of the loops I drag in have clicks and pops because of where the samples have been automatically defined.

Not absolutely sure, what you mean, but i.e. if you drag an audio loop from the audio or sample tab of the browser into the composition window or use the Session menu command "Import sample loop", it creates a sequence pointing to a Multisampla with the "sliced" loop loaded...

The automatic transient detection is a bit poor and needs finetuning, which is done from the sequence:

Rightclick the sequence and choose from the context menu: "Edit sample"...

This opens up the Audio Lab with the audio loop loaded and (normaly) a bunch of markers...

Alt+ left click previews the audio in between 2 markers to identify clicks

Move the markers to "click-free" positions and insert new ones if needed...

After the marker work is done, rightclick in the audio lab window and choose from the context menu: "Update sliced sample part"...
This will update the sequence and the regions in the Multisampla and your loop should be (mostly) fine in terms of what is possible ...

Now you can drag this sequence into the browser to save the loop as a muclip...


Not sure, if this was your question though

[Stephan326]

It does answer it. although you are right. the function should perform a bit better..

[MuTools]

Thanks. The other "instant" solution would be to have "no grid" as the standard default for new compositions. Those of us who want auto-quantize can easily turn it on and even save it as our own default in a template.

But for new users (particularly beginners, who might not even be aware that quantizing exists and wouldn't know the word to Google the docs), a "what you play is what you get" default setting would probably be best.

I disagree. When I bought my first keyboard, an XP-60, I knew nothing about making music, and I do mean NOTHING. I switched Quantise off as I thought it'd be more 'natural' but I quickly learned it's a necessary tool, for beginners especially.

It would be easier for advanced users to create a template than a beginner.

+1.