
Recherche avancée
Médias (1)
-
Bug de détection d’ogg
22 mars 2013, par
Mis à jour : Avril 2013
Langue : français
Type : Video
Autres articles (66)
-
MediaSPIP version 0.1 Beta
16 avril 2011, parMediaSPIP 0.1 beta est la première version de MediaSPIP décrétée comme "utilisable".
Le fichier zip ici présent contient uniquement les sources de MediaSPIP en version standalone.
Pour avoir une installation fonctionnelle, il est nécessaire d’installer manuellement l’ensemble des dépendances logicielles sur le serveur.
Si vous souhaitez utiliser cette archive pour une installation en mode ferme, il vous faudra également procéder à d’autres modifications (...) -
MediaSPIP 0.1 Beta version
25 avril 2011, parMediaSPIP 0.1 beta is the first version of MediaSPIP proclaimed as "usable".
The zip file provided here only contains the sources of MediaSPIP in its standalone version.
To get a working installation, you must manually install all-software dependencies on the server.
If you want to use this archive for an installation in "farm mode", you will also need to proceed to other manual (...) -
Amélioration de la version de base
13 septembre 2013Jolie sélection multiple
Le plugin Chosen permet d’améliorer l’ergonomie des champs de sélection multiple. Voir les deux images suivantes pour comparer.
Il suffit pour cela d’activer le plugin Chosen (Configuration générale du site > Gestion des plugins), puis de configurer le plugin (Les squelettes > Chosen) en activant l’utilisation de Chosen dans le site public et en spécifiant les éléments de formulaires à améliorer, par exemple select[multiple] pour les listes à sélection multiple (...)
Sur d’autres sites (13474)
-
ffmpeg errors in the daemon
3 octobre 2020, par smoto_sheiI created a shell script to compress a video using ffmpeg(4.3.1).


ffmpeg -y -i \
 '/var/www/System/Backend/Outputs/TempSaveMovie/200703_4_short_5fr_p2(100_20)_r(50_20).mp4' \
 -vcodec h264 -an \
 '/var/www/System/Backend/Outputs/MovieOutputs/200703_4_short_5fr_p2(100_20)_r(50_20).mp4'




If you run this code from the console, it will run without problems.
In fact, we're using the python
subscript.call()
to execute it. It works fine too.

cmd = 'sh /var/www/System/Backend/cv2toffmpeg.sh'
subprocess.call(cmd, shell=True)



Secondly, if I run it from a daemonized python program, I'll get an error. I get the following error.
You'll get an error like this


Input #0, mov,mp4,m4a,3gp,3g2,mj2, from './Outputs/TempSaveMovie/200703_4_short_5fr_p2(100_20)_r(50_20).mp4':
 Metadata:
 major_brand : isom
 minor_version : 512
 compatible_brands: isomiso2mp41
 encoder : Lavf58.35.100
 Duration: 00:00:06.15, start: 0.000000, bitrate: 10246 kb/s
 Stream #0:0(und): Video: mpeg4 (Simple Profile) (mp4v / 0x7634706D), yuv420p, 1280x720 [SAR 1:1 DAR 16:9], 10244 kb/s, 13 fps, 13 tbr, 13312 tbn, 13 tbc (default)
 Metadata:
 handler_name : VideoHandler
Stream mapping:
 Stream #0:0 -> #0:0 (mpeg4 (native) -> h264 (h264_nvenc))
Press [q] to stop, [?] for help
[mpeg4 @ 0x55cec17c5480] header damaged
[mpeg4 @ 0x55cec17c6840] header damaged
[mpeg4 @ 0x55cec1855f80] header damaged
[mpeg4 @ 0x55cec1866e00] header damaged
Output #0, mp4, to './Outputs/MovieOutputs/200703_4_short_5fr_p2(100_20)_r(50_20).mp4':
 Metadata:
 major_brand : isom
 minor_version : 512
 compatible_brands: isomiso2mp41
 encoder : Lavf58.45.100
 Stream #0:0(und): Video: h264 (h264_nvenc) (Main) (avc1 / 0x31637661), yuv420p, 1280x720 [SAR 1:1 DAR 16:9], q=-1--1, 2000 kb/s, 13 fps, 13312 tbn, 13 tbc (default)
 Metadata:
 handler_name : VideoHandler
 encoder : Lavc58.91.100 h264_nvenc
 Side data:
 cpb: bitrate max/min/avg: 0/0/2000000 buffer size: 4000000 vbv_delay: N/A
Error while decoding stream #0:0: Invalid data found when processing input
[mpeg4 @ 0x55cec17c8780] header damaged
Error while decoding stream #0:0: Invalid data found when processing input
[mpeg4 @ 0x55cec17c5480] header damaged



I think the problem is when you run it from a daemonized process. There seems to be a similar problem in the past.
Ffmpeg does not properly convert videos when run as daemon
I would like to ask for your help to solve this problem. Thank you for your help from Japan.


-
UnsupportedAudioFileException in LIUM Speaker Diarization after re-sampling
14 septembre 2016, par RAVI D PARIKHI am trying to configure LIUM tool for speaker diarization. This question is a follow up of UnsupportedAudioFileException in LIUM Speaker Diarization
I have tried re sampling the file using sox and ffmpeg
I am new to any sorts of programming and i have followed all steps described in LIUM quick start guide and the above link. I still get the same error. I think my input file has issues related to header as mentioned by Nikolay Shmyrev in the above link however i have no clue on how to solve it.
My code is as below :
java –jar C:\Users\Ravi\Desktop\LIUM_SpkDiarization-8.4.1.jar \ --fInputMask= C:\Users\Ravi\Desktop\converted_f2.wav--sOutputMask= C:\Users\Ravi\Desktop\converted_converted_2.seg -–help --doCEClustering
Error :
10:52.037 SEVERE AudioFeatureSetFa FileNotFoundException
java.io.FileNotFoundException:
at java.io.FileInputStream.open0(Native Method)
at java.io.FileInputStream.open(Unknown Source)
at java.io.FileInputStream.<init>(Unknown Source)
at com.sun.media.codec.audio.mp3.JS_MP3FileReader.getAudioFileFormat(JS_MP3FileReader.java:82)
at javax.sound.sampled.AudioSystem.getAudioFileFormat(Unknown Source)
at fr.lium.spkDiarization.libFeature.AudioFeatureSetFactory.getAudio(AudioFeatureSetFactory.java:162)
at fr.lium.spkDiarization.libFeature.AudioFeatureSetFactory.MakeFeature(AudioFeatureSetFactory.java:207)
</init>The input file is at https://drive.google.com/file/d/0B7Fqe9EX5JbgT09BcXpSREd4em8/view?usp=sharing
Input File Name:converted_f2.wav
I have put the command and the full output of the prompt in a word document at
https://drive.google.com/file/d/0B7Fqe9EX5JbgUUl6THNCZFgxRnM/view?usp=sharing
The inpiut file has correct sampling rate and other parameters and thus i am not able to understand the cause of the error.
Thanks a lot for the helpRegards,
Ravi -
doc/ffmpeg : improve -disposition, -stats, and -progress documentation
17 octobre 2024, par Soma Luczdoc/ffmpeg : improve -disposition, -stats, and -progress documentation
disposition :
Clarify the meaning of the default value, and how the '+' and '-'
prefixes work. Add more examples.stats :
Clarify that it appears as an "info"-level log.progress :
Add info about the "progress" key's value being "continue" or "end".
Add an example of logging to stdout.Signed-off-by : Soma Lucz <luczsoma@gmail.com>
Signed-off-by : Anton Khirnov <anton@khirnov.net>