Hi!
I use Reaper for audio editing, mixing and etc. When I used it under wine 1.4 there is no problems with VST plugins but after upgrade to 1.7 I have wine crash. The first plugin that produced this error was Recabinet. I thought that it will be one issue and it is problem of plugin. But after update to 1.7.25 I have this issue with few more plugins like Limiter6, SlickEQ, Molot (freeware), AOM Invisible Limiter.
Reaper has option to run plugins with very simplified gui (but not usefull in most cases), and plugins works fine. And wine falls with embedded plugin gui. I hope this tendency will not be progress.
VST Plugins embedded GUI crash
Re: VST Plugins embedded GUI crash
aboba I think you are starting to learn what happens when people don't report failures so they can be fixed.
Wine making replacement for Windows part is very complex. The rule is if it works under Windows yet it does not work under wine there is a issue that needs a bug report.
http://wiki.winehq.org/RegressionTesting if you can would be a good step forwards. Do make sure if you have a pulseaudio patched version of wine you test with Pulseaudio audio patch disabled.
This issue could be also coming from the fact wine supports more librares now.
Also without a log of wine debugging we cannot guess what the issue is.
http://wiki.winehq.org/FAQ#get_log
Wine making replacement for Windows part is very complex. The rule is if it works under Windows yet it does not work under wine there is a issue that needs a bug report.
http://wiki.winehq.org/RegressionTesting if you can would be a good step forwards. Do make sure if you have a pulseaudio patched version of wine you test with Pulseaudio audio patch disabled.
This issue could be also coming from the fact wine supports more librares now.
Also without a log of wine debugging we cannot guess what the issue is.
http://wiki.winehq.org/FAQ#get_log
Re: VST Plugins embedded GUI crash
Thanks for the answer.
I will try to upload the log file some day soon when I will have more free time.
By the way, first thing that I thinking about when crash produced that the reason is new wine libraries or new implementations of graphic libs. It's because the Reaper launch splash screen was without transparency (black color as replacement, wine 1.4), but after wine upgrade to 1.6 trancparency appeared.
And last question about creating of bug issue. This problem is complex, few plugins have this issue. What kind of bug request would I create? Separate for the each plugin or something more appropriate?
I will try to upload the log file some day soon when I will have more free time.
By the way, first thing that I thinking about when crash produced that the reason is new wine libraries or new implementations of graphic libs. It's because the Reaper launch splash screen was without transparency (black color as replacement, wine 1.4), but after wine upgrade to 1.6 trancparency appeared.
And last question about creating of bug issue. This problem is complex, few plugins have this issue. What kind of bug request would I create? Separate for the each plugin or something more appropriate?
Re: VST Plugins embedded GUI crash
aboba the answer is at this stage I don't know if it should be one or many bug reports.
Getting the logs out of wine can be very critical to help work out if the bugs are in fact identical or independent. The more exact method for something that has worked but does not now is do the regression test process to find what patch/patches added to wine that broke the application.
Just because something looks the same on screen does not mean what the application is doing to achieve it is the same.
There is a triage team on wine bugzilla who will attempt to merge bugs in case they are in fact identical but from different plugins/programs. I do try to recommend avoiding overworking them.
Also do try the latest version of wine with the number of patches that go into wine some errors can be found and already fixed.
Getting the logs out of wine can be very critical to help work out if the bugs are in fact identical or independent. The more exact method for something that has worked but does not now is do the regression test process to find what patch/patches added to wine that broke the application.
Just because something looks the same on screen does not mean what the application is doing to achieve it is the same.
There is a triage team on wine bugzilla who will attempt to merge bugs in case they are in fact identical but from different plugins/programs. I do try to recommend avoiding overworking them.
Also do try the latest version of wine with the number of patches that go into wine some errors can be found and already fixed.
