
Recherche avancée
Autres articles (27)
-
MediaSPIP v0.2
21 juin 2013, parMediaSPIP 0.2 est la première version de MediaSPIP stable.
Sa date de sortie officielle est le 21 juin 2013 et est annoncée ici.
Le fichier zip ici présent contient uniquement les sources de MediaSPIP en version standalone.
Comme pour la version précédente, 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 (...) -
Mise à disposition des fichiers
14 avril 2011, parPar défaut, lors de son initialisation, MediaSPIP ne permet pas aux visiteurs de télécharger les fichiers qu’ils soient originaux ou le résultat de leur transformation ou encodage. Il permet uniquement de les visualiser.
Cependant, il est possible et facile d’autoriser les visiteurs à avoir accès à ces documents et ce sous différentes formes.
Tout cela se passe dans la page de configuration du squelette. Il vous faut aller dans l’espace d’administration du canal, et choisir dans la navigation (...) -
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 (...)
Sur d’autres sites (4479)
-
avformat/mov : discard data streams with all zero sample_delta
6 juillet 2022, par Zhao Zhiliavformat/mov : discard data streams with all zero sample_delta
Streams with all zero sample_delta in 'stts' have all zero dts.
They have higher chance be chose by mov_find_next_sample(), which
leads to seek again and again.For example, GoPro created a 'GoPro SOS' stream :
Stream #0:4[0x5](eng) : Data : none (fdsc / 0x63736466), 13 kb/s (default)
Metadata :
creation_time : 2022-06-21T08:49:19.000000Z
handler_name : GoPro SOSWith 'ffprobe -show_frames http://example.com/gopro.mp4', ffprobe
blocks until all samples in 'GoPro SOS' stream are consumed first.Signed-off-by : Zhao Zhili <zhilizhao@tencent.com>
-
PyAV/ffmpeg : How to resolve 'Reinit context to WxH ... deprecated pixel format'
26 mai 2023, par hi im BaconI am using the
pyav
library to read and process video data and as I am reading through the videos I am getting lots (and lots) of the following output.

I am creating the videos by segmenting either a much larger source file or RTSP/HTTP IP camera.


I would love to understand what this output actually means, and what I can do to prevent its output


ffmpeg creating videos :


ffmpeg -y -i https://manifest.googlevideo.com/api/... -pix_fmt yuvj422p -c:v libx264 -an -vf scale='min(1280,iw)':'min(720,ih)':force_original_aspect_ratio=decrease -r 12 -vsync cfr -x264opts keyint=12:min-keyint=12 -f segment -segment_format matroska -segment_time 5 -initial_offset 1656497474.686672 -strftime 1 /tmp/tmp87cc1n2o/%Y-%m-%dT%H%M%S.mkv -loglevel error



python :


container = av.open(io.BytesIO(...))
for frame in container.decode(video=0):
 ...



2022-06-30 14:45:00,964 DEBUG:****:Creating <***.core.generators.av.AVGenerator object at 0x7f13340abd50> with target path: <_io.BytesIO object at 0x7f13341c93b0>
2022-06-30 14:45:00,966 DEBUG:libav.h264:Reinit context to 1280x720, pix_fmt: yuv420p
2022-06-30 14:45:00,966 DEBUG:libav.h264:Reinit context to 1280x720, pix_fmt: yuvj422p
2022-06-30 14:45:00,984 DEBUG:libav.h264:Reinit context to 1280x720, pix_fmt: yuv420p
2022-06-30 14:45:01,045 DEBUG:libav.h264:Reinit context to 1280x720, pix_fmt: yuv420p
2022-06-30 14:45:01,046 DEBUG:libav.h264:Reinit context to 1280x720, pix_fmt: yuvj422p
deprecated pixel format used, make sure you did set range correctly
deprecated pixel format used, make sure you did set range correctly
 (repeated 9 more times)
2022-06-30 14:45:01,194 DEBUG:libav.h264:Reinit context to 1280x720, pix_fmt: yuv420p
deprecated pixel format used, make sure you did set range correctly
deprecated pixel format used, make sure you did set range correctly
2022-06-30 14:45:01,215 DEBUG:libav.h264:Reinit context to 1280x720, pix_fmt: yuv420p
deprecated pixel format used, make sure you did set range correctly
deprecated pixel format used, make sure you did set range correctly
 (repeated 17 more times)
2022-06-30 14:45:01,384 DEBUG:libav.h264:Reinit context to 1280x720, pix_fmt: yuv420p
deprecated pixel format used, make sure you did set range correctly
deprecated pixel format used, make sure you did set range correctly
 (repeated 3 more times)
2022-06-30 14:45:01,398 DEBUG:libav.h264:Reinit context to 1280x720, pix_fmt: yuv420p
deprecated pixel format used, make sure you did set range correctly
deprecated pixel format used, make sure you did set range correctly
 (repeated 22 more times)
2022-06-30 14:45:01,550 DEBUG:libav.h264:Reinit context to 1280x720, pix_fmt: yuv420p
deprecated pixel format used, make sure you did set range correctly
deprecated pixel format used, make sure you did set range correctly
 (repeated 2 more times)
2022-06-30 14:45:01,592 DEBUG:libav.h264:Reinit context to 1280x720, pix_fmt: yuv420p



-
Why A .FLAC File Converted by FFMPEG Cause File Explorer Unresponse on Windows 10 [closed]
20 juillet 2022, par Alex KingMy File Explorer Always showing "Working on it."
I've tried many resolutions.
First,I disconnect my NAS drive. seems fine.
I test many times on diffirient windows 10/11 versions.
I thought it was SMB problem on windows. But i was wrong.


Today I'm using FFMPEG convert .wav to .flac.


.\ffmpeg.exe -i $Source -c:a flac $Dest 



Just simple like this. Blow my computer up.


Even worse, explorer.exe crash after I'm trying to open FF output folder.


It's not the poblem from "Quick access" or "Search Index".


I'm now 100% percent confirm the flac files that ffmpeg made will cause file explorer crash.


I can't solve it without knowing the reason.


Might related to audio file tag vorbis ?


This is my FFMPEG info


ffmpeg version n5.0.1-4-ga5ebb3d25e-20220428 Copyright (c) 2000-2022 the FFmpeg developers

built with gcc 11.2.0 (crosstool-NG 1.24.0.533_681aaef)