[FFmpeg-user] Decimation with ppsrc=1 malfunctions

2020-12-26 Thread Mark Filipak (ffmpeg)

Decimation with ppsrc=1 malfunctions.

Paul fixed this somewhat, but it's still in trouble.
Since I eliminated threading and decimation as the cause, I suspect that frames numbers are being 
bollixed.


The report package is here:
https://www.dropbox.com/t/zu4cezneCJIsdmUu

Expires Jan 2, 2021.
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".

Re: [FFmpeg-user] issue with kmsgrab

2020-12-26 Thread Nasty Phoenix
Le samedi 26 décembre 2020 à 10:09 +0100, Nasty Phoenix a écrit :
> Hello
> 
> I encountered problem using kmsgrab
> 
> theflyingman@theflyingman-Aspire-5745:~/Vidéos$ sudo ffmpeg -loglevel
> verbose -v verbose -y -f kmsgrab -i - -vf 'hwdownload,format=bgr0'
> /home/theflyingman/Vidéos/output.mp4
> ffmpeg version 4.2.4-1ubuntu0.1 Copyright (c) 2000-2020 the FFmpeg
> developers
>   built with gcc 9 (Ubuntu 9.3.0-10ubuntu2)
>   configuration: --prefix=/usr --extra-version=1ubuntu0.1 --
> toolchain=hardened --libdir=/usr/lib/x86_64-linux-gnu --
> incdir=/usr/include/x86_64-linux-gnu --arch=amd64 --enable-gpl --
> disable-stripping --enable-avresample --disable-filter=resample --
> enable-avisynth --enable-gnutls --enable-ladspa --enable-libaom --
> enable-libass --enable-libbluray --enable-libbs2b --enable-libcaca --
> enable-libcdio --enable-libcodec2 --enable-libflite --enable-
> libfontconfig --enable-libfreetype --enable-libfribidi --enable-
> libgme
> --enable-libgsm --enable-libjack --enable-libmp3lame --enable-
> libmysofa 
> --enable-libopenjpeg --enable-libopenmpt --enable-libopus --enable-
> libpulse --enable-librsvg --enable-librubberband --enable-libshine --
> enable-libsnappy --enable-libsoxr --enable-libspeex --enable-libssh
> --
> enable-libtheora --enable-libtwolame --enable-libvidstab --enable-
> libvorbis --enable-libvpx --enable-libwavpack --enable-libwebp --
> enable-libx265 --enable-libxml2 --enable-libxvid --enable-libzmq --
> enable-libzvbi --enable-lv2 --enable-omx --enable-openal --enable-
> opencl --enable-opengl --enable-sdl2 --enable-libdc1394 --enable-
> libdrm 
> --enable-libiec61883 --enable-nvenc --enable-chromaprint --enable-
> frei0r --enable-libx264 --enable-shared
>   libavutil  56. 31.100 / 56. 31.100
>   libavcodec 58. 54.100 / 58. 54.100
>   libavformat58. 29.100 / 58. 29.100
>   libavdevice58.  8.100 / 58.  8.100
>   libavfilter 7. 57.100 /  7. 57.100
>   libavresample   4.  0.  0 /  4.  0.  0
>   libswscale  5.  5.100 /  5.  5.100
>   libswresample   3.  5.100 /  3.  5.100
>   libpostproc55.  5.100 / 55.  5.100
> 
> 
> You can see the ffmpeg logs with my card0 and renderD128 (the devices
> i
> found in /dev/dri/) in https://pastebin.com/BbP0Ea2Q
> 
> Everything seems ok but the video file is a grey/blank screen with
> some
> small blackline
> 
> I don't understand and my goal is after the video will be ok to add
> sound with this videoscreencapture.
> 
> Regards
> 
> NastyPhoenix
> 
> 
> 

___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".

Re: [FFmpeg-user] How to decipher FFMEG version number?

2020-12-26 Thread Reindl Harald



Am 26.12.20 um 05:52 schrieb Gyan Doshi:



On 26-12-2020 05:12 am, Dan Bridges wrote:

I build FFMPEG under Win10 using media-autobuild_suite
(https://github.com/m-ab-s/media-autobuild_suite)

https://github.com/m-ab-s/media-autobuild_suite

Is it possible to decipher the version number:

ffmpeg version N-100471-g85bd703b3a-g5b48d2af43+1 Copyright (c)
2000-2020 the FFmpeg developers
   built with gcc 10.2.0 (Rev6, Built by MSYS2 project)



The media-autobuild_suite adds some out-of-tree patches on top of 
ffmpeg, so its version number is non-standard.


However, it can still be deciphered.

N indicates that the build is of the master branch of ffmpeg.

100471 is the commit count. See the number on the blue bar just above 
the file listing at https://github.com/FFmpeg/FFmpeg


The 2nd g-prefixed hash - g5b48d2af43 identifies the latest ffmpeg 
commit at time of building.


It can be viewed at https://github.com/FFmpeg/FFmpeg/commit/5b48d2af43

+1 represents the number of out-of-tree commits applied on top


well, smart versioning would have the intended version of the next 
release somewhere in the code

https://ffmpeg.org/releases/

[harry@srv-rhsoft:~]$ ffmpeg
ffmpeg version 4.3.1 Copyright (c) 2000-2020 the FFmpeg developers

what is so hard in a snapshotbuild having 4.3.2 or whatever si the 
intended next release as usual and then N-100471-g85bd703b3a-g5b48d2af43+1

___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".