there are various MOD CV plugins for logic operations (CV Changed, Logic Equal, Logic Larger, Logic OR), but they don’t appear to have inputs or outputs…
are they actually functional?
am i missing something?
thanks for any help!
4 Likes
Like you I would really enjoy some explanations or examples, it seems like it could program some events inside pedalboards but it stays obscure for now !
3 Likes
This one was also one of my open tabs since a while 
They seem to be working fine. Can you elaborate a bit more? What aren’t you able to do?
i just don’t understand how to use these plugins to control anything else…
let’s look at a specific example: the “CV Changed” plugin. i’ll outline exactly what i’m doing, so we know what we’re talking about…
i put an “AMS LFO 2” on a pedalboard. then i set its frequency to 0.05Hz – plugging its output into a CV Meter shows the slow change of values, positive and then negative. i turn on “Manage CV Ports” and name the LFO output “lfo”. then i put a “CV Changed” plugin on the board, go into its parameters, and assign its ON/OFF to the “lfo” CV value.
indeed, “CV Changed” works – it switches OFF when “lfo” goes negative, and it switches ON when “lfo” goes positive.
my problem is that i don’t see any way to use that ON/OFF switching to control anything else, because there’s no output from the “CV Changed” plugin that could be assigned to anything else (either by plugging a cable or by naming a CV Port).
…it feels like i must be just missing something about what these CV logic plugins are supposed to do, or how to actually use them.
help?! pretty please?! 
@plutek, where did you find these plugins if I may ask? I cannot find them in the beta section of the plugin store.
Them not having inputs/outputs can be explained by them not being finalized for use on the MOD platform. (they need to be defined as MOD-CV-Ports before they show up)
There is now a plugin called “Logic Operators” which provides the functionality in an all-in-1 plugin, and it’s available from the official side of the store: Logic Operators - MOD Devices
//Jesse
2 Likes
thanks @jesse … yes, just before reading your reply i found that newer CV logic plugin!
when i’m in the plugin store and search “logic” (with “beta” enabled), i see this:
… you can see the 4 non-functional ones along with the new multipurpose one.
perhaps the old ones should be removed?
2 Likes
is it possible that these are just being seen on my Duo X, since i installed them a while ago, but actually don’t currently exist in the store?
3 Likes
Thanks for getting back so quickly!
As far as I am aware they are already removed from the store, but for obvious reasons we do not remove any plugins from users’ devices. (In fact, I don’t even think we are able to)
If you uninstall them they should no longer show up. Could you please confirm that for me? If they still show up then I will create a ticket for us to fix it.
3 Likes
yes… in fact they no longer show up in the store, once i’ve removed them from the device.
this brings up an interesting quandry; as you’ve pointed out, you can’t (and shouldn’t) remove old plugins (no longer in the store) from users’ devices – we may depend on those in pedalboards we use.
however, i would suggest adding something in the store which flags plugins very obviously which are installed, but which are no longer in the store. that would alert users to possibly investigate better, more current, replacements for deprecated plugins at their discretion.
for example, had there been some indicator that these old CV logic plugins had been deprecated, i would have looked for current replacements, and then probably would have found the new one.
there could be an added filter category in the store: “installed but deprecated”, or somesuch.
5 Likes
Probably, even a simple “deprecated” tag, analogous to the “update” when browsing the store would be enough. This should be very little work to implement.
2 Likes
sure thing… as long as there’s a way of listing everything that’s installed but also deprecated, like there’s an “update all” button. then the user can decide what to do with them.
1 Like
That would make sense as well if you have them installed (otherwise they won’t show up). Anyway, if for example, you have them loaded in a saved pedalboard, I still think that the pop-up would work better.
From another perspective, the idea of the popups is to deliver useful messages and something similar to what appears now when you have an update or a Control Chain device connected. If we can up-use something that is already in place and/or if we can create something that works for multiple things the implementation work will be easier and pay off more.
1 Like
Of course the popups would be much better. I was just suggesting a simple solution that would put little or no weight on the devs shoulders to implement, since I guess that the fact that you already have in place an API that queries the store in order to compare the versions of the installed plugins can be effortlessly enhanced to trigger the “deprecated” label in case a plugin has no correspondence.
But if you have time and resources for something better, so be it
4 Likes
Actually you are right. We were both worried about the same thing but looking from different perspectives.
I was looking from the perspective that we already have popups appearing, so it would be “simply” adding more and with different triggers.
2 Likes
from the point of view of what a user might want to know, i’d personally want to answer these questions:
-
when i load a pedalboard, does it contain deprecated plugins? a popup is ideal for this case.
-
what are all the currently installed but deprecated plugins on my device? another search filter in the store seems ideal for that.
…both use existing mechanisms, but they really do different things - and i think both things are important. if we answer only question #1, then we don’t know what else is installed on the device, which might need attention. if we answer only question #2, we don’t know which pedalboards actually use the deprecated plugins. …so, for a complete solution to this issue, the two questions/mechanisms lean on each other…
it brings up another, related question:
what pedalboards on this device use any particular plugin? something in the store which would answer that question, while browsing plugins, would be really useful as well! 
5 Likes
Actually after @Tarrasque73 feedback/perspective I think both notification types would be the best. Because they inform you in different occasions and in windows that are not having a huge relationship.
2 Likes
Just adding a perspective: I am personally not a big fan of popups. Once would be fine but if it popped up every time I open a pedalboard, I’d probably be annoyed.
Then again I am slowly turning into a grumpy old fart so being annoyed would be the default mood anyway 
2 Likes
lol. yup, i get that!
yeah, i’d probably get annoyed as well, but less annoyed than not knowing when i’m using deprecated plugins!
1 Like
That’s exactly something that we talked about right the first time that the idea popped up ( 
).
The popups should be helpful and not distractful. Appear only when needed (for example if you load one of these plugins or when you open a pedalboard that has them loaded) but stay for like 10 seconds. Nowadays we already have plenty of distractions and the focus here should always be to make music, not to be aware of everything.
2 Likes