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.

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

Timecode out of sync with FrameOutputNumber #74

Open
BlueprintBen opened this issue Jan 13, 2024 · 1 comment
Open

Timecode out of sync with FrameOutputNumber #74

BlueprintBen opened this issue Jan 13, 2024 · 1 comment

Comments

@BlueprintBen
Copy link

BlueprintBen commented Jan 13, 2024

I'm using Decklink input with the hopes of having a timecode associated with each incoming frame. Unfortunately it appears that the timecode is updated on a different thread than the frames themselves, and as a result, within many Update() ticks the OutputFrameNumber has increased but the timecode remains the same, or the timecode has increased but the OutputFrameNumber remains the same. This makes it very difficult to assign a timecode to a particular frame.

  • Unity version: 2020.4.43f1
  • AVPro DeckLink version: 1.9.7
  • Operating system version: Windows 11
  • Hardware model: Decklink Studio 8K Pro
  • Cables used: SDI
  • Desktop Video version: 12.7
  • Video mode (resolution, frame-rate, pixel-format): 1920x1080, 30fps,10bit YUV422

Steps to reproduce the behavior:
Create a blank project with the AVPro Decklink Plugin and a script like this one, which, in Update() checks if either the Timecode or the OutputFrameNumber for a DecklinkInput has updated, and if so, prints a message if one field has changed but the other has not.

Here's an example of a log file produced based on the repro steps.

Am I doing something wrong? Is there a way to acquire the timecode specifically associated with the frame that is avilable as OutputTexture at a given time?

(edit: I'm hoping for Ancillary Data to also be synchronizable)

Copy link

stale bot commented Mar 17, 2024

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale Stale label Mar 17, 2024
@RichRH RichRH removed the stale Stale label Mar 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants