Hyperdeck Mark Timecode - Goto(TC)

[Curtismacd31]

Hi There,

I would like to request a feature to add. This would mark the timecode of the selected hyperdeck recording, possibly to a variable or to a text file located on the attached machine.

Then when Goto(TC) is chosen as an option you can tell it to go to the variable or to read the text file to get the timecode, then goto the timecode available.

Thanks
Curtis

[sphlabs]

Interesting idea. Do you see this as a sort of clipboard or something more elaborate, where one could build up a list of markers?

[Curtismacd31]

a list would be great. The only problem I would be the ability to see the list? where and how would you select a timecode to goto? although you could have a list and you could cycle next/previous then goto previous marker or goto next marker. that may work.

[ClickTrackAudio]

This is a fantastic feature request. I'd fully support this as we would use this feature.
Maybe the use case would be:

1. Have a limited number of available "markers" For example, 4 or 8 markers. Buttons "Marker 1-4"
2. User hits a button called "Mark" to capture the timecode.
3. Timecode populates the next available marker list
4. User hits "Marker x" button followed by "GoTo(TC)

Devil is obviously in the details, but I could see this as a huge benefit.

[alexhackney]

I think this could be done like vmix does with its replay.

You have a button called Set Marker X and that button would set the current timecode as a marker in that slot. In the BFC panel you could have an option to set the marker with an amount of time subtracted or added.

For instance, you hit the button to set the marker at 1:23:25. In the panel you've set it to the marker minus 5 seconds. So it would store marker X at 1:23:20.

Then you'd have a play marker x button that would play that particular marker. Seems pretty straight forward.

I would think BFC would just have a HyperDeck Marker option that would let you create as many different markers as you want. I havent dug in to this enough to see how it works on the backend but I would imagine it would be pretty simple to do.

[AndyHuska]

I've been strategizing on this.

So far, using BFC 2.2.0 beta, I can store a time code in a custom variable in the format hh:mm:ss;ff

I'm not able to do a programatic Goto TC because the TC text field will not accept a variable. Also, the timecode option to the function requires a REGEX_TIMECODE, and one of different format than what TCs are read in...it needs hh:mm:ss:ff (the difference is semicolon vs colon on the last field). This brings up two things to address, at least:

1. The REGEX_TIMECODE definition is part of the BFC core, so probably should just update the module to export the proper time code format so it doesn't have to be manipulated before use. (This may be already fixed in the latest hyperdeck module

2. How can we make fields accept variables?

From there I want to come up with a way to trigger actions when TCs are reached, like Play to Mark1 then make ATEM Fade to Black etc. The triggers that are available in BFC 2.2.0 don't seem up to the task, but we'll see.

[istnv]

..it needs hh:mm:ss:ff (the difference is semicolon vs colon on the last field).

The REGEX_TIMECODE should be updated to allow either.
The colon(:)/semicolon(;) is part of the timecode and distinguishes between Drop Frame ';' and Non-drop which uses ':'

[thumperdisney]

+1 for his request

[LikeThisReview]

See my request #82. When Goto (timecode) supports variables then we can created custom variables to hold the desired mark points. Goto Clip (name) > Set custom variable Markpoint > Goto (timecode) using the variable (Markpoint in this example).

[tubalois]

+1 any news?

[ClickTrackAudio]

This definitely makes sense and would be a welcome addition!

…

On Oct 11, 2023, at 11:01 AM, tubalois ***@***.***> wrote: +1 any news? — Reply to this email directly, view it on GitHub <#12 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AOW3KWTCDIUEAZYHLIBUPHTX62YGJANCNFSM4JR624SA>. You are receiving this because you commented.