Re: [FFmpeg-user] Conversion wav -> mp3 -> wav

wav is uncompressed, you can put 15 minutes 10 seconds of really horrible music (or even just silence) in there, it will still be 154 MB. The relationship between quality and file size only exists for compressed formats and you will find that the mp3 is much smaller than the wav.

[FFmpeg-user] invalid video parameters (-15) with h264_qsv

Hi list, I'm trying to encode using h264_qsv, but I'm getting "Error initializing the encoder: invalid video parameters (-15)". Command line: ffmpeg -i src.mp4 -c:v h264_qsv -preset:v faster -q 5 -look_ahead 0 -loglevel debug test.mp4 Full log output: https://pastebin.com/raw/BNZyK0KA MediaSDK

Re: [FFmpeg-user] Is there a reason the default vsync for the mp4 muxer is not 2?

>2018-05-23 16:24 GMT+02:00, André Hänsel <an...@webkr.de>: >>>> I added -vsync 2 to the command line options and I got a file >>>> that has roughly the same number of frames as the input. >> >>> But it is - unfortunately! - an invalid file. &g

[FFmpeg-user] Is there a reason the default vsync for the mp4 muxer is not 2?

I was re-encoding a video with: ffmpeg -i in.mp4 -c:v libx264 -movflags faststart -crf 30 out.mp4 and surprisingly the output file was much larger (9 MB) than the input file (3 MB). I examined the files with: ffprobe -show_entries frame=pict_type,pkt_size -of csv in.mp4 and I noticed that the

Re: [FFmpeg-user] Is there a reason the default vsync for the mp4 muxer is not 2?

>> I added -vsync 2 to the command line options and I got a file >> that has roughly the same number of frames as the input. > But it is - unfortunately! - an invalid file. Is there a ticket/additional info about what is/can be invalid in this file? With -enc_time_base -1 -vsync 2 my output

Re: [FFmpeg-user] vaapi: Impossible to convert between the formats

> > How should I go about debugging this further? > > First step is to provide the command line you tested together > with the complete, uncut console output. > > Carl Eugen See below for another console output, this time with loglevel "trace". I noticed this line: [mpeg4 @ 0x555f040fe2e0]

Re: [FFmpeg-user] vaapi: Impossible to convert between the formats

> > How should I go about debugging this further? > > First step is to provide the command line you tested together > with the complete, uncut console output. > > Carl Eugen # ffmpeg -hwaccel vaapi -vaapi_device /dev/dri/renderD128 -hwaccel_output_format vaapi -i test.avi -c:v h264_vaapi

[FFmpeg-user] vaapi: Impossible to convert between the formats

I'm trying to transcode an MPEG4 avi to MP4 with VAAPI, but I'm getting an error: Impossible to convert between the formats supported by the filter 'Parsed_null_0' and the filter 'auto_scaler_0' Error reinitializing filters! Failed to inject frame into filter network: Function not implemented

Re: [FFmpeg-user] Sending partial GOP / flushing buffers

> $ ffmpeg -f avfoundation -framerate 30 -s 1280x720 -pixel_format yuyv422 -i > default -an -c:v libx264 -profile:v main -level 3.2 -preset medium -tune > zerolatency -b:v 2000k -flags +cgop+low_delay -movflags > empty_moov+omit_tfhd_offset+frag_keyframe+default_base_moof+isml -x264opts >

[FFmpeg-user] Green line with vaapi scaling

When I scale with scale_vaapi, it results in a green line at the bottom of the image, see attachment. Command line: ffmpeg -hwaccel vaapi -vaapi_device /dev/dri/renderD128 -hwaccel_output_format vaapi -i bbb.mp4 -vf "scale_vaapi=w=240:h=135:format=yuv420p,hwdownload,format=yuv420p" -frames 1

Re: [FFmpeg-user] Green line with vaapi scaling

> Can you retest with git head? > > Build FFmpeg from source and retest. I don't think I can do that easily, but I found a static build on the FFmpeg website. It's supposed to support VAAPI: # ./ffmpeg -hwaccels ffmpeg version N-46272-g3a56ade1f-static https://johnvansickle.com/ffmpeg/

Re: [FFmpeg-user] vaapi: Impossible to convert between the formats

> Intel devices do not support MPEG-4 part 2 at all. Then it's clear and no problem at all. May I suggest bumping the loglevel of [mpeg4 @ 0x555f040fe2e0] Codec mpeg4 profile 0 not supported for hardware decode. to at least "info", if not "warning"? Then it would have known immediately what

[FFmpeg-user] Get video info with ffmpeg, then exit

I'd like to get the media info, specifically the duration, with ffmpeg (not ffprobe). I can parse this from the "Input" output: > Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'test.mp4': > Metadata: > ... > Duration: 00:00:33.41, start: 0.00, bitrate: 5778 kb/s The videos in question have

Re: [FFmpeg-user] ff_frame_thread_encoder_init failed when run via PHP exec

> > It works perfectly when I log in to the console via putty and run it. But > > when I run it via exec() in PHP it always comes back with > > ff_frame_thread_encoder_init failed Error initializing output stream 0:0 -- > > Error while opening encoder for output stream #0:0 - maybe incorrect > >

Re: [FFmpeg-user] ff_frame_thread_encoder_init failed when run via PHP exec

> I ran ffmpeg with ulimit -a but it comes back with unrecognized option 'a' Not ffmpeg, just "ulimit -a". It will show you the current resource limits that are set in that environment. PHP might set some and then you will see it in the output. ___

[FFmpeg-user] frag_duration ignored when segmentation is used

Hi list, this successfully generates a fragmented MP4: ffmpeg -i rtsp://192.168.1.202:554/ch01.264 -map 0:0 -c:v copy -frag_duration 400 out.mp4 But this doesn't, it generates a normal MP4 (ftyp-free-mdat-moov): ffmpeg -i rtsp://192.168.1.202:554/ch01.264 -map 0:0 -c:v copy -frag_duration