
Recherche avancée
Autres articles (24)
-
Supporting all media types
13 avril 2011, parUnlike most software and media-sharing platforms, MediaSPIP aims to manage as many different media types as possible. The following are just a few examples from an ever-expanding list of supported formats : images : png, gif, jpg, bmp and more audio : MP3, Ogg, Wav and more video : AVI, MP4, OGV, mpg, mov, wmv and more text, code and other data : OpenOffice, Microsoft Office (Word, PowerPoint, Excel), web (html, CSS), LaTeX, Google Earth and (...)
-
ANNEXE : Les plugins utilisés spécifiquement pour la ferme
5 mars 2010, parLe site central/maître de la ferme a besoin d’utiliser plusieurs plugins supplémentaires vis à vis des canaux pour son bon fonctionnement. le plugin Gestion de la mutualisation ; le plugin inscription3 pour gérer les inscriptions et les demandes de création d’instance de mutualisation dès l’inscription des utilisateurs ; le plugin verifier qui fournit une API de vérification des champs (utilisé par inscription3) ; le plugin champs extras v2 nécessité par inscription3 (...)
-
Encoding and processing into web-friendly formats
13 avril 2011, parMediaSPIP automatically converts uploaded files to internet-compatible formats.
Video files are encoded in MP4, Ogv and WebM (supported by HTML5) and MP4 (supported by Flash).
Audio files are encoded in MP3 and Ogg (supported by HTML5) and MP3 (supported by Flash).
Where possible, text is analyzed in order to retrieve the data needed for search engine detection, and then exported as a series of image files.
All uploaded files are stored online in their original format, so you can (...)
Sur d’autres sites (3781)
-
How to reduce fps to reduce filesize using ffmpeg ?
10 septembre 2024, par AsasI recorded the video in waaaay to high of fps and its like over 100 gb now, i dont want any quality degradation just to lower the fps to a reasonable 60 but when i googled i got the result which converted my video but the size is the same for some reason
I tried


ffmpeg -y -i input_video.mp4 -c copy -f h264 output_raw_bitstream.h264
ffmpeg -y -i input_video.mp4 -vn -acodec copy output_audio.aac
ffmpeg -y -r 24 -i output_raw_bitstream.h264 -i output_audio.aac -c copy output.mp4



but replaced numbers and names for what is in my case but it outputs the same 100 plus filesize


-
7 Fintech Marketing Strategies to Maximise Profits in 2024
24 juillet 2024, par Erin -
Different filesizes for images generated using octave and python
22 février 2017, par Lakshay GargI 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
endNext, 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-
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
-
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 dues to octave and python using different bit-depths to store the images, I changes the octave code to use 8 bit numbers
im1 = uint8(255*ones(100,100)); # white
im2 = uint8(zeros(100,100)); # blackand 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
-