
Recherche avancée
Médias (5)
-
ED-ME-5 1-DVD
11 octobre 2011, par
Mis à jour : Octobre 2011
Langue : English
Type : Audio
-
Revolution of Open-source and film making towards open film making
6 octobre 2011, par
Mis à jour : Juillet 2013
Langue : English
Type : Texte
-
Valkaama DVD Cover Outside
4 octobre 2011, par
Mis à jour : Octobre 2011
Langue : English
Type : Image
-
Valkaama DVD Label
4 octobre 2011, par
Mis à jour : Février 2013
Langue : English
Type : Image
-
Valkaama DVD Cover Inside
4 octobre 2011, par
Mis à jour : Octobre 2011
Langue : English
Type : Image
Autres articles (44)
-
Participer à sa traduction
10 avril 2011Vous pouvez nous aider à améliorer les locutions utilisées dans le logiciel ou à traduire celui-ci dans n’importe qu’elle nouvelle langue permettant sa diffusion à de nouvelles communautés linguistiques.
Pour ce faire, on utilise l’interface de traduction de SPIP où l’ensemble des modules de langue de MediaSPIP sont à disposition. ll vous suffit de vous inscrire sur la liste de discussion des traducteurs pour demander plus d’informations.
Actuellement MediaSPIP n’est disponible qu’en français et (...) -
Librairies et binaires spécifiques au traitement vidéo et sonore
31 janvier 2010, parLes logiciels et librairies suivantes sont utilisées par SPIPmotion d’une manière ou d’une autre.
Binaires obligatoires FFMpeg : encodeur principal, permet de transcoder presque tous les types de fichiers vidéo et sonores dans les formats lisibles sur Internet. CF ce tutoriel pour son installation ; Oggz-tools : outils d’inspection de fichiers ogg ; Mediainfo : récupération d’informations depuis la plupart des formats vidéos et sonores ;
Binaires complémentaires et facultatifs flvtool2 : (...) -
Support audio et vidéo HTML5
10 avril 2011MediaSPIP utilise les balises HTML5 video et audio pour la lecture de documents multimedia en profitant des dernières innovations du W3C supportées par les navigateurs modernes.
Pour les navigateurs plus anciens, le lecteur flash Flowplayer est utilisé.
Le lecteur HTML5 utilisé a été spécifiquement créé pour MediaSPIP : il est complètement modifiable graphiquement pour correspondre à un thème choisi.
Ces technologies permettent de distribuer vidéo et son à la fois sur des ordinateurs conventionnels (...)
Sur d’autres sites (6142)
-
Finding corrupted videos with opencv
16 septembre 2022, par tuskerI have huge video dataset (about 500000 16 frame length clips). Some of the videos produce messages like


[mpeg4 @ 0x561b46a44b80] marker does not match f_code
[mpeg4 @ 0x561b480c0740] Error at MB: 4718
[mpeg4 @ 0x561b4811b640] header damaged



I want to find which videos cause the problem.

First I tried with this https://superuser.com/questions/100288/how-can-i-check-the-integrity-of-a-video-file-avi-mpeg-mp4 solution, but I got nothing in the error files.

My second idea was to read the first image of a video and if it throws an error, save the filename to a file. However, it seems this is not an error message : although the messages appeared on console,
read
returned withsuccess=True
.

Then I tried to print the filenames to standard error (where the warning messages also go), saving it to a file and do some postprocessing to extract the videos which has problem.


import os
from tqdm import tqdm
import sys

folder = '/path/to/videos'
for f in tqdm(os.listdir(folder)):
 sys.stderr.write('BEFORE VIDCAP ' + f + '\n')
 vidcap = cv2.VideoCapture(os.path.join(folder,f))
 sys.stderr.write('BETWEEN VIDCAP AND SUCCESS' + f + '\n')

 success, image = vidcap.read()
 sys.stderr.write('AFTER SUCCESS ' + f + '\n')



However, the standard error outputs in the following order :


AFTER SUCCESS
[mpeg ...] 
[mpeg ...]
...
BEFORE VIDCAP



It doesn't make sense how can it happen in this order, some broken videos should be seen somewhere between BEFORE and AFTER. (And the ones following or preceding are not broken neither if I try to open them individually.)


My last idea was to create for every video a file, making it as the stderr and check the non-empty files. (I know it's insanely unefficient, but I didn't have any other idea.)


for f in os.listdir(folder):
 sys.stderr = open(f + '.txt', 'w')
 vidcap = cv2.VideoCapture(os.path.join(folder,f))
 success, image = vidcap.read()



This doesn't work also, all the error files are empty, although the messages still appear on standard error.



So my questions are the following :


- 

- What would be an efficient solution for this problem ?
- How is this order of outputs (first code example) possible ? There is some parallelism under the hood ?
- Where are this messages going if not to the standard error (second code example) ? If yes, why are they printed to the console instead of the specified error file ?








-
Finding corrupted videos with python
16 septembre 2022, par tuskerI have huge video dataset (about 500000 16 frame length clips). Some of the videos produce messages like


[mpeg4 @ 0x561b46a44b80] marker does not match f_code
[mpeg4 @ 0x561b480c0740] Error at MB: 4718
[mpeg4 @ 0x561b4811b640] header damaged



I want to find which videos cause the problem.

First I tried with this https://superuser.com/questions/100288/how-can-i-check-the-integrity-of-a-video-file-avi-mpeg-mp4 solution, but I got nothing in the error files.

My second idea was to read the first image of a video and if it throws an error, save the filename to a file. However, it seems this is not an error message : although the messages appeared on console,
read
returned withsuccess=True
.

Then I tried to print the filenames to standard error (where the warning messages also go), saving it to a file and do some postprocessing to extract the videos which has problem.


import os
from tqdm import tqdm
import sys

folder = '/path/to/videos'
for f in tqdm(os.listdir(folder)):
 sys.stderr.write('BEFORE VIDCAP ' + f + '\n')
 vidcap = cv2.VideoCapture(os.path.join(folder,f))
 sys.stderr.write('BETWEEN VIDCAP AND SUCCESS' + f + '\n')

 success, image = vidcap.read()
 sys.stderr.write('AFTER SUCCESS ' + f + '\n')



However, the standard error outputs in the following order :


AFTER SUCCESS
[mpeg ...] 
[mpeg ...]
...
BEFORE VIDCAP



It doesn't make sense how can it happen in this order, some broken videos should be seen somewhere between BEFORE and AFTER. (And the ones following or preceding are not broken neither if I try to open them individually.)


My last idea was to create for every video a file, making it as the stderr and check the non-empty files. (I know it's insanely inefficient, but I didn't have any other idea.)


for f in os.listdir(folder):
 sys.stderr = open(f + '.txt', 'w')
 vidcap = cv2.VideoCapture(os.path.join(folder,f))
 success, image = vidcap.read()



This doesn't work also, all the error files are empty, although the messages still appear on standard error.



So my questions are the following :


- 

- What would be an efficient solution for this problem ?
- How is this order of outputs (first code example) possible ? There is some parallelism under the hood ?
- Where are this messages going if not to the standard error (second code example) ? If yes, why are they printed to the console instead of the specified error file ?








-
FFmpeg on Qt Creator
10 novembre 2022, par c47296I have got FFmpeg compiled using MSYS2. I have a strange issue that appeared only recently.the app crashes.
This is my main file :


#include "mainwindow.h"
#include <qapplication>
#include <qdebug>

extern "C" {
#include <libavdevice></libavdevice>avdevice.h>
#include <libavformat></libavformat>avformat.h>
#include <libavutil></libavutil>avutil.h>
#include <libavcodec></libavcodec>avcodec.h>
}


int main(int argc, char *argv[])
{
 //qDebug() << av_version_info();
 // avdevice_register_all();
 QApplication a(argc, argv);
 MainWindow w;
 w.show();
 return a.exec();
}
</qdebug></qapplication>


The program runs but crashes if I call 'avdevice_register_all()' and others FFmpeg functions,but only call 'av_version_info()' is runs, not crashes.
I don't really know how to solve this ?


I have already tried to use google solving the problem,but no result.