MuLab 7.0.47

[Taron]

Which demo song?

AH, sorry, I mean the default setup...it was late last night! When you start up mulab for the first time, you know. (...without key. Haven't asked you for the key, yet. May I ask now?)

That startup setup: [MuDrum] [A Space Journey]

If you just make patterns with the mouse, both MuDrum and I Like Moog go straight up to max amp. One more note and it clips.
Ideally you go up no higher than -3db, you know, leaving some room for the mix. And total perfection would be a limiter on the master that is dialed in to the arrangement.

As for the mouse cursor, it's well worth fixing! Either just drop the misleading eraser cursor altogether or set it to eraser when the right mouse button has been used and is held. Right now, holding right mouse button goes into PANNING, which really should be middle mouse button!

Some fine tuning of that handling is pretty recommendable.

[Taifunk]

I was able to recreate the error previously reported, this time has not disappeared inputs, but it appeared an input in musynth. Edit:I attached the patch

The Musynth having a modulation input, that's indeed a strange and serious issue! How can i repeat that? Any hints on the type of actions you do when such inputs appear/disappear?

while I built the patch I noticed this ,It has often happened dragging the module from the rack
the step sequencer inputs/output disappeared and reappeared after
the modulation input in musynth it is still there when I open the patches I posted.
Tomorrow I will try to do some tests and capture the problem

I had forgotten a particular about the problem ,this occurs only after you reload the patch and modifying the same patch not when starting a project from scratch.
now the problem after several test seems not happen again but maybe something is related to another problem happened now
I tried to do some non-permitted actions ,when you drag a mux rack from the modular area in the same mux ,Instead of appearing "this is not allowed" mulab crashes previously I had noticed and reported that something strange happens but I had not realized it was related to this.
and I noticed that there is a problem with the "this is not allowed"
for example by connecting a vst to audio to modulation converter It appeared the message
I closed and reopened mulab and everything is back to work
same with the problems related to the input/outputs that disappear.
maybe a problem with my system and windows permission?

problems related to the input/outputs that disappear

EDIT:ok I confirm,impossible to reproduce the problem this problem occurs only with version 7.04 (and I can not replicate)
Now everything seems to be solved and related to what I said before
tried with all previous versions the problem does not recur, only if you load the patch I've sent appears the green input in musynth
after I have done the following actions
delete the old installation, also eliminated the M6 folder,cleaned the system registry , created mutools folder in c: copied m7 folder and updated whit 7.06 files, started as administrator ,Now everything seems to work and I can not reproduce in any way the error
but remains the problem related to "this is not allowed" the message does not appear with some non-permitted actions and mulab freezes

a question , vst fx in the modular area receive events even when not connected to an event input?

[bibz1st]

Happy to report the Randomizer seems sorted now

[MuTools]

Which demo song?

AH, sorry, I mean the default setup...

Ok taken note, will check.

Haven't asked you for the key, yet. May I ask now?)

Sure, pls email me.

[MuTools]

Happy to report the Randomizer seems sorted now

Thx

[MuTools]

There is a new M7.0.7 in http://www.mutools.com/galaxa/

What's changed:

Removed the "Right-Click = Delete Notes" preference and made that standard behavior in the piano roll editor. So now there are only 2 simple ways to delete notes with the mouse: Double-click them, or right-click them.

Updated doc page: http://www.mutools.com/galaxa/docs/mula ... ditor.html

So mouse tool usage in the piano roll should be unambiguous and easier and faster now and answering the most requested behavior. I hope this new behaviour suits all users. Pls let me know.

How to update:

OSX: Replace the existing M7 MuLab.app file by the new version in the small zip file.

Windows: Replace the existing M7 MuLab.exe and MuLab.ID files by the new versions in the small zip file.

[runaudio]

this is great liking the right click easier and faster now

[Taifunk]

+1 that's great

[bbreakz]

is it possible to create a return on stop action?
if I stop playback in the middle of a loop, I'd like it to return to the start position/loop position.

[runaudio]

+1 return to the start position/loop position.

[MuTools]

It's already in there: Shortcut function "Play / Stop-And-Return"

[pljones]

Removed the "Right-Click = Delete Notes" preference and made that standard behavior in the piano roll editor.

Hm, so to quantize notes, I have to select them the right-click somewhere else rather than the selection (otherwise I deleted the notes) to get the right-click menu -- I realise this hasn't changed, it still feels wrong that right-click on the selection doesn't get it's context menu to me but I guess most people seem to think it's more obvious to delete. As Ctrl isn't currently modifying right-click behaviour, maybe that could be used to bring up the context menu on the note selection?

Other than that, it feels a lot nicer not having the hover-eraser.

[Taron]

Does it still say 7.0.2 or am I downloading the wrong windows 64bit file?
Just want to make sure, because the mouse cursor still shows the eraser when hovering over notes in the pattern editor.

[sl23]

I agree with pljones on this, it seems strange to right click elsewhere to show an items context menu?!

[MuTools]

it still feels wrong that right-click on the selection doesn't get it's context menu to me but I guess most people seem to think it's more obvious to delete. As Ctrl isn't currently modifying right-click behaviour, maybe that could be used to bring up the context menu on the note selection?

I agree with pljones on this, it seems strange to right click elsewhere to show an items context menu?!

That's why i have been trying to avoid right-click = delete for many years. But in the end it seems to cause more pain than gain. So in the end i agree with what many users have been asking for a long time: Right-click note = delete note. Pls search this forum for all posts on this topic, recent and longer time ago.

I won't go for the [Ctrl]+click a note to open the part/sequence context menu for 2 reasons:

1) It's indeed so that right-click on note = delete note is an exception on the right-click rule. But as stated above, after years of debate over this i' have been convinced that this is the only pragmatic solution, with the biggest balance between gain/pain. Now that said i don't think it's a good idea to make another exception upon than exception.

2) In principle a right-click opens the context menu for the clicked object. Notes don't have a context menu. If you want the context menu of the part/sequence, right-click the background. In fact that's constistent behaviour as it is now.

All this said there is one thing i can do and though i prefered to avoid it it's ok with me to do so: Making the right-click = delete notes a preference again. But then if you would switch it to Off then you return to the M6 behavior which has some imperfections too, as has been pointed out by users. Again i'd prefer not making it a preference, so pls don't request this if it's not really really necessary. The background area for right-clicking the part/sequence context menu usually is much much bigger than the area taken by notes so i think the new behavior should not be a problem, more a little shift in what we're used too, but in the end with a better feel and faster workflow.