Open GoogleCodeExporter opened 9 years ago
HTTPS is currently not supported in LAV, due to the lack of proper win32 SSL
support in the ffmpeg library. Its something that can hopefully be fixed in the
future, though.
Original comment by h.lepp...@gmail.com
on 30 Jan 2014 at 10:49
A follow up question: To my understanding, VLC is also based on the ffmpeg
library, albeit perhaps a special version for VLC only. It is interesting in
this regard that VLC is indeed able to stream HLS from a https server. I would
like to understand how they have a achieved this. Would it be by creating a
separate version of ffmpeg, or is this code in the VLC itself? Of course one
would have to address VLC with a VLC question, but it it never the less very
interesting if anyone here could make a comment or anticipation/guess. Maybe
the same solution would be easy to implement in LAV?
Sidenote: But VLC lack compliance to a lot of GPU's, for example ATI HD3xxx,
and thus, comparing a http (not https) stream, while MPC with LAV may impress
us with 1-4 % cpu usage while also keeping a cool GPU (52 dgr Celius), VLC
would escalate to +70% cpu usage and a GPU temp at 70 dgr Celcius, on the very
same stream. That is quite a difference. (VLC is much better as soon as it is
compliant with the GPU, though.)
Original comment by c...@hdsoundlab.com
on 4 Feb 2014 at 7:24
One could make HTTPS work by adding external libraries that provide HTTPS
support, however, I do not want to include any huge external libraries for
this, hence no HTTPS support until a way is implemented to use the Windows
HTTPS support.
Original comment by h.lepp...@gmail.com
on 4 Feb 2014 at 3:42
Original issue reported on code.google.com by
c...@hdsoundlab.com
on 30 Jan 2014 at 8:17