Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Any ideas how to avoid the double window open ? #9

Open
kunitoki opened this issue Feb 4, 2014 · 3 comments
Open

Any ideas how to avoid the double window open ? #9

kunitoki opened this issue Feb 4, 2014 · 3 comments

Comments

@kunitoki
Copy link
Contributor

kunitoki commented Feb 4, 2014

When you open the editor, a small not updated window is opened behind the plugin gui.
Since the plugin editor is a different process and so cannot be reparented in another process (or maybe yes?), is there a way to beautify it ? Eventually would be cool if deleting the small window, also the plugin gui will be closed.

@abique
Copy link
Owner

abique commented Feb 4, 2014

I have a branch for this, the idea is to embed the wine window into the X11 window of the host.
See the branch xembed.

You can also find help on this in #winehackers at irc.freenode.org.

This branch does not work yet, you have to find out why the window embedding doesn't work.

Good luck :-)

@goof03
Copy link

goof03 commented Apr 12, 2014

Hi ! thanks you save my Bitwig demo test (can't get midi out working no fluidsynth too) … :-)
All my favorites VST work with your bridge in Bitwig … But i get this black window too i'm on latest arch.

And sometimes if you open close many VST i cant close Bitwig but anyway … We cant get the moon … I go to delete ableton and my Windows partition ;-) Finally …

@abique
Copy link
Owner

abique commented Apr 12, 2014

Hi,
It's good to see a fellow archer ;-)
Can you tell me the list of vst you tried?
As I said above, to have only one window, you need to use the xembed branch, which doesn't work right now.
If I get some time I'll have a second look.
Cheers, Alex.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants