MuLab & MUX Vst 5.5.2

[BlackWinny]

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.

It's not at all the same situation.

In RTF files, DOC files, image files, WAV files, MID files, etc. all the included elements are passive elements. They are exclusively data. They don't depend on 32-bit or 64-bit treatment.

In Mulab and MUX session files are included elements among which are necessarily active elements, not data but treatments, therefore which rely heavily on the environment where they will be used, because they are active processes which are totally dependent on the 32-bit or 64-bit engine.

So once more, an association could be done if there was exclusively one edition installed at a time, but therefore it forbids the ability to have several editions installed simultaneously. Since Mutools offers the liberty to have several editions simultaneously, it can't offer at the same the ability to make an association file->program. It would be an antinomy.

[fluffy_little_something]

Yes, I guess it is Windows' fault, it may be a bit confused by two Mulabs
I do find it odd that Windows or Mulab looks in the 32-bit session folder when opening the 64-bit version of Mulab, though.

Do I get that right; except for external plugins of course, i.e. when using only Mulab and its own modules, one might open existing sessions in both versions?

Anyway, I have deleted Mulab 64 and those old sessions, were no good anyway. Was ancient stuff from back when I first bought Mulab

When will the new version be finished? If you need a little cash infusion, you might do a pre-sale. I will certainly upgrade...
Am already curious what the new stuff will be that warrants a major new version

[BlackWinny]

If you need a little cash infusion, you might do a pre-sale. I will certainly upgrade...

A kind of subscription to participate financially to the support of the development?

Yes, if it would be possible, I immediately follow!

[BlackWinny]

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.

Very good tips that I'm learning there!

[MuTools]

When will the new version be finished?

A test version of M6 will certainly be available this month, hopefully next week.

If you need a little cash infusion, you might do a pre-sale. I will certainly upgrade...Am already curious what the new stuff will be that warrants a major new version

A kind of subscription to participate financially to the support of the development?

Yes i've also been thinking that path, but nothing decided yet.

[sl23]

I hope you don't go the subscription route!
The trouble with that is the end user suffers. Why? Because they end up paying money for nothing. We would basically renting mulab for however long, and after creating all those sessions, we'd never own mulab and therefore once subscriptions stop we lose the privileges associated with them.

What would that mean? Essentially we can't go back and edit sessions once subscription stops. I feel subscription is just another way to penalize the poor! Lets say i subscribe for few months, create say, 10 sessions then can't afford to pay for several months. While the subscription is stopped i'm stuffed, i can't carry on with my music. Maybe the subscription will be yearly, but the same applies regardless. Bad move, never thought you'd go the way!

Be a major shame for that to happen. I love mulab, and though i never used luna i kept an eager eye on it back then waiting for improvements. Mulab has become the easiest and best tool in my opinion, please don't ruin it with subscriptions. If anything, increase the price, i'd pay double for it as it's well worth the money. And i'm sure others would be willing...

[fluffy_little_something]

No, I was not talking about subscription at all. I simply thought to myself that like most small developers MuTools probably is not doing too well and thus suggested being able to pay for the upgrade license in advance so that Jo does not feel like he needs to rush the new version just to make money fast.

[sl23]

I know you didn't mean that, i was referring to BlackWinny's comment which Jo was in agreeance with.

[BlackWinny]

I know you didn't mean that, i was referring to BlackWinny's comment which Jo was in agreeance with.

I have never talked about periodic subscription. Only a kind of voluntary donation once to support the development team because of a very exceptional enjoyment with the result of their work and to encourage their passion on their current development, nothing else.

One time, as the person wants. Because MuTools is a very, very little company which makes only TWO products and improves them permanently, and it's worth to encourage them.

[fluffy_little_something]

I was not talking about a donation, either. Simply paying the update fee before the release. But since the update will come so soon, it is probably pointless now. I thought v6 would take several more months

[pljones]

There's always different ways to do something.

You could pay only for the future: keep paying, the future is yours. What's past is already yours and you get to keep it. At whatever point you start, you get to own a licence that covers all past versions and the current one. Keep paying, you'll keep getting an updated licence. More overhead and development work for Jo, of course, as he needs to issue all subscribers with new licences that work with all old versions and the latest one but no future ones. But there's no "lock out" if you stop paying with that model. You'd have just what you have today, except you wouldn't get any future updates (unlike today, where Jo's been very generous with updates).

That model is pretty much the same as "low cost updates", anyway, except you would, indeed, sometimes "pay for nothing" if there was no update to release. But maybe sometimes you'd still get "something for nothing" if there were multiple releases between two subscription payments. It would offer that balance.

[sl23]

@ BlackWinny:
Oh right, sorry, my mistake. I thought you meant removing the current fee and having subscriptions only.

@pljones:
I suppose that could be done, but as you pointed out more work for Jo.

I think first and foremost the best, and gentlest form of charging more would be to stop giving away two "versions" for the price of one. That would effectively double the income for MuLab without increasing the price per version. As much as I have trouble getting the money to pay, due to family responsibilities. But MuLab is definitely an excellent competitor in the DAW market and Jo needs the income.

That way, no extra work for Jo creating subscriptions in the software, no worries for users, no increase in prices, yet Jo benefits with extra income from his work. Sounds best for all concerned.

@Jo:
Can't wait for next MuLab, I'm keeping fingers crossed but won't hold my breath! No worries though, I understand your predicament.

[fluffy_little_something]

It would help if Mulab got better reviews. But reviewers are so used to those giant DAW's with all their features and fancy interfaces that they are spoiled and consider any DAW inferior that does not compete on that level. In reality Mulab is pretty good for most people except professional studios I assume. It sounds very good without my doing much, doesn't drown me in freakish features and thus force me to take decisions I don't understand, and it looks good by now, especially the DAW component.

The only thing I miss is being able to use the single outputs of my drum modules. But maybe I have just not figured out, yet, how to do that I have not really dealt with all the details, I might simply have missed something...

[MuTools]

It might make sense to highlight the currently selected patch and/or put it at the top of the drop-down menu of the VST window. Currently when I have a plugin with lots of presets and pick the, say, 114th, the next time I open the drop-down menu I am back at position 1 again and number 114 is not highlighted when scrolling down. If patches don't have numbers it might be difficult to find them again in such a long list.

Even if the program would be highlighted at the moment the list pops up chance is very small that you will see it because the highlight in that list follows your mouse and so the highlight will be immediately changed.

Well i was mistaken, found a way doing it so the current program is highlighted. It's in M6.

[fluffy_little_something]

Cool, that helps
In Mixcraft the currently selected patch becomes the top patch. E.g. if I select patch 15, the next time I open the menu that patch is the one at the top of the list and the first 14 are no longer displayed (except when deliberately scrolling up of course).