search

JoepVanlier / ysfx

Hosting library for JSFX
Apache License 2.0
39 stars 3 forks source link

[BUG] Some JSFX plugins GUIs are not showing correctly in BespokeSynth #50

Open crshrprt opened 2 months ago

crshrprt commented 2 months ago

Describe the bug I tried a few JSFXs from the JoepVanlier JSFX repo and when opening them in the JoepVanlier ysfx vst3 they don't show the GUI correctly. With the jpcima ysfx the plugin's GUI is showed correctly.

This problem seems to happen only in BespokeSynth, AFAIK. In Ardour the JoepVanlier ysfx vst3 load the JSFX plugin's GUI correctly.

To Reproduce Steps to reproduce the behavior:

  1. Load JopeVanlier ysfx vst3 in BespokeSynth
  2. Click on "Load" end select Saike_Yutani.jsfx
  3. The plugin is loaded but the GUI is not showing correctly

On the left jpcima ysfx vst3, on the right JopeVanlier ysfx vst3 See screenshot: ysfx

Desktop:

JoepVanlier commented 2 months ago

Interesting. I just tried with bespoke 1.2.1 (on windows, ubuntu 24.4.1 and debian 12.7.0) and the latest nightly on windows. For me it's exactly the opposite. jpcima's comes up blank and ysfx-s shows the UI.

afbeelding Left here is tag v0.0.2 (which was the last commit on the jpcima repo), right is last release.

Did you compile these from source? Is it possible something funny happened with linking JUCE? For me, I end up having to wipe my build folder every time I switch between a commit before or after the transition to JUCE8. It seems that not everything triggers correctly to fully rebuild on my end (shouldn't be an issue on CI where the artefacts are produced though).

What version of ysfx from jpcima is this? Do you know which commit it was at?

Does it also happen if you load only ysfx-s (never load ysfx first in that same session)?

Is it possible something got cached funny? Is it possible to reset the VST cache in bespoke?

Do you know at which release it stopped displaying the UI?

Can you show me the right side of the UI of ysfx-s? What happens if you click the scaling button?

crshrprt commented 2 months ago

Did you compile these from source? Is it possible something funny happened with linking JUCE? For me, I end up having to wipe my build folder every time I switch between a commit before or after the transition to JUCE8. It seems that not everything triggers correctly to fully rebuild on my end (shouldn't be an issue on CI where the artefacts are produced though).

What version of ysfx from jpcima is this? Do you know which commit it was at?

I tried to delete the old jpcima ysfx and compiled again, starting fresh from scratch, the last jpcima's commit. Now also the the jpcima's ysfx can't display Yutani GUI:

jpcima_ysfx_youtani

Does it also happen if you load only ysfx-s (never load ysfx first in that same session)?

Yes, compiled the latest JopeVanlier's ysfx, cleared the plugin cache, restarted BespokeSynth and the result is the same.

Is it possible something got cached funny? Is it possible to reset the VST cache in bespoke?

I tried to clear the cache and even removing all the plugins in .vst3, also removed every plugin cache file in BespokeSynth, just in case.

Do you know at which release it stopped displaying the UI?

No version is displaying Yutani's GUI. I tried also 0.02 and 0.04.

Can you show me the right side of the UI of ysfx-s? What happens if you click the scaling button?

latest ysfx-s, right side:

2024-09-17_13 00 12 315

latest ysfx-s, scaled:

youtani_scaled

latest ysfx-s, resized

youtani_resized

For completeness of information I'm using Xorg.

If in your tests with Debian 12 everything worked I suspect it could be some newer package in Sid that might create this issue.

JoepVanlier commented 2 months ago

Interesting. Just to be clear, yesterday, I didn't recompile on debian. I used the artefact from CI.

I just compiled it on Debian (in virtualbox) to see if the plugin works there and it did. So for me, it's really a mystery.

Would it be worth giving the artefact a shot? Or would that not be compatible?

crshrprt commented 2 months ago

It's a mistery indeed. I just tried this one and it doesn't work. Feel free to close this issue, as for now I don't have any clue why it should work on Debian 12 and not on Sid, beside some newer package causing this issue. This case seems now most likely since I tried on another machine with Sid and I have the same problem, so it's not specific of my main machine. If I find some new clues I will let you know.

JoepVanlier commented 2 months ago

Curious. I'll leave it open for now, in case someone else notices the issue and has some ideas on things to try.