-
Notifications
You must be signed in to change notification settings - Fork 516
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
Weird error messages when using ff* wrappers #2812
Comments
You must use a trailing '/' after the port number, otherwise it will be considered as an option , see http://wiki.gpac.io/Filters/filters_general/#generic-declaration The error from the muxer side is the one forwarded by libavformat upon connection close but there's no way of differentiating from any other IO error, hence the result. Maybe we could just ignore and abort without setting the error ? |
I confirm it works with a trailing slash. Note that I had put a double colon
FFmpeg doesn't display this message (but is it present and they hide it or is it GPAC's code sequence?):
|
I misunderstood that '::' was not needed (but '/' was). And FFmpeg does also output the errors, so GPAC is good here. Closing. |
For example I can start and playback an srt:// stream, but these errors are confusion:
and (playback):
The text was updated successfully, but these errors were encountered: