MuLab & MUX Vst 5.5.2

[fluffy_little_something]

While the Chrome association was deleted, the problem remains that Windows does not allow me to associate Mulab with Mulab session files anymore, it treats Mulab as if it were not there
I will replace Mulab except the user folder now, maybe that helps...

[fluffy_little_something]

While the Chrome association was deleted, the problem remains that Windows does not allow me to associate Mulab with Mulab session files anymore, it treats Mulab as if it were not there
I will replace Mulab except the user folder now, maybe that helps...

PS: No, it didn't. Seems I have to live with the fact I can't open Mulab sessions by clicking on them anymore...

[BlackWinny]

With Mulab you should never open a session from Windows.

When you open Mulab, in the gang screen you have buttons in a vertical grey panel in front of the Welcome panel. If you choose "Recent" it allows you to open a recent session, regarding the edition 32/64 bit. If when you exit Mulab you save yourself your sessions the little list opened shows you, among the sessions, this one with the name you gave when you saved it. And if you exit Mulab by clicking "Save and Quit" when you close directly Mulab, this button will show you this session by its timestamp.

And by this way, Mulab manages itself the place of your sessions (in the subdirectory "User\Library\MuSession\" of the actual edition of Mulab you are using for that session), so that Mulab shows you always the sessions which are made with this edition and not with another edition. It assures the full compatibility.

So we have never to open a session by Windows since Windows doesn't know anything of your possible different Mulabs which can be installed in parallel. Windows have no clue to decide without error which one to use. This can be possible only for applications which are installed by one exclusive edition at the same time.

And also, when someone wants to have only one 32-bit edition and only one 64-bit edition, when upgrading you just need to preserve your "user" subfolder. The best way is to make backups of this folder.

And it would be nice if Mulab could backup a copy of this "user" folder elsewhere, by security, as it is never very of great size. A copy "as is" or a copy "zipped". But it's another request which in itself has nothing to do with the present story.

[BlackWinny]

The choice to not be able to open a session by a click in Windows is logical when we think that there can be several parallel editions of Mulab (5.1, 5.2, 5.3, 54, 5.5... and all that in 32-bit and 64-bit). As it is an excellent possibility offered by Mulab, Windows can't decide arbitrarily which one to use... and yourself you couldn't create a different association for each of these editions since the extension of the file name of the sessions is the same.

It would be possible only if Mulab was installed by an installer which wouldn't allow the installation of parallel editions, (so only one which is exclusive, it means a renoncement to this great possibility to have as much as we want) and furthermore if the 32-bit and 64-bit editions of Mulab had different extensions for their session names.

[fluffy_little_something]

What do you mean by "from windows"? File associations serve that very purpose. I click on a file and the corresponding program is opened. Just like you can you open an RTF text document by clicking on the file, instead of opening Word first and then via Open... In fact, clicking on a file is preferable because for many file types one can use several programs, depending on what is installed on the computer in question. The computer picks the correct, associated application.

And it did work up until yesterday when unfortunately I updated 64-bit Mulab.
Now I can't even manually select Mulab anymore in the window that asks me to pick a program to open a Mulab session with. Mulab is treated as if it were not there on my computer.

[BlackWinny]

What do you mean by "from windows"? File associations serve that very purpose. I click on a file and the corresponding program is opened. Just like you can you open an RTF text document by clicking on the file, instead of opening Word first and then via Open... In fact, clicking on a file is preferable because for many file types one can use several programs, depending on what is installed on the computer in question. The computer picks the correct, associated application.

And it did work up until yesterday when unfortunately I updated 64-bit Mulab.
Now I can't even manually select Mulab anymore in the window that asks me to pick a program to open a Mulab session with. Mulab is treated as if it were not there on my computer.

Our posts have met a collision. Read my last post just above yours and you'll understand why it is not possible when we have the choice of parallel simultaneous editions. To allow this Windows association would definitively forget the ability to have several parallel editions.

[fluffy_little_something]

The choice to not be able to open a session by a click in Windows is logical when we think that there can be several parallel editions of Mulab (5.1, 5.2, 5.3, 54, 5.5... and all that in 32-bit and 64-bit). As it is an excellent possibility offered by Mulab, Windows can't decide arbitrarily which one to use... and yourself you couldn't create a different association for each of these editions since the extension of the file name of the sessions is the same.

It would be possible only if Mulab was installed by an installer which wouldn't allow the installation of parallel editions, (so only one, a renoncement to this great possibility to have as much as we want) and furthermore if the 32-bit and 64-bit editions of Mulab had different extensions for their session names.

As I said, it did work until yesterday. What happens when you double-click a Mulab session file in Windows Explorer?

[fluffy_little_something]

And it did work up until yesterday when unfortunately I updated 64-bit Mulab.
Now I can't even manually select Mulab anymore in the window that asks me to pick a program to open a Mulab session with. Mulab is treated as if it were not there on my computer.

Our posts have met a collision. Read my last post just above yours and you'll understand why it is not possible when we have the choice of parallel simultaneous editions. To allow this Windows association would definitively forget the ability to have several parallel editions.[/quote]

Maybe Windows picks the last program used for that file type. Just like it picks Windows here for rtf files even though I also got Open Office installed, which could handle the very same file type. To Windows the various Mulab versions are just different programs I suppose, like Word and Open Office.

Maybe Jo will tell us

[BlackWinny]

The choice to not be able to open a session by a click in Windows is logical when we think that there can be several parallel editions of Mulab (5.1, 5.2, 5.3, 54, 5.5... and all that in 32-bit and 64-bit). As it is an excellent possibility offered by Mulab, Windows can't decide arbitrarily which one to use... and yourself you couldn't create a different association for each of these editions since the extension of the file name of the sessions is the same.

It would be possible only if Mulab was installed by an installer which wouldn't allow the installation of parallel editions, (so only one, a renoncement to this great possibility to have as much as we want) and furthermore if the 32-bit and 64-bit editions of Mulab had different extensions for their session names.

As I said, it did work until yesterday. What happens when you double-click a Mulab session file in Windows Explorer?

When in Windows Explorer you double-click a file, Windows first looks if it is an application. If it is an application it launches it. If it is not an application, Windows looks in a first database (for the system conventional applications, this one is in the registry, here "HKEY_CLASSES_ROOT\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExts") if there is an association. If there is one it launches the associated program. If there is no association in this tree of the registry, it looks here "HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExts" where are the associations made by the user or by the system for this user independently of possible other users of the machine).

But sometimes, bad uses of the associations may lead someone to have issues in the registry. Very often, with the associations, the issue is a duplication of an association (a previous association hasn't been correctly removed when creating a new association with the same extension), so Windows doesn't know which one to use. It behaves then as if it hadn't any association for this extension.

[fluffy_little_something]

Again, what happens when you click on a Mulab session file in the file browser on your computer? Try it, I am curious

[BlackWinny]

Again, what happens when you click on a Mulab session file in the file browser on your computer? Try it, I am curious

It happens simply that Windows asks me if I want to associate this extension with an application and launch that application.

And that's normal to have this question from Windows since there's no association for the extension .MuSession... and it must not be.

So at this question, for this extension one must never choose to associate it with Mulab.exe. If you do it, Windows will always launch that edition regardless the fact that your session is 32-bit or 64-bit and that leads to an evident anomaly.

So this association must be never created:

[fluffy_little_something]

On my computer, when I click on a 64-bit session file, Mulab 64 is started and I am asked to pick the file (the file clicked on as such is not opened), but the Recent button contains the 32-bit sessions, which is odd and doesn't help.

When I click on a 32-bit session file, Mulab 64 used to be started, until I ran your program to delete file associations Now, neither version starts and both the latest session and its backup have the .musession file ending in the name, unlike before when only the backup file had the .musession file ending. (With 64-bit sessions, still only the backup files have the .musession file ending in their names.)

It seems that Windows does not know what to do with files with that file ending anymore (unlike up until yesterday). And Windows seems to treat 64-bit Mulab differently than 32-bit Mulab, one might say preferably.

[pljones]

On my computer, when I click on a 64-bit session file, Mulab 64 is started and I am asked to pick the file (the file clicked on as such is not opened), but the Recent button contains the 32-bit sessions, which is odd and doesn't help.

Windows doesn't know a MuSession file is either 32bit or 64bit. It knows *nothing* about them.

All Windows knows is someone told it to run "<somepath>\mulab.exe <filename>.MuSession" when <filename>.MuSession is clicked. That's *all* a file association is.

MuLab actually doesn't look at the name "<filename>.MuSession" when you run it. So running it like that has no point. You get the same effect as if running "<somepath>\mulab.exe". (It could do, but then you'd need different file extensions per version.)

Of course, if you click a 64bit MuSession but <somepath>\mulab.exe is the 32bit MuLab, Windows will do what it's been told and run the 32bit MuLab.

Confusingly, Windows7 has 32bit and 64bit registry entries separate. You have to clean from both to get rid of all trace of unwanted entries.

[MuTools]

Exactly, it only affects the internal synth sounds. Although I do think Mulab as a whole (including external plugins) sounds slightly brighter now, but maybe I am wrong. The difference could also be due to my ears being better now than a year ago

It must be the latter. Which is a good thing.

Just checked, it was version 5.1.5 according to the deleted backup folder in the trashcan. I noticed while upgrading that the old folder did not have the Rex Shared Library, yet. Maybe it has to do with that...

The REX file has nothing to do with the overall sound. Nor do i see a reason why your M5.1.5 session would sound different in the latest M5.5.2. If you can make a M5.1.5 session that sounds very different in M5.5.2, pls mail it to me. Mu modules only pls, no VSTs, no samples.

About file associations: Just a quick note: MuLab has nothing to do with the file associations on Windows. So whatever you write here about MuLab also applies to any other app, and vice versa.

[MuTools]

When you open Mulab, in the gang screen you have buttons in a vertical grey panel in front of the Welcome panel. If you choose "Recent" it allows you to open a recent session, regarding the edition 32/64 bit.

Tip 1: You can even drop a .MuSession file on that startup dialog and then MuLab will start with that session.

Tip 2: Whenever you choose a file with Mu's file browser, you can drop a file on that file browser so to switch it to that file/folder. This also applies when choosing a sample, MIDI file, etc... It's for all file browsers.