Closed LikeThisReview closed 1 year ago
I may have fixed this accidentally, but this isnt happening for me following some other changes I have made. Could you give this a retest once the updated module is in the beta builds?
Julian, Looks like you fixed it! Many thanks!!
Op vr 6 okt 2023 om 21:12 schreef Julian Waller @.***>:
I may have fixed this accidentally, but this isnt happening for me following some other changes I have made. Could you give this a retest once the updated module is in the beta builds?
— Reply to this email directly, view it on GitHub https://github.com/bitfocus/companion-module-bmd-hyperdeck/issues/97#issuecomment-1751291606, or unsubscribe https://github.com/notifications/unsubscribe-auth/A25NECHIYQTFDFSATRNEEYDX6BJ3TAVCNFSM6AAAAAA4JILJTCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONJRGI4TCNRQGY . You are receiving this because you authored the thread.Message ID: @.***>
Recording Time Remaining is set incorrectly set to —:—:— $(hyperdeck:recordingTime), $(hyperdeck:slot1_recordingTime), $(hyperdeck:slot1_recordingTime) and $(hyperdeck:slot1_recordingTime) often incorrectly indicate —:—:— while there actually is a recoding time available (for example slot info indicates “recording time: 10799”). Observed that when the codec is changed, suddenly the correct recording time is displayed.