Re:Wine 2.0 released
by broodbucket on Tuesday January 24, 2017 @09:39PM
(#13477964)
I'd imagine the main issue is VSTs.
[ Parent
| on HN ]
Re:Wine 2.0 released
by squarefoot on Tuesday January 24, 2017 @11:50PM
(#13478628)
Some VSTs work flawlessly, others can be problematic and others do not work at all. You need to check them one by one, but surely a lot of them work.
(edit):
VSTs incompatibility doesn't just affect WINE but Windows itself from version to version. If you take a look at Reaper (reaper.fm), it has some options to run VSTs in various compatibility modes. This paired with WINE's ability to fake a different Windows version "emulation" should help with more problematic VSTs.
There are some VST bridge programs that use WINE underneath. I haven't actually used any yet so I can't attest to their usefulness.
https://github.com/abique/vst-bridge https://github.com/phantom-code/airwave
Re:Wine 2.0 released
by jedimastert on Wednesday January 25, 2017 @06:46PM
(#13487364)
I don't actually use too many VSTs. I can generally make everything I need to make with the built in plug ins