Hello again, so the scanner works perfectly now - thanks! I still have crashing API when trying to close the window. Also I see it doubled? (see below)WilliamK wrote: Thu Jun 13, 2019 2:08 pm New file uploaded. I fixed something in the plugin's constructor, should not crash anymore.
I also improved the naming when it finds multiple files, it adds --1 --2 --3 to the filename.
Wusik X42 BETA (Windows only for now) - Instrument/Effect Bridge and more
-
- KVRian
- 885 posts since 29 Jan, 2017
You do not have the required permissions to view the files attached to this post.
-
- KVRian
- 885 posts since 29 Jan, 2017
Hybrid3 is still not producing any sound and crashes when attempting to close the window (just like Waves). The view is duplicated just as above
Last edited by 0degree on Thu Jun 13, 2019 7:03 pm, edited 1 time in total.
-
- Banned
- Topic Starter
- 5089 posts since 12 Jun, 2001 from Wusik Dot Com
I just uploaded a new file. Fixed some FXB/FXP stuff and other internal problems.
June 13 2019 - V1.0.2 (BETA08)
- Fixed problems with the plugin interface closing by itself.
- Added a new option to the Options menu: Auto Bridged Window To Top - disabled by default. So the bridged window will only come to focus so you can edit it if you click on it first, if this option is selected it will bring the window to the top when you move the mouse over instead.
- Fixed a problem with Automation not working on some hosts.
- Added support to Shell Plugins (EG: Waves).
- Fixed some problems loading certain VST plugins.
- Fixed a problem with plugin's filenames having unsupported characters.
- Fixed a problem when saving non-bridged files and after having it bridged. Now a .wconfig file will be created even if the file is not bridged, this way the code knows that the file was generated by Wusik X42 and can directly handle it (delete/re-create).
- Fixed a problem when loading FXB/FXP files: it wasn't relisting the preset/program list names.
As for the problem above, I still have no idea on what's going on. But I'm starting to think is due to the way I handle windows. As I "steal" the window from one process to another so I can move it when you move the window inside the host. Maybe Waves plugins, been at it uses OpenGL, is making something different and won't allow me to do what I'm doing.
I will figure something out...
June 13 2019 - V1.0.2 (BETA08)
- Fixed problems with the plugin interface closing by itself.
- Added a new option to the Options menu: Auto Bridged Window To Top - disabled by default. So the bridged window will only come to focus so you can edit it if you click on it first, if this option is selected it will bring the window to the top when you move the mouse over instead.
- Fixed a problem with Automation not working on some hosts.
- Added support to Shell Plugins (EG: Waves).
- Fixed some problems loading certain VST plugins.
- Fixed a problem with plugin's filenames having unsupported characters.
- Fixed a problem when saving non-bridged files and after having it bridged. Now a .wconfig file will be created even if the file is not bridged, this way the code knows that the file was generated by Wusik X42 and can directly handle it (delete/re-create).
- Fixed a problem when loading FXB/FXP files: it wasn't relisting the preset/program list names.
As for the problem above, I still have no idea on what's going on. But I'm starting to think is due to the way I handle windows. As I "steal" the window from one process to another so I can move it when you move the window inside the host. Maybe Waves plugins, been at it uses OpenGL, is making something different and won't allow me to do what I'm doing.
I will figure something out...-
- Banned
- Topic Starter
- 5089 posts since 12 Jun, 2001 from Wusik Dot Com
Indeed, I will double check my code and see how I'm doing things. The idea is to be able to see the window handle of the bridged application and from the original hosted plugin change its position. Is more of a hack, but from the Windows SDK it seems to be ok to do it, as Windows does allow that. 
Maybe the problem is just that I'm doing something wrong. 
I will figure it out soon.
Maybe the problem is just that I'm doing something wrong. I will figure it out soon.-
- KVRian
- 885 posts since 29 Jan, 2017
Cool, thanks a lot. Also it makes sense to test this stuff with Reaper/FL Studio vs Bitwig/Ableton because in case of the latter ones you have topmost window without parent if I remember correctly
-
- Banned
- Topic Starter
- 5089 posts since 12 Jun, 2001 from Wusik Dot Com
Ok, I'm having problems with the Waves plugins. They all get detected as MONO and don't make a single sound. So I'm trying to figure out why this is happening. Maybe I need to setup something so I can host them correctly. 
-
- Banned
- Topic Starter
- 5089 posts since 12 Jun, 2001 from Wusik Dot Com
Bad news. JUCE is indeed not loading correctly the Waves plugins. So I'm hoping they can fix this or that I can fix this. I will debug to see how it's reporting the number of inputs and outputs, as right now even their plugin hosting example is loading all Waves plugins as 1/1 in/out.
-
- Banned
- Topic Starter
- 5089 posts since 12 Jun, 2001 from Wusik Dot Com
GOOD news. 
Found the problem, it was on MY END... .... will have a fix tomorrow or so... need to rewrite several things on the scanner and hosting side of things. 
Found the problem, it was on MY END... .... will have a fix tomorrow or so... need to rewrite several things on the scanner and hosting side of things. -
- Banned
- Topic Starter
- 5089 posts since 12 Jun, 2001 from Wusik Dot Com
New file uploaded. Be sure to clear your scan list and rescan as I fixed some serious stuff and this requires a rescan, sorry.
June 13 2019 - V1.0.2 (BETA12)
- Fixed problems with the plugin interface closing by itself.
- Added a new option to the Options menu: Auto Bridged Window To Top - disabled by default. So the bridged window will only come to focus so you can edit it if you click on it first, if this option is selected it will bring the window to the top when you move the mouse over instead.
- Fixed a problem with Automation not working on some hosts.
- Added support to Shell Plugins (EG: Waves).
- Fixed some problems loading certain VST plugins.
- Fixed a problem with plugin's filenames having unsupported characters.
- Fixed a problem when saving non-bridged files and after having it bridged. Now a .wconfig file will be created even if the file is not bridged, this way the code knows that the file was generated by Wusik X42 and can directly handle it (delete/re-create).
- Fixed a problem when loading FXB/FXP files: it wasn't relisting the preset/program list names.
- Fixed a problem with mono plugins and also other types of bus layouts (you will need to rescan so the code works correctly).
- When changing if a file is bridged or not, it will check if the file is a shell-plugin (Waves) and apply the settings to all right instances.
Be sure to clear your scan list and rescan as I fixed some serious stuff and this requires a rescan, sorry.June 13 2019 - V1.0.2 (BETA12)
- Fixed problems with the plugin interface closing by itself.
- Added a new option to the Options menu: Auto Bridged Window To Top - disabled by default. So the bridged window will only come to focus so you can edit it if you click on it first, if this option is selected it will bring the window to the top when you move the mouse over instead.
- Fixed a problem with Automation not working on some hosts.
- Added support to Shell Plugins (EG: Waves).
- Fixed some problems loading certain VST plugins.
- Fixed a problem with plugin's filenames having unsupported characters.
- Fixed a problem when saving non-bridged files and after having it bridged. Now a .wconfig file will be created even if the file is not bridged, this way the code knows that the file was generated by Wusik X42 and can directly handle it (delete/re-create).
- Fixed a problem when loading FXB/FXP files: it wasn't relisting the preset/program list names.
- Fixed a problem with mono plugins and also other types of bus layouts (you will need to rescan so the code works correctly).
- When changing if a file is bridged or not, it will check if the file is a shell-plugin (Waves) and apply the settings to all right instances.
-
- KVRian
- 885 posts since 29 Jan, 2017
Ok, this update fixed GUI for Waves plugins. There's still problem with some Air plugs tough. Also in case of Waves there +574dB spike produced in one channel only and there's no params available for automationWilliamK wrote: Fri Jun 14, 2019 12:31 am New file uploaded.
June 13 2019 - V1.0.2 (BETA12)
- Fixed problems with the plugin interface closing by itself.
- Added a new option to the Options menu: Auto Bridged Window To Top - disabled by default. So the bridged window will only come to focus so you can edit it if you click on it first, if this option is selected it will bring the window to the top when you move the mouse over instead.
- Fixed a problem with Automation not working on some hosts.
- Added support to Shell Plugins (EG: Waves).
- Fixed some problems loading certain VST plugins.
- Fixed a problem with plugin's filenames having unsupported characters.
- Fixed a problem when saving non-bridged files and after having it bridged. Now a .wconfig file will be created even if the file is not bridged, this way the code knows that the file was generated by Wusik X42 and can directly handle it (delete/re-create).
- Fixed a problem when loading FXB/FXP files: it wasn't relisting the preset/program list names.
- Fixed a problem with mono plugins and also other types of bus layouts (you will need to rescan so the code works correctly).
- When changing if a file is bridged or not, it will check if the file is a shell-plugin (Waves) and apply the settings to all right instances.
-
- KVRist
- 315 posts since 13 Jun, 2009
Have a feature request, shouldn't be complicated. I´ll elaborate what and why.
What jbridge does, it adds jbridge text to both name and developer name so Maschine for example can read both original and bridged version (I think reaper too).
I know some hate that, if they plan to use just bridged versions, but what if a user wants to use bridged plugins of same format just to occasionally take advantage of midi processors or oversampling in x42. Having both bridged and original version available for use is an advantage.
Another real world possibility example: Very often, like me, ppl have 100s of plugins. You work and need to call up a plugin just to discover it doesn't work well when bridged. So you´ll have to close project, go "unbridge" and what not to go to original version. Idea is gone especially if it happens more than once. Another advantage to have both available at same time.
One another thing, all my plugins are organized into folders by what they do and if I use just x42 bridged I would have hard time to find the right tools I need at certain moment. Example: half compressors/saturators etc aren't named as comp-saturator.
Ofcourse this should be optional when creating bridged files, for ppl that want just bridged versions only.
Must complain, in kushview Element, especially standalone, it doesnt work. Its doing kind of light show, closing-opening gui very frequently. After sometime it crash Element.
There is a free version of Element standalone available: https://kushview.net/element/download/
Idea was to create buffer between daw and plugins but so far its crashing daw instead of creating a safe buffer. At this point original plugin versions are more stable to use.
I believe in this project but we are not there yet. If you make it change name like jbridge I wouldn't rely on just 1 version of plugin (x42 version or original) therefore safer to use. Or at least when it start working in Element I could use them trough it.
Also, forgot, in p2000 is also behaving funky, cutting gui elements (x42 menu mostly) or doing light show or just crash.
What jbridge does, it adds jbridge text to both name and developer name so Maschine for example can read both original and bridged version (I think reaper too).
I know some hate that, if they plan to use just bridged versions, but what if a user wants to use bridged plugins of same format just to occasionally take advantage of midi processors or oversampling in x42. Having both bridged and original version available for use is an advantage.
Another real world possibility example: Very often, like me, ppl have 100s of plugins. You work and need to call up a plugin just to discover it doesn't work well when bridged. So you´ll have to close project, go "unbridge" and what not to go to original version. Idea is gone especially if it happens more than once. Another advantage to have both available at same time.
One another thing, all my plugins are organized into folders by what they do and if I use just x42 bridged I would have hard time to find the right tools I need at certain moment. Example: half compressors/saturators etc aren't named as comp-saturator.
Ofcourse this should be optional when creating bridged files, for ppl that want just bridged versions only.
Must complain, in kushview Element, especially standalone, it doesnt work. Its doing kind of light show, closing-opening gui very frequently. After sometime it crash Element.
There is a free version of Element standalone available: https://kushview.net/element/download/
Idea was to create buffer between daw and plugins but so far its crashing daw instead of creating a safe buffer. At this point original plugin versions are more stable to use.
I believe in this project but we are not there yet. If you make it change name like jbridge I wouldn't rely on just 1 version of plugin (x42 version or original) therefore safer to use. Or at least when it start working in Element I could use them trough it.
Also, forgot, in p2000 is also behaving funky, cutting gui elements (x42 menu mostly) or doing light show or just crash.