The MuLab 4.3.1 pre-release is available in http://www.mutools.com/mulab/cedar

How to install: http://www.mutools.com/mulab/docs/installation.html

What's changed since M4.2.2:

• Windows: Both 32 bit and 64 bit versions.
  
• When previewing audio files and samples, user now has more control over the preview volume, pitch etc...
  
• You can now rename VST plugins apart from their DLL name.
  
• Event Delay: Delay Time display includes the units.
  
• "Add New Audio Track" now also monitors the audio file while browsing.
  
• In some cases an empty tool tip was shown.
  

About a 64 bit version for OSX: The OSX abstraction layer needs a serious rewrite in order to do so. I expect this to be done in the M5 development stage.

Cheers!
Last edited by mutools on Sat Jun 30, 2012 3:39 am; edited 1 time in total

About this sample preview: The first time you preview a sample this will create an "Audio File Previewer" in the session MUX, if no such exists already.
Then you can change all kind of aspects of that specific sample player (e.g. volume, pitch) or even setup an FX rack after it etc. All is saved with your session Of course you can also save it in your default template session.

Jo, I know it's probably completely uneconomic but is it worth looking at a Linux and/or JACK port whilst rewriting the abstraction layer?

4.3.1 64bit doesn't let me pick anything but "None" as the audio driver when I install it under "C:\Program Files" with the same permissions as 32bit (under "C:\Program Files (x86)"). The licence agreement pop up appears every time I run, too. So I'm guessing it's got problems writing settings.

(Edit: Just to confirm, run from a non-protected folder, it's fine. Like I say, usually Win7's magic seems to make the settings go somewhere else (%LOCALAPPDATA%?) automatically, so I was surprised it didn't work for the x64 version.)

If many people would want this, then i'll evaluate. It also must make sense economicly, otherwise i'm taking risks wrt the future of MuLab, MUX, ...

Technically the OSX abstraction layer and a Linux abstraction layer would be 2 different things, maybe with some overlaps as they both share a common base. But the OSX side is all about Cocoa, that's not there in Linux.
Last edited by mutools on Sat Jun 30, 2012 4:03 am; edited 1 time in total

Yes, cfr the install info ( http://www.mutools.com/mulab/docs/installation.html ) it's recommended not to install MuLab in Program Files. That Win 7 virtual store thing is absurd, imho.

(It's so weird - I install under "Program Files (x86)" by deleting the folder and copying in afresh, get told to do it as Admin and do; none of the set up files go there, as they're still magically found every time! Do the same under "Program Files" and it has a hissy fit... /sigh/ Computers, who'd have 'em?)

That was fast, I hope you don't burn yourself out
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). Is it bug-free already? I guess I will wait a couple of more releases, just in case...

Although I have W7 64-bit, I hardly have any programs and applications that support it, yet, so I have little experience with 64-bit stuff. Are sessions recorded in the 32-bit version compatible with, i.e. playable in the 64-bit version. There is a 64-bit version of my favorite synth vst as well, but I wonder if I could open the dozens of 32-bit patches I have already programmed.

And soon Windows 8 will be launched, probably more work ahead for you

64bit version works flawless on my system.

Great work!

[edit]: 32bit sessions load correctly, if you have the 64bit versions of any used VSTs installed. Mulab patches will load anyway if you copy the user folder in the 64bit install. Patches of VSTs appear to load in both 32 and 64bit versions (u-he, NI, Steinberg, Fabfilter)
Last edited by AndreasD on Sat Jun 30, 2012 4:31 am; edited 1 time in total

I don't quite understand. Why are you trying to "install" it in Programs in the first place? Is says somewhere that one is NOT supposed to install it like any other program. Basically Mulab is like a jpg or mp3 file, you can move it anywhere and run it from there. I have Mulab in my docs for backup folder on my desktop.
Last edited by fluffy_little_something on Sat Jun 30, 2012 4:30 am; edited 1 time in total

All data should be compatible - it's only the program code that is different.

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

Just scanning my 64bit plugins... seems much slower than the 32bit scan (but it's a while since I had to do the whole 32bit folder, fortunately!). OK, it's died on one (Camel Alchemy) - hm, but that's the plugin failing... (I hate "pop under" windows.)

No crashes during the scan - fantastic! Only one "Disabled" - iZotope Vinyl (no idea I had that - expired demo, I expect).

I have been running the 32bit version perfectly happily and having Win7 act like it's meant to act when a program attempts to write to Program Files (x86), by redirecting the writes to %LOCALAPPDATA%. Whilst that may surprise you to know that Win7 actually worked for me, I was surprised when it stopped working with the 64bit version. I guess Microsoft think that by the time an app is converted to 64bit, it should also be converted to using their new config data system...

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

So should I bother with this on OSX. I'd love to launch MuLab and not have to go into the midi setup each time... If I go to Snow Lion what is going to happen?

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.