Why the heck did we remove idle effects for audio spectrum that was one of my favorite features of the program. Please bring it back or someone tell me how to fix it because I cant find it anywhere.
We have moved this functionality to a new system of Macros because the old way wasnât fully compatible with the app and had high maintenance.
It basically meant that anywhere we set or interact with effects needed to have a split in it and instead of managing one effect (and recording history, adding shuffle support etc) we had to juggle 3 different effects.
Very few users actually used the system (<3%) and it created a lot of support issues with people not understanding how to disable it, or how to get it to interact with other systems in app
The new way to create the audio rule is as following:
The real reason is that the SignalRGB team decided they wanted to try and suck money out of their customers by paywalling previously-free features behind a $5USD/month subscription.
I mean, is there any valid, logical reason that as soon as the update was pushed to move this feature behind a paywall, the devs on the subreddit started saying âweâll be adding this feature to the free version immediatelyâ and âcontact the support team on Discord to have them enable it on your accountâ, and four months later itâs radio silence?
And the worst part is, the team actively discourages downgrading/hides older versions & forces updates for the program, so even if you downgraded to an older version before this hare-brained scheme was thought up, the program will force you to update anyways, without your explicit consent.
Audio visualizer was the only feature I used SignalRGB for. Without it, and without me willing to pay $5 a month, SignalRGB is no better or any more advanced than any other basic RGB program. Iâm switching back to OpenRGB (the original project that served as a base for SignalRGB) until this is resolved. 
Cool, now post how to do it without paying you, like we could before the update
Macroblocks will be released to free users too, so you can do the same without needing to pay for it. This wonât be paywalled.
Is there any news on when these Macroblocks will be released for free users?
Hi Mike, Iâm working on this now.
Weâve been slammed with tons of fixes, features, and upgrades this year. Regarding the delay in solutions for the âwhen audio is playingâ ruleset; well, that one is on me.
Hereâs the story.
The original framework for the ruleset (when media is playing, when idle) was just sort of an experiment for me. Fast forward two years and several employees later: Most folks in marketing here thought that it wasnât widely used. In fact, when we measured, only about 10% of our users made use of that feature and most were pro users already.
The logic that drove this was really limiting from a maintenance perspective, and wasnât extensible. It polluted the lighting manager and was intended to allow additional rules for âwhen app is runningâ, etc; but the interface wasnât flexible enough to make this work the way we wanted. This actually ended up being a catalyst for design of the framework that became âmacrosâ. Macros are really more like automations, and are extensible and expandable via javascript. One of the first things we did, was make sure that the âmediaâ ruleset worked well for pro users who use it.
This left free users in the cold, I realize that. The plan was to open up a couple of macros (automations) for free users, and then let pro users create an unlimited number of them. Then, we got insanely busy. We had a few big hurdles that got prioritized higher up like fixing QOL issues around Layouts and the Devices page combined with executing on our partnerships with other companies. It has been a schedule battle, but weâre closer to this happening.
The guys on our team are far from greedy capitalists, I promise. We try to be very very cognizant of this balance though, and we appreciate the feedback. Watch the beta channel in the next couple of weeks.
Thanks for hanging in there with us; weâre happy to have you here. 