You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Stream bitrate (kbits) is communicated via the API and displayed when called on Macro Deck buttons.
Current Behavior
Macro Deck does not show bitrate change from 0 in the variables section. Subsequently, the buttons calling for those values to be displayed also show "0". this applies when calling obs_fractal_kbits (fractal = my pc name) or the obs_default_fractal_kbits.
Steps to Reproduce
Create Macro Deck button with {obs_fractal_kbits} variable to show on the button.
Start streaming
observe the bitrate does not change in Macro Deck variables and
Anything else we should know?
The websocket is connected and CPU usage, for example, displays just fine. I am also able to change scenes via the API using Macro Deck buttons. i.e. everything seems to be working fine except for the bitrate variable(s).
The text was updated successfully, but these errors were encountered:
Operating System Info
Windows 11
Other OS
No response
OBS Studio Version
Other
OBS Studio Version (Other)
30.2.3; Websocket 5.5.2
obs-websocket Version
Git
OBS Studio Log URL
https://justpaste.it/f8ybc
OBS Studio Crash Log URL
No response
Expected Behavior
Stream bitrate (kbits) is communicated via the API and displayed when called on Macro Deck buttons.
Current Behavior
Macro Deck does not show bitrate change from 0 in the variables section. Subsequently, the buttons calling for those values to be displayed also show "0". this applies when calling obs_fractal_kbits (fractal = my pc name) or the obs_default_fractal_kbits.
Steps to Reproduce
Anything else we should know?
The websocket is connected and CPU usage, for example, displays just fine. I am also able to change scenes via the API using Macro Deck buttons. i.e. everything seems to be working fine except for the bitrate variable(s).
The text was updated successfully, but these errors were encountered: