[FFmpeg-devel] [PATCH] sftp: support reading config from ~/.ssh/config

Lukasz Marek lukasz.m.luki2 at gmail.com
Wed Mar 11 13:05:23 CET 2015

On 11.03.2015 11:15, Nicolas George wrote:
> Le primidi 21 ventôse, an CCXXIII, Florian Jacob a écrit :
>>> Do we have a way to apply
>>> ffmpeg-specific options?
>> We can force to use no compression in the code, by adding this line:
>> ssh_options_set(libssh->session, SSH_OPTIONS_COMPRESSION, "no");
>> after parsing the config file.
> I think that is not what Reimar had in mind, but rather something like this:
> ssh_set_app_tag(libssh->session, "ffmpeg");
> ssh_set_app_tag(libssh->session, "multimedia");
> Match tag=multimedia
> Compression off
> Unfortunately, there is no "tag" criterion for the Match directive. Maybe
> the OpenSSH guys would be amenable to a patch.
>> 		      This would also mean that the user can't configure to use
>> compression for ffmpeg even if they want to, though, but this wasn't possible
>> before either.
>> One might could argue that connections that benefit and work faster with the
>> compression option are too slow to stream media, anyway.
>> Other thoughts?
> I firmly believe in the following principles:
> 1. If the user made an explicit choice, the application must obey, even if
>     the choice seems stupid.
>     In the case of SSH: compression is disabled by default, so enabling it is
>     an explicit choice.
> 2. Applications should as much as possible try to both leave the choice to
>     the user and have a sensible default, but if for some reason it is not
>     possible (poor API on a library), then priority should be given to user
>     choice.

Isn't this compression transparent? I can play media files with both 
compression on and off.

More information about the ffmpeg-devel mailing list