Fix FFmpegOptions parsing and enable local network access #281
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
We might also have to differentiate between packet read error and eof. We currently assume any read error to be eof, which works for files but might be wrong, especially for lossy streams. I will align with how ffplay does it. |
brabebhin
approved these changes
Jul 29, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This should allow for receiving UDP streams from different PC as in #280.
If format cannot be detected, try to increase probesize, max_probe_packets and analyzeduration in FFmpegOptions!
https://www.ffmpeg.org/ffmpeg-formats.html
Also check e.g. fifo_size for UDP:
http://www.ffmpeg.org/ffmpeg-protocols.html#udp