http://bugs.winehq.org/show_bug.cgi?id=32637
Bug #: 32637 Summary: Some VST plugins that used to work with dssi-vst now fail Product: Wine Version: 1.5.20 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs@winehq.org ReportedBy: m.tarenskeen@zonnet.nl Classification: Unclassified
Created attachment 43067 --> http://bugs.winehq.org/attachment.cgi?id=43067 running VSTi plugin TAL-U-NO-LX-V2.dll using dssi-vst on Fedora 17: error backtrace
I use dssi-vst to run VST synth/effect/audio plugins. For example TAL-U-NO-LX-V2 from Togu Audio Line used to run and sound prefectly. But now it fails. I am attaching a backtrace file.
http://bugs.winehq.org/show_bug.cgi?id=32637
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |regression
--- Comment #1 from Austin English austinenglish@gmail.com 2013-01-06 21:52:49 CST --- Please run a regression test.
http://bugs.winehq.org/show_bug.cgi?id=32637
--- Comment #2 from mt m.tarenskeen@zonnet.nl 2013-01-07 02:28:29 CST --- I guess with "regression test" you mean trying to find the latest wine version that did not yet expose this bug?
I am trying to downgrade to an older wine version. But it's not an easy task due to several dependancies on my Fedora system. I'll keep trying and searching.
In case anyone else wants to try to reproduce this bug, it also happens with this small and free VST plugin, that is derived from TAL-U-NO-LX-V2.dll:
http://kunz.corrupt.ch/downloads/plugins/install_TAL-Chorus-LX.zip
I am using dssi-vst-0.9.2-6 on Fedora 17, but experienced the same problem using Festige.
http://bugs.winehq.org/show_bug.cgi?id=32637
--- Comment #3 from mt m.tarenskeen@zonnet.nl 2013-01-07 02:30:34 CST --- P.S. I am sure it used to work fine before. Otherwise I would not have payed the registration fee for TAL-U-NO-LX-V2.dll.
http://bugs.winehq.org/show_bug.cgi?id=32637
Bruno Jesus 00cpxxx@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |00cpxxx@gmail.com
--- Comment #4 from Bruno Jesus 00cpxxx@gmail.com 2013-01-07 07:46:14 CST --- (In reply to comment #2)
I guess with "regression test" you mean trying to find the latest wine version that did not yet expose this bug?
The regression test will be able to find the exact code change that caused the problem. Read more here: http://wiki.winehq.org/RegressionTesting
http://bugs.winehq.org/show_bug.cgi?id=32637
--- Comment #5 from Christian Dannie Storgaard cybolic@gmail.com 2013-01-27 12:16:32 CST --- Created attachment 43363 --> http://bugs.winehq.org/attachment.cgi?id=43363 backtrace log for Wine 1.5.22
This happens in Wine 1.5.22 as well. If I can get Ubuntu 64bit to compile 32bit Wine, I'll do a regression test.
mt, do you remember which Wine version did work?
http://bugs.winehq.org/show_bug.cgi?id=32637
--- Comment #6 from mt m.tarenskeen@zonnet.nl 2013-01-27 14:09:00 CST --- I don't really remember when this first started to happen. Sorry. But let's try some guessing:
TAL-UN0-NO-LX version 2.0 was released on 27.09.2012, according to the TAL website. I have seen this version and newer versions work on my Fedora 17 system
The %changelog section of the rpm specfile for wine for Fedora 17 shows: wine version 1.5.13 was built on Sep 15 2012 wine version 1.5.14 was built on Sep 29 2012 So my guess is it must have happened somewhere between 1.5.14 and 1.5.20
Hope that helps a little bit.
http://bugs.winehq.org/show_bug.cgi?id=32637
Christian Dannie Storgaard cybolic@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |cybolic@gmail.com
--- Comment #7 from Christian Dannie Storgaard cybolic@gmail.com 2013-01-28 04:51:31 CST --- Okay, I've tested u-no-lx-v2 using Wine from version 1.5.14 to version 1.5.22 and it breaks like reported in 1.5.16 and up.
The backtrace(s) mentions "WINPROC_wrapper+0x19() in user32", but I couldn't find anything in the Git logs that mention a change to WINPROC since 2009, so I don't know if that's the right place to look.
Anyway, I'll try to set up a proper regression test, but if anyone knows where to look from this info, you are more than welcome to beat me to it.
http://bugs.winehq.org/show_bug.cgi?id=32637
--- Comment #8 from mt m.tarenskeen@zonnet.nl 2013-08-21 17:55:01 CDT --- Any news on this bug?
http://bugs.winehq.org/show_bug.cgi?id=32637
--- Comment #9 from Austin English austinenglish@gmail.com 2013-08-21 19:32:24 CDT --- (In reply to comment #8)
Any news on this bug?
No one has performed a regression test yet..
https://bugs.winehq.org/show_bug.cgi?id=32637
--- Comment #10 from mt m.tarenskeen@zonnet.nl --- Hi,
I have good news and bad news. Using now wine version 1.7.34 on Fedora 21 the above mentioned VST plugins started to be usable again! Something has changed that is good for this issue.
There is still a smaller problem with TAL-U-NO-LX-V2.dll.
The dropdown menus that show the patchnames look strange and are only half readable. Something strange with font handling? I have some trouble making a screendump to demonstrate the what it looks like on my screen. Maybe someone else can confirm the issue?
https://bugs.winehq.org/show_bug.cgi?id=32637
Ken Sharp imwellcushtymelike@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED
--- Comment #11 from Ken Sharp imwellcushtymelike@gmail.com --- (In reply to mt from comment #10)
Hi,
I have good news and bad news. Using now wine version 1.7.34 on Fedora 21 the above mentioned VST plugins started to be usable again!
https://bugs.winehq.org/show_bug.cgi?id=32637
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #12 from Alexandre Julliard julliard@winehq.org --- Closing bugs fixed in 1.7.49.