Recherche avancée

Sur d’autres sites (4688)

• Using 'overlay_cuda' in ffmpeg with transparency in input frames

  16 mai 2023, par time4tea

  I'm trying to overlay a full frame image on top of an MP4, in ffmpeg, using as much hardware-assistance as possible.

  


  This is for https://github.com/time4tea/gopro-dashboard-overlay

  


  I have the non-GPU overlay working totally fine, and would like to take advantage of the GPU now.

  


  The inputs to ffmpeg are :

  


  

  • a stream from an MP4 file - with 1 audio and 1 video stream

  


  • frames from the dashboard software, which are supplied as raw RGBA frames, at the same frame size as the movie.

  


  


  I've managed to get the overlay sort of working using the nvidia extensions, but it doesn't work as it uses nv12 frame formats which don't have any idea of transparency (AFAIK) so the overlaid frame completely obscures the movie frame - makes sense.

  


  The incantation that does this is (put on separate lines to try to keep the different sections - inputs / transforms / outputs - obvious) :

  


  ffmpeg -y -report -hide_banner -loglevel info 
-hwaccel cuda -hwaccel_output_format cuda 
-i movie.mp4 
-f rawvideo -framerate 10.0 -s 1024x576 -pix_fmt rgba -i - 
-filter_complex [0:v]null[mp4_stream];[1:v]format=nv12,hwupload_cuda[overlay_stream];[mp4_stream][overlay_stream]overlay_cuda,hwdownload,format=nv12 
-vcodec h264_nvenc 
-rc:v cbr -b:v 20M -bf:v 3 -profile:v high -spatial-aq true 
-movflags faststart 
output.mp4


  


  When i try to use yuva420p (which I believe is the correct format, but happy to be corrected) - in all various different places, for example :

  


  ffmpeg -y -report -hide_banner -loglevel info 
-hwaccel cuda -hwaccel_output_format yuva420p 
-i movie.mp4 
-f rawvideo -framerate 10.0 -s 1024x576 -pix_fmt rgba -i - 
-filter_complex [0:v]null[mp4_stream];[1:v]format=yuva420p,hwupload_cuda[overlay_stream];[mp4_stream][overlay_stream]overlay_cuda,hwdownload,format=yuva420p -vcodec h264_nvenc 
-rc:v cbr -b:v 20M -bf:v 3 -profile:v high -spatial-aq true -movflags faststart output.mp4



  


  I get flavours of the same error message :

  


  Impossible to convert between the formats supported by the filter 'Parsed_null_0' and the filter 'auto_scaler_1'

  


  AIUI - auto scalers are inserted into the pipeline when things don't match resolutions or formats - but here everything should match ?

  


  Using a filter_complex of [1:v]format=yuva420p,hwupload_cuda[overlay_stream];[0:v][overlay_stream]overlay_cuda,hwdownload,format=yuva420p i.e not using a null filter, which I put in just to make quickly changing filters easy, has the same error.

  


  Impossible to convert between the formats supported by the filter 'graph 0 input from stream 0:0' and the filter 'auto_scaler_1'

  


  I have looked at the suggested similar questions, and they don't appear to solve the problem for me.

  


  Thanks for any suggestions !

  


• Non-monotonous DTS in output stream previous current changing to This may result in incorrect timestamps in the output file

  21 juillet 2020, par Vitalis Hommel

  I am having a file.txt with rather close snippets

  


  file 'input.mp4'
inpoint 1.5402465510368346
outpoint 2.722609395980835
file 'input.mp4'
inpoint 3.192511146068573
outpoint 7.074568028450012
file 'input.mp4'
inpoint 7.851800565719604
outpoint 9.023683423995971
file 'input.mp4'
inpoint 10.054571752548219
outpoint 12.008032734394073
file 'input.mp4'
inpoint 18.70977670431137
outpoint 21.20993923664093
file 'input.mp4'
inpoint 24.51183382153511
outpoint 26.465287650823594
...


  


  I concat them with

  


  ffmpeg -safe 0 -f concat -i file.txt out.mp4


  


  and I tried

  


  ffmpeg -use_wallclock_as_timestamps 1 -safe 0 -f concat -i file.txt out.mp4


  


  Yet I get

  


  [mp4 @ 00000178c514cc00] Non-monotonous DTS in output stream 0:1; previous: 2069, current: 2067; changing to 2070. This may result in incorrect timestamps in the output file.
[mp4 @ 00000178c514cc00] Non-monotonous DTS in output stream 0:1; previous: 2070, current: 2067; changing to 2071. This may result in incorrect timestamps in the output file.
[mp4 @ 00000178c514cc00] Non-monotonous DTS in output stream 0:1; previous: 2071, current: 2067; changing to 2072. This may result in incorrect timestamps in the output file.
[aac @ 00000178c50f8a80] Queue input is backward in time
[mp4 @ 00000178c514cc00] Non-monotonous DTS in output stream 0:1; previous: 2758, current: 2756; changing to 2759. This may result in incorrect timestamps in the output file.
[aac @ 00000178c50f8a80] Queue input is backward in time
    Last message repeated 5 times
[mp4 @ 00000178c514cc00] Non-monotonous DTS in output stream 0:1; previous: 7581, current: 7579; changing to 7582. This may result in incorrect timestamps in the output file.
[aac @ 00000178c50f8a80] Queue input is backward in time
[mp4 @ 00000178c514cc00] Non-monotonous DTS in output stream 0:1; previous: 7582, current: 7579; changing to 7583. This may result in incorrect timestamps in the output file.
[aac @ 00000178c50f8a80] Queue input is backward in time
[mp4 @ 00000178c514cc00] Non-monotonous DTS in output stream 0:1; previous: 7583, current: 7579; changing to 7584. This may result in incorrect timestamps in the output file.
[aac @ 00000178c50f8a80] Queue input is backward in time
[mp4 @ 00000178c514cc00] Non-monotonous DTS in output stream 0:1; previous: 7584, current: 7579; changing to 7585. This may result in incorrect timestamps in the output file.
[aac @ 00000178c50f8a80] Queue input is backward in time
[mp4 @ 00000178c514cc00] Non-monotonous DTS in output stream 0:1; previous: 7585, current: 7579; changing to 7586. This may result in incorrect timestamps in the output file.
[aac @ 00000178c50f8a80] Queue input is backward in time
[mp4 @ 00000178c514cc00] Non-monotonous DTS in output stream 0:1; previous: 7586, current: 7579; changing to 7587. This may result in incorrect timestamps in the output file.
[aac @ 00000178c50f8a80] Queue input is backward in time
[mp4 @ 00000178c514cc00] Non-monotonous DTS in output stream 0:1; previous: 7587, current: 7579; changing to 7588. This may result in incorrect timestamps in the output file.
[aac @ 00000178c50f8a80] Queue input is backward in time
[mp4 @ 00000178c514cc00] Non-monotonous DTS in output stream 0:1; previous: 7588, current: 7579; changing to 7589. This may result in incorrect timestamps in the output file.
[mp4 @ 00000178c514cc00] Non-monotonous DTS in output stream 0:1; previous: 7589, current: 7579; changing to 7590. This may result in incorrect timestamps in the output file.
[aac @ 00000178c50f8a80] Queue input is backward in time
[mp4 @ 00000178c514cc00] Non-monotonous DTS in output stream 0:1; previous: 7590, current: 7579; changing to 7591. This may result in incorrect timestamps in the output file.
[aac @ 00000178c50f8a80] Queue input is backward in time


  


  And the final file is cut at wrong places.

  


  How to make the file.txt work ?

  


• Understand your visitors by seeing where they click, hover, type and scroll, and replay their actions in a video

  18 mai 2017, par InnoCraft — Plugins

  Hi, this is Mike from InnoCraft, the company of the makers of Piwik Analytics which is used by over 1 million websites and apps in over 150 countries.

  I’m very proud to introduce you to our Heatmap & Session Recording feature which lets you analyze your visitors’ behaviour on a whole new level that was not possible before.

  With Heatmaps you can see where people think something is clickable but it is not, how far down the page do they scroll, whether they see your important buttons and Call To Actions, or even whether you can re-position your page layout to put the important content in more visible places. Both the mouse movements and all clicks are recorded and viewable on these new beautiful heatmap visualisations.

  With Session Recordings, you get to see a video showing exactly what a visitor did on your pages, including all mouse movements, scrolls, text typed in the keyboard, and more. Using these recordings you can improve the usability on your website, replace costly (and less effective) eye tracking sessions, and you can now see exactly what problems your visitors experience or how they behave on your website. This gives new insights and ability to understand what your users think.

  -> Read the rest of the story on the Heatmaps & Session Recordings Marketplace page.

  What does the new Heatmaps reports look like ?

  Here is below just a little preview of the new Heatmaps reports.

  1) Mouse move and Click Heatmaps

  

  2) A Scroll Heatmap

  

  What does the new Session Recording look like ?

  You can replay videos of exactly what your users did on your websites including mouse moves, scrolls, typing in forms, and more.

  1) Listing all recorded video sessions

  

  2) Playing a recorded video session

  

  Where do I get Heatmaps & Session Recording for Piwik ?

  The new premium plugin is available on the Piwik Marketplace :

  Get Heatmaps & Session Recording on the Marketplace

  This is a premium plugin for Piwik and comes with our 14 day money back guarantee and 1-click installation & updates (all product updates come for free).

  You can also signup for a free Piwik Cloud-hosted trial to discover the power of Heatmaps & Session Recordings !