MuTools

Nielzie · Post by **Nielzie** » Wed Nov 23, 2011 5:34 pm

mutools wrote:
Nielzie wrote:Jo, could it be possible when hovering over the cpu meter bar with the mouse to give give a read out of the current processor load percentage instead of just "CPU Meter"? That would be very convenient
Can't do this atm, sorry.
Feel free to resend this FR some time after M4 has been released.

Ok, will do

MuTools · Post by **MuTools** » Wed Nov 23, 2011 7:29 pm

Background info: Unfortunately there is no time anymore for additional feature implementations in MuLab 4.0. The time left between now and release will all be invested in stabelizing, optimizing and finalizing M4.0. Only bugs and real workflow probs will be handled before 4.0 release. (besides finalizing the library, the skin and the docs).

flugel45 · Post by **flugel45** » Thu Nov 24, 2011 7:30 am

It's been ages since I looked at Mu.lab (v1)...

I'll get straight to my main question: Is it 64-bit native yet (Or coming in M4)?

Thanks.

MuTools · Post by **MuTools** » Thu Nov 24, 2011 8:32 am

No, not yet.
Taking the risk i'm asking something stupid: Why do you need 64-bit?
I mean: The 32-bit version runs fine on a 64-bit system.
And afaik (almost) all 64-bit vsts also exist as 32-bit, right?
So what's really missing today?

That asked, i'm sure MuLab will make the move one day once i got the tools.

pljones · Post by **pljones** » Thu Nov 24, 2011 8:37 am

Multi-processor support is more pressing than 64bit support, in my view - the performance gains are likely to be far, far higher.

Nielzie · Post by **Nielzie** » Thu Nov 24, 2011 9:10 am

The only gain with a 64-bit version would be that it can access more RAM (beyond the 32-bit 4GB limit), which would make it a better choice when using many sample(r)s.

I agree that multi-processor support is more favourable atm.

flugel45 · Post by **flugel45** » Thu Nov 24, 2011 9:39 am

mutools wrote:No, not yet.
Taking the risk i'm asking something stupid: Why do you need 64-bit?
I mean: The 32-bit version runs fine on a 64-bit system.
And afaik (almost) all 64-bit vsts also exist as 32-bit, right?
So what's really missing today?

That asked, i'm sure MuLab will make the move one day once i got the tools.

Thanks for the quick reply.

You are correct - for some reason I was thinking in terms of MULAB being hosted - not as a host. Good to hear it runs fine under 64 bit OS!

Lack of multi-processor support is a concern, though, as I use a lot of plugs in my projects, and utilizing only 1 of the 4 cores in my system would be a huge step back for me.

Will certainly keep an eye on future development.

Trancit · Post by **Trancit** » Thu Nov 24, 2011 2:01 pm

flugel45 wrote: Lack of multi-processor support is a concern, though, as I use a lot of plugs in my projects, and utilizing only 1 of the 4 cores in my system would be a huge step back for me.

You are not alone...

Branis · Post by **Branis** » Fri Nov 25, 2011 8:43 pm

When moving sends to different slots in a Rack, it turns to "send to nothing". The same happens if you copy a send and paste it to another slot, it gets pasted as "send to nothing".

pljones · Post by **pljones** » Fri Nov 25, 2011 9:46 pm

Ah, that must be what happened to me back on page 5...

I never did track it down.

MuTools · Post by **MuTools** » Fri Nov 25, 2011 10:17 pm

Branis wrote:When moving sends to different slots in a Rack, it turns to "send to nothing". The same happens if you copy a send and paste it to another slot, it gets pasted as "send to nothing".

Yes that's normal behaviour, a consequence of how things are wired up. Can't do much about this at the moment, but i've added a note on the future wishlist.

MuTools · Post by **MuTools** » Fri Nov 25, 2011 10:18 pm

There is an updated M4065 patch in the same webfolder.
The change-log tells what's changed.

sorohanro · Post by **sorohanro** » Fri Nov 25, 2011 10:31 pm

Can I try also the new version ?

pljones · Post by **pljones** » Fri Nov 25, 2011 11:11 pm

4.0.65 and ugh. Forgot to turn on my AudioFire, got the "Unable to start audio engine", so hit close on the main window. After clicking the quit-no-save option, MULAB hung until "Internal thread loop time-out error @ abstrctdngn[225]". (Okaying that proceeded as expected to the "do you really want to quit?" dialog.)

MuTools · Post by **MuTools** » Sat Nov 26, 2011 11:06 am

sorohanro wrote:Can I try also the new version ?

Sent you an email

MuTools

KVR Audio

M4 Test