Skip to content

Bug: SetMediaInputCursor fails on UTF-8 input names (e.g. accents), but other methods succeed #1300

@floMallard

Description

@floMallard

Operating System Info

Windows 11

Other OS

No response

OBS Studio Version

Other

OBS Studio Version (Other)

31.0.3

obs-websocket Version

5.1.0

OBS Studio Log URL

https://obsproject.com/logs/UIoiW9qkyClm9XZV

OBS Studio Crash Log URL

No response

Expected Behavior

SetMediaInputCursor find the source when the name contains accents and sets the cursor to the correct time.

Current Behavior

SetMediaInputCursor does not find the source if it contains accents

Steps to Reproduce

  1. Create a scene and add a Media source named "Source média"
  2. Using obs-websocket-java, connect to OBS Studio and send a request to set the media "Source média" to whatever timing you can reach with your media source
    3.See the response log saying OBS Studio cannot find the media

Anything else we should know?

I'm seeing inconsistent behavior when using SetMediaInputCursor in OBS Studio 31.0.3 (embedded obs-websocket):
The media source is named "Source média" and appears correctly in GetInputList and OBS UI
GetMediaInputStatus works and shows duration/state/cursor correctly
But calling SetMediaInputCursor with "Source média" fails with error code 600 (No input was found)
If I rename the source to "Source media" (ASCII only), the exact same request works
I verified the string is normalized using Normalizer.Form.NFC, so it's not a Unicode composition issue

Tested with obs-websocket-java and the WebSocket plugin in IntelliJ

P.S.: I'm not sure but I think some actions one the scenes named "Scène X" did not work properly either

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions