LinuxMusicians

testing the plugins:

https://www.youtube.com/watch?v=EYU3HA0HRuc

- tor-helge

finally got around to record a video, with sound this time.. (but unfortunately a bit low volume).. i went through the plugins, one by one, and tested them, so that you can get at least an impression of what the plugins do.. and, you can say that this is the current state of the KODE framework repos...

did some more gui work: https://i.imgur.com/Tj1UATL.png vst3 in ardour, using cairo (on top of xlib/xcb) so far, i have avoided giving any considerations to the looks or design.. the widget painting, and the events/functionality is separated, so it's very, very easy to make a variant of a widget tha...

sjaehn wrote: ↑Sun Sep 05, 2021 9:28 pmI do not plan for VSTs YET. I'll look for LV2 on other platforms first. But I don't know where I'll go in the future. Maybe I'll port the B.Music plugins to DSP. But B.Oops will not be the first plugin. Too complex.

too bad..
it would be interesting to try these plugins..

- tor-helge

Well, GPLv3 would certainly fit everything as it's compatible with all major licenses still in use (except [L]GPLv2 without the "any later version clause", ironically! :lol:), and it's used by major frameworks like JUCE and VST3 so I suppose it's not a problem for FLOSS users. i'm not too...

GPLv3 is considered a "viral" license (I don't like the term because virus are usually bad things but there are actually good viruses which help us stay healthy :D). This means that as soon as your code interacts with GPLv3 code (and this includes linking), your code must be GPLv3 too. So...

d.healey wrote: ↑Sat Sep 04, 2021 11:40 am Can the GUI use vectors or only images?
I don't see a license file or headers in the source.

both vector gfx and bitmaps..
and, need to think a little more about licensing..
gpl3 is the most probable, it seems..

- th

First, congratulations for the release! Second, even if I am not a lawyer, if you have any questions about licensing feel free to PM me. But in short, from what I've seen from your license.txt file, you could travel the same road as JUCE and: 1) Make it GPLv3+ 2) Ask contributors to sign a CLA 3) S...

i posted a few plugins here:
viewtopic.php?f=44&t=23604

- tor-helge skei

(2009-2021, and still evolving) the last few days, i've been focusing on the gui "a picture says more than a thousand words", they say: https://i.imgur.com/N7io37m.png source code (the KODE framework itself, and the plugins): https://github.com/skei/kode2 i compiled a bunch of test plugins...

thread is getting off-topic... :shock: but, well, well.. vst3 with gui works in bitwig, reaper, carla, qtractor, ardour.. (not using the steinberg's sdk).. gui-less lv2 seems to work in reaper, but haven't tested it much (not a high priority).. xlib/xcb gui, working on widgets: https://i.imgur.com/X...

at least on qtractor, the Vst::IAudioProcessor interface is only instantiated when the component is ready and setup immediately before actual runtime processing; the scan process (which reports 0 ins and outs in your case) won't do any of that so the critical issue is more about what you and your p...

Your bus information is incomplete (and because the object has not been initialized, the fields you forgot to set may be filled with garbage). ouch... this made me look into the BusInfo struct again, and, you're right.. so i added the missing flags and busType, and the plugins started working! than...

i did a full overlaul of the bus/channel system in my plugin framework.. and read everything i could find related to that in the official sdk/docs, steinberg forum and from google searches.. and then i added some VERY extensive logging, printing out all sorts of information for all vst3 calls my plu...

Linux Mint, because (almost) everything just works, and you can focus on the important things - the music..