Warm and I have been working on that already. It's not there yet, but it's coming. Stay tuned!Hi guys,
Is there a way to send osc message with the plugin ?
Warm and I have been working on that already. It's not there yet, but it's coming. Stay tuned!Hi guys,
Is there a way to send osc message with the plugin ?
I think something similar to this should do what you want to achieve.Is there a way to set a variable to a fixed value based on what's written inside a .txt file? I keep track of certain stuff in a single line in a .txt and it would help me a lot (Considering that I've seen this can do the opposite already, modify a .txt file).
I'd do this:
View attachment 93930
Notable differences are:
- Only on change
- I use this for everything! It ensures that the macro only runs once when the condition becomes true, instead of continuously while it's true.
- Any source on Current Scene
- This works regardless of what you add or remove later, so you don't have to keep coming in here and changing the macros. If you have multiple videos and you only want it to do this for one of them, then you would still specify the exact one, instead of Any on Current.
- Playing and less than X time remaining
- This gives it X time to figure out that the condition is true (check your scan interval on the General tab), but it's usually pretty quick about it.
- Ended has always been somewhat vague to me. Does it have to have been playing first? Or is it *always* Ended, except for when it's playing, even if it hasn't played at all yet? Depending on the answer to that, is the Ended signal short enough to be missed sometimes? Playing and almost done, doesn't have that ambiguity.
- Transition over the same X time
- This gives a nice professional look, as the video is practically over anyway, and the last X time of it is still playing during the transition. That gives the impression that it could have gone on longer, but you made a production decision to end it there. In other words, you appear proactive instead of reactive.
I was going to suggest immediate playback, one after the other, so you wouldn't have to hit the button every time, but your mention of theater made it "click". I've done sound for some theatrical performances and seen behind the scenes of some others, and yeah, you can't automate the timing like that! What you asked for is exactly what you need.Using studio mode, what I would want OBS to do is switch the Preview to the "next in line" Scene after a media file has finished playback.
Now as soon as Media1 is finished playing back (and becomes black due to "show nothing when playback ends" being ticked in Media1 properties), I want Scene2 to become the Preview. Then I press <Transition> and Media 2 starts playback, and when it's finished Scene3 is in the Preview, etc.etc.
Using it for basic theatre playback btw.
Thanks! It did exactly what I was looking for, this will help me optimize my twitch rewards even further!I think something similar to this should do what you want to achieve.
It assigns the content of a given file to a variable.
View attachment 93939
What exactly are you referring to here with "title"?im need simple change the title live before initiate, im use .bat to start and stop stream automate, via scheduletask , its work, but im need change one by one the titles and midia in youtube, hard job...
need comand to add .bat change title
or change title in open obs, im use (start /d "D:\youtube\obs mega1\bin\64bit" obs64.exe --portable --scene "a" --collection "1" --startstreaming --minimize-to-tray)
or obs script to change title schedule, from list titles ramdom
please sugestions thanks
I think you are looking for the "Scene Item Visibility" action and not the "Source" action.So I think I'm nearly there... I have a few dozen short videos, and when I go to the scene they're in, I want the 1st video to play - Then the next time I leave and return to the scene I want just the 2nd video to play, etc. I currently have a variable incrementing and being appended to another "prefix" variable, but when I go to enable a source called the variable, AdvSS warns that the obs UI cannot globally control sources, and it doesn't work.
Is this possible to set up? Also I see there's Macro Reset Counter, not sure what this means but maybe could help?
Ah, you nailed it of course! Thanks so much Warmup, works like a charm now!I think you are looking for the "Scene Item Visibility" action and not the "Source" action.
You could do this in a second macro:1. is it possible to define an ELSE statement ? I check an area for pattern, if match, source becomes visible. Now I want the source to be invisible if pattern does NOT match, but I dont see option for Else statement. Workaround is creating mirrored condition, but thats extra computing requirement :(
You might be right on that one. There's average brightness, which is fairly easy to specify, but I don't see color either:2. I see no color matching, only pattern. Now I could make a green pattern image, but isnt it easier to compute just checking for color ?
it should work as easy as possible :) I think RGB is most common. And if putting a threshold, it should even trigger on different color spaces.You could do this in a second macro:
View attachment 94154
You might be right on that one. There's average brightness, which is fairly easy to specify, but I don't see color either:
View attachment 94155
Having some experience myself behind the scenes of this sort of thing, average color is not all that hard to compute, but it *is* surprisingly hard to specify.
Again, it's entirely doable, but you have a lot more questions to answer about how it should work.
- Do you want a brightness calculation of a specific channel instead of overall?
- Do you want an exact color? That works for computer-generated things but not a camera. A camera would need a tolerance, so how do you specify that tolerance?
- What about different color spaces? RGB, HSV, YCrCb, etc. Each of them makes different things easy or hard.
If you really understand how the color spaces work, you'll see that that's technically nonsense. Yes, it makes perfect sense to a layman, but good luck coding it!it should work as easy as possible :) I think RGB is most common. And if putting a threshold, it should even trigger on different color spaces.
Actually it can work similar to the pattern match selecting a specific area, just with color and Threshold.
I think as long as the thresshold can be changed, the colorspace of the user should not be so much of a problem, as he can change the thresshold according if it triggers the match or not, while debugging (match is blinking green in the rules page).If you really understand how the color spaces work, you'll see that that's technically nonsense. Yes, it makes perfect sense to a layman, but good luck coding it!
For example, where you see "orange", a computer only sees numbers:
This is using the BT.709 standard for YCrCb. Other standards exist too, which give slightly different results.
- RGB: Red = 100%, Green = 50%, Blue = 0%
- HSV: Hue = 30deg, Saturation = 100%, Value = 100%
- YCrCb: Luminance = 57%, Chrominance_Red = 27%, Chrominance_Blue = -31%
Etc.
- If you've somehow encoded some other information in the RGB channel values because those are the most accessible for you or because our eyes see that directly, then of course you'll want to use that.
- If you're looking for a specific color in a scene, regardless of lighting, then HSV or something similar might be good. RGB is terrible for that.
- YCrCb is often used in broadcast because it provides the brightness directly and the color separate from that. Once that exists, the two sets of information can be encoded differently, to preserve the brightness more than the color. (this was even true in analog TV, to be backwards-compatible with black-and-white sets) OBS's default is NV12, which is a specific version of this. If you're detecting something related to the details of broadcast, then you'll probably want to use this one.
The different color spaces don't really matter as much for picking the color to start with, as the software can easily do that conversion. The trouble comes in specifying the tolerance. It's completely different, for just one example, to specify a color in a scene as range of Red, a range of Green, and a range of Blue, than it is to specify a range of Hue, and completely ignore the Saturation and Value.
I will try to look into it. :)I think as long as the thresshold can be changed, the colorspace of the user should not be so much of a problem, as he can change the thresshold according if it triggers the match or not, while debugging (match is blinking green in the rules page).