Issue and Request about obs-websocket-js

[haganbmj]

I haven't been able to get a bounds value out of obs-websocket, I don't believe those values come out of obs-studio at all right now.

I'm not entirely sure on changing dimensions, I know at the moment obs-websocket doesn't support that. Palakis has a placeholder for that functionality, though, so it might be possible with the current obs-studio API and just hasn't been written.

[Palakis]

No, atm you can't move an item or change its size. Gonna check this out in the coming days.

[kendotpm]

Any progress on this? Was toying with an idea of a NodeCG dashboard panel using this to change a scene's sources / transforms on the fly and wanted to see how far I could push that.

Specifically looking at these:

• SetSceneItemPosition & SetSceneItemTransform

[Palakis]

@krazyken04 the bounds issue is fixed in the current codebase of obs-websocket. It will be included in the next release of obs-websocket.

[haganbmj]

I'm rewriting this project from scratch. Just have had some other priorities and stuff that comes first.
I'll have Position/Transform in there, they're not currently in a 'released' version of obs-websocket. If you'd like to have the functionality now you can call the following methods, but I can't guarantee I'll keep this internal formatting for the next version.

ws._sendRequest('SetSceneItemPosition', { 'item': 'SOURCE_NAME', 'x': 123, 'y': 123 }, callback);
ws._sendRequest('SetSceneItemTransform', { 'item': 'SOURCE_NAME', 'x-scale': 2.5, 'y-scale': 2.5, 'rotation': 90 }, callback);

Callback will just be the standard err, data as a pass/fail.

[haganbmj]

Rewrite was published. I'll be doing some documentation and stuff, but in the meantime read here for more info
Note that I pretty much abandoned all the custom method names and such.

#16 (comment)