obs-websocket icon indicating copy to clipboard operation
obs-websocket copied to clipboard

Bug: SetCurrentPreviewScene doesn't set preview when called after SetCurrentProgramScene

Open WORMSS opened this issue 3 months ago • 0 comments

Operating System Info

Windows 10

Other OS

No response

OBS Studio Version

Other

OBS Studio Version (Other)

31.1.2

obs-websocket Version

5.1.0

OBS Studio Log URL

https://obsproject.com/logs/HA63R18Ad7gH2vGn

OBS Studio Crash Log URL

No response

Expected Behavior

Expected behavior is:

  1. The scene I set as the current program becomes the current program
  2. The scene I set as the current preview becomes the current preview.

Current Behavior

The Current behavior is:

  1. The scene I set as the current program becomes the current program
  2. The scene I set as the current preview is completely ignored and the preview is whatever was the previous current program.

Steps to Reproduce

  1. Have 4 scenes: Scene A, Scene B, Scene C, Scene D.
  2. Have Scene C set as the current program, have Scene D set as the current preview.
  3. Run either of these two pieces of code.
    await obs.call('SetCurrentProgramScene', {
      sceneUuid: UUID_SCENE_A,
    });
    await obs.call('SetCurrentPreviewScene', {
      sceneUuid: UUID_SCENE_B,
    });
    await obs.callBatch([
      {
        requestType: 'SetCurrentProgramScene',
        requestData: {
          sceneUuid: UUID_SCENE_A,
        },
      },
      {
        requestType: 'SetCurrentPreviewScene',
        requestData: {
          sceneUuid: UUID_SCENE_B,
        },
      },
    ]);
  1. Observe that Scene A is CORRECTLY set as the current program
  2. Observe that Scene B is NOT set as the current preview after this code runs.

Anything else we should know?

No response

WORMSS avatar Oct 05 '25 22:10 WORMSS