2017-02-28 20:32 GMT+01:00 w_boba :
> I know about snapshots, I tend to stick to "latest stable" branch,
> which is 3.2.4-4 at the moment.
Please be assured that there is nothing "stable" about our
release branches and - fortunately for you - nothing "unstable"
about current FFmpeg git head.
Not
Am 28.02.2017 um 20:32 schrieb w_boba:
I know about snapshots, I tend to stick to "latest stable" branch, which is
3.2.4-4 at the moment
there is no "3.2.4-4" there is only "3.2.4" and while i am normally not
a friend of the "only latest git supported"-attitude if you need to
solve a proble
Thank you, Reindl
I know about snapshots, I tend to stick to "latest stable" branch, which is
3.2.4-4 at the moment.
--
View this message in context:
http://www.ffmpeg-archive.org/CodecPrivateData-is-empty-when-h264-vaapi-encoder-used-tp4679371p4679378.html
Sent from the FFmpeg-users mailing l
Am 28.02.2017 um 20:20 schrieb w_boba:
Thank you, Mark!
I am not very familiar with GIT.
I have just rebuilt FFmpeg from master and now everything is fine
next time just go to https://ffmpeg.org/releases/ and scroll at the
bottom, you can even download
https://ffmpeg.org/releases/ffmpeg-s
Thank you, Mark!
I am not very familiar with GIT.
I have just rebuilt FFmpeg from master and now everything is fine.
W.
--
View this message in context:
http://www.ffmpeg-archive.org/CodecPrivateData-is-empty-when-h264-vaapi-encoder-used-tp4679371p4679376.html
Sent from the FFmpeg-users mail
On 28/02/17 18:52, w_boba wrote:
> Mark,
>
> As I have mentioned in my first post, I am working with ffmpeg version
> n3.2.4-4-g36fff6c, which is near-current, and commit you have mentioned is
> dated Dec 2016. I believe that commit is already included in my branch, last
> commit I see there is da
Mark,
As I have mentioned in my first post, I am working with ffmpeg version
n3.2.4-4-g36fff6c, which is near-current, and commit you have mentioned is
dated Dec 2016. I believe that commit is already included in my branch, last
commit I see there is dated Feb 2017.
W.
--
View this message in
On 28/02/17 17:25, w_boba wrote:
> I forgot to add: "CodecPrivateData" attribute is "required" for SmoothStream
> according to MS document:
>
> https://msdn.microsoft.com/en-us/library/ff728116%28v=vs.95%29.aspx
I'm not familiar with this format at all, but it looks like it will be
generating t
I forgot to add: "CodecPrivateData" attribute is "required" for SmoothStream
according to MS document:
https://msdn.microsoft.com/en-us/library/ff728116%28v=vs.95%29.aspx
--
View this message in context:
http://www.ffmpeg-archive.org/CodecPrivateData-is-empty-when-h264-vaapi-encoder-used-tp46
I am trying to use new CPU with VA-API enabled h264 encoder on FFmpeg (ffmpeg
version n3.2.4-4-g36fff6c).
I have no issues encoding "offline" files with h264_vaapi encoder, but when
I try to encode live streams and push output to SmoothStream server (using
ISMV muxer) new streams do not work.
Ex
10 matches
Mail list logo
