Thank you again for the update. I'm using the newest version now. I see the new dropdown to tell the program which source to monitor, but is multi-monitoring support no longer a feature? Currently I've told RecORDER to monitor the source for my Steam games, but having the option to monitor and organize different sources for games that fail to auto-hook in OBS would be a really great feature to have if it ever could work.
If not it's not really a big deal, it just means that one or two games might not being organized in the correct folder.
Hello, to be truthful, the "
multi-monitoring support" was never a feature.
Let me give some context on why it wasn't one:
When I started working on this script long time ago I was not that well versed in Python.
I also did not fully understood how scripting in OBS worked, so I went with whatever way seemed to make the most sense.
I thought about making the drop-down list (just as we have now), but it was too hard at the time so I settled for something similar.
Which was the
list of elements that you manually populate with names of the sources you want the script to use.
Hence, the birth of
SOURCE_NAMES list.
Even if the user gave all of his sources on the list, what was actually going on in the background was these:
1.
Get all sources from current scene
2.
Go through all of the sources and compare the name of source currently being checked with what was in the
SOURCE_NAMES list.
2.1 (
If there was a match)
Get the source uuid (unique identifier), save it in memory and go straight to set-up of all logic neccessary for script to work [Basically,
if there was a match, then nothing else was checked and the checking ended there]
2.2 (
If there was a mismatch; ex. no source with the name was found)
Print out an error message and until fixed, put all recordings in the fallback folder ("Manual Recording")
TLDR; Check if there is a source with the same name as in the
SOURCES_NAMES, if there is - grab the first one that matched and go, if there's not - prompt the user to make sure everything is alright.
Currently, this is no longer a issue, because user can select from properties all sources that match the necessary requirements:
* Has window title information (only the ones that can hook can do that) [exception would be a Display Capture, you can still select it in the script, but you will get notified that it is not supported)
* Has video output
* (In next update) Is not hidden on source list
I am still working out edge situations where the script might not perform as good, but as long as people send me their reports, I can cover as much ground as possible.
Also a word from me about having multiple video capable sources (Window Capture/ Game Capture/ Display Capture in this case) in one scene.
You can do it of course, but do keep in mind that my script purpose is to organize in the same way ShadowPlay or Nvidia Experience work.
You record the game/window, my script takes this window title and then uses it to neatly organize your recordings.
If you have multiple ones active, the recording will be organized under the one that was configured in the properties.
I could go the same way as the other scripts and use 3rd party libraries to get better results of course, but it would defeat the main purpose behind my script, which was to make the script as minimal as possible (I would code in lua, but I don't enjoy the language) and to make it work using OBS available stuff.
I can see a situation where you even use DisplayCapture with my script and just name the fallback folder to your fancy and record that way.
Sorry for long read, but I wanted to convey everything on my mind.
