Clicks won't work anymore with latest wine staging

[paulalbertdev]

Hi !
Just wanted you to know that there is a click issue with the latest wine staging version.
I documented it here : https://bugs.winehq.org/show_bug.cgi?id=47104
And somebody seems to already have found a workaround, but it seems to imply some modifications on your side.
BTW, do you plan to release another stable version ?
Thanks a lot for your work anyway !!!

[g-insn]

Please see comment 5 from that bug report: https://bugs.winehq.org/show_bug.cgi?id=47104#c5

Is there a way to do what you need to do for vst-bridge without abusing wine internals? For example, using a dummy forwarding window, I've no idea if that's possible.

Generally speaking, __wine stuff is for internal use only and can the behavior that relies on them can change at any time. It worked before by chance but it actually broke some Wine expectations such as tooltips already.

[abique]

Hi,
I haven't worked on this code for a long time.
I would like the wine guys to suggest a clean solution for reparenting, I don't have so much knowledge about wine to do that for them.
If they can't I think it is fine also, but it means that we don't have a solution so far.
I'm sorry I'm very busy with Bitwig Studio and the Linux port of u-he plugins.

I hope that we can get a wine plugin host in bitwig studio in the future, that way we'll be able to create win32 host window and do the embedding using windows api, also we'll be able to use both vst2 and vst3 plugins.

Cheers,
Alex

[paulalbertdev]

Salut Alex !
You work for Bitwig and u-he ?! Wow that's nice ! I've been using your vst bridge with BWS for almost 2 years now !
I don't know anything about wine development nor VST development, but I've seen in the comment nb 5 of the winehq thread I've open that the developer called Gabriel (I think he is @g-insn too) started to suggest some kind of fix/hack. Maybe he could give you the hint you need !
I keep my fingers crossed, and thank you all a lot for all that work you're doing for the users community we are.
And yes, in the future, not having to use a bridge server with Bitwig could be a very powerful solution and a big advantage for BWS, but for now I imagine that The Grid is the priority ^^

Big up

Paul

[kwalker99]

Hi,
I haven't worked on this code for a long time.
I would like the wine guys to suggest a clean solution for reparenting, I don't have so much knowledge about wine to do that for them.
If they can't I think it is fine also, but it means that we don't have a solution so far.
I'm sorry I'm very busy with Bitwig Studio and the Linux port of u-he plugins.

I hope that we can get a wine plugin host in bitwig studio in the future, that way we'll be able to create win32 host window and do the embedding using windows api, also we'll be able to use both vst2 and vst3 plugins.

Cheers,
Alex

So why are Bitwig not pulling this code into Bitwig? Would be great if Bitwig supported running WIndows VST's as several competitor products currently do...

And please ask Bitwig to fix the awful velocity display in the piano roll, Steinberg got it right 25 years ago and still has the right idea, the Piano Roll in Bitwig is in need of serious work...

[zezic]

For anyone interested in VST bridges - there is another one called yabridge in case you missed it. It works pretty well with Bitwig, has support for resizable UI's and supports recent Wine versions (I'm running it right now with Wine Staging 5.10).

[mirh]

There's also airwave.