M8.3.4 beta

[mevla]

In short, a file dialog would be a useful option to load license files.

Removing the capability of typing the license as it was found in MUX v.7 is quite a drastic change which I presume was based on some customer support complaining about difficulties in entering the long license text when these people could have copied/pasted it in MUX 7 already. Since these people do not understand that they can use copy/paste, let's remove the capability of entering characters manually altogether ?

[e-crooner]

I don't understand why the key is so incredibly long now.

[mevla]

You know, I cannot run the MUX update I bought recently. Because I cannot enter the license. This is described in detail in this thread. So unless you add a file load option for the incredibly new long license, the updated MUX is useless in this case.

However I do appreciate the work you've done on MUX and I appreciate using the previous MUX that I can run (entering manually the key - and yes, I retried three times because of typos) for its creative aspects. So instead of asking for a reimbursement (and potentially go at it with paypal/credit card) I prefer to give you the upgrade money.

I can't run the new MUX and keep the money. You did great work. Failure on the lack of a file load for the license (in this context), but that's a detail in all the work you did.

Cheers.

[MuTools]

You know, I cannot run the MUX update I bought recently. Because I cannot enter the license. This is described in detail in this thread. So unless you add a file load option for the incredibly new long license, the updated MUX is useless in this case.

You mean on Linux, right?

[e-crooner]

Stupid situation. It doesn't say on the MuTools site that there is a Linux version, so it is not MuTools' fault. On the other hand, one can't say people should test it before buying because you only get a key after buying

[MuTools]

On the other hand, one can't say people should test it before buying because you only get a key after buying

Linux is not supported.
There are no issues at all inserting a user key on the supported platforms.

[mevla]

I have for approx $2500+ of Windows VST running in Linux. None are supported. I try them. If they run fine w/o workarounds and crazy stuff, OK.

I tried the MUX demo the first time, it ran fine.

So OK. Bought it. I entered the license manually. All fine. Used it in a few pieces.

And it was posted here on Sat Jun 01, 2019 9:20 am in "MUX: new user (Linux)"

MUX was then recently updated (this thread).

It is very likely that the updated MUX will work.

BUT now the license is ridiculously long AND the option of typing the license using the keyboard was removed.

This change was not announced as per the first message of this thread (of which I've taken a snapshot).

That is a summary in a few clear and concise lines.

I gather by your reply that you will not add a file load option for the license, is that right ?

[MuTools]

I've indeed no intention to add extra ways to insert the user key 1) because Linux is not supported, 2) because you're the only user asking for it, and i have so many feature requests by other users on the supported platforms, so it would be incorrect in several ways, 3) because where does it stop to add dev time to an unsupported platform as also drag-drop doesn't seem to work on Linux. So it would be a dead end street.
It's a pity that you did not ask for a refund before receiving your personal user key then there would not have been an issue, not for you, not for me. I'm sorry that MUX is not (yet) supported on Linux.

[MuTools]

PS: I find it very strange that copy-paste does not work. I asked this already but iirc you did not answer the question: If you copy the user key to the Linux clipboard and then paste it in a plain text editor then do you see the exact same user key as you copied it? (attention do not post your user key in this public forum)

[mevla]

Thanks for your reply. I actually did reply to the copy/paste question in this thread (simply search for 'paste'). The reply was:

Why ? My guess is that it depends on the framework/tools/UI kit used in Windows development. For instance it works with Rob Papen synths such as Blue2, Predator2, Go2. It works with the approx. 104 Melda Production plugins for copying/pasting presets. So it depends. The exact technical software reason I haven't investigated, having many other things to do.

It's a pity that you did not ask for a refund before receiving your personal user key then there would not have been an issue, not for you, not for me.

It's an impossible situation:

The MUX update ran fine.

Then I got the key.

Then I saw that it was impossible to enter it manually. Ctrl-V, right-click does not work.

So no way of foretelling what was going to happen.

To illustrate here is the work text editor for source code, emacs, and some text that's selected for pasting. If it matters, the MUX Paste button stays grayed out even though there's text in the copy buffer.

Do not worry about the money. As I mentioned, I appreciate your work, MUX is a great synth that runs fine on Linux, lots of creativity. I'm OK to give the money.

MUXcopyPaste.jpg

[MuTools]

Thanks for your reply. I actually did reply to the copy/paste question in this thread (simply search for 'paste').

Sorry i must have missed that.

The reply was:
Why ? My guess is that it depends on the framework/tools/UI kit used in Windows development. For instance it works with Rob Papen synths such as Blue2, Predator2, Go2. It works with the approx. 104 Melda Production plugins for copying/pasting presets. So it depends. The exact technical software reason I haven't investigated, having many other things to do.

MuLab does nothing special wrt using the Windows clipboard. It simply uses the standard functions.

It's a pity that you did not ask for a refund before receiving your personal user key then there would not have been an issue, not for you, not for me.

It's an impossible situation:
The MUX update ran fine.
Then I got the key.
Then I saw that it was impossible to enter it manually.

It has never been supported to enter user keys manually. Ok in M7 it was technically possible but explicitly not recommended. The recommended way both in M7 and M8 is copy-paste. In M8 i also added an extra way: Paste the user key in a plain text file and drop that text file on the Insert User Key dialog.

To illustrate here is the work text editor for source code, emacs, and some text that's selected for pasting. If it matters, the MUX Paste button stays grayed out even though there's text in the copy buffer.

Then there is no plain text on the Windows clipboard.
Anyway, it makes no sense to discuss this in depth as it would mean i would have to investigate this and i don't have Linux. Linux is not supported and that's the main issue. If both copy-paste and drag-drop don't work, and even right-click doesn't work, then who says opening a file will work... That's what i mean with a dead-end street, it's an unsupported platform and so there could be many things that don't work as expected. It would be incorrect, also wrt other FRs, if i would blindly try adding workarounds for issues on a unsupported platform. (blindly as i cannot test it)

Do not worry about the money. As I mentioned, I appreciate your work, MUX is a great synth that runs fine on Linux, lots of creativity. I'm OK to give the money.

Thank you for not making an issue of that.
I really hope you'll find MUX useful on a supported platform.

[nenneb]

Only an idea, maybe that can help:
I guess, the entered user-key must be stored somewhere (registry, appdata ...), maybe it's possible for mevla to enter it there?

But I agree to mutools, that there are more important dev-wishes. For me tempo-track, (chord)info-track, fixed editing position when selecting another track in edit-mode ....

[nenneb]

Two further questions:

1) Fullbucket released a vocoder (simulation of the Korg VC10), which has two stereo-audio in's: One for the carrier (signal to be modulated) and one for the modulator (typically mic). If I insert that in a rack, I get the mod-connection, but cannot reach the carrier, not even in modular-area, as the rack offers one audio-in only.
Only if I insert the VC-10 directly in the modular-area, I can access the second audio in - but can't open it's gui in composer ...
I'd expect to route another rack's audio out to the VC-10-carrier-in, but again I only reach it's modulator-in only.
Any idea?

2) I found the possibilty to "render to audio-track(s)" when right-clicking a rack or a module in modular area. Cool!
Shouldn't that work in the same way when right-clicking a single sequence?

[mevla]

Thanks for your reply. I just want to add a few technical observations.

It has never been supported to enter user keys manually. Ok in M7 it was technically possible but explicitly not recommended. The recommended way both in M7 and M8 is copy-paste. In M8 i also added an extra way: Paste the user key in a plain text file and drop that text file on the Insert User Key dialog.

I also tried drag/drop a text file. Although the "+" button shows up when dragging the file over the license field, the actual paste does not work.

Then there is no plain text on the Windows clipboard.

I'm afraid there could be. It work very well with the 104 Melda Production plugins. A preset text is copied from the KVR Melda forum into the Linux clipboard. Then the preset button is clicked on a Melda plugin and the preset is loaded. Linux is certainly not supported ... ask Vojtech !

This is why I mentioned that there's more to it that can include what GUI toolkit is being used.

Anyway, it makes no sense to discuss this in depth as it would mean i would have to investigate this and i don't have Linux. Linux is not supported and that's the main issue. If both copy-paste and drag-drop don't work, and even right-click doesn't work, then who says opening a file will work... That's what i mean with a dead-end street ...

Well, you can be assured that file dialogs work ... I load MUX presets all the time, and do all kind of other operations using I/O dialogs Aside from that, the $2500+ of Windows plugins that I regularly use all installed correctly using Windows file dialogs and all of them can load their presets. If they would not be able to do that basic thing I would not have spent that money after all.

Aside from this, the Linux Firefox web browser is indeed loading the MUX web page when the MUX demo is terminated. So there are system interactions.

If you're interested and have 5 minutes, here's a feature list of the Wine (Wine Is Not an Emulator) layer used in Linux to interface with Windows apps. The project started in 1993. On top of Wine is linvst which bridges VST apps.

https://wiki.winehq.org/Wine_Features

I really hope you'll find MUX useful on a supported platform.

Yes, MUX 7 is fantastic... on Linux. A very neat synth, very well designed. Lots of creativity. I hope it gets more recognition !

[e-crooner]

Only an idea, maybe that can help:
I guess, the entered user-key must be stored somewhere (registry, appdata ...), maybe it's possible for mevla to enter it there?

But I agree to mutools, that there are more important dev-wishes. For me tempo-track, (chord)info-track, fixed editing position when selecting another track in edit-mode ....

I don't think Mulab writes the user key or anything else into the registry etc. After all, one can "install" on a USB pen drive as well.
Judging from the text format, the key is encrypted and saved in the UKD file right in the Mulab folder. UKD probably stands for User Key whatever.
Makes me wonder, maybe it is possible to create that file on a Windows computer and then copy it into the Mulab folder on your Linux system. That would be a one-time process.

Just removed that file out of curiosity, Mulab switches to demo mode, so it is definitely that UKD file in User->Settings.