M8.3.4 beta

[MuTools]

Thx for upgrading! Did you grab your initial user key? (just a yes/no question, i mean don't post any user key here)

[mevla]

I do not remember seeing anything looking like a user key: as soon as I clicked 'buy' it went to paypal. paypal had a problem though as it would not go back to the web site. I then got the paypal confirmation email, so I just closed the browser.

[MuTools]

Please check your inbox (or spam folder), your personal user key should be there now.

[mevla]

Thanks, I got it. I wanted to wait until I tried it to reply, but did not have the time to do so yet.

[mevla]

It's not possible to type characters into the license box of version 8. That makes it in this case impossible to enter the license key since copy/paste does not work in this setup. It would be so nice to have an option to read the license from a text file.

[e-crooner]

Why does copy and paste not work?
Ctrl-C for copying and Ctrl-V for pasting always works.
Oops, just noticed you are on Linux. Seems it is Ctrl-Shift-V there.

[MuTools]

To insert your user key copy it from the email (best including the dashed lines) then paste it into the Insert User Key dialog. There also is a paste button on the user key dialog.
See this video:

[mevla]

Again, copy/paste does not work on this system with this application.

Maybe a picture or two...

MUX 7 : It's possible to type characters :

MUX7InsertKey.jpg

MUX 8 : It's impossible to type characters (and copied characters in the system's buffer are not recognized hence the PASTE button is not activated - deadlock on this system)

MUX8InsertKey.jpg

Again, reading the license from a file could be an alternative.

[mevla]

Why does copy and paste not work? Ctrl-C for copying and Ctrl-V for pasting always works.

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.

Oops, just noticed you are on Linux. Seems it is Ctrl-Shift-V there.

I develop software on Linux for 15 years now. Brings bread and butter to the table, buys houses and cars, sends kids to universities. And yes, it includes knowing how to copy and paste, incredible !

Ctrl-C, Ctrl-X and Ctrl-V works in Linux, and there's also the native way in which you can copy/paste without touching the keyboard.

[MuTools]

Typing characters indeed is not supported in the M8 user key dialog. That's intended because user keys are long text blocks and typing it would be time consuiming and high chance on errors. You must use copy-paste plain unformatted text. Make sure you copy the user key text on the clipboard. To ensure yourself it's properly copied on the clipboard paste it again in Notepad or a similar simple plain text editor. Note that Linux is an unsupported platform so i can't advice on how to properly copy-paste on Linux.

[MuTools]

PS: If copy-paste doesn't work on your Linux machine, try pasting the user key in a plain text file and save it, then drop that text file on the user key dialog, that should work too as that dialog accepts a text file drop.

[mevla]

I tried by dropping a text file onto the license dialog box: unfortunately it does not work.

Yes, Linux is not a supported platform. And I got MUX 7 on the basis of:

1) It works well on Linux
2) It offers great capabilities of sound production

Unfortunately with version 8 the first point might have to be crossed out, and that's a drastic change from version 7.

[dakkra]

Perhaps (and I'm just shooting in the dark) a file chooser/dialog to be able to select a text file with the licence key? Under Wine it's possible to place the license key file under the emulated file system. I know linux is not supported, but it seems like a decent way to keep some form of work around.

I just tried to bridge MUX with https://github.com/psycha0s/airwave but as it turns out, airwave is horribly out of date. I spent three hours sifting through legacy SDKs, error logs, and more just for the symbol tables to not get built properly (it's missing SDK paths that exist but weren't linked and dear god I don't want to delve into the CMAKE tree to fix that).

I'm assuming then Mevla that you're not running Bitwig natively, but via Wine so as to be able to use windows VST on linux (I've seen you on the melda forums of couple of times). Bitwig Linux doesn't recognize dll's, hence my attempt at airwave and why I'm assuming you're running it under Wine.

I've used Mulab on linux in the past with Wine + WineAsio routed through JACK. It wasn't stellar, but it got the job done. MUX however is in a different technology stack, thus making it not as easy to port without the host also being under Wine.

I'll try to help the best I can, but I'm caught in between exams which limits my time.

[mevla]

Perhaps (and I'm just shooting in the dark) a file chooser/dialog to be able to select a text file with the licence key?

Thanks for the reply on the subject and the input.

I totally agree that a 'load license file' option can be useful whatever the OS is. Moreover, file dialogs are the nuts and bolts of software applications, and MUX is already using such.

I use wine-staging and linvst. After reading countless problems and all sorts of workaround by people, I found that linvst is the simplest way IMHO. It's as close as plug and play as it can be. I run Bitwig 2.4.3 Linux, installed using the Bitwig Debian package.

Bitwig Linux does not recognize dll files: true. And this is where the simplicity and 'magic' of linvst comes into play. For each dll a same linvst shared object (.so, the equivalent of .dll) is copied under the plugin's name. Bitwig naturally sees the .so and loads it. In turn the .so will load the VST .dll with the help of wine. For instance:

Code: Select all

-rw-rw-r-- 1 mevla mevla 10912768 Nov 26 05:44  MUX.dll
-rwxr-xr-x 1 mevla mevla    93056 May 27  2019  MUX.so*

The MUX.so is actually linvst.so that was renamed. This is done for every Windows plugin.

Aside from Linux plugins (including all u-he), I run all Melda production plugins (approx. 104 or so), most Rob Papen synths, all Voxengo audio processing, most Tone2 synths, all Sugar Bytes, Synthmaster One and 2, most IK Multimedia, several Image Line synths, many Sonic Charge, all Psychic Modulation and Fathom. Since I do not have any Windows ties, I do not have any previous Windows VST that I must run. It means that when I try a VST demo and it does not run well, I simply drop it, no questions asked. When it runs fine I then consider how useful an addition it can be to create music.

I haven't really tried to run MuLab. I'm OK with Bitwig and trying to know and use it very well, and Harrison Mixbus32C for mixing exported tracks.

[mevla]

Bitwig runs fine on Linux since the very beginning of versions 1.x. When I sit to create music., it is to create music. I had enough of software matters and I do not want to 'fiddle' around with finding and trying workarounds and stuff like that: just want to do music. A little of configuration is OK but not too much.

I edited the replies as I do not want to sound 'angry' or to get misplaced interpretations. I describe a technical problem. This said, I appreciate a lot the design and general work done on MUX, as I find it's a very nice synth, fun to use and has a lot of good things going for it.