Is there a multimode filter that lets you sweep from high pass to bandpass to low pass?
Hello @Dymaxion,
I don’t know if the Filta plugin by OpenAV might do what you want:
There is also a Bandpass Filter available:
Maybe some other forum members might suggest better solutions…
Greetings and God bless
Marius
1 Like
Yeah… I’m ideally looking for something with at least resonance, and ideally poles/slope
Of these, the Tal-Filter-2 is the only one that’s continuously variable, but there doesn’t seem to be a way to set the frequency, only the resonance and an LFO rate and depth. The FOMP Moogs are great, but I’d be back to manually blending between them. The AMS VCF is almost perfect, but the filter type controls are discrete, not a crossfade.
3 Likes
Another one — the ability to name the outputs on all the switchers — audio, CV, and MIDI — and have those names show up on the device screen.
Also, at least a four-way CV switch, but preferably up to eight. A four-way switch, for instance, is needed when you’ve got a mono effect that you may want to have running on either one channel, the other, or both. With a static voltage input, a four-way switch, and logic gates, you can build a drop-down list that provides all the options.
Alternatively, a plugin that does this directly — provides 2-4 CV output ports, lets you create a number of combinations, name each one of them, and select the value that goes to each CV port in each combination.
Also, it would be great to be able to change the displayed range and units for Control to CV — if you’re using this to indirectly control a couple of other plugins, having it display 0-10V is less than useful.
1 Like
You can do this already. When you are assigning a parameter to anything, if you click the Advanced Settings you can set the name. Take a look here.
I can name the parameter, but not the parameter values — for the CV Switcher, for instance, the values are just “1”, “2”, and “3”.
2 Likes
Would be useful to give a custom name to pages and show it somehow.
In my case, a have an amp on path A and same amp on path B. I like to have gain on knob 1, volume on knob 2 and treble on knob 3. I use this configuration on page 1 and page 2 but I have no immediate info about if I am on path A or B (I have to memorize that page 1 is for path A and page 2 is for path B).
Or maybe we have two plugins with same parameter names but I find difficult to recall if parameter on page 1 is from plugin X and parameter on page 2 is from plugin Y. This would be more complicated if you use more pedalboards. Parameter name customization is not that helpful since name length is limited. A workaround would be to let a parameter name to use not used space of other unused slots but this would work only if we use less than 3 parameters on a page, but it’s just a kind of workaround. Adding a custom page name would help a lot.
4 Likes
Moving the measurement unit on the right of the value would make room for a full row for page name
5 Likes
Reducing the vertical space between title bar and main area and reducing the parameter bar height would make room for a two rows param name.
Reorganizing sections and vertical unused space we could have a first row for page title and two rows for parameter name.
4 Likes
I agree that there are dead space that could be exploited but you have to be careful because all that text clustered together may be difficult to de-cypher once you are standing up playing your instrument on a live stage with the lightshow going on around you.
There are many factors that needs to be taken into account when designing screens for devices like this such as the type of font used in this case seems to be “Fixed”, meaning that an “i” takes the same amount of pixels than an “m” in width. This limits the number of characters you can put on the display.
The second issue is that these screens are low resolution and the pixels are bulky. Because of this, there is not many font sizes that can be used before all becomes unreadable.
As shown in @redcloud’s last screen mockups, I don’t think the size of text in the yellow/red/blue areas would allow for that many characters since the mockup uses proportional characters instead of fixed.
3 Likes
Of course the character used is not right but the idea of doubling (at least) available characters remains. Descriptions would help when you have to turn the knobs and a that time you are near the device, shouldn’t be a problem to read smaller fonts (unless you want to turn knobs standing because of your 6 ft long arms 
)
This would not be a good idea with the displays used. The small font on these displays becomes almost completely useless. If I remember correctly, they’re 128x64 pixel displays. This doesn’t leave very many pixels for small fonts…also from a UX/UI design perspective it is not very pleasing or practical. Less is definitely more in this case. Just my 2 cents
1 Like
It’s not a matter of using a smaller font but to use unused empty spaces leaving font size untouched.
1 Like
Using scrolling text would help also.
3 Likes
I like the idea, but if you look at the size of the current ‘large’ text, it’s actually 5 pixels tall. I don’t think you can actually get any smaller than that - but yes, you may be able to squeeze another line in with all the suggestions you gave.
There’s always room for improvement in efficient use of the available space.
Edit: Can anyone confirm the actual resolution of the screen? All I can find is the dimensions. If we had the resolution it would be easier to do mockups that were actually feasible.
2 Likes
It is 7 pixels actually. Again, I’m not talking about decreasing the font size but just about optimization of unused space.
We can save 2 more pixels by restyling the top bar
I was referring to the parameter text, not the title text at the top.
I wasn’t suggesting you were saying make the text smaller really, just that I question whether you can fit three rows like in your yellow/red/blue mockup. Maybe a second row.
Do you know the resolution of the screen by chance? It would be fun to do some mockups.
1 Like