-
Notifications
You must be signed in to change notification settings - Fork 102
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
Open stream at current position #451
Comments
|
unfortunately it still plays the first part of the stream even with "Config.Player.AutoPlay = false" |
I just retested to ensure AutoPlay=false works. Can you provide a log file? |
Autoplay=false works, but when I set the position of the steam and then call play, the first half second of the beginning of the stream plays before it skips to the current stream position. I'm setting the position on the stream itself since it's a combination of raw hevc streams via ssh, so all I know is the length of the stream in bytes, not how long it is etc. Even with autoplay=false I'm assuming it's still buffering the data to play |
I'm not sure yet how you use it, but the proper way and build-in way to seek will flush the packet queue after the seek has been completed and it will decode until the first video frame to present it. Did you check the (trace) logs? Does the demuxer brings old packets after seek? |
This is an example of what is happening, I added some log output you can see. I can't use the player seek because i dont know the time in ms that i need to jump to, I only know the percentage. Its a raw HEVC stream over SSH so there is no information about current position / length in ms [16:46:54 DBG] Opening New Stream I am calling flush before i call play: flyleafHost1.Player.Flush(); |
Is there any way to open a stream at a predetermined position? Whenever I call Player.OpenAsync(stream) it resets the current position of the stream to the beginning. If i set the position of the stream and flush after i get the first half second of the beginning of the stream first.
The text was updated successfully, but these errors were encountered: