Hi,
> 3. When I tried to use FFmpeg 4.0.6, I do not have any problem to build it. I
> have even done simple smoke test successfully for our final product.
Are you saying with older source, following the same steps gives you functional
output? I thought you were trying to configure the build wit
Hi,
man ffmpeg-codecs recommends apl0 as prores_ks -vendor:
http://ffmpeg.org/ffmpeg-all.html#Private-Options-for-prores_002dks
whereas the WIKI says ap10:
https://trac.ffmpeg.org/wiki/Encode/VFX#Prores
Which one is it?
--
LAST SHIP HOME
Winner of the German Ocean Film Award 2019
--->> https:/
Hi,
Thanks for your response.
1. You are right.
The error message with the git head in my previous email looked like
an encoding issue. So I have done git clone at ubuntu 18.01 again and I got the
same error message I had
for FFmpeg 4.3.1 like followings :
src/libavformat/udp.c:296:28: error:
Hi,
I will try to explain one step at a time.
Can you explain one step at a time, as in explain the steps you took (one
command line at a time)? Maybe it’s because I’ve never cross compiled
ffmpeg but your mentioning cmake makes me think you are messing up the
build system. Like there’s no info
Hi,
Thank you very much for your response.
Upon your suggestion, I have done git clone the current git head, but I have
faced different problem.
I will try to explain one step at a time.
1. my build environment :
a. Target Android OS : 7.1.2
b. Alexa AVS version : 1.18.0
c. cmake ver
Am Fr., 28. Aug. 2020 um 18:38 Uhr schrieb Hyoung Kim via ffmpeg-user
:
>I am a newbie about FFmpeg.
>I just need it for using Alexa AVS 1.18.0.
>
> While I try to build the FFmpeg for Android, I got a build error like
>
> src/libavformat/udp.c:290:28: error: member reference b
Hi,
Could anybody answer my question in the below email? It looks to have
something to do with my compiler (cxx, cmake 3.6.4..., r16 (ndk)) and the udp.c
source though.
Thanks.Hyoung-Taik Kim
Sent from Yahoo Mail on Android
On Fri, Aug 28, 2020 at 12:38 PM, Hyoung Kim via
ffmpeg-user wr
If I understand correctly, you want to first convert to 10 bit and then
> upload
> to cuda (and nvenc).
I am trying to keep the transcode completely on the GPU using CUDA to
decode then NVENC to encode, avoiding sending the data to the cpu and back
again.
> The "pix_fmt" option will try to con
On Sunday, 30 August 2020, 23:21:16 BST, Edward Park
wrote:
> I'm not sure what you are referring to, what's there to spread fud about??
I'm not sure what he's referring to, either, but just be aware you're talking
mainly to software engineers here and they have a well-deserved reputat
