daw integration

[RustoMCSpit]

vs code extensions:

this would be an insane feature but heres the idea.

remember when i told you to change the documentation to allow people to install presets inside of plugins such as

"Difficulty expanding plugins with new presets.'

'Extend existing plugin functionality by installing additional presets (inside the plugin itself)'

note: add the 'inside the plugin itself' to the documentation

i cant remember if or where you put it but you listed off how you could use open audios downloading utilities in different mediums such as a website, an application, and a plugin. you may have put that in the downloading / installation document.
edit: you did

the feature im proposing is that you can use a daw as a way of downloading plugins. do you know how vscode has an extensions window? that but for daws. i imagine ardour and lmms are prime candidates as theyre big projects and FOSS but there may be licensing issues.

now i understand this is mainly in their control, not yours. youre just providing a registry and they have to implement. what im suggesting is to try to brand this project in a way that theyd be inclined to put the work in to integrating it. theyve dozens of developers and getting them using (and reliant) on the software would be a huge help and theres a mutual benefit. this would be a leg up on every propietary daw out there, theyve nothing like it (except maybe ableton with its build your own device stuff).

this is a very basic rundown of my idea, it needs to be expanded later

[RustoMCSpit]

im not going to alert LMMS or ardour (or any of the other foss daws (e.g. chipbox, tuneflow, stargate, dawdreamer, meadowlark, helio, gridsound, etc.) until this is more developed and out of its beta stage, thats why id like for this idea to be expanded on and in mind while developing the infrastructure early on.

[RustoMCSpit]

also this isnt just limited to downloading, this can include sending projects to other users, user accounts, reviews and comments, etc. all of this would require collaboration with daws.

we somewhat inadvertently even have some sort of version control with the way it logs changes to a project.

e.g. #15 this could become a gui where people can upload and fill in metadata, and download through daws. all of this again needs daw collaboration, im just trying to get you to understand my vision here.

somewhat like bandlab i think. imagine soundcloud integrated into a daw...? i hope you get what im trying to describe. this would require the daw devs to work with you but if this is branded right, and has the infrastructure, i see it working. especially if it works more as a modular component that just pops out as a window (though full integration into daws would be amazing from an aesthetics, and ui and ux flow perspective).

[kmturley]

Hello,
This is a great suggestion, but i'd imagine quite large scope in practice.
We would need to build an Audio plugin which can connect to the Registry and download/install other plugins.
I have seen examples where other plugins allow installing of remote presets, so i'm sure it's possible.
I don't have much experience in native audio plugin development, so we would need someone with those skills.
There is a way to embed web views/code inside a native audio plugin, which could allow us to reuse similar code between the app, website and native plugin.
Definitely a good idea, but will need a lot of thought and effort to make it work.

[RustoMCSpit]

We would need to build an Audio plugin which can connect to the Registry and download/install other plugins.

well again we could either make it DAW agnostic, which would mean making a plugin, or we could integrate into a daw(s) itself like vscode extensions and be able to click into it inside the daw (exactly like vscode extensions, as in it's not built on top as a module but integrated). the former is less user friendly but far more easy, the latter would require developers to make a lot of internal infrastructure for each daw. granted, it could be made into a simple window module which pops out and then each daw would just put a wrapper around it.

frankly, i dont think a plugin makes any sense for this. either integrate fully (dependent on if the daw's devs believe in this project and think it'll be worth it) or have a daw agnostic module that can be easily wrapped.

[RustoMCSpit]

'Extend existing plugin functionality by installing additional presets (inside the plugin itself)'

note: add the 'inside the plugin itself' to the documentation

[RustoMCSpit]

I don't have much experience in native audio plugin development, so we would need someone with those skills.

i recommend this framework if you want to start https://github.com/robbert-vdh/nih-plug

Definitely a good idea, but will need a lot of thought and effort to make it work.

frankly, this idea should be vetted by more experienced people in this field. im going to send this into some discords