'Migrating' Yabridge plugs

[Garyg]

Hi,

If I wanted to test out a different distro, should it be possible to copy my existing wine_c folder and .reg files to the new system to save reinstalling my windows plugins?

Assuming of course I had the same version of wine and yabridge on both installs?

Thanks.

[Largos]

I copied a c drive contents across and it was fine for the small amount of windows vst I have. I can't speak for yabridge but that's really quick to setup anyway.

[Garyg]

thanks.

setting up wine and yabridge is pretty painless, it was more the thought of having to reinstall and authorise a bunch of windows plugs (valhalla, unfiltered audio etc). Which to be honest is pretty painless too just... tedious

[nevis]

If you have a single wine prefix, then it should be straightforward unless you use "unusual paths" which you would also need to teach the new yabridge installation.

I use 2 prefixes, i.e. "2 wine installations", because some plugins will require different DLLs like Direct3d etc.
So I made a quick text file if I did anything other than the plain vanilla installation to get the plugins to work. Should I ever need to move, re-install etc.

Example excerpt:
Cableguys Shaperbox, FilterShaperXL: switch to OpenGL in options, GUI works fine so far now
Tritik Irid: installed dxvk (latest) with winetricks
BLEASS (all): installed dxvk (latest) with winetricks

[GMaq]

I think @glowrak guy is a specialist at this, I'm sure he has hundreds of Windows VSTs in his .wine folder and I seem to recall in other posts that he simply copies .wine over to new installs but he would be better to fill in the details..

I agree after just upgrading my Studio OS that installing and licensing (both Win and Lin Plugins) is tedium maximus

[glowrak guy]

The wine registry files often contain perhaps most/all of the authorizatios data (I'm no expert about that) but with a new install of wine, I back-up the default files to a nearby folder, as seen in the pic,

wine-registry files.jpg (10.14 KiB) Viewed 732 times

and re-use those with the successful tedious authorizations. Some devs will put needed files in Documents, or their own data folders. So I keep all serial numbers and related files in backups. I also screenshot and name the pics of important steps of sometimes crazed installation regimens, in case I have a forgetfullitis attack

I don't often update things that work fine, for example, with IK and NI things currently working, the new wine-staging version will be tested on a separate installation. And even then, a drastic improvement would be needed to get me to budge. And I need improvement far more than the software. An old guy once said, 'There are very few friendly things lurking in the shadows'
Cheers

[Impostor]

If I wanted to test out a different distro, should it be possible to copy my existing wine_c folder and .reg files to the new system to save reinstalling my windows plugins?

I'm dual booting an "old" and a "new" linux distro, with home folders on distinct partitions, while having yet another partition for shared data. Thus, my .wine, .steam, and .plugin folders reside on the data partition, and my two home folders just contain symlinks to them. Seems to work ok.

One could think that may screw up permissions on the data drive, but I guess that's prevented by simply taking user-ownership of the mount point (/mnt/data/ in my case) in each install.

[Garyg]

Thanks all your comments, most helpful.

Example excerpt:
Cableguys Shaperbox, FilterShaperXL: switch to OpenGL in options, GUI works fine so far now
Tritik Irid: installed dxvk (latest) with winetricks
BLEASS (all): installed dxvk (latest) with winetricks

This is the next thing I should look at, additional wine prefixes. I have pretty much all the windows plugins I want working out of the box, just the default prefix but have a couple (audiority, newest linplug etc) that don't update the gui, believe dxvk is a possible solution...

[glowrak guy]

If I wanted to test out a different distro, should it be possible to copy my existing wine_c folder and .reg files to the new system to save reinstalling my windows plugins?

I'm dual booting an "old" and a "new" linux distro, with home folders on distinct partitions, while having yet another partition for shared data. Thus, my .wine, .steam, and .plugin folders reside on the data partition, and my two home folders just contain symlinks to them. Seems to work ok.

One could think that may screw up permissions on the data drive, but I guess that's prevented by simply taking user-ownership of the mount point (/mnt/data/ in my case) in each install.

That's an excellent setup, easy for important backups, and without disk i/o tying up the system drive. I'll try that when I can get a large SSD for such folders. Thanks for mentioning it
Cheers

[glowrak guy]

Here is the Kontakt West Africa percussion library, with sustain pedal down to be my drummer for
a nice Guitar Rig practice jam. These plugins were migrated from an early 2023 AVLinux, to the newest version,
but with quite a bit of tinkering on my part, but I'm delighted with the possibilities

GuitarRig-WestAfrica.jpg (229.95 KiB) Viewed 468 times

[Impostor]

That's an excellent setup, easy for important backups, and without disk i/o tying up the system drive. I'll try that when I can get a large SSD for such folders. Thanks for mentioning it 8)

You're welcome :)

I configured it that way because I find in-place upgrading the OS always a bit of a pain. So I decided to just permanently dual boot old and new versions. And to prevent the need for copying large amounts of data between home folders, the extra data partition. So when the time calls for an upgrade, I can just overwrite my oldest OS and home partitions, while keeping my current one.