MuTools

MuTools · Post by **MuTools** » Fri Dec 23, 2011 5:34 pm

Nielzie wrote:Thanks! Who's Calum by the way? I noticed he/she is mentioned quite frequently in the change logs

Calum designed the main skin 'LooxPhat'.

MuTools · Post by **MuTools** » Fri Dec 23, 2011 5:37 pm

Trancit wrote:Now you produced a graphic bug...
Modules in the MUX (either in the deep or in the play editor) don't get greyed out, if processing is turned off...not good

Yep noticed it too, but after the upload. Sorry about that. Fixing it. I reworked the way rack slots etc are done and it's all related.
I think the rack slots are perfect now.

mutools wrote:* Oscillators now have the option to start at fixed start phase from 0 to 359 degrees. See Oscillator context menu -> Edit Properties.
Thx very much for this...very usefull for harder attacks in unison sounds...

But atm I don't know how to translate the degree values...
For my understanding (e.g. a simple sine wave):
0 deg. = startpoint
90 deg. = first max of the wave
180 deg. = second zero crossing
270 deg. = minus max of the wave
359 deg. = short period before the wave ends...

Is that correct so far???

Yep!

MuTools · Post by **MuTools** » Sat Dec 24, 2011 1:11 am

Updated MuLab 4.0.80 packages in http://www.mutools.com/mulab/cedar

It's a full package update as some graphic files have changed, and the packages also contain more new patches by AndreasD. Thanks Andreas!

What's changed:

* Fixed an issue with the module boxes, they didn't show the muted state as intended.
* Even when racks/slots have no specific color, they get a default color when focussed.
* MuDrum: When copy-pasting a pad to another pad, the pasted one's name wasn't immediately refreshed. Fixed.
* Test alert has gone.

This is a first pre-release version.

pljones · Post by **pljones** » Sat Dec 24, 2011 8:31 am

mutools wrote:This is a first pre-release version.

Whee!!

Merry Christmas :harp:

MuTools · Post by **MuTools** » Sat Dec 24, 2011 11:24 am

Oops, the long working days have their consequences:
I forgot to include the new graphic files in the newest M4.0.80 package for Windows. Updated now. If you already downloaded M4.0.80 for Windows, please redownload. OSX package was/is ok.

> DiGiT < · Post by **> DiGiT <** » Sat Dec 24, 2011 11:46 am

using 4.0.80 i opened a track i made before and tried to delete a plugin from the master rack, top slot. it wouldnt give me a menu until i messed around with the next slot which was empty at the time. after i got the menu from the second slot, the first slot gave me a menu and i was able to delete my plugin.

MuTools · Post by **MuTools** » Sat Dec 24, 2011 11:50 am

That's weird. Is this repeatable? If yes, how?

> DiGiT < · Post by **> DiGiT <** » Sat Dec 24, 2011 11:56 am

it could have been because the plugins i had running were maxing the processor. i need to upgrade my computer.

MuTools · Post by **MuTools** » Sat Dec 24, 2011 12:19 pm

I still find it strange because one single advantage of MuLab not yet processing multi-cored is that the UI always keeps a core to do the job. So even when maxing out the audio process, the UI should stay snappy. That is supposed you have a dual (or more) core system, i assume you don't have a single core system, right? Thinking further: Maybe there were some other apps or plugins that were doing multi-core and so the UI performance was squeezed in that way?
During my experiments with multi-core i clearly noticed how the UI performance was squeezed as i was stressing multi-cored audio processing. That's logical of course. In the future MuLab MC you'll have the choice how many cores are used for audio; By default it's set to 'Auto' which is using all available cores. So on an 8 core system, for example, one could prefer to use 7 cores for audio and keep 1 for the UI.

> DiGiT < · Post by **> DiGiT <** » Sat Dec 24, 2011 12:49 pm

yeah im on a P4 single core. that must be why.

MuTools · Post by **MuTools** » Sat Dec 24, 2011 1:34 pm

Sorry bout my wrong assumption. Yes that explains things.
I want to add more dedicated and flexible mixdown functions aka freeze.
Whatever the system, it is always possible to reach the cpu limit.
So freezing will remain a handy feature on any machine i think.
I have a track-based mixdown scheme on paper, but it didn't make it in M4.0 cause i was running out of time. To be done.

> DiGiT < · Post by **> DiGiT <** » Sat Dec 24, 2011 4:08 pm

jo thanks for all your hard work. please let me know when M4 is up for sale and ill grab it from you. happy holidays.

Nielzie · Post by **Nielzie** » Sat Dec 24, 2011 7:11 pm

> DiGiT < wrote:jo thanks for all your hard work. please let me know when M4 is up for sale and ill grab it from you. happy holidays.

+1 I'll buy instantly

Won't be long I guess now it is in pre-release stadium

And a little reminder to squeeze the high res icon in the final package

pljones · Post by **pljones** » Sun Dec 25, 2011 10:34 am

Oops.

I tried "Cut" on a VSTi and got "Internal thread loop time-out error @ rddtprtctn[10]" - at this point MULAB needs a Task Manager kill to get out.

I'll see if it's reproducible.

--

Well, nearly - MULAB froze again but must have recovered before hitting the time-out limit.

The VSTi in question is KlangDrum. I'll see if others do it.

--

OK, I've been through my (limited) collection and can't find any others that behave the same. KlangDrum is a SynthEdit VSTi - I don't have any other recent ones to compare with.

AndreasD · Post by **AndreasD** » Sun Dec 25, 2011 10:49 am

"Cut" on a VSTi works fine here.
M4.0.80

Andreas

MuTools

KVR Audio

M4 Test