falktx @falktx@mastodon.falktx.com

@pkirn @tidalcycles MIDI out in Redux means it can now be used in modular environments too, should work nicely inside carla and other synths 🤔

actually the same code works on Qt6.9, so maybe nothing else needed...?

Got wayland subsurface-as-plugin-UI now working for Qt6 hosts now too!

Though because it needs to access private APIs the code looks a bit "special" 😆
But I think it should be possible to expand the supported Qt versions by adding a couple of these...
What do you think, too nasty?

https://github.com/falkTX/wayland-audio-plugin-test/blob/ce3120ba52a1696f5f323948922e281f113cc92b/qt6-host.cpp#L40

@x42 yes yes that is what I meant, the gtk3 code is too tied to x11.

the jalv gtk3 code is quite complex, I think it might be easier for me to add a little support in carla instead.

but really wish getting some wayland related pointers/data out of Qt was a bit easier..
without it I cannot do the fancy "keep plugin UI on top of carla" thing under wayland

embedding custom wayland UI stuff on top of gtk3 and gtk4 based applications works! 🎉

the gtk APIs to get down to the wayland surface are a bit awkward, but at least its accessible.
I tried the same with Qt6 and couldn't find a way to have it return the underlying wl_surface pointer. 🤷

I got an LV2 plugin UI with this setup working, but no hosts to try it out against.
Modifying jalv.gtk3 is likely the easiest path... 🤔

WIP test code dump at https://github.com/falkTX/wayland-audio-plugin-test

doing some experiments with wayland and audio plugin UIs...
I have seen a proposal for that relies on a lot of proxy setup, but really don't like it.

so I did some tests with subsurfaces, and it seems very promising.
I have a big host window providing its surface to a "plugin" window for which it creates a subsurface to draw on.
Then the host can take control over subsurface for positioning, z-index, etc

Event input works with this approach too.

boring screenshot: grey = host, yellow = plugin

@trancefish good luck!

@zombiewarrior @prokoudine ocenaudio is not opensource and likely never will be https://github.com/ocenaudio/ocenaudio-translations/issues/12

@nielso separation of tasks and devices helps here then. Only the "dumb" phone has a sort of shared contact list

@x42 @thisven ah well its just for talking with family and friends stuff, not really work related.

though the CEO has my contact there there for emergencies

@x42 I never saw such thing and honestly have no idea what that is about.
What "contact list"? email is kept separate, so not that... sms and phone calls are not on the smartphone, so there is nothing to read from there...

do people really keep a centralized list of all their contacts?

I have people scattered around:
- IRC
- telegram
- signal
- line (korean chat app thing)
- sms/calls
- email threads
- nextcloud chat

very few are in more than 1

@thisven @x42 noted, and left whatsapp for somewhat similar reasons.

I was able to convince some family members to leave whatsapp for telegram, I am not able to convince them to switch to signal.

I also use regular phone calls for friends&family sometimes too, which would be even worse privacy-wise.

@x42 well all work stuff uses google and slack, telegram is only for talking with family and friends so it won't be a problem.
in any case all team meetings go through "AI" 🤮 for notes and other things, GDPR is out of the window already

@albertyeah you can start anytime! First thing though is learning a programming language that can work for audio plugins.

C++ is the most common one and best supported overall while being quite tricky to get to know really well, while Rust is new and not yet so common but likely easier to start..?

So it all depends on your experience.

Anyhow, I make https://github.com/DISTRHO/DPF for dealing with plugins, but as usual documentation is a bit lacking.

my work system surely likes to notify me of updates...

@prokoudine well those are in a similar situation too, I think we can count with our hands the amount of maintained open-source audio editors.

I was thinking of more generic terms, for any standalone audio tool (like a synth) for "apps".

I did mention "apps and plugins" on purpose, standalone-only audio tools are not very common, luckily