On Feb 27, 2017, at 6:55 PM, JD wrote:
Well, could you at least provide the full args to ffplay, to play back an
incomplete transcode to mp4?
> On Mon, Feb 27, 2017 at 3:56 PM, PaulYurt wrote:
>
> JD, Can you substitute ffplay for ffmpeg in your tests?
On Mon, Feb 27, 2017 at 7:43 PM, Lou wrote:
> On Mon, 27 Feb 2017 10:49:31 +0100 Martin Ždila wrote:
> I am unable to register to trac.ffmpeg.org because it thinks I am a
> > spammer.
>
> Please try again. I made some changes, but let me know if it continues
>
Hey gang - do any of you know a Platform eng in NYC with some solid FFMPEG
chops?
If so, GIPHY would love to chat with them about a senior level eng role!
Thanks,
(Mike Cohen - A.K.A. Batman)
*BatPhone:* 617.999.0818
___
ffmpeg-user mailing list
2017-02-28 11:15 GMT+01:00 Rick Corteza :
>
>> On Feb 27, 2017, at 5:11 PM, Carl Eugen Hoyos wrote:
>>
>> 2017-02-27 5:15 GMT+01:00 Rick Corteza :
>>
>>> Prior to joining files with cat I often convert them using
>>> ffmpeg -i
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.
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:
Just seeing this now. If filters is the wrong solution for setting points for
Decklink SDI output, what would be the correct way to do so?
~Thomas
On 2/22/17, 3:39 PM, "ffmpeg-user on behalf of Carl Eugen Hoyos"
wrote:
> On Mar 1, 2017, at 12:05 AM, Carl Eugen Hoyos wrote:
>
> 2017-02-28 11:15 GMT+01:00 Rick Corteza :
>>
>>> On Feb 27, 2017, at 5:11 PM, Carl Eugen Hoyos wrote:
>>>
>>> 2017-02-27 5:15 GMT+01:00 Rick Corteza
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
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
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
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
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
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
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
15 matches
Mail list logo