-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
strange behavior of strings #2
Comments
Hey, sorry I'm unfamiliar with StreamFX, because I only have a Mac. I have looked into it and it looks pretty cool. I don't know what the properties or key should be, but it looks like if X works and it's "Filter.Transform.Position.X" : x then shouldn't Y be: "Filter.Transform.Position.Y": y Cause Right now it is: "Filter.Transform.[msgArray[3]].Y" : y If you wanted that variable to be "Position", after the msgArray.shift(), 'msgArray[0]' should then equal "Position" Another debugging thing you could try to see if Y or Z is a different key name. obs.send("GetSourceFilterSettings) after that you can .then() and console.log whatever is going on in the 'filterSettings' properties. Sorry if this info isn't much help, but it's my best guess |
Wow! I am very interested in controlling StreamFX via OSC. Please keep me posted and provide other details if possible. Thanks! h/t: @jshea2 for directing me here. |
Hi, I don't know if it should be here or is actually an obs websockets issue, but I used the following code (hacked some of yours) because I want to use the streamFX plugin through OSC. If it works I can give you my code if you want it when finished.
I am not familiar much with javascript per se but thought I knew enough about programming languages to do this... Anyway. In the following piece of code, changing the x position works, but y and z don't. As I want to make the code versatile I'd like to use variables and not have to type out every single string. Do you have any idea why this wouldn't work? I get no error message. You see a few variations, but any variation gives the same result.
The text was updated successfully, but these errors were encountered: