Thank you too!
Doesn't matter. Added it to both since some sources only have audio, some only have video. I believe one Move Transition filter does this as well.
I myself want this too, as I do have to fit to screen most of the time. The reason I did not add it initially is because of how sources vs. scene items are handled in OBS, as Transform is scene-dependent, whereas the already supported features in this plugin are scene-independent. Rest assured, I already have a plan on how to do this, so thank you for also stating that you need it, as it gives me a push.
Hmm...that *would* be tricky. Especially to keep the "obvious" (to me at least) workflow of having a Blackout scene that never goes away, with an empty source of each type just to set the defaults for those types. To add new stuff, I just add a scene and then add a source, the usual way, and my custom defaults apply to what I just added.
No, Transform is scene-dependent. Think about it. You can add a source in one scene with Fit to Screen, and in another, the same source can be smaller, or use Stretch to Screen. I would be glad to explain the details further but I don't want to confuse you with code if you are not familiar with the OBS API hahaha
I was thinking that each source in each scene was independent, to the extent that the Transform would work the same as the other settings. Or are the other settings linked across scenes? (put the same source in two scenes, look at their settings, change one, and see the other change too) I haven't really tried.
For example, properties of a source will be the same no matter if they are duplicated in a scene or in other scenes. Even if the layout is different, properties, filter, audio monitoring, etc, will all be the same on any scene. Transform is different because it is on a "scene item", not a source. You can have the same source in a scene, duplicated, with one placed on the left, the other on the right.
Oh crud! Yeah, I'd call that an oversight on OBS's side, to not specify the scene where a new thing was created. It would have to *have* that information, so why not pass it on?
Well, it doesn't have that information, scenes do. See Jim's reply here https://discord.com/channels/348973006581923840/731208645848727593/1002227394737877083. I'd say it's more of a design decision, rather than an oversight, as this is not how filters were intended to be used, though Jim himself agrees that this is better user experience.
That's definitely a feature. I use it in many ways.
I meant that the callback when a new source is created should also include the scene that it's on. Then you don't have to search for it. That's the oversight.
You do have a point, but I'd say that's more because scenes, transitions, and filters are also considered sources in the backend, which do not necessarily have to be added to a scene. The signal handler for source creation is called when these are created, not just the input sources. So considering all these in mind, simplicity is better.
Oh. Okay. But as I've seen in building media systems (sound, lighting, video, etc.), "simplicity" becomes highly deceptive because of the irreducible complexity of what it's trying to be. You can move the complexity to where you don't normally see it, but you can't get rid of it. And if you move it too far from where it normally wants to sit, you have to add *more* complexity overall just to make it appear "simple". (a manager/wrapper, for example)
I mostly agree, especially with including the scene, but it's not for me to say. I haven't contributed much yet to the OBS project to have a say in things. What's more, this is probably a very niche use case so I doubt OBS devs would approve of such breaking change with very little gain. Keep in mind that bigger plugin devs like Exeldro and Warmuptill have written bigger and more plugins so if this was actually something they needed, they would have asked for it long ago. Anyway, there's a function to retrieve the current scene, so that will let me skip iterating through all scenes like 99% of the time. The 1% is just from custom scripts doing their thing and adding sources to other scenes.
Ah! Okay. So it's not all *that* bad.
search current_scene
if found
return current_scene
for all scenes
search scene
if found
return scene
return nullyep, that's exactly the algorithm i'm planning to implement. just can't start right now since i've still got some deadlines to meet, and from my experience, even relatively small changes lead to long testing and debugging time hahaha
Ooohhh, I think that's right. I think I do remember the same source in multiple scenes having the same filters too. I had forgotten about that because I don't normally do things that way. But yes, it is something that must be accounted for.
I'm not really sure what else, but I'm thinking whether i need to separate the options for copying Transform stuff, like position, crop, etc. Personally I don't think I need to separate them. Just have a "Transform" option and that will copy the bounding box size and crop, similar to what the "Copy/Paste Transform" on the context menu does.