module timecode versus hyperdeck display timecode and timecode

[LikeThisReview]

[Enhancement 8] In hyperdeck status Preview the module timecode variables $(hyperdeck:timecodeHMSF), $(hyperdeck:timecodeH) , $(hyperdeck:timecodeM), $(hyperdeck:timecodeS), and $(hyperdeck:timecodeF) show the hyperdeck "display timecode" (from Transport info) and in any other status (Playback mode) it shows hyperdeck "timecode" (from Transport info).
This enhancement request is for adding hyperdeck variables "displayTimecode" and "timelineTimecode" from Transport info where displayTimecode is always "display timecode" (from Transport info) and timelineTimecode is always "timecode" (from Transport info). The HMS, H, M, M, S variables are not really needed as we have substring.
The new variables allow clip and end timecode for example. In Preview mode I also like to display timelineTimecode on the REC button (and display timecode only when status is Recording).

> Timeline Output is "Timeline"; when it is set to "Clip" $(hyperdeck:timecodeHMSF) displays the recorded timecode.

By the way. When polling timecode is enabled (500 ms) on the connection then in the GUI the REC button displaying $(hyperdeck:timecodeHMSF) is flickering.

[sphlabs]

You are half-right in surmising the source of timecode used in the module. The variables are always derived from the deck's displayTimecode info, and never looks at timelineTimecode. This was done so that the displayed time on Companion would match that displayed on the actual deck.

I'm not sure I understand the use-case you are describing from the addition of timelineTimecode variables? Can you elaborate on what additional functionality that would allow? I can see a risk of confusion for a lot of users as to when and why the two variables would be the same or different.

[LikeThisReview]

Stephen, Thanks for your email. Must admit that I'm not sure I understand the Timecode concepts from the Hyperdeck completely. Especially now I have a second Hyperdeck and when experimenting with ISO recording and looking into the Timecode settings. What I try to accomplish is putting timecode information on the SKIP buttons and F.FWD and Rewind buttons to indicate clip start TC, clip end TC, and start timeline TC and end timeline TC. I'm trying to make it more obvious "where I am in the clip and in the timeline" in terms of time recorded and what the time was when recording. If you are afraid it confuses people, then perhaps it is best to place the request on hold until I come back to you (it will take me some time to better understand these TC settings and hyperdeck behaviour). In the meantime I can work with the hyperdeck ethernet control to explore things. Regards, Nico Op za 9 mrt 2024 om 20:37 schreef Stephen Harrison ***@***.***

…

: You are half-right in surmising the source of timecode used in the module. The variables are always derived from the deck's displayTimecode info, and never looks at timelineTimecode. This was done so that the displayed time on Companion would match that displayed on the actual deck. I'm not sure I understand the use-case you are describing from the addition of timelineTimecode variables? Can you elaborate on what additional functionality that would allow? I can see a risk of confusion for a lot of users as to when and why the two variables would be the same or different. — Reply to this email directly, view it on GitHub <#107 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A25NECEOS76BHFQYFY4VF33YXNQJLAVCNFSM6AAAAAA6RHFQM6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSOBWHE2TQMRYGI> . You are receiving this because you authored the thread.Message ID: ***@***.***>