oscmessage /[type]/transition [duration] not fully working ?

[gllmAR]

Hi,

Tried to make transition duration time work but without success

/Fade/transition 5000

Does not make a error, it can change the transition type but not transition time.

hacking in a function for SetCurrentSceneTransitionDuration in index.js solved my issue and could be useful for changing only the transition time

        //Set SetCurrentSceneTransitionDuration
    else if(msg[0].includes('/SetCurrentSceneTransitionDuration')){
        logEverywhere("SetCurrentSceneTransitionDuration")
        console.log(`OSC IN: ${msg}`)
        logEverywhere(`OSC IN: ${msg}`)
        var msgArray = msg[0].split("/")
        msgArray.shift()
        console.log("Messge array: " + msgArray)
        logEverywhere("Messge array: " + msgArray)
        return obs.call("GetCurrentProgramScene").then(data => {
        obs.call("SetCurrentSceneTransitionDuration", {
            'transitionDuration': msg[1]
        }).catch(() => {
            logEverywhere("ERROR: Invalid SetCurrentSceneTransitionDuration Type Syntax. See Help > API")
        })
    })
    }

system : macos 12.6, OBS 28.03 OSC-for-OBS 3.1

Thanks for your software.

[jshea2]

/transition command is updated in v3.1.1 release. I'll keep this ticket open incase anyone else has issues with this command.

[pmaillot]

tested today and it works/worked fine for me (latest OSC for OBS release)

[jorgepablot]

Is it needed to use OBS 28? I am running 30.1.2, and web socket 5.4.2, transitions are not working for me, actually only Fade 5000 works. I can change scene transition, but when triggering transitions via /Fade/transition "300" or other numbers or types, they always change as Fade 5000 or don't work reliably