Closed sdmoore68 closed 1 year ago
Sorry, slightly confused, what version did you rollback from?
This is likely result of this temp fix https://github.com/bitfocus/companion-module-obs-studio/commit/8d15877ef0e0bf4ab01ced8d2a7302ed2655b64c
However, this should all be moot with OBS 28 / Companion 2.4 beta
I had to roll back from OBS 28 due to plugin incompatibility.
Regards, Sid Moore
Proverbs 3:3 Let love & faithfulness never leave you; bind them around your neck, write them on the tablet of your heart.Then you will win favor & a good name in the sight of God & man.
On Sun, Oct 9, 2022 at 5:19 PM bryce @.***> wrote:
Sorry, slightly confused, what version did you rollback from?
This is likely result of this fix 8d15877 https://github.com/bitfocus/companion-module-obs-studio/commit/8d15877ef0e0bf4ab01ced8d2a7302ed2655b64c
However, this should all be moot with OBS 28 / Companion 2.4 beta
— Reply to this email directly, view it on GitHub https://github.com/bitfocus/companion-module-obs-studio/issues/180#issuecomment-1272630137, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACVKP3Z2TH6XYOHMYQKBVPLWCMZGFANCNFSM6AAAAAARA2726A . You are receiving this because you authored the thread.Message ID: @.***>
@sdmoore68 Got it. Right now the only real option is you could:
This should prevent the error in the log
Got it, thanks! My plan is to upgrade next week.
As far as I know, storage from the growing logs are the only resources that are getting abused. Are there other resources I should monitor until then? Can I delete the log?
Regards, Sid Moore
Proverbs 3:3 Let love & faithfulness never leave you; bind them around your neck, write them on the tablet of your heart.Then you will win favor & a good name in the sight of God & man.
On Tue, Oct 11, 2022 at 6:15 PM bryce @.***> wrote:
@sdmoore68 https://github.com/sdmoore68 Got it. Right now the only real option is you could:
- Upgrade obs-websocket by itself to 5.0.1 using this installer https://github.com/obsproject/obs-websocket/releases/tag/5.0.1, and continue using OBS 27.
- Use a beta build of companion (version 2.4) that is compatible with obs-websocket 5
This should prevent the error in the log
— Reply to this email directly, view it on GitHub https://github.com/bitfocus/companion-module-obs-studio/issues/180#issuecomment-1275336363, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACVKP3ZZZGPLTSDVJIVEHI3WCXRGZANCNFSM6AAAAAARA2726A . You are receiving this because you were mentioned.Message ID: @.***>
I don't think there should be any other concerns resource-wise.
Let me know if you have any issues after the upgrade!
I rolled back to WebSockets to 4.9.1 and OBS to 27.2.4 (64-bit, windows). I am not sure when it started but Companion is spewing critical entries in thee log every second.
22.10.09 16:51:12 instance(obs): Media time remaining parse error: RangeError: Invalid time value 22.10.09 16:51:11 instance(obs): Media time remaining parse error: RangeError: Invalid time value 22.10.09 16:51:10 instance(obs): Media time remaining parse error: RangeError: Invalid time value 22.10.09 16:51:09 instance(obs): Media time remaining parse error: RangeError: Invalid time value 22.10.09 16:51:08 instance(obs): Media time remaining parse error: RangeError: Invalid time value 22.10.09 16:51:07 instance(obs): Media time remaining parse error: RangeError: Invalid time value 22.10.09 16:51:06 instance(obs): Media time remaining parse error: RangeError: Invalid time value
Version Information: