search

jshea2 / OSC-for-OBS

Control and listen to OBS via OSC
113 stars 7 forks source link

/scene does not work #7

Closed HarlekinSimplex closed 3 years ago

HarlekinSimplex commented 3 years ago

I have tried the following OSC calls from my TouchOSC surface to activate the scene 'CAMERA': /scene CAMERA /scene/CAMERA /previewScene CAMERA /previewScene/CAMERA Further I tried to use different scene names with spaces in them to check if that works. All of them did not work to activate my scene CAMERA at OBS.

Other calls like /go /back /toggleStudioMode do work as expected, so my setup in general is configured well.

Probably its an issue with the value range send alongside the OSC string. However I haven't found any documentation regading those numbers and what is expected here to make those call work as expected.

SD-phase commented 3 years ago

I have the same issue...I am following the OSC commands as per the readme file... @jshea2 pls help! In addition to whats mentioned above i cannot get the following to work:

-- /fitToScreen -- /duplicateCurrentScene....I get error= (Invalid OSC command. Please refer to OBSosc OSC Command List in 'Help' > 'API')..I cannot access the 'Help' >'API' documentation frm within OSC for OBS -- /[scene_name]/[source_name]/filterVisibility [0, off, false or 1, on, true]....I get error=(Invalid Syntax. Make Sure There Are NO SPACES in Source Name and Filter name. /[Scene Name]/[Source Name]/visible 0 or 1, example: /Wide/VOX/visible 1)..there are no spaces in my string. Also source visibility on/off works just fine!

Also would there be a way to toggle audio source mute 'on/off' with one button?

Thanks in advance!! [Running Macbook Pro with TouchOSC on iPad mini (Gen1)]

jshea2 commented 3 years ago

TouchOSC works a bit differently for triggering scenes because it sends an integer argument. If you join the discord I can send you a quick fix. I'm making a build with updates for TouchOSC soon. The current way to call scenes in TouchOSC is to just do /scene and use the value to the number that gets logged when you connect.

I'll look into the duplicate scene and fir to screen commands. Those are new. Make sure you're selected the source before you fittoscreen.

For the one button for the mute i can probably add a audiostatus command that can toggle between 1 and 0

SD-phase commented 3 years ago

TouchOSC works a bit differently for triggering scenes because it sends an integer argument. If you join the discord I can send you a quick fix. I'm making a build with updates for TouchOSC soon. The current way to call scenes in TouchOSC is to just do /scene and use the value to the number that gets logged when you connect.

I'll look into the duplicate scene and fir to screen commands. Those are new. Make sure you're selected the source before you fittoscreen.

For the one button for the mute i can probably add a audiostatus command that can toggle between 1 and 0

Thanks a ton!.. will look forward to these updates. It will really sort sh*t out.

jshea2 commented 3 years ago

New v2.4 release should fix these issues!

SD-phase commented 3 years ago

New v2.4 release should fix these issues!

Thank you sir!