Running commercial audio software on linux

[coolblinger]

I ordered a Intel NUC10i7FNH, so I will be making Linux music in a few days.
My question. When I will use wine-staging, which .dll should I install and where.
I have no idea yet, since I am way long time gone from windows.

Most Windows plugins will come with an installer that installs the actual VST2 plugin to C:\Program Files\Steinberg\VstPlugins aka ~/.wine/drive_c/Program Files/Steinberg/VstPlugins (with some small variations), and the VST3 plugin to C:\Program Files\Common Files\VST3 aka ~/.wine/drive_c/Program Files/Common/VST3. Feel free to join us on the yabridge Discord though if you get to that point and still have questions.

[glokraw]

After installing wine staging, run the winecfg command, and a config panel opens where basic choices can be made. In the 'Drives' tab, tick the box for 'dot files' to make browsing to presets and samples easier in .wine folder.

I make one vst path for simple plugin .dll's that don't have fancy installers that create extra data folders and files scattered across the hard-disk. This makes it easy to use linvst plugin wrapper (and now also the yabridge wrapper) in just a few locations. linvst provides a command 'linvstconverttree' that recursively seeks out plugins from a top level folder, for handy one-pass wrapping.

/home/me/.wine/drive_c/users/VstPlugins

For more complex installers from big commercial projects, I follow their default offerings, even though the plugin often winds up in a long path:

/home/me/.wine/drive_c/Program Files/Native Instruments/VSTPlugins 64 bit/Guitar Rig 6.dll

To launch a standalone win software or installer that has spaces in it's title or path, use quotes in the command:

wine /home/me/.wine/drive_c/"Program Files/Native Instruments/Guitar Rig 6/Guitar Rig 6.exe"

As your favorites emerge, trimming your .bash_history will insure that
long often-used commands are near the top of the history list so your 'up-arrow' can browse to them.

For the linux Reaper, I make a folder name based on the Reaper version number, and extract the downloads there, and for example, in bash_history there is a command line like .618/reaper.exe
to start things off. Starting things by terminal will let you kill things easily if something locks up.
Cheers

[glokraw]

I ordered a Intel NUC10i7FNH, so I will be making Linux music in a few days.

What a cool new computer! I haven't kept up with the latest designs and offerings, but I can see taking one of these on vacation, and using my IK UNO synth with rakarrack. My main computer is 4 core i7 @3.4 ghz, compared to 6 cores @ 4.7 ghz, and more efficient data paths on the motherboard Why didn't Santa know about these?
Cheers

[revvy]

nm

[BONES]

I ordered a Intel NUC10i7FNH, so I will be making Linux music in a few days.

What a cool new computer! I haven't kept up with the latest designs and offerings, but I can see taking one of these on vacation, and using my IK UNO synth with rakarrack. My main computer is 4 core i7 @3.4 ghz, compared to 6 cores @ 4.7 ghz, and more efficient data paths on the motherboard Why didn't Santa know about these?

They are definitely cool but they are not cheap. Very specific use-cases, though, so you probably get what you pay for.

[landfiets2020]

Ok I received my new computer and ran into problems right away, but we solved those.
Next problem. I use Bitwig. In AUR only the newest bitwig is present and not a full older version.
Bitwig is payed software and my license goes to 3.1.3 and not 3.3.1 like they have now.
They have a .deb file to use but Manjaro, which I installed doesn't use those.
Is there a way to unpack this .deb or shall I change distro to Ubuntu-like.
It all comes down to what is the best and fastest possibillity. When I put all my hopes on Manjaro and install for ours all kind of software but Bitwig is impossible then I will be very dissapointed. So better now make a choice than later with wasted time.
Anyone for a helpful idea to use .deb files? Or shall I switch immediately to Ubuntu/Debian

I also started with wine-staging for Omisphere. I got this running but it looks ugly. Is there anyone who knows wine well and can help to get the 'way it looks' like it should? Do I need some extra config .dll files for wine? Maybe someone can help me.

Greetings so far and don't go out of your way so only when you have time to answer

[coolblinger]

You'll just have to edit the bitwig-studio AUR package to point to your version of Bitwig:

• Do a `git clone https://aur.archlinux.org/bitwig-studio.git` somewhere (if you used yay to install the latest Bitwig Studio, this will also already be in ~/.cache/yay/bitwig-studio)
• Open the PKGBUILD in the cloned git repository and change pkgver and _pkgver to match your version
• Run `updpkgsums` in the directory of the PKGBUILD to download the .deb and update the checksums
• Finally run `makepkg -sic` to make and install the package

I'm not sure what Omnisphere looks like now or what libraries they use. If they use VSTGUI like Serum then you can try installing a native Windows version of gdiplus through `winetricks gdiplus`. Afterwards open winecfg, go to the libraries tab, add d2d1, and set it to disabled. Make sure the Wine prefix has been completely shut down (`wineserver -k`) before retrying.

[landfiets2020]

My knowledge of those pro commands is not big. I git cloned the URL and am in the bitwig-studio directory. And i did it. Thanks for the help. This was a great thing. Now I have my Bitwig.

[glokraw]

When I put all my hopes on Manjaro...

In my experience as a linux using musician, it is good luck to be familiar with several well-maintained distros, several quality daws, and have bootable access to those through various hardwares. New music software will be acquired, and the daw compatability, features and worklow vary. I use mainly Reaper, but have Harrison Mixbus, Bitwig 8-Track, and Qtractor for their benefits. I have Studio1337, Bionic64, AVLinux, two versions of Ubuntu Studio, and PCLinuxOS, all of which are used according to their strengths, and which double as backups for my commercial vsts and wine setups. (I have had Manjaro a few times, and likely will again soon, as I'm sorting my drive-space to start the new year.

I try to keep two or three fully functioning setups, where the core linux and wine are not updated, and testing the latest shiny things takes place on booted external-drive distros. (A Motif or Kronos or Fantom don't get frequent updates, so I like to have that solidarity in my software workstations as well.

There are some rare plugins that fail, and usually there is some mention in the error or terminal output to a missing setting in the video driver, so sometimes a gamer-level video config session will be fruitful. You could test Omnisphere in AVLinux and Ubuntu Studio during a live dvd session, or install them on usbstick-SD cards. AVL has wine 5.22 and a Reaper demo installed by default, and maybe also an unlicensed Harrison Mixbus. Looking forward to seeing your full Omnisphere success.

[coolblinger]

The main difference between different distros here are the different system libraries, and Wine version 5.x will behave the same on any distro regardless of system libraries.

[glokraw]

There are distro default usabilty and aesthetic differences on top of those system libraries that directly influence ones productivity and satisfaction with a linux experience. And system libraries do effect which usability and aesthetic options will work for a given distro. One distro's default system gui was driving me nuts, and it was a major PITA to change it, because the login manager had no user session options in it's screen, and system D
was being a brat I actually had to learn things that had little to do with a record button .

Cheers

[landfiets2020]

Is Wusikstation v9 working with wine?

[glokraw]

I haven purchased V9 yet, but V5 works nicely, used with Drumatoxin, Mistral,
and other excellent ArtVera soundsets.

[glokraw]

I saw that 'Only Human', a distro maintainer specializing in PCLinuxOS with the
Enlightenment system gui, has released a new musicians version, so I set up a fresh installation knowing that wine 4.x is the newest version in their repository.

Happily, I was able to copy over my wine 5.22 folders from a Ubuntu Studio setup,
and re-use the registry files, so I haven't yet had to visit Native Access or IK's package
software registration lieutenants. Kinda like the Browns leading the Steelers 35 to 10
in the first half. The suicide watch in Vegas is heating UP

My tests succeeded with Reaktor, Kontakt, and Guitar Rig version 6's, IK SampleTank 3, and Amplitube 4, and some excellent older plugins like Cobalt

A4-Max-GR6-demo.jpg

The distro also has Steam and Zoom and some other interesting content that
adds up to a healthy 3.6 gig iso download. It's easy to burn a bootable dvd or usb/SD
gizmo, and kick the tires. It has a very bright default theme, which I like in small doses, but I changed to a theme that better matches my current wallpaper and most vst guis.

I used a Fedora wineasio .rpm, installed the samba-winbind packages,
and turned off d-bus in qjackctl, and things started clicking.
Cheers

[landfiets2020]

So far, only with the gdiplus.dll in override I have running with wine-staging 5.22 and yabridge in Manjaro 20.2:
EZDrummer
Korg Legacy collection M1, Wavestation vs 1.7.0 (not the newest one)
Spectrasonics Omnisphere
Sprectrasonics StylusRMX
Sylenth 1

Wooowww, this is great. Almost all my plugins work for almost out of the box.
Just for google and people who find this intersting for trying themselves.