MuLab 4.3 (incl Win 64 bit version)

[pljones]

Oopses...

I did Templates->New, set some stuff up, then closed (without having saved). MuLab asked if I wanted to save and I said yes. It saved. To the New.MuSession template... which was unexpected...

I inserted Reaper as a Rewire plugin. The signal doesn't appear to be getting through at all. Is it just me, just Reaper or ..?

(EDIT: Just checked, doesn't work in 4.3.1 32bit, either...)

And are there any noticeable advantages of the 64-bit version?

There are no advantages other than large sample libs can load under 64bit. As this did not happen yet, it makes no difference to me.

Heh, the session I mention above loads up and the process space is 2,641,636Kb... 64bit is one reason I've used Reaper in the past.

[fluffy_little_something]

And are there any noticeable advantages of the 64-bit version?

There are no advantages other than large sample libs can load under 64bit. As this did not happen yet, it makes no difference to me.

So I suppose it is good for the guy who wanted to get Omnisphere...

I hope CPU usage will be reduced once multi-core support is implemented. 64-bits don't seem to have anything to do with that.

[MuTools]

By the way... "Analog Marimba 2" seems to have wandered off at some point.

Confirmed. I'll research & fix.

[MuTools]

So should I bother with this on OSX.

There are some other new/improved things in M4.3 as well, so yes

I'd love to launch MuLab and not have to go into the midi setup each time...

I know. Sorry that i can't do everything at the same time.

If I go to Snow Lion what is going to happen?

OSX indeed is a very volatile platform.

[MuTools]

And are there any noticeable advantages of the 64-bit version?

I've the impression this 64 bit version is a bit faster too.

[pljones]

And are there any noticeable advantages of the 64-bit version?

I've the impression this 64 bit version is a bit faster too.

It's subtle but the UI does definitely feel more responsive.

[MuTools]

I thought the 64-bit version was planned for much later this year (I think I read somewhere that multi-core support was higher on your list of priorities).

Indeed, for MuLab multi-core had higher priority than 64 bit. But while developing the MUX Vst, i concluded that a 64 bit version for the MUX Vst was necessary from the start. That's why i switched priorities. Developing the 64 bit version for MuLab and MUX Vst is 99.9% the same job. The updated MUX Vst 32+64 bit packages will be available soon.

[fluffy_little_something]

And are there any noticeable advantages of the 64-bit version?

I've the impression this 64 bit version is a bit faster too.

If the old version is not fast enough, I can always increase the bpm value

[fluffy_little_something]

I thought the 64-bit version was planned for much later this year (I think I read somewhere that multi-core support was higher on your list of priorities).

Indeed, for MuLab multi-core had higher priority than 64 bit. But while developing the MUX Vst, i concluded that a 64 bit version for the MUX Vst was necessary from the start. That's why i switched priorities. Developing the 64 bit version for MuLab and MUX Vst is 99.9% the same job. The updated MUX Vst 32+64 bit packages will be available soon.

Fair enough...

[MuTools]

And are there any noticeable advantages of the 64-bit version?

I've the impression this 64 bit version is a bit faster too.

If the old version is not fast enough, I can always increase the bpm value

I meant CPU wise, not tempo wise. But you knew that right

[sl23]

Do you plan on combining the 32/64 bit exe files so there's just one set of files which auto detect the system your using?

If not, how about combining the two zip folders into one? So when you d/l an update you get this in the zip file:
MuLab.exe
MuLab64.exe
User folder
App folder
App64 folder (if different from 32bit folder)

[pljones]

Do you plan on combining the 32/64 bit exe files so there's just one set of files which auto detect the system your using?

If not, how about combining the two zip folders into one? So when you d/l an update you get this in the zip file:
MuLab.exe
MuLab64.exe
User folder
App folder
App64 folder (if different from 32bit folder)

Please don't do this. I've never seen it done and it would completely mess up my filing system. The settings for the two installs will be different (different VST plugin folders, etc), for a start...

[fluffy_little_something]

Do you plan on combining the 32/64 bit exe files so there's just one set of files which auto detect the system your using?

If not, how about combining the two zip folders into one? So when you d/l an update you get this in the zip file:
MuLab.exe
MuLab64.exe
User folder
App folder
App64 folder (if different from 32bit folder)

Please don't do this. I've never seen it done and it would completely mess up my filing system. The settings for the two installs will be different (different VST plugin folders, etc), for a start...

Not to mention that you would have to download much more than you actually need, and that with every update.

[fluffy_little_something]

And are there any noticeable advantages of the 64-bit version?

I've the impression this 64 bit version is a bit faster too.

If the old version is not fast enough, I can always increase the bpm value

I meant CPU wise, not tempo wise. But you knew that right

Yes. German sense of humor, sorry

[pljones]

I inserted Reaper as a Rewire plugin. The signal doesn't appear to be getting through at all. Is it just me, just Reaper or ..?

OK, confirmed as "just me" (I shall not elaborate further... )

MUX (32bit) works bridged from Reaper x64 via ReWire from MULAB 64bit. As does MuVerb.