Advanced Scene Switcher 1.37.2

[zagorskey]

I will try to look into it.

What do your macros look like?
Maybe I can think of a workaround.


That should be doable using a macro like this:
View attachment 115862
You will of course have to adapt the channel name, the "!MyChatTrigger", and scene accordingly.

Hi again,
I can see that Exeldro has now updated the Aitum Vertical plugin to 1.6.1 with:
- Add option for other plugins to get and switch scene

Could you please look into this so that our vertical scenes/sources based on the new OBS canvas system could be used again in our Advanced Scene Switcher macros?

99% of my macros are currently based on Scene Item visibility leading to a chain reaction once a vertical source is shown.

 

[Warmuptill]

Hi again,
I can see that Exeldro has now updated the Aitum Vertical plugin to 1.6.1 with:
- Add option for other plugins to get and switch scene

Could you please look into this so that our vertical scenes/sources based on the new OBS canvas system could be used again in our Advanced Scene Switcher macros?

99% of my macros are currently based on Scene Item visibility leading to a chain reaction once a vertical source is shown.

You can find a first release which supports getting sources from other canvas' such as the Aitum Vertical plugin here on GitHub:

draft canvas scene support pull request run · WarmUpTill/SceneSwitcher@5eb6ba9

An automation tool for OBS Studio. Contribute to WarmUpTill/SceneSwitcher development by creating an account on GitHub.

github.com

You will have t be logged into GitHub to be able to download it at the bottom of the page.
If that should be problem, let me know, and I will try to share the build some other way.

Let me know if you face any issues in that test build.

 

[VOXBUENOGAMING]

Hello! So I had updated both OBS and Advanced Scene Switcher to the latest versions, but Adv Scene Switcher is not showing up underneath the TOOLS tab. I've tried uninstalling and reinstalling multiple times to no avail, and would just like some insight about the problem with a possible fix. Has this problem come up before?

 

[Warmuptill]

Hello! So I had updated both OBS and Advanced Scene Switcher to the latest versions, but Adv Scene Switcher is not showing up underneath the TOOLS tab. I've tried uninstalling and reinstalling multiple times to no avail, and would just like some insight about the problem with a possible fix. Has this problem come up before?

The most likely scenario is that at some point you have manually moved the location of your OBS installation.
In that case the installer is assuming OBS is at a different location on your filesystem compared to where it actually is and puts the files in the wrong location.

You can work around this problem by manually installing the plugin using the contents of the zip archive.

Installation

An automation tool for OBS Studio. Contribute to WarmUpTill/SceneSwitcher development by creating an account on GitHub.

github.com

 

[VOXBUENOGAMING]

The most likely scenario is that at some point you have manually moved the location of your OBS installation.
In that case the installer is assuming OBS is at a different location on your filesystem compared to where it actually is and puts the files in the wrong location.

You can work around this problem by manually installing the plugin using the contents of the zip archive.

Installation

An automation tool for OBS Studio. Contribute to WarmUpTill/SceneSwitcher development by creating an account on GitHub.

github.com

I went and installed OBS and all under the C Drive, and things were recognized instantly. Thank you so much!

 

[Warmuptill]

I have released a beta version of the upcoming update for the Advanced Scene Switcher plugin on GitHub:

Release Advanced Scene Switcher 1.32.0-beta1 · WarmUpTill/SceneSwitcher

Important notes: The minimum supported OBS version is OBS 31.1.1. Please make sure to back up your settings! If you run into any issues, please either post in the OBS forums or create an issue on ...

github.com

If anyone is willing to give it a try short feedback, if everything works as expected would be much appreciated!
This is especially true for the MacOS variant, as currently I don't have a way to test it.

Here is a change list (more details, including screenshots of some of the changes are on the GitHub release page):

---

Important notes:​

• The minimum supported OBS version is OBS 31.1.1.
• Please make sure to back up your settings!
• If you run into any issues, please either post in the OBS forums or create an issue on GitHub!

Additions:​

• Added the option to set Twitch stream tags.
• Added the option to set content classification labels of a Twitch stream.
• Added the option to change the language of a Twitch stream.
• Added support for commercial start event in the Twitch condition.
• Added the option to enable, disable, and toggle macro highlighting to the "Macro" action.
• Added the option to check if a macro's actions were recently performed.
  This is intended to be used as another possibility to reduce the frequency the actions of a given macro are executed.
• Added the option to en-, disable, and toggle the OBS preview.
• Improved the "File" condition type:
  • Added support for file existence check.
  • Added support for "is file" check.
  • Added support for "is folder" check.
  • Added more macro properties.
• Added the option to select "Any" in applicable scene item selections.
  This should enable some users to simplify their macros.
• Added the option to group macro docks into a single dock window.
  You can find more information here: https://github.com/WarmUpTill/SceneSwitcher/wiki/Macro-docks
• Added "canvas" selection support to various scene item actions and conditions.
  The option to select the canvas will be visible if more than one canvas is available, for example, when the Aitum Vertical plugin is installed.
• Added the option to check the current scene of the "Aitum Vertical" plugin to the "Scene" condition.
• Improved the "Switch scene" action:
  • Added the option to switch to the next and previous scenes in the scenes list.
  • Added the option to switch to the scene at a given index of the scenes list.
  • Added support to switch the current scene of the "Aitum Vertical" plugin.
• Added the option to automatically start the plugin on a given scene as was previously possible with the removed "Scene Trigger" tab.

Other changes:​

• A warning will now be displayed if an invalid script file is detected in the "Script" macro segments.
• Added the option to disable the shutdown confirmation dialog.
• Slightly improved visibility of highlighted macro segments in light themes when selecting macro properties.
• Keep current transform setting selection when switching sources in the "Scene item transform" action and condition.
• Added macro property to the "Media" condition indicating which source matched the given parameters.
• Updated zh-CN locale (Tiefsee5037008).
• Always enable selecting the location at which to install the plugin when running the Windows installer, even if the plugin is already installed.
• Certain dependencies have been marked as optional in the generated deb package for Linux.
• Minor UI cleanup.

Fixes:​

• Fixed multi-action stream deck buttons not triggering macros correctly.
• Fixed that the connection to the Twitch event server was lost when an invalid channel is selected.
• Fixed Twitch event server connection not being able to reconnect.
• Fixed queued nested macros duplicating their conditions and actions.
• Fixed certain drop down menus cutting off a few characters of the displayed text.
• Fixed macro property selections of nested macros not being saved.
• Fixed a potential freeze when closing OBS.

 

[NudelForce]

Hi, sorry if this has been asked before, but what I found about "python" in this discussion did not fit my question.
I have set up the plugin and it is working. Before I sent a hotkey as a trigger action. But now I wanted to execute a python script when I switch scenes. However the script does not seem to get executed.
How can I get the log the python script spits out?

This is my code:

from pythonosc.tcp_client import SimpleTCPClient

def main():

    ip = "192.168.178.27"
    port = 16284
    preset_id = 0

    client = SimpleTCPClient(ip, port)
    client.send_message("/OBSBOT/WebCam/Tiny/TriggerPreset", [0, preset_id])
    print(f"Sent OSC message to /OBSBOT/WebCam/Tiny/TriggerPreset with preset_id={preset_id}")

if __name__ == "__main__":
    main()

I want to send the command to my OBSBOT camera to set it to a preset. When I execute the script in VS Code it works.

 

[beesarr]

Just to avoid a misunderstanding: You seem to facing a different kind of issue.
The original problem was indeed an outdated installation of the plugin being used, which was very old and thus not compatible with OBS 32.
At least the last 5 releases or so are all compatible with OBS 32.

The problem on your end seems to be a partial / corrupted installation of the plugin.
The plugin tries to create the default macro condition and action and fails to do so and thus you see this message.

Did you manually install the plugin or use the installer?
Or you using OBS in "portable" mode?
Did you ever manually move your OBS installation to a different folder?

You can find more information about how to install the plugin manually without the installer here:

Installation

An automation tool for OBS Studio. Contribute to WarmUpTill/SceneSwitcher development by creating an account on GitHub.

github.com

Thank you for the reply!

I had tried to reinstall the program before to see if that was the issue, but since I did a manual install, it probably didn't install properly. After following your guide I was able to reinstall the plugin properly this time!

Before updating my OBS to OBS 32, I had no issue with the plugin, but after, it had stopped working. After reinstalling and seeing the plugin was now working properly but not running my macros, I checked my plugin settings and realized half of my macros had been reset. More specifically, the part of every macro after the "If this, then this.." the "..then this" part was reset to be blank. It got reset with the update I assume, but I was able to set it back up and get it working! So for anyone having this particular problem, I suggest checking if you're having the same issue and following my steps! A bit confusing, but I'm glad to be back to being able to use the plugin!!

 

[Garryk]

Hello!

For some reason, the issue still persists occasionally, and reward events from Twitch sometimes don't arrive. I'm attaching the relevant logs.

Thank you!

 

[Warmuptill]

Hi, sorry if this has been asked before, but what I found about "python" in this discussion did not fit my question.
I have set up the plugin and it is working. Before I sent a hotkey as a trigger action. But now I wanted to execute a python script when I switch scenes. However the script does not seem to get executed.
How can I get the log the python script spits out?

This is my code:

from pythonosc.tcp_client import SimpleTCPClient

def main():

    ip = "192.168.178.27"
    port = 16284
    preset_id = 0

    client = SimpleTCPClient(ip, port)
    client.send_message("/OBSBOT/WebCam/Tiny/TriggerPreset", [0, preset_id])
    print(f"Sent OSC message to /OBSBOT/WebCam/Tiny/TriggerPreset with preset_id={preset_id}")

if __name__ == "__main__":
    main()

I want to send the command to my OBSBOT camera to set it to a preset. When I execute the script in VS Code it works.

Can you share a screenshot how you have set up your macro to execute the python script?

The most likely problems, if you are using the "Run" action are:

• A relative path is used and thus the file cannot be found.
• The script path is not passed correctly to the python executable.

If you are using the "Script" action it should be as simple as just pasting the code from your "main" function into the "run" function, and adding the required imports.
Should look something like this:

Thank you for the reply!

I had tried to reinstall the program before to see if that was the issue, but since I did a manual install, it probably didn't install properly. After following your guide I was able to reinstall the plugin properly this time!

Before updating my OBS to OBS 32, I had no issue with the plugin, but after, it had stopped working. After reinstalling and seeing the plugin was now working properly but not running my macros, I checked my plugin settings and realized half of my macros had been reset. More specifically, the part of every macro after the "If this, then this.." the "..then this" part was reset to be blank. It got reset with the update I assume, but I was able to set it back up and get it working! So for anyone having this particular problem, I suggest checking if you're having the same issue and following my steps! A bit confusing, but I'm glad to be back to being able to use the plugin!!

Thanks for the update!

I assume this might have been caused by the plugin running but not being fully initialised due to the broken install.
It only kept the part of the settings it was able to "understand" and discarded the rest.

I added code to still keep the settings even it doesn't understand them at the moment with the recent beta release.
So hopefully those types of issues will resolves themselves in the future once the broken installation is fixed again.

Hello!

For some reason, the issue still persists occasionally, and reward events from Twitch sometimes don't arrive. I'm attaching the relevant logs.

Thank you!

Thanks and sorry! I will look into it!
Did it only happen yesterday or on other days as well?
(Background: Just want to make sure it is not simply a side effect of the AWS outage)

 

[Garryk]

Can you share a screenshot how you have set up your macro to execute the python script?

The most likely problems, if you are using the "Run" action are:

• A relative path is used and thus the file cannot be found.
• The script path is not passed correctly to the python executable.

If you are using the "Script" action it should be as simple as just pasting the code from your "main" function into the "run" function, and adding the required imports.
Should look something like this:
View attachment 116208


Thanks for the update!

I assume this might have been caused by the plugin running but not being fully initialised due to the broken install.
It only kept the part of the settings it was able to "understand" and discarded the rest.

I added code to still keep the settings even it doesn't understand them at the moment with the recent beta release.
So hopefully those types of issues will resolves themselves in the future once the broken installation is fixed again.

Thanks and sorry! I will look into it!
Did it only happen yesterday or on other days as well?
(Background: Just want to make sure it is not simply a side effect of the AWS outage)

This has happened very rarely since your last update. But yesterday, it happened almost every time I received events from Twitch.

 

[JayLIve]

Hi, I'm trying to figure out how to automate something. I have a scene, and I would like to send a JSON code to a device at a specific point. I have the Advanced Scene Switcher installed, and have the below setup. If I past that https code into a web browser it works perfect, however when I start "scene" and wait 5 secconds, it doesn't seem to trigger. I am very new to programing so I'm assuming I'm doing something wrong. how can I get this to work?

 

[Warmuptill]

Hi, I'm trying to figure out how to automate something. I have a scene, and I would like to send a JSON code to a device at a specific point. I have the Advanced Scene Switcher installed, and have the below setup. If I past that https code into a web browser it works perfect, however when I start "scene" and wait 5 secconds, it doesn't seem to trigger. I am very new to programing so I'm assuming I'm doing something wrong. how can I get this to work?

View attachment 116221

You will have to split the URL and the query parameter like this:

I will see if I can implement some sort of automation for that step to make it more user friendly.

 

[JayLIve]

That worked, thanks!!!

 

[NudelForce]

Can you share a screenshot how you have set up your macro to execute the python script?

The most likely problems, if you are using the "Run" action are:

• A relative path is used and thus the file cannot be found.
• The script path is not passed correctly to the python executable.

If you are using the "Script" action it should be as simple as just pasting the code from your "main" function into the "run" function, and adding the required imports.
Should look something like this:
View attachment 116208

Thanks for your reply
I used an absolute path, so that shouldn't be the issue.

I changed it to an inline script, like in your screenshot: (note: I switched the IP settings but that stillt works executing from vs code)

import obspython as obs
from pythonosc.tcp_client import SimpleTCPClient

def run():
  ip = "127.0.0.1"
  port = 16284
  preset_id = 0

  client = SimpleTCPClient(ip, port)
  client.send_message("/OBSBOT/WebCam/Tiny/TriggerPreset", [0, preset_id])
  print(f"Sent OSC message to /OBSBOT/WebCam/Tiny/TriggerPreset with preset_id={preset_id}")

Unfortunately that still doesn't work from OBS.
I know the condition is triggered because I put a System Tray message in the execution part just before the python part which shows up.
Also, this def run() and import obspython as obs I didn't know of. Where is the documentation for that?

 

[Warmuptill]

Thanks for your reply
I used an absolute path, so that shouldn't be the issue.View attachment 116234
I changed it to an inline script, like in your screenshot: (note: I switched the IP settings but that stillt works executing from vs code)

import obspython as obs
from pythonosc.tcp_client import SimpleTCPClient

def run():
  ip = "127.0.0.1"
  port = 16284
  preset_id = 0

  client = SimpleTCPClient(ip, port)
  client.send_message("/OBSBOT/WebCam/Tiny/TriggerPreset", [0, preset_id])
  print(f"Sent OSC message to /OBSBOT/WebCam/Tiny/TriggerPreset with preset_id={preset_id}")

Unfortunately that still doesn't work from OBS.
I know the condition is triggered because I put a System Tray message in the execution part just before the python part which shows up.
Also, this def run() and import obspython as obs I didn't know of. Where is the documentation for that?

I assume the auto generated wrapper code enabling the communication with the advanced scene switcher is missing in your script file.
(A warning will be printed if that is detected in the recent beta release)

You can find documentation regarding this specific issue and scripting in general here in the wiki:

Scripting

An automation tool for OBS Studio. Contribute to WarmUpTill/SceneSwitcher development by creating an account on GitHub.

github.com

 

[hpanioniv]

@Warmuptill Just letting you know I finally got Stream Deck working, my firewall was behaving in unexpected ways lol. Got that resolved and now all is good, thanks!

 

[Laczkó]

Hi,

I've a logic that I couldn't find an automation with ASS for, maybe somebody have an idea.
I've a bunch of scenes:
Scene 1, scene 2, scene 3, ..., scene n
I make a loop of some of the scenes in the following way: a macro starts "scene 1" at a specific time, than an other macro switch to "scene 2" after "scene 1" was played for 10 seconds, after another 10 seconds comes "scene 3" and so on, until "scene m" is played for 10 seconds (m=<n), than a macro not switch to "scene m+1", but to scene 1. This way I can easily change the length of the loop which is necessary, I want to change it quite frequently.
I want the loop to goes on for 1 minute except if more time needed to all the scenes showed at least once (so if more than 6 scenes are in the loop). Currently I have a macro, that cut off the loop at a specific time by switching to a scene that isn't part of the loop, so I have to set up the cut off time manually to one minute later than the loop starts if it has 6 or less scenes in it and to 10 seconds times the number of scenes in the loop later than the loop starts if it has more than 6 scenes in it. Is there a way to define a macro that adjust the cut off time to match the criteria above automatically?

 

[Warmuptill]

Scene 1, scene 2, scene 3, ..., scene n
I make a loop of some of the scenes in the following way: a macro starts "scene 1" at a specific time, than an other macro switch to "scene 2" after "scene 1" was played for 10 seconds, after another 10 seconds comes "scene 3" and so on, until "scene m" is played for 10 seconds (m=<n), than a macro not switch to "scene m+1", but to scene 1. This way I can easily change the length of the loop which is necessary, I want to change it quite frequently.

This part I would implement like so:

• Setup variables:
  One to handle the counting. (counter)
  One to store the current scene check. (current scene name with counter suffix)
  One to store the name of the scene to switch to (next scene name with counter suffix)
  Optionally one to store the point at which to restart the loop. (restart) This could be hardcoded in the later macro, but you mentioned you will change it frequently.
  
  
• Setup a helper macro to populate the scene name variables based on the counter value:
  
  
  It won't need any conditions as we will trigger it from another macro.
• Add the macro which does the scene switching based on the variable values we set up earlier:
  
  
• Add a final macro to restart the loop:
  
  

You can import these example macros using this code:

AABGGnic7Vzdb9s2EP9XBKIPW2d5kuXESt62NMMMNG0Wp+3DWgy0dJK5ypRBUm5aI//7jtS38+UsbdN1fCigHO+Ox/v46Y4WuiFLGolcksM/N4TTJZBDcnxBl6sMyICkIi9W5FCJAqo/nlFFyeGGRHmW0ZWEmBwmNJO4LNknFA4uLweNotkHpqKFIyPg4Mwpcjs5d6K84ApEq75SsKKFhBldw6+woGuWC3LoVdQOj6BZBllDiBYQvT/KecwUy7mc8tNtjpwfLShPWx3yPVsdX0D0ks8UFaqlq3z1S1SqSV7k6lnOWyFt2iIX6oiJqGDqeE2zgmreLsdRgTqWjTVH2rapPitytxbfyrQhWjN0HrxhMCDq40o/XuI2nCnjmDUIafb3kRrn0fsZKMV4KrWsgJRJ7eT2cJTHNMMjPUPWOqRa7A3jcf4Bo2UWBmRB5VnBfy2U0spLPqSd6jhcoaIHVSGf03nH4QuWLjL8p6ZJG5hzUbTOFLX+c7jAwxDcj1SR7tHNnkSf+eraq5KGq1Fvk9Kiiqnd36ECHG32sCfxmzboNhFjsZbRrppithMar6V0TdW4muiGcy+cJ8mBO/E9cMf7oe+Gk9HInc8TmET7XjAe+WQrXka8TLZmw9kqYwpjdppLVmYWluRKl6Yf7umqMs9BGF6+qxQco22lkptlg739RtbTknVq/J6r9/BR1sE03ixpKPyucXqXpPI0zeB0m9y602wrIV0CV910vIoWTbX0cyfq0sjJRyczjwMCnM4zLV9a23Mm02ExIIOMWZ6yyBRIXAhToSd5zBKma2FDFFvCX2ivVIIyXhaSBH0AeX3teXfVHpLN1jPIICpdv6lE9gY1EEaFEOiSCgk10UFoXNRQ6MgiSdiFzkzK11hVrS5ygnaSy9oK3yCijrReGz6daYXDp8Q49FxQXob/nIoUlFlsiw5SuMBkS1iqTSwd2kZfKNYBqXxVxVMfu3NajDaNHjvUHyiGoY3vdYEL7g5cq2D0L0M/MJaclzz9lUetgr+kee+SOlbGujKzkAXJiPhw0Tmr3z3p3dnMESkflMptnta+a0kagou7wrtTcOYZovMrrljWFkb5Ti+9Z05wXit5rIitqWCmEgfN44sKNJo+qV4YVStT9GzGYqemO7Lxsn7Ti9ell3SoebF8veU8v++8Br2xaga1E6Yx5oeLeSGL+UwJ9EfVK7Uh6OVMw2WawOuZDACddsCLVLQTitlqdrxeMMF8PdOMXdxqG8KbgUsLol24mX65Oyp3NMVsu8poBP21imjSmdyIl9v7lnHtbbukanF8sRIgy1iTHxzf+ckZOU+dwPnR+dkZk04inYp8uWq7UMZXhapp5BdUkXLHeEXbWEf8sNQwNcza6kWexZ12j11ZIK4LpkAVHtd1TWqumci5Dvfrfua9mh2fnZ69/G36/JjcDAheAwjXVrupdFiuUHdPhtWpZdJ/uzEym01RbnobRsVMQAtt0qTec+ApBu4GiRWNY2TCUQCtGYfaYAkN/CA+xPnyRbGcg7iS6P1y6bIeYzJ19vO2WFM8CmIY6O4+1TEoc+VvmfM/ChDYPZEnQ5kvYcgBO7J4WCoqObbP39P8LbxqTAdKqk5UD3vQeynUmSqb19CtEa3fVIGZDl7W5bTp9HMCoJy6oG2ZsXPvjRVtRyx7896bBXDTt3bmVVCmfGS/aHRj8w4NKkNyUh5u08n0rzy0Vu8qO7PamfUzzqxjfxxDHEQuJHsJ/hXHbkijuTuPJsEYJuHexBs/bGYND5qxc+Tdb2TFCXfQPn75kbU31OAf0AURTTDA8LoBtBIgypp4w2KctH4HnTvkcN8zI/ZOCtpbspuB02KNxZr/PNZMvEkSTw5GLk3ikTuO/cg9mIwP3PAgieKRP5rA3uRhWDNusWa8v3cvrBkHwVe9HvsmLlBumTl3vaj6tyOpuZNynmwqhZf3HVE9O6LaEdWOqP+LEbW0pQ9zjEcCtCqdajjCOW8715FvidOBNnv1ZnHN4prFtW8O175g/7bbTzO2ebMgZ0HOgtzXbt4wY1UuTKLlgqWM08ypbXrUbu2hwDa2wGaBzQLbfwrY7n1Pf4Z76RPaa3l7Lf8dXMsHPqXe/iR2/WQycsejMHTnEPpuvB/QMAy8wIf9B362Gozae3nvfvfyweTr3st/A6PcI3y5+tkbqScbUaKkQ1W/izIG9WfBHRuFqw3KZ/kM9boGVf8Ui83CJxC5Q6WjFlAN0+UXlU6C7YXzlrRnfEs0v4+tT5Y55m4S345GrvXlo3a23vWtrGdndNvK2lb2O2ll/6cXkb7FNottFtsstn2vH8nc1EtbqLNQZ6HOQt2XhzpA5o8V0H3AiXjNJOsz3hfbtA0WzCyYWTD7vsFsx59X3rVI0vs/SHbusSRdV5uUV6eQ0CJTzWd4nd9vdhtJd9fXXs51ZUZXZPyuUNvSbcn5g9qjZI/cuu/NmHyX7c21KYa5gCooTcyIPwxGQ8+dg6Jo8z9BL/GH

Note that the helper macro is not strictly necessary and you could put that part of the logic in the scene switch macro.
It just think it makes it a bit cleaner to have that part separated and you might want to reuse it to setup up initial values on OBS startup.

I want the loop to goes on for 1 minute except if more time needed to all the scenes showed at least once (so if more than 6 scenes are in the loop). Currently I have a macro, that cut off the loop at a specific time by switching to a scene that isn't part of the loop, so I have to set up the cut off time manually to one minute later than the loop starts if it has 6 or less scenes in it and to 10 seconds times the number of scenes in the loop later than the loop starts if it has more than 6 scenes in it. Is there a way to define a macro that adjust the cut off time to match the criteria above automatically?

For this I would introduce another variable which tracks if all scenes have been visited.
This is the case if the "Restart" macro was executed at least once.
So, simply append something like this to the end of the action list:

Then introduce another macro which pauses the scene switch macro if more than 60 seconds have passed or the "every scene was visible" was set to "true".

Hope that helps!

 

[NudelForce]

@Warmuptill thank you for the link. Didn't think about looking in the github for a Wik.
Got it to work!

With inline:

import obspython as obs
from pythonosc.tcp_client import SimpleTCPClient

def run():
  print("Swiching to Table")
  ip = "127.0.0.1"
  port = 16284
  preset_id = 1
  client = SimpleTCPClient(ip, port)
  client.send_message("/OBSBOT/WebCam/Tiny/TriggerPreset", [0, preset_id])
  print(f"Sent OSC message to /OBSBOT/WebCam/Tiny/TriggerPreset with preset_id={preset_id}")
  return True

For using a file i needed to add the script_load stub

def script_load(settings):
    def run_wrapper(data):
        id = obs.calldata_string(data, "id")
        if id == "path/to/the/script/py-osc-scene-switcher-1.py":
            ret = run()
            obs.calldata_set_bool(data, "result", ret)
    sh = obs.obs_get_signal_handler()
    obs.signal_handler_connect(sh, "advss_run_temp_script", run_wrapper)

What would autogenerate that function?
Also my IDE (VS Code) does not recognize obspython. Can you tell me how to make that one known?