Thanks, Marton, - inline.
On Thu, Nov 17, 2016 at 09:56:54PM +0100, Marton Balint wrote:
> > If there is no option to select the output device, i would suggest:
> > - Document that there is no such option, eg: following the documentation for
> > "-devices".
> > - Print in the output of "-devices" which the actual current output device
> > is.
> >
> > If there is an option, pls. let me know and document.
> ffplay can't use libavdevice output devices, it uses the SDL drivers.
So "ffplay -devices" lists output devices that itself can not use ?
> That may be caused by the reason that ffplay currently wants to use
> a hardware accelerated renderer with VSYNC support. I guess a
> fallback can be implemented to use any available renderer if that
> fails.
Sounds right. ffplay works locally, but i had to run it remotely via Xwindows
and that swhere it failed.
Fallback would be lovely. Remote troubleshooting is extremely helpfull
in many cases.
> >Finally: in latest git, ffplay is not even built without SDL2 library
> >discovered on the system. That doesn't seem to be right either.
>
> Why? FFplay does need SDL2, it can't work without it.
How does someone compiling ffmpeg learn about this dependency ?
(i was kinda guessing it...)
Eg: i can't remember that i've seen this in a README, and the configure for
ffmpeg does not show this dependency in it's output.
Cheers
Toerless
> Regards,
> Marton
> _______________________________________________
> ffmpeg-user mailing list
> [email protected]
> http://ffmpeg.org/mailman/listinfo/ffmpeg-user
>
> To unsubscribe, visit link above, or email
> [email protected] with subject "unsubscribe".
--
---
[email protected]
_______________________________________________
ffmpeg-user mailing list
[email protected]
http://ffmpeg.org/mailman/listinfo/ffmpeg-user
To unsubscribe, visit link above, or email
[email protected] with subject "unsubscribe".
