Stroke Glow Shadow 1.0.2

[FiniteSingularity]

Very nice plugin. I am still figuring it out. I did notice that when I installed it with the Windows Installer on Windows 11 Pro, it replaces the OBS Studio name with Stroke Glow Shadow when I hover over my Microphone on the taskbar. Here is screenshot of it. It is the only plugin that I have installed in OBS that has done this. I am using OBS 30.2.2. Is this intended behavior?

Thanks in advance. :)

View attachment 105778

I'm glad you're enjoying the plugin.

Thank you for letting me know about this. What you're seeing is definitely not the intended behavior, and isn't something I've seen myself. The SGS plugin doesn't touch any audio input devices, so its very strange that it is showing up like that. I'll see if I can replicate it, and if so will try to figure out a fix.

 

[mredodos]

hi why when i activate shadow my cam change illumination?

 

[FiniteSingularity]

hi why when i activate shadow my cam change illumination?View attachment 107632
View attachment 107633

Hi mredodos,

That was a bug in the rendering pipeline that I thought I had fixed. Can you get me a log file so that I can see what your setup is and try to figure out why it is happening on your OBS? To get me a log file, go Help --> Log Files --> Upload Current Log File, then either paste the link it gives you here, or DM it to me if you dont want it to be public. That will help me troubleshoot what might be happening.

 

[mredodos]

Hi mredodos,

That was a bug in the rendering pipeline that I thought I had fixed. Can you get me a log file so that I can see what your setup is and try to figure out why it is happening on your OBS? To get me a log file, go Help --> Log Files --> Upload Current Log File, then either paste the link it gives you here, or DM it to me if you dont want it to be public. That will help me troubleshoot what might be happening.

https://obsproject.com/logs/zqS5atzLBNFbZ6vX

 

[FiniteSingularity]

https://obsproject.com/logs/zqS5atzLBNFbZ6vX

Thank you for the log. I'm not seeing anything in particular in the logs that would cause this.

One question- I see you have a filter applied right before the stroke filter. What kind of filter is that (I'm trying to see if I can replicate your problem locally).

 

[TMBGeeks]

Did "auto padding" ever get implemented? I've spent all day trying to find a combination of filter order and/or scene nesting to allow a stroke and drop shadow while still being able to resize my camera via only the camera's borders (e.g. - excluding the stroke/shadow). Currently I have 200px buffer padding because I never know what effects I may add in the future and at least auto-padding would fit camera + effects exactly even if resizing camera-only bounds isn't possible.

Also, I'd like to second @mredodos issue, I get the same haze on the preview (only when the filter is set to visible) on a fresh install.

 

[TMBGeeks]

It seems like the solution was to have a group containing my camera (or whatever source you want to have a stroke/shadow) and a color source. The color source is hidden and has a size >= the canvas and is simply for padding. Then the effects filters are applied to the group. Some effects from other plugins such as Advanced Mask's rounded corners need to be applied directly to the camera though so it's still all very confusing as to why a stroke would apply to the visible portion (the most logical in my opinion) but rounded corners applies to the whole, including the hidden portions.

 

[FiniteSingularity]

Did "auto padding" ever get implemented? I've spent all day trying to find a combination of filter order and/or scene nesting to allow a stroke and drop shadow while still being able to resize my camera via only the camera's borders (e.g. - excluding the stroke/shadow). Currently I have 200px buffer padding because I never know what effects I may add in the future and at least auto-padding would fit camera + effects exactly even if resizing camera-only bounds isn't possible.

Also, I'd like to second @mredodos issue, I get the same haze on the preview (only when the filter is set to visible) on a fresh install.

I’m currently updating Composite Blur, but SGS is next up on my ToDo list, and I’ll be addressing both issues. So very soon!

 

[FiniteSingularity]

It seems like the solution was to have a group containing my camera (or whatever source you want to have a stroke/shadow) and a color source. The color source is hidden and has a size >= the canvas and is simply for padding. Then the effects filters are applied to the group. Some effects from other plugins such as Advanced Mask's rounded corners need to be applied directly to the camera though so it's still all very confusing as to why a stroke would apply to the visible portion (the most logical in my opinion) but rounded corners applies to the whole, including the hidden portions.

The reason for this- Advanced Masks applies to the entire source’s canvas, as with an alpha channel, there is no way to know if the transparent parts of the source are due to a rectangular cut (which would make sense for advanced masks), or if they are abstract (like a face cam chroma key). However we do know that the source’s canvas, as defined by OBS is rectangular, and so we can mask based on those dimensions.

SGS on the other hand uses an edge detection algorithm (computationally expensive) to put pixels on any alpha zero pixels that are within some distance of the transition to non-alpha-zero pixels.

Hopefully that clarifies things a bit. And feel free to ask more questions.

 

[ParanormalBanana]

Quick question but is it normal that this plugin just uses up my GPU like crazy? I tried adding a stroke and a shadow to my camera and OBS GPU consumption went from 12 to 35%, having them enabled created huge stutters in my game. Is there a fix? I'm using a 7900XT

 

[FiniteSingularity]

Quick question but is it normal that this plugin just uses up my GPU like crazy? I tried adding a stroke and a shadow to my camera and OBS GPU consumption went from 12 to 35%, having them enabled created huge stutters in my game. Is there a fix? I'm using a 7900XT

That is a great question, and there are several reasons you might be seeing increased GPU use. My first question would be how are you measuring GPU usage? With many GPUs/Drivers, the GPU core speed is scaled with increasing usage. So that 35% consumption might be at a very low GPU core speed.

The second thought would be- how large of a stroke are you attempting to add. The current algorithm for Stroke/Glow/Shadow uses a blur algorithm to calculate the stroke, and this blur algorithm computational usage scales with stroke size. That said, with a 7900XT, I wouldn't expect to see a truly high GPU usage even at some of the larger stroke sizes (thus why I suspect what you are seeing an artificially high GPU usage due to how Windows/Drivers determine what the usage is).

In terms of Glow and Shadow, it also uses a blur algorithm, but is able to use a more efficient algorithm called "Dual Kawase". So you may want to switch the blur type setting to Dual Kawase, and see if that helps things.

I am currently working on a completely new Stroke algorithm that uses what is called a "Jump Flood" algorithm, and is significantly more efficient, especially at larger stroke sizes. I hope to have this new release (that also includes some neat new features) within the next couple of weeks.

 

[Tubez7]

Hi. I've got a quick question regarding which package is the most suitable for installation on an M4 Macbook Pro. The installer includes 3 different packages macos-arm64, macos-universal, and macos-x86_64.

Is there any reason to choose the universal version over the arm64 package in certain circumstances?

 

[FiniteSingularity]

Hi. I've got a quick question regarding which package is the most suitable for installation on an M4 Macbook Pro. The installer includes 3 different packages macos-arm64, macos-universal, and macos-x86_64.

Is there any reason to choose the universal version over the arm64 package in certain circumstances?

For an M4 I'd just go with the arm64 installer. The Universal is more for if you've got multiple systems you want to install the plugin on, and some are the new Arm processors, while others are older x86 systems.

 

[ziorufus]

I tried on OBS 31 and it seems not to work. Is there any update available?

 

[FiniteSingularity]

I tried on OBS 31 and it seems not to work. Is there any update available?

Hi @ziorufus . Sorry to hear you are having issues with the plugin. It should work without issue on OBS 31. Can you please post a link to a fresh log file here (or DM me the link). To do so, restart OBS and go to `Help --> Log Files --> Upload Current Log File` and copy the link it gives you. That will help me to troubleshoot what might be going on.

 

[Talonis]

Works for me with OBS 31.

 

[maxlucid]

https://obsproject.com/logs/zqS5atzLBNFbZ6vX

@mredodos ,

My testing suggests that the issue only occurs in OBS' preview and projector windows when those windows are displayed on monitors that have bits_per_color=10, like those in your OBS log. The correct brightness is - at least on my system - always displayed in:

1. those same OBS preview and projector windows if I change my monitor's color depth to 8bpc,
2. OBS' built-in Preview dock, and
3. my streams & recordings.

If that matches your experience, we can continue to use and recommend these Stroke, Glow, & Shadow filters with confidence that viewers of our streams & recordings do see everything at the correct brightness.