I see nothing wrong with your current approach (the "multiple machines" variant is what I do) but, for future reference:
- The approach they're talking about is using a virtual machine, not Wine... that means literally installing a real copy of Windows 7 into a piece of software which allows you to run one OS inside another. (It's like an emulator, except that instead of running on a CPU implemented in software, Windows 7 will be running at full speed because the virtual machine tool will be leveraging the real CPU's "virtualization extensions" to split the real CPU up into one or more sandboxed virtual CPUs... it's how VPS (Virtual Private Server) web hosting works.)
The only potential complications are making sure the virtualizing GPU drivers are installed in Windows 7 (you're not gaming, so you shouldn't have to worry about the virtual GPU not being advanced enough) and figuring out how to specify that certain devices (eg. your dongle) are assigned exclusively to the virtual machine so they can function the way they would with dual-booting. (Historically, it's been popular for people who are stubborn about Linux and gaming to give one GPU to Linux (eg. their onboard GPU) and another GPU exclusively to the Windows VM so they can use the Windows GPU drivers and the monitor's input switcher and have perfect compatibility and performance on the GPU too... though I think I heard that you need a certain class of motherboard to do that with PCIe devices rather than just USB ones.)
The virtual machine will emulate the video card, mouse, keyboard, audio device, and network card, and that allows Windows 7 to show up in a window inside Linux instead of taking over those things exclusively. Likewise, what it sees as a hard drive will be stored inside a big file on Linux and you use something like Samba/Windows File Sharing to get your files back and forth.
- Even with Wine, you shouldn't need to convert any VSTs. If the host application is a Windows EXE running in Wine or a virtual machine, then the VSTs should be Windows VSTs.
Fascinating, thanks for the clarification. When I used Linux for my music creation, I was actually using Reaper For Linux. It ran natively on Linux. but for Windows softwares, I had to use Wine to install them, then a converter (LinVst or Yabridge) to convert the vst's to the Linux format, <.so>. You can also install the Windows version of Reaper using wine, but almost nobody does that, as the native Linux version works much better. When I tried it, I could not use Windows vst's for some reason. Should have been able to, but they just didn't work.
I'm tempted to go back to the Reaper forum, and start a discussion about what you have described above. The "native only" folks would grumble about it, but the ones who need Windows vst's might be very interested.
- - - Updated - - -
- - - Updated - - -
What Wine has to do with it? You would be running Windows in Virtualbox, so Wine is not necessary. In Virtualbox and other virtual machine applications you can connect any USB device to the guest (virtual machine). The device will work even if it is not installed in the host (has no drivers). All you need is drivers for the guest operating system. In the case of the USB dongle, Windows should detect it and automatically install drivers. That's the whole point. That's how I used my Iomega ZIP drive. I couldn't install it on Windows 11 (host), so I passed control of my parallel port to Windows XP (guest), the drive was detected and installed the official XP drivers.
PS: in case you didn't understand, when connecting a device to the guest OS, it is disconnected from the host, so it doesn't have to be installed on the host first, as it won't be there, are you physically disconnected it and moved to a different computer. All device data pass directly to the guest OS, the host doesn't interfere.
I should have specified that I was using Reaper For Linux, which runs natively on Linux, and works much better than installing the Windows version of Reaper via Wine. But to use vst's on the Reaper for Linux version, you have to use Wine to install them, then a converter to change them to the <.so> format, which Linux can use.
If I have the time, I might try this, but for now I'm in the midst of reworking all my projects, and only have time for that. I actually did try fooling around with the dongle to try and get it recognized in Linux, using Windows as a guest in Virtual Box. I remember asking a question on Linux Questions Forum about this. But I never stuck with it long enough to succeed.
But I'm still skeptical it would work. Ilok isn't just about drivers, it's about recognizing which operating system the license is on. I think the Ilok would fail to see that the license is on my Linux drive, because, in fact, it is on the Windows virtual drive. You can't have an Ilok working across systems like that, unless I'm mistaken. If you could, it would defeat the purpose of the Ilok, and they designed it to be impervious to all attempts to get around it.