Composite Blur

Composite Blur 1.6.1

Download
Overview Updates (12) Reviews (20) History Discussion
Oh dear. OBS informed me of the 33 update which I approved.
Realised a bunch of the plugins are now out of date so downloaded the 33 version or the Windows (not installer version and also the installer version)
Firstly the installer versions once again give me the error message - no I don't use Windows Defender, I use ESET, which will notify me any time it has an issue.
So I tried unpacking the non installer version and got lost with where to put the files. Because I'm now dealing with 33 not the previous version.
 
The installation location depends on if you're running OBS in portable mode or not.

If you're not running in portable mode (e.g., you used the OBS installer, installed it to `C:\Program Files\obs-studio`), then you are going to put the plugin folder from the zip in: `C:\ProgramData\obs-studio\plugins`. So you should see an `obs-composite-blur` folder in the Program Data plugins folder, and inside that folder there should be a `obs-composite-blur.dll`, `obs-composite-blur.pdb`, and a `data` folder.

If you're running in portable mode (e.g., you added a `portable_mode.txt` file to the root of your OBS installation), then you'll going to put the plugin folder from the zip in: `<YOUR OBS ROOT FOLDER>/plugins`

Please let me know if that helps.
 
FiniteSingularity updated Composite Blur with a new update entry:

Installer Bugfix 1.6.1

This is a bugfix for the Windows Installer for Composite Blur. If you were having issues installing Composite Blur 1.6.0 with the windows installer, please give this version a try.

NOTE: I have included separate zips/installers/debs compatible with OBS 33+ and OBS 30-32. Please make sure you download the file labeled with your version of OBS.
Click to expand...

Read the rest of this update entry...
 
Hey there!

I updated OBS to v33 and also updated Composite Blur with the v33 compatible zip you provided by placing the obs-composite-blur folder into the new plugins folder. However, OBS was still complaining that it wasn't compatible.

I thought it may be because I still had the old files in the v32 folder locations so I deleted those, but then OBS said the plugin wasn't installed anymore. So I updated Composite Blur with the v32 zip and now it's working fine, except OBS sees it as a "legacy" plugin.

For whatever reason, OBS 33 is ignoring the obs-composite-blur folder in the plugins folder. I'm not exactly sure what I'm doing wrong?

It's working for now, but I'd love to actually update properly. Any advice would be lovely.

Thanks!
 
ManedCalico said:
Hey there!

I updated OBS to v33 and also updated Composite Blur with the v33 compatible zip you provided by placing the obs-composite-blur folder into the new plugins folder. However, OBS was still complaining that it wasn't compatible.

I thought it may be because I still had the old files in the v32 folder locations so I deleted those, but then OBS said the plugin wasn't installed anymore. So I updated Composite Blur with the v32 zip and now it's working fine, except OBS sees it as a "legacy" plugin.

For whatever reason, OBS 33 is ignoring the obs-composite-blur folder in the plugins folder. I'm not exactly sure what I'm doing wrong?

It's working for now, but I'd love to actually update properly. Any advice would be lovely.

Thanks!
Click to expand...
Which plugins folder are you placing it in? The one in `ProgramData`, or the one in your obs folder? If the one in your OBS folder, you need to make sure (with v33) that you're actually running in portable mode (e.g.- you have a `portable_mode.txt` file in your obs program folder).

If thats still not working, it would be great if you can provide me with a log file. Just go to `help-->logs-->upload current log` and paste the url it gives you in a response here (or DM it to me).
 
GroundByte said:
Hello,

updated to OBS version 33.0.1(installed via deb download from the github release page) and updated the plugin as well on Ubuntu studio (Ubuntu 26.04). However, the plugin isn't being loaded with the manager popping up a warning and flagged with "error"

here's a link to the log; https://obsproject.com/logs/64tAQIsE8Q3zjOmb

Hope this information help!
Click to expand...
Thank you for the log file. That error typically would occur if it is trying to load the older version of the plugin with the new OBS. Where did you get the new version from? Here on the forum? Can you please make sure that the version of the plugin you downloaded was the 1.6.1 release? I may need to figure out if for some reason the installation of the new plugin is not overwriting the old version.
 
FiniteSingularity said:
Which plugins folder are you placing it in? The one in `ProgramData`, or the one in your obs folder? If the one in your OBS folder, you need to make sure (with v33) that you're actually running in portable mode (e.g.- you have a `portable_mode.txt` file in your obs program folder).

If thats still not working, it would be great if you can provide me with a log file. Just go to `help-->logs-->upload current log` and paste the url it gives you in a response here (or DM it to me).
Click to expand...

I have OBS installed so I'm placing it in the folder located here:
C:\Program Files\obs-studio\plugins
inside of a subfolder named "obs-composite-blur", but I've also tried it outside of the subfolder as well.

Is that the correct path?

I'll DM you the log.

Thank you so much for your help!
 
FiniteSingularity said:
Thank you for the log file. That error typically would occur if it is trying to load the older version of the plugin with the new OBS. Where did you get the new version from? Here on the forum? Can you please make sure that the version of the plugin you downloaded was the 1.6.1 release? I may need to figure out if for some reason the installation of the new plugin is not overwriting the old version.
Click to expand...
I downloaded the zip from here on the forum, specifically "obs-composite-blur-1.6.1-OBS33-linux.zip" and used the deb file within it. I'd check to see if I have an old version floating around that taking precedence over the new version, but I'm unsure how to check to see it as I can't search for the deb packages in discover.
 
You must log in or register to reply here.
Back
Top