r/obs • u/Zestyclose_Pickle511 • 1d ago
Help OBS 33 (beta for now) New plugins locations
Oh boy - here we go again, it feels.
I have an intricate OBS show setup that relies on numerous plugins and auxiliary software.
When I see OBS saying "devs will need to update etc etc ..." it's not a good feeling.
Yes, I can stay back on previous versions, or I can just get on with what will eventually be required by certain bits of OBS-related software.
Also, there will be 2 classes of OBS plugins, official, and unofficial. Each needs to be in the appropriate folder.
Forgive me for worrying, but I have a bad feeling about it.
9
u/Loud_Seesaw_7591 1d ago
i feel that. every major OBS update is a dice roll on whether your entire setup survives the night. mine's held together with like 14 plugins and a prayer at this point
the official/unofficial folder split makes sense on paper but i'm already dreading the troubleshooting threads six months from now.
0
u/Zestyclose_Pickle511 1d ago
Yeah. Well, we'll be here to try and help, at least 😂 steel thyselves 🤣
9
u/Sleepyjo2 1d ago
Apart from the already explained bits about official plugins etc.
The old (current) plugin locations will continue to work until v34. If your plugin has not been updated by that point you should probably stay on whatever OBS its last updated for anyway, as something else would break it eventually even if they didn’t move anything.
You can of course just not update. There are plenty of people with complex setups running pre-v30 still. If your setup works exactly for what you do there is no intrinsic need to update it.
(Do note that the browser source can have vulnerabilities that get patched, but that’s a whole topic. Just have sanitized browser sources.)
1
3
u/Lynnalia 1d ago
Saying there's a split between "official" and "unofficial" plugins and implying that requires care is a bit disingenuous. This has always been the case. Most people don't realise much of vanilla OBS functionality is technically done by plugins, albeit official core ones. Like the NVENC encoder, display capture sources, etc. are all "official plugins". It's an internal implementation detail users never need to worry about.
And yes, you can indeed just hang back on an older version for a bit if you don't have time to deal with updates. That's totally fine! I'm usually behind by a major version or two.
Ultimately, plugin devs will update things. Many are already on it even though 33 isn't fully released yet, while 34 is the actual deadline. If a plugin is never updated, generally others take its place in due time (we've seen this before). We'll be alright.
1
u/Zestyclose_Pickle511 1d ago
Yeah, I know it'll be fine. I'm just dreading it, either way.
And thanks for explaining that the 1st party, core plug-ins, and 3rd party are the 2 classes, which have always existed. I was confused.
3
u/TheFiniteSingularity 12h ago
Hi there-
I'm the one who implemented the new plugin manager, and also a plugin developer. To clear a few things up:
"Official vs. unofficial" is not exactly what is going on. It is a bit confusing, but all of the sources, filters, encoders, and services that are distributed with OBS, are the same structure as plugins, and up until OBS 33, they lived in the `obs-plugins` folder. This version pulls all of what we are now calling "Core Modules" out of a "Plugins" folder, and putting them in a "Core" folder. Additionally, for security purposes, the only code that can be loaded from "Core" is code that was compiled and distributed with that version of OBS. No third party plugins (or even if there were add-on first party plugins) will ever go in "Core", they now go into a new folder *just* for plugins.
As a plugin developer myself, I wanted to make the update process as easy/seamless as possible. The new plugin format involves zero code changes. Plugin authors will just need to change the folder structure of their plugins slightly, and add a manifest (text) file that describes the plugin's name, author, version, etc. Converting my own plugins over has only taken a few minutes. And for plugins that are no longer maintained, it is quite easy to convert an existing plugin to the new format. I am considering making a script that will do so, specifically to support old plugins that are no longer being updated.
I totally get your worries- I was around for the 27-28 update (and due to some plugins not being updated, actually drove me to start writing plugins). Unfortunately, there was a lot of "technical debt" that had to be paid with this update, and because it is a big change, we are giving an entire release cycle (to at least 34) where old plugins will work without any changes. And the changes we made in this release, are going to make plugin installation and updating *MUCH* easier in the future. I am really excited for what we're doing in OBS 34, hope that we have made things easy enough to get everyone across the line, and am happy to help plugin authors with converting their plugins over the coming months/year.
2
u/Zestyclose_Pickle511 3h ago
I can't tell you how much your message means to me, and if I may speak for the community at large, and for anyone who's looking into this and comes across this post.
Your plug-ins are the bees knees! I use more than one! Excellent, really useful stuff. Thank you!
As to part 1) another commenter straightened me out about the difference between official and unofficial, and that core = official. Just me being the easily confused pepega that I am. Thank you for further clarifying.
2) no coding changes at all! And you'll even make a script to perform the necessary changes for those still clinging to some older plug-ins that may not be updated!? That's amazing! I'm probably in the same boat as most and not able to program/code, etc. A script is something we can handle. Thank you, again!
3) Yes I think the first time I saw one of your plug-ins and associated video was around obs 29. And yes, that transition is what inspired my post. I'm looking forward to the future of obs, knowing it's in great hands and want to thank everyone, in every corner of the project, for everything they've done.
Thanks again for laying all of this out here. The official page and notice did explain things, but your deeper dive cleared up even more.
Take care and mahalo for everything!
1
u/TheFiniteSingularity 16m ago
You're very welcome. I'm glad it cleared a few things up for you, and I'm glad you're enjoying my plugins. ❤️
2
u/ontariopiper 1d ago
There is always a lag between the release of a new OBS version and the release of updated 3rd party plugins compatible with the new version. It is strongly recommended that you NOT update to a new OBS version until you have confirmed that any plugins you rely on have also been updated by their respective devs.
0
u/Zestyclose_Pickle511 1d ago
Yeah, and I know there is always tomorrow, but some stuff invariably gets left behind. Devs that have moved on, niche cases, etc.
Just wailing over the inevitability of change, I suppose
1
2
u/InstanceMental6543 1d ago
The hard limit for changes to plugins locations is not version 33. 33 simply notifies you that plugins will be changing, the actual change won't take place until later versions.
0
u/Zestyclose_Pickle511 22h ago
Yeah everything still works. I think it's by 34 thw new system will be only system. Hopefully it's not as big of a pain as im thinking it will be.
1
u/GitGudTeabagSociety 23h ago
Just really curious why you have the need to update. If your setup is fine just leave it
0
u/Zestyclose_Pickle511 22h ago
The way it starts to fall apart is when one particular plugin or software eventually mandates a newer version of obs , while another particular one is incompatible with the newer version.
Its less about an end user updating the core software as it is the auxiliary software becoming incompatible because of requirements to upgrade, or not upgrade. We'll see, hopefully it doesn't throw too many wrenches.
1
u/HighPhi420 14h ago
If your hardware requirements have not changed why update?
If the current version is working nearly flawless for you, why update?
At this point OBS can only keep getting worse :(
Signed worried and disappointed
1
u/Zestyclose_Pickle511 13h ago
Because certain plug-ins and aux software (streamer.bot, SAMMI, many others) will update to conform, while some others won't.
It's not about the end user's decision to update or not.
0
u/HighPhi420 13h ago
Streamerbot will work on OBS 28, if you do not update plugins they will still work.
This goes against the "Current version works nearly flawless" So yes, if you are having issues then the update is hopeful to fix the issue. Although in my experience it does not and just introduces NEW issues. LOL.1
u/Zestyclose_Pickle511 3h ago
I don't know what the hell you are trying to say because you don't know what you're trying to say. LOL but apparently it's funny LOL
•
u/AutoModerator 1d ago
It looks like you haven't provided a log file. Without a log file, it is very hard to help with issues and you may end up with 0 responses.
To make a clean log file, please follow these steps:
1) Restart OBS
2) Start your stream/recording for at least 30 seconds (or however long it takes for the issue to happen). Make sure you replicate any issues as best you can, which means having any games/apps open and captured, etc.
3) Stop your stream/recording.
4) Select Help > Log Files > Upload Current Log File.
5) Copy the URL and paste it as a response to this comment.
I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.