You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
MMQ is not precise in its export, especially in cases like H264 data where starting from P frames might cause downstream modules to fail. But a side-effect of this is: in cases like rendering where the output may look out of sync.
Describe the solution you'd like
We should enhance the valve module to filter frames based on start, end timestamps.
Once, end timestamp is reached, the valve module should act like a pass through module
Describe alternatives you've considered
Each downstream module implementing its own filtering logic
Additional context
MMQ -> Decoder -> Renderer
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
MMQ is not precise in its export, especially in cases like H264 data where starting from P frames might cause downstream modules to fail. But a side-effect of this is: in cases like rendering where the output may look out of sync.
Describe the solution you'd like
We should enhance the valve module to filter frames based on start, end timestamps.
Once, end timestamp is reached, the valve module should act like a pass through module
Describe alternatives you've considered
Each downstream module implementing its own filtering logic
Additional context
MMQ -> Decoder -> Renderer
The text was updated successfully, but these errors were encountered: