Script Approval Process

khaver

Member
I know I've preached patience to other contributors who've commented on the time it takes to have a resource approved, but I just noticed someone else's LUA script that was submitted on Dec. 11th was approved recently (control-audio-sources-volume-toggle-mute-with-hotkeys), while one that I submitted on Dec. 1st is still waiting (RGB Tool). This is the first time I've noticed something like this happening.
 

khaver

Member
It's been exactly 1 month since I submitted a LUA filter to this forum and it still has not been approved. In this time, like I mentioned in my previous post, only one other resource has been approved, and it was submitted after I submitted mine. I already have some changes I'd like to make, but don't want to update it until it's been released to the public first. I know this project is all voluntary, run by just a handful of people, but it seems there should be a quicker process. It's making me have second thoughts about creating more resources to share here if they'll end up stuck in approval limbo.

Rant over.
 

upgradeQ

Member
You could also write your scripts in a bundle, pack it in single script and just release updates to that script, this works perfectly for filters whose you can enable or disable one by one in runtime. Properties have ability to be hidden with obs_property_set_modified_callback which you can use to make control panel UI for all packed filters. Check out code structure for properties there : StreamFX , Move transition , obs-libre-macros

P.S. if you update resource description this will also trigger approval process.
 
Top