-
Notifications
You must be signed in to change notification settings - Fork 37
"The maximum pts value in seconds is unknown." while streaming #691
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
Comments
@FredrikNoren, I can't comment on the correctness of your implementations of read and seek, since I'm not familiar with the expected behavior of websockets. I can, however, comment on the expectations of the Currently, the implementation of Is the video you're decoding a live video stream, or is it a video file accessible from a websocket? I'm afraid that the |
@scotts It's a live video stream, with the mime type So "Streaming video" in the docs doesn't include live video; it's only a method for streaming a fixed sized videos? |
@FredrikNoren, that is correct. I created issue #695 to track live stream decoding as a feature. Can you comment there more about your use-case? We'll also use that issue to track how popular the feature request is. Thank you! |
Ok will do. I'll close this then |
🐛 Describe the bug
This might be me using torchcodec wrong, but I'm trying to stream video data using a websocket. This is my code:
Which gives me this output:
I think my first question is; have I implemented seek correctly? Especially seeking from the end feels weird in a stream; right now it's just seeking from what's available at the moment.
Versions
I'm using torchcodec 0.4.0 and torch 2.7.0
The text was updated successfully, but these errors were encountered: