
Recherche avancée
Médias (1)
-
Video d’abeille en portrait
14 mai 2011, par
Mis à jour : Février 2012
Langue : français
Type : Video
Autres articles (77)
-
Websites made with MediaSPIP
2 mai 2011, parThis page lists some websites based on MediaSPIP.
-
Creating farms of unique websites
13 avril 2011, parMediaSPIP platforms can be installed as a farm, with a single "core" hosted on a dedicated server and used by multiple websites.
This allows (among other things) : implementation costs to be shared between several different projects / individuals rapid deployment of multiple unique sites creation of groups of like-minded sites, making it possible to browse media in a more controlled and selective environment than the major "open" (...) -
Personnaliser les catégories
21 juin 2013, parFormulaire de création d’une catégorie
Pour ceux qui connaissent bien SPIP, une catégorie peut être assimilée à une rubrique.
Dans le cas d’un document de type catégorie, les champs proposés par défaut sont : Texte
On peut modifier ce formulaire dans la partie :
Administration > Configuration des masques de formulaire.
Dans le cas d’un document de type média, les champs non affichés par défaut sont : Descriptif rapide
Par ailleurs, c’est dans cette partie configuration qu’on peut indiquer le (...)
Sur d’autres sites (12582)
-
ffmpeg mkv to mp4 container not changed
26 août 2020, par Rioconverting from mkv to mp4 is not working for me ffmpeg is running fine but the container is still mkv this is cmd i am running


for %%i in (*.mkv) do ffmpeg -i "%%i" -c copy -c:a aac -b:a 320k -movflags +faststart "%%i.mp4"



output after ffmpeg is done


General
Complete name : C:\laragon\www\run\730428.mp4
Format : Matroska
Format version : Version 4
Overall bit rate mode : Variable
Encoded date : UTC 2020-08-21 07:01:37
Writing application : mkvmerge v48.0.0 ('Fortress Around Your Heart') 64-bit
Writing library : libebml v1.4.0 + libmatroska v1.6.0
FileExtension_Invalid : mkv mk3d mka mks



-
Is ffmpeg broken for h.264 RTP Output ?
13 mars 2023, par GroovyDotComI used wireshark to capture the RTP stream sent with :


ffmpeg -f lavfi -i "testsrc=duration=5:size=cif:rate=25" -pix_fmt yuv420p -g 25 -bf 2 -an -c:v libx264 -f rtp rtp://127.0.0.1:1234 > play.sdp


ffmpeg -version
ffmpeg version git-2020-03-15-c467328 Copyright (c) 2000-2020 the FFmpeg developers


As can be seen in bold, RTP timestamps go forward and backward. I expect them to be the same for every packet in the frame and then only go forward by 40ms (+3600 at 90khz clock) as per the H.264/RTP spec.


Also, according to that spec, the last packet in a frame should have its marker-bit set but here almost all the packets have this bit set.


Am I doing something wrong ? Not understanding something ? Or is ffmpeg support for writing H.264 RTP simply broken ?


SSRC=0xA49C3DC9, Seq=3595, Time=3153114809

SSRC=0xA49C3DC9, Seq=3596, Time=3153114809

SSRC=0xA49C3DC9, Seq=3597, Time=3153114809

SSRC=0xA49C3DC9, Seq=3598, Time=3153114809, Mark

SSRC=0xA49C3DC9, Seq=3599, Time=3153125609, Mark

SSRC=0xA49C3DC9, Seq=3600, Time=3153118409, Mark

SSRC=0xA49C3DC9, Seq=3601, Time=3153122009, Mark

SSRC=0xA49C3DC9, Seq=3602, Time=3153136409, Mark

SSRC=0xA49C3DC9, Seq=3603, Time=3153129209, Mark

SSRC=0xA49C3DC9, Seq=3604, Time=3153132809, Mark

SSRC=0xA49C3DC9, Seq=3605, Time=3153147209, Mark

SSRC=0xA49C3DC9, Seq=3606, Time=3153140009, Mark

SSRC=0xA49C3DC9, Seq=3607, Time=3153143609, Mark

SSRC=0xA49C3DC9, Seq=3608, Time=3153158009, Mark

SSRC=0xA49C3DC9, Seq=3609, Time=3153150809, Mark

SSRC=0xA49C3DC9, Seq=3610, Time=3153154409, Mark

SSRC=0xA49C3DC9, Seq=3611, Time=3153168809, Mark

SSRC=0xA49C3DC9, Seq=3612, Time=3153161609, Mark

SSRC=0xA49C3DC9, Seq=3613, Time=3153165209, Mark

SSRC=0xA49C3DC9, Seq=3614, Time=3153179609, Mark

SSRC=0xA49C3DC9, Seq=3615, Time=3153172409, Mark

SSRC=0xA49C3DC9, Seq=3616, Time=3153176009, Mark

SSRC=0xA49C3DC9, Seq=3617, Time=3153190409, Mark

SSRC=0xA49C3DC9, Seq=3618, Time=3153183209, Mark

The RTP specification, defined in RFC 3550, states that "the timestamp reflects the sampling instant of the first octet in the RTP data packet. The sampling instant must be derived from a clock that increments monotonically and linearly in time to allow synchronization and jitter calculations" (Section 5.1).


-
Why do you need analytics for your WordPress ?
7 avril 2020, par Joselyn Khor — Analytics Tips, Plugins