Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Feature request: Control Hyperdeck metadata (shot, take, etc.) #77

Open
PhotoJoseph opened this issue Sep 16, 2022 · 13 comments
Open

Feature request: Control Hyperdeck metadata (shot, take, etc.) #77

PhotoJoseph opened this issue Sep 16, 2022 · 13 comments
Labels
enhancement New feature or request

Comments

@PhotoJoseph
Copy link

Whenever I import hyperdeck media into Resolve, there's always some metadata already in place, and of course its all wrong. There's camera name, scene shot take, etc. Probably a lot more. If there was a way to control that… ooh that'd be lovely!!
@sphlabs sphlabs added the enhancement New feature or request label Jan 16, 2023
@LikeThisReview LikeThisReview mentioned this issue Sep 3, 2023
Open
@sphlabs
Copy link
Collaborator

sphlabs commented Mar 9, 2024

I'm working on this now, and it occurs to me that there is a good case for exposing some of the project info on the config page of a Hyperdeck connection. Project name, Director, Camera & Camera Operator could all be configured on a per-machine basis, as that info doesn't change very often.

There can also be actions to change this info, so one wouldn't need to go back to the config page to make changes, but I can see a lot of scenarios where it would be nice to set, say, the camera ID once, and always have that saved to all clips on that deck.

I don't think this approach makes sense for the clip info (take, reel, scene, etc.) but I'm open to suggestions.

@LikeThisReview
Copy link

Stephen,
If possible, please create variables for all meta data. Information on Edit Connection page is not preferred (as in current setup we can’t access this info like Reel). Want to display that info on buttons as well.

A content creator wants to change project name for each youtube video for example?! But OK, if there is an action for this.

It looks like Black magic no longer refers to project name as such but product name (I guess because they use project name now for the cloud).

Indeed Clip info needs to be all variables, if possible a set for current clip and fir next clip (slate for next)

If camera id = A and Reel is 8 the SD Card is with volume name A008 and file suffix is also A008.

@PhotoJoseph
Copy link
Author

I'm working on this now, and it occurs to me that there is a good case for exposing some of the project info on the config page of a Hyperdeck connection. Project name, Director, Camera & Camera Operator could all be configured on a per-machine basis, as that info doesn't change very often.

Agreed; it'd be great to get this info in there, and right this doesn't change often (if ever in some setups)

There can also be actions to change this info, so one wouldn't need to go back to the config page to make changes, but I can see a lot of scenarios where it would be nice to set, say, the camera ID once, and always have that saved to all clips on that deck.

Right; I have six decks and while I can route any camera to any deck, it's almost always the same. So yes asigning the camera number to the deck would be extremely useful.

I don't think this approach makes sense for the clip info (take, reel, scene, etc.) but I'm open to suggestions.

Reel, Scene and Take are the primary fields used. It's interesting that there are many more fields you can use, but if you look at Blackmagic's own field recorders, the Video Assists, the only shot metadata you can adjust on there is Reel, Scene and Take. There's also a "good take last clip" button that's pretty awesome. Making a button on the streamdeck that tells all hyperdecks to mark the last shot as a good take would be amazing.

In case it helps, as a comparison to what BMD does with its own hardware, here are photos of the metadata pages on the Video Assist recorders:

IMG_0419
IMG_0420
IMG_0421

@LikeThisReview
Copy link

LikeThisReview commented Mar 11, 2024 via email

@PhotoJoseph
Copy link
Author

Thanks Nico -- I was showing the fields that are populated by the device, not how they are populated. But yes, if you wanted to completely recreate the Video Assist experience, here are those pages.

IMG_0422
IMG_0424

@LikeThisReview
Copy link

LikeThisReview commented Mar 11, 2024 via email

@sphlabs
Copy link
Collaborator

sphlabs commented Mar 11, 2024

Thanks for all the comments and feedback.

In terms of project data on the config page, I see this as being optional and useful for people who do things like ISO recording, where these settings will rarely change for a deck. Think of them as startup settings as, by setting in config they get pushed to the deck on connection without needing to push any buttons. [aside: in my testing the Shuttle does maintain project settings between power-cycles, but I do wonder if that is the case for all models]

My plan is that all project settings are still exposed as variables, and settable through actions, so there wouldn't be any loss of functionality in that way. The question would be what should happen to the config settings if an action changes those values… I'm inclined to leave the config fields unchanged and emphasise the 'startup values' state of them. The downside is that the config screen could potentially show values that are not currently saved in the deck (although a quick Save would fix that).

As for the clip (and lens) data, that would all be kept to actions/variables/feedback. The VideoAssist interface (I have one of those as well) is very similar to the Hyperdeck Extreme, which is why I believe all of these settings are present in other decks, as the rest only allow you to set the Camera through the interface.

@PhotoJoseph
Copy link
Author

All sounds reasonable to me. Perhaps difficult to truly evaluate until trying it, so I'm of course more than happy to beta test for you and provide feedback.

@LikeThisReview
Copy link

LikeThisReview commented Mar 11, 2024 via email

@PhotoJoseph
Copy link
Author

Hi @sphlabs have you found the time to make any progress on this? We're all excited to see 😊

cheers
-Joseph

@PhotoJoseph
Copy link
Author

@sphlabs can we collectively offer some financial compensation to you to move this forward? I'd really love to see this added, and I'm sure many others here would as well. It's definitely worth $$ to me. I can't speak for @LikeThisReview but I'd be happy to pony up some cash 😊

@LikeThisReview
Copy link

LikeThisReview commented Jun 20, 2024 via email

@sphlabs
Copy link
Collaborator

sphlabs commented Jun 21, 2024 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@sphlabs @PhotoJoseph @LikeThisReview