MuLab 7.0.47

[MuTools]

Was playing around with v6 and noticed that when playing keys very gently, there is sometimes no sound at all, as if there were a velocity threshold. With other synths that is not the case, no matter how gently one plays, there is always a very silent sound.
Will that be changed in v7?

I don't understand what you mean.
There is no 'velocity threshold' in MuLab.
Can you pls be more specific.

Is there already a screenshot of v7 or do I have to download the beta for that?

http://www.kvraudio.com/forum/download/file.php?id=7574

[samardac]

MuLab 7 will be available very soon, i expect in about 1 or 2 weeks, if nothing unexpected pops up.
If you want to buy it right away, then please buy a MuLab 6 user key, email me about this and i'll send you a temporary M7 test user key. That's the quickest way to start using M7. Then when M7 is (pre)released you'll get a free upgrade to M7 ie. your permanent M7 user key.

Thanks I just asked because I thought that if I bought v6 and when you release v7 I'll have to buy it again.

[fluffy_little_something]

Oh, I thought Mulab/Mux was one of those synths that seem to have a velocity threshold. Just checked again, turning velocity sensitivity off in a patch. Then indeed there is no threshold (A velocity sensitivity of 100% is just not recommendable, though.)
On another synth I am currently demoing (Hybrid 3) that is unfortunately not the case, it's a weird feeling playing that synth and last night I thought it was the same with Mulab.

First I thought there was something wrong with my keyboard, but Sylenth works just the way - I think - it should be.
Do different synths handle the velocity values they receive from the controller in different ways, or is it always linear?

I don't see much of a difference judging from the screenshot. The news is probably under the hood But I notice that the record button has moved to the other drive buttons, good decision

[MuTools]

There is a new MuLab 7.0.26 in http://www.mutools.com/galaxa/mulab/

What's changed:

• Event List Editor: When multiple events are selected and one of these event's value is double-click to edit it, then the selection was unintendedly reset to that one event. Fixed.
• Fixed an issue with the anti-crack protection.
• Some other micro improvements.

How to update:
Make sure you already have installed the complete M7.0.24 package. Then:
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.
mutools.com

[Taifunk]

Thanks Jo
Edit:I forgot to say that I really like the new improvements for the level compressor

[Simon Posford]

Font are lovely like the good old times :p

By the way the bug about the popup (right click) is not fixed.

[MuTools]

By the way the bug about the popup (right click) is not fixed.

Which bug? Pls elaborate.

[Hermu]

audio rendering logic problem, after rendered audio track was deleted:

1. left mouse click on rack for track and select 'Render to audio track(s)' - rendered audio track was created
2. delete created audio track
3. left mouse click on rack for track and select 'Render to audio track(s)' - Check box ask for 'Overwrite last rendered version' and Yes was selected and track was rendered again, but no rendered audio track was created

[MuTools]

I'm not sure what's the most logical in that case cause you also told MuLab you don't want a track for that audio file. What do other users think: Should a new track be created again in that case?

[Hermu]

I'm not sure what's the most logical in that case cause you also told MuLab you don't want a track for that audio file. What do other users think: Should a new track be created again in that case?

Whatever the case may be, if i select 'Render to audio track(s)' - i would expect a rendered created audio track

[sl23]

If the option is given to perform an action and the action isn't performed, that's a bug?

That's my interpretation from what I can tell from that description.

If you render audio, delete it and then decide to either keep it or change it then rerender it, then why not? Yes it should, unless I missed the point here?!

[Taifunk]

Found a problem with the level compressor and audio envelope follower,after copying a modules the settings "use rms windows" is always on .

[MuTools]

Sorry you guys are right, i thought it was called Render To Audio File(s), but it's indeed Track(s) so yes. Ok will tune it.

[MuTools]

Found a problem with the level compressor and audio envelope follower,after copying a modules the settings "use rms windows" is always on .

Thanks for reporting, will be fixed in the next version.

[Taifunk]

Found a problem with the level compressor and audio envelope follower,after copying a modules the settings "use rms windows" is always on .

Thanks for reporting, will be fixed in the next version.

Thanks Jo
sorry for the delay in reporting but I noticed only now that this happens also when you reopen a project or patch,the settings are not saved properly.