ample
<https://stackoverflow.com/questions/47505257/ffmpeg-impossible-to-convert-between-the-formats-supported-by-the-filter>
on stackoverflow on how to initialize the OpenCL platform before use.
On 25 April 2018 at 21:23, Dennis Mungai <dmng...@gmail.com> wrote:
> With OpenCL en
Retry with the rstream option:
ffmpeg -re -i rtsp://admin:admin@192.168.1.234/ch0_0.h264 -an -c:v copy -f
segment -segment_time 60 -segment_wrap 10 -reset_timestamps 1 result%d.mp4
On 11 May 2018 at 00:00, Good Developer
wrote:
> I hope it is an easy question
You need to install nasm.
On 5 May 2018 at 22:03, Sundar Ranganathan <
sundar.ranganat...@reflexisinc.com> wrote:
> Folks,
> I am up against it. The message ./configure comes up with is:
> ---
> nasm/yasm not found or too old. Use --disable-x86asm for a crippled build.
>
> If you think
On MacOSX?
There's videotoolbox, but I'm yet to confirm if HEVC accelerated encoding
works with it..
On 18 May 2018 at 23:08, Gabriel Zachmann wrote:
> Does anybody know of any hardware that would work with my MacBook Pro and
> speed up conversion to H265 (HEVC) ?
>
> I
).
On 18 May 2018 at 23:42, Dennis Mungai <dmng...@gmail.com> wrote:
> On MacOSX?
>
> There's videotoolbox, but I'm yet to confirm if HEVC accelerated encoding
> works with it..
>
> On 18 May 2018 at 23:08, Gabriel Zachmann <z...@cs.uni-bremen.de> wrote:
>
>> Does
You're using a hwupload instance without a -hwaccel method or device
selected. You should add -hwaccel vaapi to the ffmpeg options (before
declaring the input at -i).
On Mon, Jun 18, 2018, 23:38 Victor Helmholtz
wrote:
> Hi,
>
> I am trying to encode raw yuv file using VAAPI hardware
Can you retest with git head?
Build FFmpeg from source and retest.
At the moment, you're using FFmpeg 3.3.1-1.
On 13 June 2018 at 21:22, André Hänsel wrote:
> When I scale with scale_vaapi, it results in a green line at the bottom of
> the image, see attachment.
>
> Command line:
> ffmpeg
Upload the config.log for inspection.
On 13 June 2018 at 07:55, Anand Singh wrote:
> Hi,
>
> i am getting error while building FFMPEG extension for exoplayer, i
> executed this command as provided in the documentation :
>
> ./configure \
> --libdir=android-libs/armeabi-v7a \
>
Hello,
Can you provide the output of:
ffmpeg -buildconf
And how you installed the NVIDIA driver?
And what platform/OS you're on?
For linux, run:
lsb_release -a
Normally, with the installation of the NVIDIA driver through the
distribution's package manager (yum, apt, dnf, etc), it should
In production, drop this: -hwaccel cuvid -c:v mpeg2_cuvid
There's a reason mpv devs do not recommend cuvid, in particular.
https://github.com/mpv-player/mpv/commit/dbef5b737e2f994f02923c8214cba368b663a655
On 5 June 2018 at 11:55, Mitja Pirih wrote:
> Hi,
>
> I am transcoding a live channel
And with CUVID, in particular: It's decoders are very fragile.
You did mention that disabling hwaccel (cuvid?) raised your processor load
significantly, correct?
Can you confirm whether you're applying any filters down the encoder
pipeline?
Also, what processor are you using?
On 6 June 2018 at
Neither nasm nor yasm could be found on your platform.
Install either (i'd recommend nasm) and retry.
On 27 June 2018 at 19:03, robert warren zugates wrote:
> enclosed is the log from the latest ffmpeg file.
>
>
> ___
> ffmpeg-user mailing list
>
Also, one question to the OP:
What version/variant of the Media SDK did you use to build FFmpeg?
Is it the one issued in the licensed Media SDK or the opensource iMSDK (see
https://github.com/Intel-Media-SDK/MediaSDK)?
Either way, you may need to insert a hwupload filter into the video filters
Hey,
Any feedback on the solution posted above?
On Wed, Jun 20, 2018, 09:03 Dennis Mungai wrote:
> Also, one question to the OP:
>
> What version/variant of the Media SDK did you use to build FFmpeg?
> Is it the one issued in the licensed Media SDK or the opensource iMSDK
I understand. I realized my mistake.
Your suggestion on the ticket worked.
On 26 July 2018 at 22:10, Carl Eugen Hoyos wrote:
> 2018-07-26 22:04 GMT+02:00, Dennis Mungai :
> > [f=mp4:movflags=frag_keyframe+empty_moov] pipe:1 > test_channel.mp4"
>
> As explained el
Also, can you provide the output of vainfo?
On 27 July 2018 at 09:27, Yang Zhang wrote:
> It will cause you get the "partial HW acceleration" error message
> always. there is a patch fix the problem I remember, but I couldn't
> find the patch in the latest FFmpeg
>
> On 7/27/18, qw wrote:
> >
Hello there,
According to this commit
https://git.videolan.org/?p=ffmpeg.git;a=commit;h=5a88e8c36581fed09c7db6dc7229f1fd9ab5559d
, A53CC support was added to the NVENC encoder.
For lavc, its' also enabled by default:
https://ffmpeg.org/pipermail/ffmpeg-devel/2016-September/199200.html
Is it
to the P6000 also
> Thanks
>
> Any other models?
>
> -Mensagem original-
> De: ffmpeg-user [mailto:ffmpeg-user-boun...@ffmpeg.org] Em nome de Dennis
> Mungai
> Enviada em: quinta-feira, 23 de agosto de 2018 13:27
> Para: FFmpeg user questions
> Assunto: Re: [FF
Hello there,
For users with this specific card (and FFmpeg installed), kindly clarify on
the following:
(a). How many simultaneous encoder sessions can you run on this card?
(b). Have you ran into any issues, such as stuttering and dropping streams
with multiple concurrent encodes?
I ask
Hello there,
Does your budget allow for a newer line of NVIDIA GPUs, such as the Quadros
based on Pascal?
If so, get the Quadro P6000.
Plenty of VRAM, + all the NVENC encoder features you may need, such as HEVC
high-depth encoding and vastly better encoder performance overall.
Refer to this:
---
> De: ffmpeg-user [mailto:ffmpeg-user-boun...@ffmpeg.org] Em nome de Dennis
> Mungai
> Enviada em: quinta-feira, 23 de agosto de 2018 13:54
> Para: FFmpeg user questions
> Assunto: [FFmpeg-user] A question on the Quadro P6000 and maximum
> simultaneous NVENC encodes in FFmpeg
>
>
gt; it.
>
> On Fri, Aug 24, 2018 at 5:51 AM Dennis Mungai wrote:
>
> > No.
> >
> > This is as tested on the Tesla P100.
> >
> > On Fri, 24 Aug 2018 at 00:26, Pedro Daniel Costa <
> > portaln...@outlook.com.br>
> > wrote:
> >
> &
ec. so there is -hwaccel nvdec is a wrong option.
>
> On 8/24/18, Dennis Mungai wrote:
> > For full GPU transcoding, shouldn't -hwaccel be nvdec?
> >
> > FFmpeg's documentation on this is missing, but for NVENC, the decoder
> > should be set to nvdec.
> >
> >
are
> acceleration transcoding. other channels use the GPU encoding only. this
> should can let you transcoding more channels. and fix the stutter problem.
>
> You can use "nvidia-smi dmon" to check the usage of NVDEC/ENC chips.
>
> On Fri, Aug 24, 2018 at 6:02 AM
h264_nvenc ...
>
>
>
> On 8/24/18, Dennis Mungai wrote:
> > Is it possible to disable hwaccel decode explicitly in an FFmpeg
> instance?
> >
> > Say, -hwaccel none such that no hardware-accelerated decoder instance is
> > initialized on launch?
> >
DA® Cores 5,120###
> > #
> > Double-Precision
> > Performance 7 TFLOPS 7.8 TFLOPS
> > Single-Precision
> > Performance 14 TFLOPS 15.7 TFLOPS
> > Tensor
> > Performance 112 TFLOPS 125 TFLOPS
> > GPU Memory 16 GB HBM2
>
Also, the output of:
ffprobe -i "path-to-sec-file"
That way we can tell the codec type and container details of the file
you're encoding.
On Mon, 27 Aug 2018 at 23:28, Paul B Mahol wrote:
> On 8/27/18, LH wrote:
> > Okay, can we go back a step. How do I get the data that you want? After I
>
You mentioned 30 streams. And more cause this to "fail".
Perhaps the Quadro line has a maximum simultaneous encoder limit of 30,
similar to the GeForce's limit of 2?
On Wed, Jul 18, 2018, 19:28 Yugandhar Veeramachaneni
wrote:
> Hello everyone,
>
> I'm currently using an NVIDIA Quadro P4000 GPU
Hello there,
Here's something you can try:
ffmpeg -init_hw_device vaapi=amd:/dev/dri/renderD129 -hwaccel vaapi
-hwaccel_output_format vaapi -hwaccel_device amd -filter_hw_device amd -i
fs_experiental_method.avi -vf 'format=nv12|vaapi,hwupload' -y -c:v
h264_vaapi -qp:v 21 -sei
Also, see this list:
https://developer.nvidia.com/video-encode-decode-gpu-support-matrix
You have the Quadro P4000, which is artificially crippled to ~2 concurrent
sessions according to the documentation above.
On 18 July 2018 at 22:34, Dennis Mungai wrote:
> NVENC runs on a discrete sili
flags=2'
> [graph 0 input from stream 0:0 @ 0x55986d15f2c0] Setting 'frame_rate' to
> value '30/1'
> [graph 0 input from stream 0:0 @ 0x55986d15f2c0] w:1920 h:1080
> pixfmt:yuv420p tb:1/30 fr:30/1 sar:0/1 sws_param:flags=2
> [AVFilterGraph @ 0x55986d196c40] query_formats: 3 queri
Also, related.
Is there a way to determine encoder defaults?
Does ffmpeg have such an option to print out encoder defaults?
On Tue, Sep 11, 2018, 16:02 Moritz Barsnick wrote:
> On Tue, Sep 11, 2018 at 16:38:37 +0430, Ali Shirvani wrote:
> > Is this variation in output size normal? or should I
Hello, and good morning.
I have ran into a problem with the HLS muxer, as shown below.
I want to generate three HLS renditions from a single input file, and
a master playlist pointing to the renditions.
Here's the command line used:
ffmpeg -loglevel debug -threads 4 -filter_complex_threads 4
Here is how it works:
When FFmpeg is built with libx265 support, options passed to the underlying
encoder must be passed wrapped in the documented syntax. For example,
libx264 expects -x264opts.
However, what you're reading online is for the command line x265 utility,
which takes in and
Hello there,
That's not the correct syntax. Pass these arguments as:
-x265-params "--no-sao:fps=24000/1001:p=veryslow:"
Make sure all options are in form key=value with value set to 1 if
it's a boolean option.
On 5 April 2018 at 11:11, Daniel wrote:
> Hello,
> I
Correction:
Based on your snippet:
/usr/local/Cellar/ffmpeg/3.4.2/bin/ffmpeg -stats -loglevel 24 -i
surce.mkv -map 0:a -map 0:v:0 -c:v libx265 -crf 20 -c:s copy -c:a copy
-x265-params "no-sao" -ss 5000 -t 5 destination.mp4
On 5 April 2018 at 11:29, Dennis Mungai <dmng...@gma
This is not the place to post such emails.
For one, you're launching FFmpeg through a wrapper, and two, how FFmpeg was
built on your platform is not known.
Run the same directly via FFmpeg, and post your results here, including the
build configuration of the FFmpeg binary you're using.
On Fri,
Yes, it's bad.
Install nasm.
If you're on Mac OSX 10.13.3, use macports to install the package.
After installation, it's as simple as:
$ sudo port install nasm
See https://www.macports.org/
On 5 April 2018 at 13:03, Jeffery Durand wrote:
> Hi,
>
> ./config gave
Hello,
Can you provide the output of vainfo?
On 18 April 2018 at 23:00, pilot constatinus wrote:
> Hi, i was recently trying out vaapi acceleration in ffmpeg. It works well
> with h264 hevc and vp8, but not with vp9. The output i get is:
>
> ffmpeg -vaapi_device
Hello, Gralfus.
This is how you should provide a sample for use:
https://www.ffmpeg.org/bugreports.html
Typically, extract the sample using a tool such as dd. Take this
snippet (quoted from the link above):
dd if=sample-file of=small-sample-file bs=1024 count=1
Then you would upload the
April 2018 at 19:43, Stuart Porter <stuart.por...@ctvc.co.uk> wrote:
> Thanks Dennis.
>
> Will VAAPI work on Win7?
>
> On Wed, 25 Apr 2018, 17:36 Dennis Mungai, <dmng...@gmail.com> wrote:
>
>> Try this if you can use VAAPI:
>> https://gist.github.com/B
Try this if you can use VAAPI:
https://gist.github.com/Brainiarc7/7b6049aac3145927ae1cfeafc8f682c1
On 25 April 2018 at 19:18, Micael Silva wrote:
> Are you using Intel i5, right? Have you checked if is it possible to use
> the hardware acceleration encoding? Many
Start by referring to HLS' muxer documentation:
https://www.ffmpeg.org/ffmpeg-formats.html#hls-2
And from FFmpeg: ffmpeg -hide_banner -h muxer=hls
When you're done with the documentation and are still unable to
achieve that goal, come back and report the issue you're experiencing.
On 15 March
Hello there,
Have you tried using the restream option?
ffmpeg -re -i capture_device -vaapi_device /dev/dri/renderD128
-movflags +faststart
-vf 'format=nv12|vaapi,hwupload' -c:v h264_vaapi {$encoder_opts} outputfile.
Try and report back.
On 20 March 2018 at 05:30, Kai Hendry
With OpenCL enablement, I'd like to know what platform you're on.
Wndows, a variant of Linux or Mac OSX.
From there, we can assist with build issues.
On 25 April 2018 at 19:44, Dong QingDan wrote:
> Hello.
> How are you?
> I am trying to compile ffmpeg4.0 with opencl.
>
You may want to look into using hls.
For usage reference, see:
ffmpeg -h muxer=hls
On Thu, Nov 1, 2018, 16:38 Abhisek Techie Hi,
> Since , ffserver is not supported I configured rtmp module in nginx .But
> still want to know which format to use for watching live stream in android
> mobile.
>
>
I'll correct that and update the question, thanks.
On Tue, 6 Nov 2018 at 11:08, Paul B Mahol wrote:
> On 11/6/18, Dennis Mungai wrote:
> > Hello there,
> >
> > From this patchwork:
> >
> https://git.ffmpeg.org/gitweb/ffmpeg.git/commit/8b8b0e2cd26cf1f522c630859fcb
Hello guys,
From the documentation available on FFmpeg's support for OpenMAX IL, the
only backend I can confirm to be officially supported (correct me if I'm
wrong) is the library provided for the Raspberry Pi, namely libbcm_host.so
and libopenmaxil.so, satisfied by the packages libraspberrypi0
A few observations:
The MX150 does not support NVENC, meaning that any NVENC-based hwaccels are
out of the window.
However, that same laptop is most likely to have Optimus, giving you access
to the Intel's Integrated graphics platform from which you can use either
QSV or VAAPI for hwaccel
On Wed, Jan 23, 2019, 21:18 Mahmood Naderan Carl,
> Please see the make output at https://pastebin.com/BzpEHvjV
>
>
> Regards,
> Mahmood
>
>
>
>
> On Wed, Jan 23, 2019 at 9:44 PM Mahmood Naderan
> wrote:
>
> >
> > Thanks for the quick reply. The config log can be seen at
> >
On Tue, Jan 15, 2019, 07:38 Sagar Lakhani hello,
> I am new to this community, i have used ffmpeg in my server in which i have
> live streams and i am segmenting them and then storing after a while i
> concat the segmented files and then output these to udp.
> Firstly i got a problem of open file
On Tue, 25 Dec 2018 at 07:22, dd wrote:
>
> Very magical with your guide, it works well.
> Thanks a lot for your quickly reply, I am very grateful.
> Merry Christmas!
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> At 2018-12-25 02:35:35, &qu
On Mon, 24 Dec 2018 at 21:23, dd wrote:
> Dear my friend,
> We replace cpu with gpu to ffmpeg recently, I set the gpu device no, but
> it still use default device 0.
> As the following problem Code:
> ffmpeg -hwaccel_device 2 -hwaccel cuvid -i a.mp4 -vf
> “scale=1080:720,overlay=()” -c:v
Hello there,
I'll answer the second part, concerning GPU acceleration:
First, consider what platform you're on. With Windows, you have access to
QuickSync (Intel), NVENC (Nvidia Kepler+) and AMD's VCE through AMF (On AMD
GCN-class hardware).
On Linux, you have access to VAAPI (on Intel and to a
Hey there,
Take a look at this:
https://gist.github.com/Brainiarc7/988473b79fd5c8f0db54b92ebb47387a
Do reach out if you need further assistance.
On Mon, Nov 26, 2018, 16:48 hans gerte Hi, need some help. i read a lot of forums and googled it, but i got more
> confused.
> i have a Ubuntu 14.04
Hello there,
On the system using more VRAM, can you lower the -surfaces value from 8 to
~6?
Also, in place of h264_cuvid, use nvdec instead.
Example:
ffmpeg -c:v nvdec -surfaces 8 -f mpegts -i
https://samples.ffmpeg.org/V-codecs/h264/HD-h264.ts -vcodec libx264 -preset
veryfast -crf 23 -c:a
Go through the output of:
ffmpeg -h muxer=hls
What build of FFmpeg are you using? Note that on this mailing list, only
git head is supported.
-Dennis.
On Fri, 30 Nov 2018 at 22:19, bra vo wrote:
> I would like to segment a live mpegts udp stream into hls and there are two
> constraints:
>
>
On Wed, 19 Dec 2018 at 16:35, qw wrote:
> Hi,
>
>
> I build zeromq-4.2.5, and build ffmpeg with --enable-libzmq. How to build
> tools/zmqsend?
>
>
> Thanks
>
>
> Regards
>
>
> Andrew
> ___
> ffmpeg-user mailing list
> ffmpeg-user@ffmpeg.org
>
On Mon, 28 Jan 2019 at 00:17, Carl Zwanzig wrote:
> On 1/27/2019 1:08 PM, Reindl Harald wrote:
> > well, when i started compile something from source i did my homework 15
> > years ago where internet was expensive
>
> Cool, when I started building-from-source most software was distributed on
>
On Sun, Jan 27, 2019, 23:56 Reindl Harald
>
> Am 27.01.19 um 21:38 schrieb Dennis Mungai:
> > Hello there,
> >
> > I'm building ffmpeg on centos 7 and one issue keeps cropping up:
> >
> > libass. Yes, its' installed. But ffmpeg's ./configure stage won't de
tion:
rpm -q libass-devel
libass-devel-0.13.4-6.el7.x86_64
Carl, thanks for the assistance. I'll install the missing package and
retest.
On Mon, 28 Jan 2019 at 00:06, Reindl Harald wrote:
>
>
> Am 27.01.19 um 22:03 schrieb Dennis Mungai:
> > On Mon, Jan 28,
On Mon, Jan 28, 2019, 00:02 Reindl Harald
>
> Am 27.01.19 um 21:59 schrieb Dennis Mungai:
> > On Sun, Jan 27, 2019, 23:56 Reindl Harald >>
> >> Am 27.01.19 um 21:38 schrieb Dennis Mungai:
> >>> Hello there,
> >>>
> >>>
On Mon, 28 Jan 2019 at 00:09, Carl Eugen Hoyos wrote:
> 2019-01-27 22:03 GMT+01:00, Dennis Mungai :
>
> > 1. pkg-config --libs --cflags freetype2
> > -I/usr/include/freetype2 -I/usr/include/libpng15 -lfreetype
> >
> > 2.pkg-config --libs --cflags frib
On Thu, 21 Mar 2019 at 05:25, Александр via ffmpeg-user <
ffmpeg-user@ffmpeg.org> wrote:
> Hello, I am trying to do full hardware video transcoding with scaling.
>
> Here is my console command:
> ffmpeg -hwaccel nvdec -hwaccel_output_format cuda -i "input.mp4" -vf
> scale_cuda=-2:360 -c:v
On Thu, 4 Apr 2019 at 01:52, Nick wrote:
> I started like 6 4k to dash(mp4) codings on a machine with around 34 GB
> RAM. In addition, after coding I used ffprobe to analyze them per frame.
> (everything parallel using docker instances)
> At the end I have weird erros. Some chunks in the middle
put of
> > > > $ PKG_CONFIG_PATH=/usr/local/src/ffmpeg/lib/pkgconfig pkg-config
> --cflags --libs freetype2
>
> -I/usr/include/freetype2 -I/usr/include/libpng15 -lfreetype
>
> On Thu, Apr 4, 2019 at 12:35 PM Moritz Barsnick wrote:
>
> > On Thu, Apr 04, 2019 at 09:39
On Thu, Apr 4, 2019, 09:27 Shay Nagar wrote:
> Hello,
>
> I trying to compile ffmpeg like this
> "PKG_CONFIG_PATH=/usr/local/src/ffmpeg/lib/pkgconfig ./configure
> --prefix=/opt/ffmpeg --extra-cflags=-I/opt/ffmpeg/include
> --extra-ldflags=-L/opt/ffmpeg/lib --pkg-config-flags=--static
>
Hello there,
How are global headers handled in the DASH and HLS muxers in FFmpeg?
In my workflow, omitting the option -flags +global_header in both HLS and
DASH results in unplayable streams. Is this by design?
Warm regards,
Dennis.
___
ffmpeg-user
On Sat, 16 Feb 2019 at 05:29, Dennis Mungai wrote:
> Hello there,
>
> The documentation for the webm_dash_manifest muxer mentions the
> time_shift_buffer_depth option, defined as "Smallest time (in seconds)
> shifting buffer for which any Representation is guaran
On Wed, 6 Mar 2019 at 15:28, Turritopsis Dohrnii Teo En Ming <
tdteoenm...@gmail.com> wrote:
> Good evening from Singapore,
>
> Is FFmpeg 4.1.1 able to record, convert and stream 8K UHD (7680 ×
> 4320) (33.2 megapixels) video?
>
> Thank you.
>
> ===BEGIN EMAIL SIGNATURE===
>
> The Gospel for all
Hello there,
How would one pass an option to an underlying muxer when using a fifo
output?
Take this example:
https://stackoverflow.com/questions/41880004/ffmpeg-how-to-stream-to-multiple-outputs-with-the-same-encoding-independently/42111569
Wherein you have outputs like these:
-i ... -f tee
Hello there,
The hwupload_cuda has an option for a device option, which can be called up
via:
hwupload_cuda=device=n where n would be a device index listed by nvidia-smi.
Can one get away without explicitly passing the device option to the
filter, if, in ffmpeg, a global hwaccel_device is
Hello there,
The documentation for the webm_dash_manifest muxer mentions the
time_shift_buffer_depth option, defined as "Smallest time (in seconds)
shifting buffer for which any Representation is guaranteed to be available.
"
What's the equivalent option/setting for the same in the dash muxer
On Fri, 25 Jan 2019 at 17:32, Joshua Barnard <
joshua.barn...@lawrencedavid.co.uk> wrote:
> Hi all,
>
> Thank you for taking the time to read this.
>
> I'm working on a project for my company that involves creating a time
> lapse video.
>
> The issue I'm having is that I have 6TB of raw video
On Sat, 2 Feb 2019 at 19:09, Mahmood Naderan wrote:
> >Note that hardware accelerated
> >decode is targeted for real time PLAYBACK without using any CPU resources,
> >and does not necessarily imply to be faster than a software based decode.
>
> If I got the point, you are saying that GPU version
On Sat, 2 Feb 2019 at 19:39, Mahmood Naderan wrote:
> >Using your sample above:
> >
> >./ffmpeg -init_hw_device cuda=0 -i ../4k_normal.mp4 -vf
> >format=nv12,hwupload,scale_npp=1280:720 -c:v h264_nvenc 720p1.mp4
> >
> >Try that and report back.
> >
> >
>
> It fails
>
>
> $ time ./ffmpeg
On Thu, Jan 31, 2019, 22:45 Mahmood Naderan Hi,
> I want to run a multicore CPU job with ffmpeg and I think the command
> should be
>
> ./ffmpeg -i ../4k_normal.mp4 -vf scale_npp=1280:720 720p1.mp4
>
> but it fails
>
> ./ffmpeg -i ../4k_normal.mp4 -vf scale_npp=1280:720 720p1.mp4
> ffmpeg
On Sat, 2 Feb 2019 at 18:47, Mahmood Naderan wrote:
> >Then don't use the cuda filter.
>
> So, my time measurements show that
>
> CPU: ./ffmpeg -i ../4k_normal.mp4 -vf scale=1280:720 720p1.mp4
> real0m23.748s
>
> GPU: ./ffmpeg -hwaccel cuvid -c:v h264_cuvid -i ../4k_normal.mp4 -vf
>
On Fri, 12 Apr 2019 at 06:49, Phil Rhodes via ffmpeg-user <
ffmpeg-user@ffmpeg.org> wrote:
> People, please...
> I offer the following in the hope that it can be viewed as constructive
> criticism.
> The argument here is effectively one which has been raging for years -
> decades, even - and it
Hello there,
FFmpeg trac seems to be down at the moment.
Accessing tickets, such as this one https://trac.ffmpeg.org/ticket/7831 is
a no go.
Was there a scheduled maintenance in place, or is this an outage?
Warm regards,
Dennis.
___
ffmpeg-user mailing
On Sun, 14 Apr 2019 at 01:55, Reindl Harald wrote:
>
>
> Am 14.04.19 um 00:39 schrieb CherylJosie via ffmpeg-user:
> > bullshit - they are just honest and direct instead the ass-licking and
> > attack subtle which is common in the shiny business world where nobody
> > has the eggs to say his
On Fri, 12 Apr 2019 at 23:26, Jim Shupert wrote:
>
> >> I'm from the Republic of Ireland and I have found your behaviour to be
> >> inappropriate for years.
> from the heartland of the USA I offer the hopeful words of that tragic
> American
> *Rodney King*, the man whose vicious beating by the
On Fri, 12 Apr 2019 at 10:27, Reindl Harald wrote:
>
>
> Am 12.04.19 um 06:51 schrieb Dennis Mungai:
> > We need to stop making *this* a justification for the toxicity the likes
> of
> > Reindl create in this mailing list.
>
> it's bullshit, wouldn't a few fools
On Thu, 30 May 2019 at 21:40, Dennis Mungai wrote:
> Hello there,
>
> According to the VAAPI encoder docs, slice based encoding can be enabled
> for the respective encoders via the -slices:v n where n is the number of
> slices so desired.
>
> However, toggling this option
On Wed, 29 May 2019 at 08:25, Matthew Reus wrote:
> hello all ,
>
> DO libaom AV1 support gpu or not . As on libx264 and libx265 they do
> support gpu encoding
Hello there,
This may be the wrong mailing list , particularly in the case of libaom’s
AV1 encoder, but:
(a). No, no form of GPU
Hello there,
According to the VAAPI encoder docs, slice based encoding can be enabled
for the respective encoders via the -slices:v n where n is the number of
slices so desired.
However, toggling this option on for the vp9_vaapi encoder results in a
warning on initialization about slice based
On Sun, 16 Jun 2019 at 22:26, David Shuman wrote:
> I have a video recorder that outputs files with an .mts suffix. mediainfo
> identifies these files as BDAV more commonly .m2ts files I attempt to copy
> these files with the following commands
>
> ffmpeg -i
>
On Mon, 10 Jun 2019 at 02:19, Eric Ball wrote:
> Thought I'd check with the mailing list before filing a bug report.
>
> ffmpeg version 4.1.1-tessus on macOS 10.14.5
>
> test.mp4 contains 3 streams :0 h264, :1 aac, :2 aac
>
> ffmpeg -i test.mp4 -filter_complex:a "astreamselect=inputs=2:map=1"
>
On Tue, 18 Jun 2019 at 01:20, Nishant Trivedi wrote:
> Hello,
>
> I'm trying to decode a video stream for one of my projects using the
> following command:
>
> *ffmpeg -hide_banner -hwaccel cuda -nostats -i
> rtmp://:/myapp/mystream -filter_complex [0]fps=fps=1[s0] -map
> [s0] -f rawvideo
On Tue, 18 Jun 2019 at 02:06, Nishant Trivedi wrote:
> That worked! Thanks Dennis!
>
> On Mon, Jun 17, 2019 at 6:37 PM Dennis Mungai wrote:
>
> > On Tue, 18 Jun 2019 at 01:20, Nishant Trivedi wrote:
> >
> > > Hello,
> > >
> > > I'm trying to
On Thu, 9 May 2019 at 13:04, qw wrote:
> Hi,
>
>
> If I build libx265 with bitdepth=10bit, and link it with ffmpeg, what's
> command line to transcode video with libx265 8/10bit?
>
>
Hmm, add either global option below:
(a). -bits_per_raw_sample 10 and the encoder will pick both the profile and
On Thu, 9 May 2019 at 02:44, Dennis Mungai wrote:
> Hello there,
>
> I have a sample file with the following attributes:
>
> ffprobe -i rv.mkv
> ffprobe version N-93814-g48539b62fc Copyright (c) 2007-2019 the FFmpeg
> developers
> built with gcc 7 (Ubu
On Thu, 9 May 2019 at 03:06, Philip Langdale wrote:
> On Thu, 9 May 2019 02:53:01 +0300
> Dennis Mungai wrote:
>
> > >
> > > The GPU matrix published by NVIDIA only indicates support for HEVC
> > > @ 4:4:4 :
> > > https://developer.nvid
Hello there,
I have a sample file with the following attributes:
ffprobe -i rv.mkv
ffprobe version N-93814-g48539b62fc Copyright (c) 2007-2019 the FFmpeg
developers
built with gcc 7 (Ubuntu 7.4.0-1ubuntu1~18.04)
configuration: --pkg-config-flags=--static --prefix=/home/brainiarc7/bin
On Mon, Apr 29, 2019, 11:16 andrei ka wrote:
> hmm, i think one could extract frames with ffmpeg and pipe 'em into some
> gpu encoging software. or one can invent some sort of chain processing,
> like encoding video in gpu at 1 fps and then pipe into ffmpeg to split
> video into frames in cpu ?
On Sat, 4 May 2019 at 20:42, sean darcy wrote:
> Giving up on qsv, I'm trying vaapi, but ffmpeg can't find the vp9 entry
> point supported by my cpu , and found by vainfo.
>
> FWIW, hevc_vaapi works.
>
>
> ffmpeg -vaapi_device /dev/dri/renderD128 -i infile.mkv -map v -map 0:2
> -vf
On Fri, May 3, 2019, 03:35 sean darcy wrote:
> I'm getting old watching libx265 run, so I was thinkng of experimenting
> with hevc_qsv. I configured ffmpeg with libmpfx. But now I read I need a
> plugin: hevc_hw. And to get that plugin I need to install the Intel
> Media SDK, which requires me
On Fri, 3 May 2019 at 12:39, Carl Eugen Hoyos wrote:
> Am Fr., 3. Mai 2019 um 06:26 Uhr schrieb Dennis Mungai >:
>
> > See this answer on superuser for more details
> > https://superuser.com/a/1428799/473795
>
> Would you agree that this answer contains too m
On Fri, 3 May 2019 at 12:55, Carl Eugen Hoyos wrote:
> Am Fr., 3. Mai 2019 um 11:51 Uhr schrieb Dennis Mungai >:
>
> > Making assumptions on the user's technical capabilities in such a
> project,
> > on a user forum, is dangerously dismissive.
>
> That was exactly
On Thu, 11 Jul 2019 at 17:55, Алексей via ffmpeg-user <
ffmpeg-user@ffmpeg.org> wrote:
> I've a low framerated video file, recorded at 24 fps. I need change its
> framerate to 60 fps, but with smooth playback style adding. Can u help me
> to do this on my nvenc. Thanks.
Hello there,
What
1 - 100 of 278 matches
Mail list logo