Recherche avancée

Sur d’autres sites (13478)

• FFMPEG Concatenate multiple videos causes : Too many invisible frames

  2 décembre 2019, par Silmood

  i’m trying to concatenate multiple .webm files in a single one. One of these files is a simple black video generated with the next command :

  ffmpeg -f lavfi -i color=c=black:s=1920x1080:d=5.2 black.webm

  Then this is concat_list.txt

  file 'black.webm'
  
  file '1.webm'
  
  file '2.webm'
  
  file '3.webm'

  Finally i try to concatenate files with :

  ffmpeg -f concat -i concat_list.txt -c copy video.webm

  The result is a long list of this message :

  [AVBSFContext @ 0x7fcecef00180] Too many invisible frames
  
  [AVBSFContext @ 0x7fcecef00180] Failed to receive packet from filter vp9_superframe for stream 0

  Complete log

  The problem seems to be the black.webm file. I removed it from the concat_list.txt and everything works fine.

  It’s important to mention that none of these files has an audio stream.

• ffmpeg failed to drawbox and set volume

  27 janvier 2021, par Hussam Al-Barodi

  I don't know what is wrong in my command with ffmpeg.
Lets say I have a video and I want to make a black screen with muted audio between 20-30 seconds. So what I wrote is :

  


  ffmpeg -i input.mp4 -filter_complex "[0:v]trim=0:20[0v];[0:a]atrim=0:20[0a];[0:v]trim=20:30,drawbox=color=black:t=fill[1v];[0:a]atrim=20:30,volume=0[1a];[0:v]trim=30:60[2v];[0:a]atrim=30:60[2a];[0v][1v][2v]concat=n=3:v=1:a=0[outv];[0a][1a][2a]concat=n=3:v=0:a=1[outa]" -map [outv] -map [outa] output.mp4


  


  Now, I expect to have a video with 1 min length where the seconds between 20 & 30 are muted with black screen, but what I got is :

  


  20 sec correct
20 sec freezing video with no audio
40 sec black video with no audio
30 sec correct


  


  Can anyone help and tell me what is wrong in the command line ?

  


• Different filesizes for images generated using octave and python

  17 décembre 2020, par lakshayg

  I am using python (scikit-image) and octave to generate 200 images as follows

  


  Python3

  


  import numpy as np
from skimage.io import imsave

images = [255*np.ones((100,100), dtype=np.uint8),  # white
             np.zeros((100,100), dtype=np.uint8)]  # black

for i in range(200): # save alternating black and white images
    imsave('%04d.png'%(i+1), images[i%2])


  


  Octave

  


  pkg load image;

im1 = 255*ones(100,100); # white
im2 = zeros(100,100);    # black
for i=1:200
    name = sprintf('%04d.png', i);
    if mod(i,2) == 0
        imwrite(im1, name);
    else
        imwrite(im2, name);
    end
end


  


  Next, I use ffmpeg to generate two videos (alternating white and black frames) from these two sets of images using the following command

  


  ffmpeg -r 10 -loglevel quiet \
       -i ./%04d.png -c:v libx264 \
       -preset ultrafast -crf 0 ./out.mkv


  


  

  1. Sizes of image files generated by both these codes are different.

  


  


  

  • Octave white : 192 bytes, black : 98 bytes

  


  • Python white : 120 bytes, black : 90 bytes

  


  


  

  2. Sizes of video files generated from these octave and python images are significantly different from each other.

  


  


  

  • Octave filesize : 60 kilobytes

  


  • Python filesize : 116 kilobytes

  


  


  Why do we have this apparently very strange behavior ?

  


  EDIT

  


  Since it was suggested that the behavior might be due to octave and python using different bit-depths to store the images, I changed the octave code to use 8 bit numbers

  


  im1 = uint8(255*ones(100,100)); # white
im2 = uint8(zeros(100,100));    # black


  


  and now the image file sizes are nearly the same

  


  

  • Octave white : 118 bytes, black : 90 bytes

  


  • Python white : 120 bytes, black : 90 bytes

  


  


  but the problem is still the same for video files, octave : 60K, python : 116K