
Recherche avancée
Autres articles (81)
-
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 (...) -
Les sons
15 mai 2013, par -
Soumettre bugs et patchs
10 avril 2011Un logiciel n’est malheureusement jamais parfait...
Si vous pensez avoir mis la main sur un bug, reportez le dans notre système de tickets en prenant bien soin de nous remonter certaines informations pertinentes : le type de navigateur et sa version exacte avec lequel vous avez l’anomalie ; une explication la plus précise possible du problème rencontré ; si possibles les étapes pour reproduire le problème ; un lien vers le site / la page en question ;
Si vous pensez avoir résolu vous même le bug (...)
Sur d’autres sites (5905)
-
avutil/mathematics : Do not treat INT64_MIN as positive in av_rescale_rnd
1er décembre 2015, par Michael Niedermayeravutil/mathematics : Do not treat INT64_MIN as positive in av_rescale_rnd
The code expects actual positive numbers and gives completely wrong
results if INT64_MIN is treated as positive
Instead clip it into the valid range that is add 1 and treat it as
negativeSigned-off-by : Michael Niedermayer <michael@niedermayer.cc>
-
Quickly check the integrity of video files inside a directory with ffmpeg
4 février 2017, par DMTI’m desperately searching for a convenient method to check the integrity of .mp4 files inside a specific directory with folders in it. Both the names of the .mp4 files and the folders contain spaces, special characters and numbers.
I’ve already found a proper ffmpeg command to quickly identify a damaged .mp4 file, taken from here :
ffmpeg -v error -i filename.mp4 -map 0:1 -f null - 2>error.log
If the created error.log contains some entries, then the file is obviously corrupted. The opposite would be an empty error.log.
The next step would be to apply this command to every .mp4 file within the folder and its subfolders. Some guides, like here and here, do describe how to apply a ffmpeg command recursively, but my coding skills are limited, so therefore I can’t find a way to combine these commands to get the following :
A way to test all .mp4 files inside a folder (recursively) with the aforementioned ffmpeg command, that should create .log files, only if a video file does contain errors (read has some content) and it should inherit the name of the broken file, to know which file is corrupted.
Using Ubuntu Gnome 15.10.
-
12 ways Matomo Analytics helps you to protect your visitor’s privacy