Changing to Linux for music making

[keys_au1]

Not sure if it's been mentioned, but don't forget if you have any hardware editors that need direct access to USB then you are out of luck with WINE...it cannot access the USB directly at the low level required by those editors.

[BertKoor]

Just read this old truth again on Twitter:

Linux is free
if you don't value your time.

[audiojunkie]

Not sure if it's been mentioned, but don't forget if you have any hardware editors that need direct access to USB then you are out of luck with WINE...it cannot access the USB directly at the low level required by those editors.

It depends on what you are needing. Work started for improved WINE support a couple of years ago--in April 2020. It's had over 50 updates since that time:

https://source.winehq.org/git/wine.git/ ... &s=Wineusb

So, if what you are trying to use isn't working right now, it will likely work very soon. I know of some users that are using their hardware editors with no problem. It really depends on what part of the USB access is being required from the editor. Serial connections over USB work fine in WINE.

I'm pretty sure if you have a class compliant hardware device, and run an editor that communicates serialized midi commands through USB it is working for some people. I guess it depends who you speak to and what hardware editor they are using. As long as a driver is needed for your device and it doesn't exist for your Linux system it will not work, for now.

[audiojunkie]

Just read this old truth again on Twitter:

Linux is free
if you don't value your time.

Old truths no longer apply to new Linux. Things are getting better all the time.

[classic]

Now, I got it finally installed on my ssd and it is boot-able also.
Now, the ssd does not show up in the menus in bios to make it the bood hd of choice.
Did a few handling s I found in the web, but that does not change anything.
AND after 2 or 3 times it working well choosing it to boot out of the bios menue, now the password I gave the ssd does not work any more.

This is............................
Did I mention that I hate computer and cars?

[glokraw]

I tap F10 on power-up, and get a list of bootable drives. When I choose one,
I get a secondary list of the bootable options on that particular drive, based on GRUB. It could be that grub has lost track of your SSD. There are 'loveable' tutorials to reconfigure grub for new external drives, a google search should list some good ones.

The F10 tap might be a different key on your computer.
Cheers

[bulevardi]

Yabridge is currently taking a lot of CPU power here.

I'm running Guitar Rig 7 in Reaper, on Linux Mint, via Yabridge/Wine.
It slows down in time, after 30 minutes continuously changing presets to try out stuff, it starts to freeze or crash.

When recording one track, it's taking a little less CPU then what Reaper has.
But when recording more tracks, (16 as the example in the attachment below), it goes way too much.
Instead of running one Yabridge with 16 Guitar Rig instances, it's running 16 Yabridge instances for each Guitar Rig... That's not how it should be, isn't it?

yabridge.jpg

Is there any way to reduce CPU power?

[pljones]

Have you looked at YABridge's GitHub page? Whilst it's not for Guitar Rig (or NI), there's a mention of a slow death:

Plugins by KiloHearts have file descriptor leaks when esync is enabled, causing Wine and yabridge to eventually stop working after the system hits the open file limit. To fix this, either unset WINEESYNC while using yabridge or switch to using fsync instead.

and possibly

Some hosts, particularly Ardour, REAPER, Qtractor, will by default not unload VST3 modules after you close the last plugin. This means that the associated yabridge-host.exe process will keep running until you close the project. For REAPER there's an option called Allow complete unload of VST plug-ins in the VST tab of the settings dialog to disable this behaviour.

I didn't spot anything over on their Issue Tracker.

[bulevardi]

Have you looked at YABridge's GitHub page? Whilst it's not for Guitar Rig (or NI), there's a mention of a slow death:

Plugins by KiloHearts have file descriptor leaks when esync is enabled, causing Wine and yabridge to eventually stop working after the system hits the open file limit. To fix this, either unset WINEESYNC while using yabridge or switch to using fsync instead.

But I have totally no clue how to do this.
There's some explanation about 'Environment Configuration':

If you are using the default Bash shell and you're not using any of the above display managers, then you will want to add the following line to ~/.bash_profile (or ~/.profile if the former does not exist):

export WINEFSYNC=1

But I have no idea how to do so.
I'm kind of a n00b in that field and didn't find much info via google neither.

[bulevardi]

and possibly

Some hosts, particularly Ardour, REAPER, Qtractor, will by default not unload VST3 modules after you close the last plugin. This means that the associated yabridge-host.exe process will keep running until you close the project. For REAPER there's an option called Allow complete unload of VST plug-ins in the VST tab of the settings dialog to disable this behaviour.

That option was unchecked.
I checked it now, to make sure I can reduce something with that.
It doesn't seem to make any change on my System Monitor, but any bits can help !

[planetearth]

Yabridge is currently taking a lot of CPU power here.

I'm running Guitar Rig 7 in Reaper, on Linux Mint, via Yabridge/Wine.
It slows down in time, after 30 minutes continuously changing presets to try out stuff, it starts to freeze or crash.

When recording one track, it's taking a little less CPU then what Reaper has.
But when recording more tracks, (16 as the example in the attachment below), it goes way too much.
Instead of running one Yabridge with 16 Guitar Rig instances, it's running 16 Yabridge instances for each Guitar Rig... That's not how it should be, isn't it?

yabridge.jpg

Is there any way to reduce CPU power?

You mention the CPU power (which does seem excessive), but do you have any idea why Yarbridge is also using 3.5 GB of RAM? Does that account for all the plug-ins loaded via Yarbridge?

Steve

[bulevardi]

I'll have to check if that amount of RAM is the same when using it just on one track. I think it was quite high but not sure anymore.

I assume it's for all plugins loaded in yabridge. There's no other yabridge line in the list. Unfortunately I cannot see a list of plugins loaded in yabridge.

[planetearth]

I'll have to check if that amount of RAM is the same when using it just on one track. I think it was quite high but not sure anymore.

I assume it's for all plugins loaded in yabridge. There's no other yabridge line in the list. Unfortunately I cannot see a list of plugins loaded in yabridge.

Interesting. So if the single instance of Yarbridge fails....

I don't know if you saw this on the GitHub page for Yarbridge, or if it necessarily applies:

• Waves V13 VST3 plugins have memory issues, at least under Wine. They will likely randomly crash at some point. If you can avoid Waves, that would be for the best. Otherwise, try the V12 versions of the plugins if you still have a license for them.

• The Cinnamon desktop environment has some quirks with its window management that affect yabridge's plugin editor embedding. Most notably some plugins may flicker while dragging windows around, and there may be rendering issues when using multiple monitors depending on which screen has been set as primary. Enabling the XEmbed compatibility option may help, but Wine's XEmbed implementation also introduces other rendering issues.

Are you sure it's GuitarRig that's causing your problems and not a Waves plug-in?

There are other tips on the GitHub page, including using a different build of WINE. (And good luck with that!) https://github.com/robbert-vdh/yabridge ... nce-tuning

Steve

[mjolnir]

Even though it's not what I'm running, I'm thinking dual boot with Windows & Linux might be optimal.
I finally stopped distro hopping and my Linux is stable again (TimeShift helps). I read and watched tons of Linux reviews and comparisons and demoed a lot of distros.
I find Ubuntu-based distros to be more supported by big companies, but Arch-based distros to be less of a hassle. This is just my personal experience and is not a reflection on anybody else. I completely ignore the AUR to keep things stable. It's nice to mix and match strengths of any systems though.

I still get more done with multiple DAWs and multiple editors. I used to be better at it though. I'm not so efficient anymore. But I do like working in one for a while, then exporting into a different one for other advantages and workflow.

But in the long run, I'd say Linux is NOT easier than Windows, but does allow (require?) more customization but it can be a timewaster sometimes as much as I'd hate to say it.
Linux looks nicer, but Windows is more compatible. Linux sometimes plays more fair, but Windows has more users. etcetera. Therefore, I think a careful dual boot system is best. I still like stuff like MX Linux and AVLINUX, but both of them got kinda bloaty lately. I finally tried pure Arch lately, but it doesn't seem worth all the time reinstalling everything from scratch for me since my system is already fairly lean and I don't need early upgrades.

Of course I'm just rambling, but that's what I do on here LOL.
Good luck to fellow Linux users.

P.S.-lately I'm grooving on LMMS again.

[bulevardi]

@planetearth : yeah I think it has nothing to do with the Waves V13 plugins, as I was only using Guitar Rig 7 in a new project.
When duplicating the track with that plugin, I see the yabridge-line in my system monitor swelling up.

Have figures out how to do that WINEESYNC=1 to the exe files, but it didn't change anything.

I noticed my kernel is the generic one, can still try to change it to boot as the lowlatency kernel, but don't know if that'll change much for this problem.

@mjolnir: I know yes... however, I left Windows 10 years ago to finally be independent on Linux.
I also do everything from my creative work on it, Gimp, Inkscape, Rawtherapee,...
Now that I have one Windows-plugin working on it via wine, it doesn't seem to be the right way.
Changing back to Windows for just one plugin would be ridiculous... although I can use all the named software on Windows too...

Or... I can try to find some other guitar amp simulator for linux native.... such as ToneLib, Blue Cat's Axiom, Audio Assault Amplocker, etc... but wasn't that convinced with some UX related things. I preferred Guitar Rig...