
Recherche avancée
Autres articles (35)
-
Support de tous types de médias
10 avril 2011Contrairement à beaucoup de logiciels et autres plate-formes modernes de partage de documents, MediaSPIP a l’ambition de gérer un maximum de formats de documents différents qu’ils soient de type : images (png, gif, jpg, bmp et autres...) ; audio (MP3, Ogg, Wav et autres...) ; vidéo (Avi, MP4, Ogv, mpg, mov, wmv et autres...) ; contenu textuel, code ou autres (open office, microsoft office (tableur, présentation), web (html, css), LaTeX, Google Earth) (...)
-
Other interesting software
13 avril 2011, parWe don’t claim to be the only ones doing what we do ... and especially not to assert claims to be the best either ... What we do, we just try to do it well and getting better ...
The following list represents softwares that tend to be more or less as MediaSPIP or that MediaSPIP tries more or less to do the same, whatever ...
We don’t know them, we didn’t try them, but you can take a peek.
Videopress
Website : http://videopress.com/
License : GNU/GPL v2
Source code : (...) -
Keeping control of your media in your hands
13 avril 2011, parThe vocabulary used on this site and around MediaSPIP in general, aims to avoid reference to Web 2.0 and the companies that profit from media-sharing.
While using MediaSPIP, you are invited to avoid using words like "Brand", "Cloud" and "Market".
MediaSPIP is designed to facilitate the sharing of creative media online, while allowing authors to retain complete control of their work.
MediaSPIP aims to be accessible to as many people as possible and development is based on expanding the (...)
Sur d’autres sites (6295)
-
Trying to tonemap 14-bit grayscale video
12 janvier 2018, par TrevorI’m trying to generate h.264 video from raw 2-byte gray video (14-bit range encoded in 16-bit values). I can do something like :
ffmpeg -f rawvideo -pix_fmt gray16le -s:v 1280x720 -r 60 -i input.raw -c:v libx264 output.mp4
And I get video but it’s pretty dark, not sure if it’s clipping, doing a linear remap, or storing the 16-bit data and VLC is doing the remap. ffprobe is reporting
Video: h264 (High 4:4:4 Predictive) (avc1 / 0x31637661), yuvj444p(pc), 1280x720, 108 kb/s, 60 fps, 60 tbr, 15360 tbn, 120 tbc
I was figuring I’d use the tonemap filter to make a better mapping. I added a filter before the output file with
-vf
.tonemap=hable
errorsImpossible to convert between the formats supported by the filter 'graph 0 input from stream 0:0' and the filter 'auto_scaler_0'
zscale=transfer=linear,tonemap=hable
errorsImpossible to convert between the formats supported by the filter 'Parsed_tonemap_1' and the filter 'auto_scaler_1'
zscale=transfer=linear,tonemap=hable,zscale=transfer=bt709,format=yuvj444p
errorscode 3074: no path between colorspaces
I’m not sure where to proceed from here...
-
How to check if FFmpeg process is complete
5 juillet 2017, par lllazoHow can I check if
ffmpeg
process is complete.
Like if I want to perform overlaying of image to video, I want to determine when the process is completed or if the output file is already complete.So from this command
ffmpeg -i original.mp4 -i watermark.png -filter_complex "overlay=(W-w)/2:(H-h)/2" output.mp4
How can I determine if
output.mp4
is already complete.
Because if I have another function to transfer the output file somewhere, the transferred file is still incomplete by the time transfer is executed. -
aac encoding with ffmpeg result in super short file
5 janvier 2017, par MockarutanSo I’m having problem with AAC encoding. I’m trying to encode some synthetic sound waves, but it does not work as expected. The file I get gives just a super short sound when played in VLC. When I play is in ffplay is plays like I expect, but it says "duration : 00:00:00.05" which I suppose says 5 ms. But I encode a lot more than that, and it played more. So VLC plays a super short sound, ffplay plays a longer file (the expected length), but displays it with super short duration, what’s going on ?
Source : http://pastebin.com/M5MKkEL3
One of the things that looks wrong to me is this :
If you look for the variable "audio_time", if you breakpoint it and read it every encode frame, you will get this :..
Encode frame 8 : 0.00010416666666666666
Encode frame 9 : 0.00012500000000000000
(and so on)The diff is : 0.00002085, which is a 1/1000 of a the diff I expected from 47 samples frames per second, which is what the encoder wants with 48k sample rate (48k / 1024 = 47).
So why do I get a thousand of the expected data encoded ?
Feel free to point anything suspicious out !
Thanks in advance !