How to set VLC and/or Media source local file ? #1030
-
I'm using OBSv28.0.2 trying to add a media file to a media source/vlc source via websockets so I can automate playback of videos. I have successfully done this for OBSv24 with the old OBS-websockets server by setting a source settings with I'm looking at the docs here: But I do not see So how can I send a request via websockets to set a playlist item in a Meida/VLC source and begin playing it? So I added a generic events callback to see all the events. I added a media source then added a file and saw the following events.
But still not sure where to read about the |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 3 replies
-
So from what I can gather so far. It appears the transition to v5 protocol is not quick and many previous features are not yet available so the solution is to use the 4.x compat in the mean time. |
Beta Was this translation helpful? Give feedback.
-
The request you are looking for is called In 5.x, we largely clarified what specific "source" requests do by using the terms Over the course of the release and hearing feedback, it's clear that people have a hard time understanding why things are called the way they are now. During initial planning stages I had tried to make it clear that common assumptions about 4.x should not be used on 5.x, but I think I did a bad job of continuing to convey that idea. I've been wanting to spend some more time doing cleanup and improvements, specifically in the documentation sector. Unfortunately for that, my time largely depends on what I can spare from my other obligations, so things haven't progressed quite as fast as I've hoped on that front. |
Beta Was this translation helpful? Give feedback.
The request you are looking for is called
SetInputSettings
.In 5.x, we largely clarified what specific "source" requests do by using the terms
Input
(conventionally, misleadingly, called asource
in normal OBS lingo),Scene
,Transition
andFilter
. These are all "sources" in the underlying OBS API, even though they are largely very different.Over the course of the release and hearing feedback, it's clear that people have a hard time understanding why things are called the way they are now. During initial planning stages I had tried to make it clear that common assumptions about 4.x should not be used on 5.x, but I think I did a bad job of continuing to convey that idea.
I've been wanting …