The purpose of the design guide is exactly to reduce the amount of wasted space, to make things more control/information dense while still retaining some recognisable resemblance to hardware devices. This is still important for many users, especially guitarists
We indeed have thought about and even discussed here before, having an optional “simple mode” that turns all plugins into nodes that just show the title and labels for their IO
So basically yes! I like the idea and I do think it will be nice if we can do that in the future. It’s already a ticket in our system and I will add your suggestion there as another insight that puts more weight on it. I really like node based editing too!
This will not replace GUIs though. Some people just relate to it much more and want to have access to all controls in context. There is definitely still a need for GUIs
Hi all, first post here. Background as a graphic designer (though not my current work). Musically I’m a guitarist and tinkerer. I love the faux hardware look of the plugins, and get a lot of my joy when designing my pedalboards just from neatly arranging all my pedals! One of the first things I have to do upon downloading someone else’s pedalboard is neaten everything up! LOL - I think I’m getting OCD!
@Klaustrophil 's screengrabs of other editing environments are interesting. I think a lot of that efficiency and neatness of signal flow could be achieved by simply having some adjustable parameters for the leads. A tension parameter allowing them to sag or tighten would be good for a lot of layouts, as well as a way to select pancake connecters (or even direct attachment like the Bitwig Grid widgets) so pedals can be placed much closer without graphic kludges as the connecters fight for on-topness.
Generally this project is a great thing and I’d love to help out the community in the spirit of open-source.
Ok, I’ve tried to format it in a way that makes sense, created ‘polls’ for the plugins already mentioned, and made it into a ‘wiki-style’ post.
The forum limits polls to 20 items, so I split it into “Calf” and “non-Calf” - I think it’s pretty obvious that a LOT of people want ALL the Calf plugins, so I treated that one as a prioritization indicator.
Another forum limitation means that we can’t edit these polls after 5 minutes, so we can’t add plugins without losing the votes cast. For now I’m leaving it, but we’ll need to find another solution I think.
We’re going to need a way to figure out what the (non-gui) status of these plugins are - i.e. are they ready for release and just need a GUI, or is heavy work required on the plugin itself before it’s stable.
I have not added this to the list.
I looked, and can not see a functional difference between that beta plugin and the “Switchbox 1-2 ST” plugin which is already released and has a GUI. Is there a reason you are using the beta version? Right now it looks to me like it’s just a redundant plugin that needs to be purged from the repository.
MOD team: Is there some way we as the community can help facilitate cleanup of some of these plugins that appear to be redundant, like the switchboxes? Or are these not actually redundant?
These should really be called Airwindows. That is the DSP code, and I was very much confused with this name.
Maybe just link to https://github.com/hannesbraun/airwindows-lv2 as well, to be clear.
Just now seeing the poll. the 3 Band EQ already has a GUI, I just never pushed it to the store because the plugin is too simplistic and there are better EQs now.
Since polls are uneditable, I don’t think they will work for this task. I’ve changed them to simple tables instead. This is unfortunate, but necessary - though I don’t think most users will understand how to edit the wiki post to add their vote, so it may be fruitless.
Names, URLs, and Authors were all pulled directly from the official plugin store data.
I’ve updated the URLs to the one you suggested, however I am leaving the Author as it was - This is used to identify plugins. For example, if there were two plugins with the name “Parametric EQ” the Author would be the only differentiation. If this information needs to change, it needs to happen on the store end first.
I’ve marked it as deprecated, but 3 people already voted for it. If people are actively using it despite it not even having a GUI, it may be worth reconsideration of whether it deserves a spot in the repo.
The “author” in itself is correct, what is actually missing is the “brand” tag.
The airwindows plugins should have it shown by brand, not by author. The store will show brand if one is set, otherwise fallback to the author name.
It is a mistake assuming that naming is correct for plugins in beta anyway.
I’m not assuming that the beta naming is correct, merely stating that this list needs to reflect what the plugin store indicates (right or wrong) to avoid confusion.
If a user goes to the beta plugin store based on this list looking for “Vibrato” they are going to see two options, neither of which indicate “Airwindows” They will, however be able to find Vibrato by Hannes, because that’s what the store currently shows. When the store’s info changes, this list will reflect that.
I’m using a single combined Highpass Lowpass EQ called The Pilgrim by Articanaudio I installed some time ago.
You find it in the Modulator section of the Beta Plugin Store.
Some remarks:
It would be nice for the frequency dial values to show the current value in Hz or kHz.
He removed it in favour of a table because of the restrictions on polls though now that we can make those restrictions whatever we want, perhaps it’s more useful
Ah! thanks @James. Anyway…so where’s the table? Was it removed as well already?
Sorry if I’m being super blind…sometimes my brain gets quite slow, aka dummy