Open amadeusp opened 10 months ago
Hey @amadeusp thnx for the detailed report!
I'm going to have to investigate what's going on here. I'm on an older version of Bitwig myself (latest 4.x) and there everything loads correctly.
Do you have the same issue with CRSHR/FLDR/SMTHR?
These 4 plugins are built on a newer version of DPF, so it could be there is a bug in the stack.
I wanted to add that this is not limited to Bitwig Studio. In Ardour 8.1.0 (Flatpak) there is no UI as well, see:
@dromer CRSHR/FLDR/SMTHR suffer from the same issue. All the other WSTD plugins seem to work just fine, see:
@dromer I can imagine that this could have something to do with the fact that I am running both Bitwig and Ardour as Flatpak. Interestingly enough your older plugins work flawlessly with a flatpaked DAW. Is there maybe any external dependency with the newer version of DPF?
@amadeusp No there are 0 external dependencies, but I suspect it's because you are using Wayland which is known to behave poorly with parented plugin windows. I'll set up a build with an older version of DPF to see if that will work for you.
Do you have the same issue with the latest release of Cardinal? -> https://github.com/DISTRHO/Cardinal/releases/tag/23.10
@dromer I just checked and it doesn't work with X either (Bitwig and Ardour).
... downloading Cardinal for a test run right now.
@amadeusp thnx for checking!
Really odd. Can you try this build? -> https://github.com/Wasted-Audio/wstd-manglr/suites/17641384127/artifacts/1008570326
@dromer I tried Cardinal for the first time today and it seems like it doesn't run on my system out of the box. I would need to investigate why though. All the log says is as follows
com.bitwig.flt.library.metadata.reader.exception.CouldNotReadMetadataException: could not read metadata: Failed to load VST 3 plug-in /home/amadeus/.vst3/Cardinal/CardinalSynth.vst3: /home/amadeus/.vst3/Cardinal/CardinalSynth.vst3/Contents/x86_64-linux/CardinalSynth.so: cannot open shared object file: No such file or directory
@amadeusp thnx for checking!
Really odd. Can you try this build? -> https://github.com/Wasted-Audio/wstd-manglr/suites/17641384127/artifacts/1008570326
This build works flawlessly.
@amadeusp thank you for confirming!
I'll relay this information upstream. Hopefully we can find out what's wrong and get things fixed asap.
Today I'll see if I can do a 1.0.1 bugfix release for all the new plugins back to the old DPF versions to make sure this works ootb on systems like yours.
@dromer Thank you so much! It will be interesting to know what was the problem.
@amadeusp ok all the new plugins should be patched with the working framework version.
Hopefully this was the only major bug that is found on this release ;)
@amadeusp ok all the new plugins should be patched with the working framework version.
Hopefully this was the only major bug that is found on this release ;)
Fingers crossed! 🙌
Hope you will make some gnarly sounds using these :)
@dromer That is 100% my intention! Thank you for being awesome and making such amazing plugins! 🫶
@amadeusp btw I might have you try a jack standalone build later. We want to see if this is an issue specific to the plugin or more general. Also because Bitwig eats all the logs hopefully it'll say something useful on the CLI.
There was no output in the Ardour log window was there?
@amadeusp btw I might have you try a jack standalone build later. We want to see if this is an issue specific to the plugin or more general. Also because Bitwig eats all the logs hopefully it'll say something useful on the CLI.
There was no output in the Ardour log window was there?
Sure, I am happy to test it.
Nope, unfortunately Ardour is quiet about the issue as well, see:
@amadeusp can you try this latest build with updated dependencies? https://github.com/Wasted-Audio/wstd-manglr/actions/runs/8968732227
It would be nice to be able to upgrade without having users like yourself with broken UI :)
@dromer I downloaded and installed the plugin files from wstd-manglr-linux-x86_64-28b0d408 to ~/.vst, ~/.vst3, ~/.clap, and ~/.lv2 and tested the plugins in Bitwig and Ardour. Unfortunately, the UI does not appear in either of them.
@amadeusp hmm, thnx for testing. This will need more investigation to figure out ..
Maybe I'll try to install Manjaro in a VM in order to reproduce this, was hoping this wouldn't be necessary ..
@dromer Is there any way for me to generate some debug logs to maybe see what is going on?
Can you try the following from a terminal?
export DPF_CAPTURE_CONSOLE_OUTPUT=1; bitwig-studio
And then open the plugin. It should output some logs in /tmp/dpf.*.log
If not we need to prepare a debug build.
@dromer If I run export DPF_CAPTURE_CONSOLE_OUTPUT=1: bitwig-studio
I get export: not valid in this context: bitwig-studio
.
I tried export DPF_CAPTURE_CONSOLE_OUTPUT=1: com.bitwig.BitwigStudio
as well...
@amadeusp oops, that needs to be a ;
:)
And can you otherwise try latest master_me build? -> https://github.com/trummerschlunk/master_me/actions/runs/8967783370
It also uses DPF and DPF-Widgets for the UI.
@amadeusp oops, that needs to be a
;
:)
Got it! :)
However, that returns:
Bitwig Studio is already running - opening files
and afterwards (I mean, after opening the plugin in Bitwig) there is no /tmp/dpf.*.log
.
I am happy to report that both CLAP and VST3 versions of master_me seem to work flawlessly.
Of course you have to open bitwig only once with that command.
Interesting that master_me does work, though .. really no clue yet. I'll prepare a debug build for you to test.
@amadeusp try this: https://github.com/Wasted-Audio/wstd-manglr/actions/runs/8974225854/artifacts/1477597764
And maybe check the console in Ardour again? I'm not getting any tmp file with the DPF flag either ..
@amadeusp here a version with a different DPF: https://github.com/Wasted-Audio/wstd-manglr/actions/runs/8974396537
This should correctly output to a file as well, but I suspect it might also have the fixes I initially intended to test.
@dromer I (again) did not get the log output but this build renders the UI correctly! \°/
@amadeusp ok! great!
Then we know that DPF develop branch has fixed this. Thank you a lot for testing!
Issue
Unfortunately the plugin's window (UI) is not showing up, nothing happens (no error, also not in the logs) when I click on the little window icon of the device in Bitwig Studio 5.0.11 (Flatpak) on Linux.
Steps
Expected behavior
System information