MuLab 4.3 (incl Win 64 bit version)

[sl23]

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...

Why would there be two seperate install folders or VST folders? There's only one user directory for both versions which is where you'd put VST's, and if the App folder data is the same for both versions you could simply have one App folder and one User folder with only the need for both exe's. I don't see how that messes any file structure up?

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

So what about those users who happens to store MuLab on a USB device and use the app on both systems (32 & 64bit)? They have to d/l and manage two seperate installations of the same program? I never understand why dev's do make two seperate exe's this way when others combine them and auto detect which OS is being used, is there a reason for this? I'm no programmer so I wouldn't have a clue, perhaps there is a reason, just seems strange how some are combined and some aren't. Is it lack of knowledge/ability, limitations in the programming language or just laziness/easier? No offense meant there Jo, sorry, just curious.

[fluffy_little_something]

Well, I bet most people still use their DAW in a conventional way, i.e. on only one computer. And if you wish, you can always download both versions onto your USB drive. Most other programs also come in two or more separate versions...

[MuTools]

I've been asking myself the same question: Single package or separate packages. Well, the exe is different for 32 bit and 64 bit, that's a fact.
I experimented with a single package containing both exe files, but as others mentioned, some user settings (eg VST plugins) will be dependent on the platorm too, so that would have to be split. Also the LibResample.dll is different per platform. So we'll end up with a 'splitted common' package. That's why i then chose to keep it simple for now and put it in 2 separate packages. Both options (single or separate packages) have their advantages and disadvantages i think. And as you can read from the other posts, opinions are differentiated too. Feel free to elaborate further.

[MuTools]

Well, I bet most people still use their DAW in a conventional way, i.e. on only one computer. And if you wish, you can always download both versions onto your USB drive. Most other programs also come in two or more separate versions...

Yes i see it the same way.

[sl23]

Also the LibResample.dll is different per platform.

But with these sorts of differentiations, can't you simply have two LibResample files:
LibResample.dll
LibResample64.dll

I've seen this in other programs. Can you just tell MuLab64 to look for these differentiations?

In the end I realise it depends on whether it's wanted by the majority, that's understandable. I mainly asked out of curiosity. I do principally use my 64bit laptop but sometimes use my 32bit PC too as it's connected to my 42" TV! So for me it'd save having to setup different locations for different projects and having to continually locate files that would normally be in the User folder.

[MuTools]

Also the LibResample.dll is different per platform.

But with these sorts of differentiations, can't you simply have two LibResample files:
LibResample.dll
LibResample64.dll

I've seen this in other programs. Can you just tell MuLab64 to look for these differentiations?

Sure. And if it was only about this file i certainly would have chosen a single package. But as you can read there are other aspects too.

In the end I realise it depends on whether it's wanted by the majority, that's understandable. I mainly asked out of curiosity. I do principally use my 64bit laptop but sometimes use my 32bit PC too as it's connected to my 42" TV! So for me it'd save having to setup different locations for different projects and having to continually locate files that would normally be in the User folder.

Note that you can use a common user library folder: (copied from the docs)

By default your user library folder is located at the User/Library sub-folder in your MuLab installation folder. But you can set a specific folder on your system to be your MuLab User Library folder. This is done by editing MuLab/User/Settings/PreferredFilesAndFolders.Txt and update the line starting with UserLibraryFolderPath so it points to the folder you want.

This is also a handy tip if you use MuLab and MUX Vst on the same system

[MuTools]

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...

In trying to understand all aspects wrt single/separate packages, this question:

Why would a single 32 + 64 bit package completely mess up your filing system?

[MuTools]

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)

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

Having all in a single package also has advantages. Ok, if you only use it on 1 platform, then you have downloaded a couple of redundant MBs, but that's not too heavy, is it?

I'm just trying to list all advantages/disadvantages for single and separate package distributions.

[sl23]

Thanks for pointing that out Jo, I thought the same but didn't want to say.

if it was only about this file i certainly would have chosen a single package. But as you can read there are other aspects too.

What are the disadvantages? Are there many other files than LibResample.dll that would need this change?

[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)

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

Having all in a single package also has advantages. Ok, if you only use it on 1 platform, then you have downloaded a couple of redundant MBs, but that's not too heavy, is it?

I'm just trying to list all advantages/disadvantages for single and separate package distributions.

Depends on the kind of Internet access you have
Downloads was one reason I abandoned FL...

[sl23]

My d/l is limited too, I use a tethered connection to my mobile phone. I get free browsing with 150MB d/l limit a month. I can still d/l but at dial-up speeds. Only costs me £20 for 6months, you can't beat that! I don't d/l much anymore apart from app updates so it's good enough for me and my girlfriend, she loves eBay and Facebook

[AndreasD]

You will need two VSTPlugins files (where the scanned plug ins are saved) and it's probably better to store the sessions in different folders for 32/64bit as not all my VSTs are available in 64bit. Plus, products like u-he uses different names for 32/64bit plug ins (renaming them works, but then you have two u-he installation folders where patch exchange would not work).

I thought about combining 32/64 manually, but abandoned the idea.

[fluffy_little_something]

My d/l is limited too, I use a tethered connection to my mobile phone. I get free browsing with 150MB d/l limit a month. I can still d/l but at dial-up speeds. Only costs me £20 for 6months, you can't beat that! I don't d/l much anymore apart from app updates so it's good enough for me and my girlfriend, she loves eBay and Facebook

Wow, that's even worse than my access And still, we both got it much better than most people in developing countries.

[sl23]

Why would you need seperate Sessions folders for 32/64bit VST's? MuLab shows all VST's in it's list whether 32 or 64bit so not sure what you mean, though I do understand if it creates seperate folders for settings if that's something you don't want, but is it a problem at all?

Isn't there now an option to rename plugins within MuLab? Does it matter if they have different names? Just curious why you see it as a problem that's all

[MuTools]

Thanks for pointing that out Jo, I thought the same but didn't want to say.

if it was only about this file i certainly would have chosen a single package. But as you can read there are other aspects too.

What are the disadvantages? Are there many other files than LibResample.dll that would need this change?

See the other posts here.