Recherche avancée

Sur d’autres sites (9142)

• How to make transparent background of image after rotating using ffmpeg in Android ?

  18 juin 2020, par Mit Shah

  The issue I am facing is, rotating the image in app, it works as expected. But after saving the file, the difference is seen. The image is rotated but with black background instead of transparent. I have looked several places for solution but didn't succeed.

  



  I have tried this things :

  



  

  • In command, c=none, c=black@, c=black@0, c=000000, c=0x000000

  


  • With both extensions jpg and png.

  


  



  But failed to get the required output.

  



  For practical understanding, here are the two images stating Input and Output.

  



  Help me out. Thanks

  



  Input :
  


  



  Output :
  


  


• Creating App from Terminal code

  11 août 2014, par user3084141

  Good evening,
  I want to create an app that demuxes Audio from a Videofile with ffmpeg,that uses the following Terminal-code

  "ffmpeg location" -i "Source.file (Video.mp4)" -vn -ss "time" -t "sec" -acodec copy "Destination.file ("Audio.m4a")"

  I couldn’t find a ffmpeg gui for OSX that would let me do that.
  The Programm should ask for a Source file, a destination, start time and length.
  ffmpeg could be integrated or specified.

  Maybe it’s easier to Automate a Service.

  I’m sorry the I don’t have any experience on mac and automating Terminal commands.
  I have to start from 0 only a little bit visual basic experience.

• 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