search

bitfocus / companion-module-renewedvision-propresenter

Renewed Vision Pro Presenter
MIT License
31 stars 19 forks source link

ProPresenter not updating timer information after v. 7.13.2 #177

Open wallykyle35 opened 8 months ago

wallykyle35 commented 8 months ago

Describe the bug/issue Using the "Update Clock" action in companion, the time of the clock and the type of clock does not change. However, the name of the clock will update. This has been stable in each version of ProPresenter before 7.14. The rest, start, and stop clock functions still work normally.

To Reproduce

  1. Button to update Clock -> Reset clock -> Start Clock
  2. Push Button

Expected behavior The clock should update with new information, reset to the new times and start.

Screenshots Please add screenshots (or full text descriptions) showing: Image 12-27-23 at 6 55 PM

Versions/Environment (please complete the following information):

*Any Other Context No issues with this on previous versions of ProPresenter. Happens on each computer I have too

JeffR-TD commented 8 months ago

Same issue confirmed for me on my machines with Pro7.15

isaacstoops commented 7 months ago

I also had a similar issue where timers would not work after I updated my machines to ProP 7.15. I also had no other issues till we performed the update.

I was able to find a workaround (see below), however, I'm now experiencing two different issues that I hadn't before.

WORKAROUND 1) Set the Reset Clock command to a relative delay of 500ms. 2) Set the Start Clock command to a relative delay of 100ms.

See attached image for command settings: Screenshot 2024-01-23 at 10 12 32 AM

CURRENT ISSUES 1) Every so often, when pressing a timer button (see attached image for commands being sent), ProPresenter will either not respond to the command or respond by restarting the previous timer command that was sent.

2) More frequently, a timer will freeze in the stage display but continue running in the timers settings tab.

Let me know if you have a solution to these issues. I'm currently in contact with Renewed Vision about these issues but have a feeling they will (justifiably) blame Companion for these issues.

For reference, these machines are currently running MacOS Sonoma 14.2.1 (M1 chip).

humbled commented 6 months ago

Thanks @isaacstoops for sharing, but oddly the workaround (relative delays) doesn't work for us (from 3 different companion versions from 3 different machines).

EDIT: Actually the workaround does work on Companion 2.4.2 thanks but not on 3.x. If others are trying, pick a long delay (eg 1000ms) and work backwards if needed.

How's it going with Renewed Vision? Have they mentioned an API change? There must surely have been one.

nzalan01 commented 4 months ago

Has anyone had any luck with a fix or workarounds for this? Had it working fine when we were on PP7 v7.10 and Companion v2.2, but just updated recently due to a bunch of other dependant instances and new hardware and can't get the timers working.