MuLab 6.0.35 released

[MuTools]

A variety, nothing particular, but with an emphasys on the 'major' ones.
Is the problem you're experiencing repeatable?
Is it also repeatable with other VSTs?

The crash has not been repeatable so far, as I said it was the first crash of that kind.
Some plugins becoming irresponsive for some time has happened before, yes. But I don't know what to do in order to "achieve" that on purpose And after a while, they become responsive again.

And that was not the case in MuLab 5? Is it all the time about SE plugins?

[fluffy_little_something]

A variety, nothing particular, but with an emphasys on the 'major' ones.
Is the problem you're experiencing repeatable?
Is it also repeatable with other VSTs?

The crash has not been repeatable so far, as I said it was the first crash of that kind.
Some plugins becoming irresponsive for some time has happened before, yes. But I don't know what to do in order to "achieve" that on purpose And after a while, they become responsive again.

And that was not the case in MuLab 5? Is it all the time about SE plugins?

As I said it already was the case in previous versions as well.
And yes, since I never use anything else, it was always SE stuff, mostly Superwave and Phonec. No idea if it would also happen with Diva etc.
There is one plugin which I know has a bug, and the developer confirmed it, but he can't change it because it has to do with a third-party SE module. I no longer use that plugin, though.

Does Mulab log crashes?

[fluffy_little_something]

Ah, found the logging thingy

[bbreakz]

Hmm... Yeah I noticed that and found it a bit inconvenient at times.

Perhaps those grey buttons should have the same windows functions as other MuLab windows? ie Minimise/Restore and Close.

Could you change the default behaviour for opening a Rack using the track button to single-click (or give option to change it for those that like current double-click)

yeah that would be cool...

-also... just curious as to when official release for M6 might be...
thanks!

[yul]

Hello can I use my M5 key to authorize it? It doesn't seem to work. What's the deal for existing users please?
Thanks.

[dakkra]

Upgrade you M5 UL for 17 EUR

http://mutools.com/shop.html

[Reincke]

Hi, I'm on M6 too. It's a well done release and works fine even on my 4 year old netbook hardware.
There is one thing that really puzzles me: The new mouse behaviour inside the sequence editor. In M6 there are two modes, arrow and pencil. The "Default mouse tool" in M6 is "pencil", the M5-mode was similar to "arrow". No prob, I changed the default in MuLab's preferences to "arrow", and voila: new sequences will get the arrow mode like in M5.
HOWEVER: all existent sequences remain in pencil mode, even after restart MuLab. That's not what I'm expecting. Am I doing something wrong?
JR

[fluffy_little_something]

I think error logging should always be on, and that only the three latest logs should be kept so that when closing Mulab for the 4th time, the first log automatically gets deleted. This would prevent a build-up of logs. The last three logs should be enough to do troubleshooting.

[MuTools]

There is one thing that really puzzles me: The new mouse behaviour inside the sequence editor. In M6 there are two modes, arrow and pencil. The "Default mouse tool" in M6 is "pencil", the M5-mode was similar to "arrow". No prob, I changed the default in MuLab's preferences to "arrow", and voila: new sequences will get the arrow mode like in M5.
HOWEVER: all existent sequences remain in pencil mode, even after restart MuLab. That's not what I'm expecting. Am I doing something wrong?

I checked it here and when i set Default Mouse Tool to arrow, then any new part i draw indeed gets the arrow tool by default. When i load a session, also there the parts get the default arrow mouse tool. Did you reload the session after changing that preference?

[sbj]

There is one thing that really puzzles me: The new mouse behaviour inside the sequence editor. In M6 there are two modes, arrow and pencil. The "Default mouse tool" in M6 is "pencil", the M5-mode was similar to "arrow". No prob, I changed the default in MuLab's preferences to "arrow", and voila: new sequences will get the arrow mode like in M5.
HOWEVER: all existent sequences remain in pencil mode, even after restart MuLab. That's not what I'm expecting. Am I doing something wrong?

I checked it here and when i set Default Mouse Tool to arrow, then any new part i draw indeed gets the arrow tool by default. When i load a session, also there the parts get the default arrow mouse tool. Did you reload the session after changing that preference?

I have the same situation after changing the preference from pencil to
arrow and reloading the session. They're still pencil.

Windows 7 64 bit

[MuTools]

The preference is only used when creating new parts or when loading M4/M5 parts.
So if it is a session saved with M5 then the default tool should be the preference one.
If it's a session saved with M6 then the tool is the one when you saved the session because the tool is saved per sequence part. Does this explain it?

[Reincke]

Does this explain it?

Yes, I see.
But why did you decide to save the tool mode per sequence part? Does anybody really need to have different parts with permanently different tool modes? And if so, why does the default tool differ from M5? (Sorry for this probing questions. People at my age can hardly get used to something new. )

Other question: I already saved the sessions with M6 before I switched the "default mouse tool". How can I change the tool mode for all parts (hundreds of parts!) in my sessions?
JR

[MuTools]

Does this explain it?

But why did you decide to save the tool mode per sequence part?

It's a collection of data that defines the editor context, like position, zoom, tool, ...

How can I change the tool mode for all parts (hundreds of parts!) in my sessions?

And that's all sequence parts? Or also audio and automation parts? Cause only sequence parts have two tools.
To answer your question: I'm sorry but there is no way to change the mouse tool for a selection of sequence parts.

[Reincke]

Thank you for the fast reply.

It's a collection of data that defines the editor context, like position, zoom, tool, ...

My question in fact was: Why did you decide to assign "mouse tool" to the editor context, not to the session context (or application context, if exists)?
Anyway, I'll revert to the previous sessions and keep your suggestion in mind. Thanks a lot.
JR

[fluffy_little_something]

Does this explain it?

Yes, I see.
But why did you decide to save the tool mode per sequence part? Does anybody really need to have different parts with permanently different tool modes? And if so, why does the default tool differ from M5? (Sorry for this probing questions. People at my age can hardly get used to something new. )

Other question: I already saved the sessions with M6 before I switched the "default mouse tool". How can I change the tool mode for all parts (hundreds of parts!) in my sessions?
JR

Gee, what is your age? Sounds like you are 80

I guess whenever software is updated, some people are not happy with the changes. Others might love those very changes.