
Recherche avancée
Médias (1)
-
The pirate bay depuis la Belgique
1er avril 2013, par
Mis à jour : Avril 2013
Langue : français
Type : Image
Autres articles (112)
-
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 (...) -
HTML5 audio and video support
13 avril 2011, parMediaSPIP uses HTML5 video and audio tags to play multimedia files, taking advantage of the latest W3C innovations supported by modern browsers.
The MediaSPIP player used has been created specifically for MediaSPIP and can be easily adapted to fit in with a specific theme.
For older browsers the Flowplayer flash fallback is used.
MediaSPIP allows for media playback on major mobile platforms with the above (...) -
ANNEXE : Les plugins utilisés spécifiquement pour la ferme
5 mars 2010, parLe site central/maître de la ferme a besoin d’utiliser plusieurs plugins supplémentaires vis à vis des canaux pour son bon fonctionnement. le plugin Gestion de la mutualisation ; le plugin inscription3 pour gérer les inscriptions et les demandes de création d’instance de mutualisation dès l’inscription des utilisateurs ; le plugin verifier qui fournit une API de vérification des champs (utilisé par inscription3) ; le plugin champs extras v2 nécessité par inscription3 (...)
Sur d’autres sites (12356)
-
avformat/mxfenc : fix stored/sampled/displayed width/height
14 janvier 2023, par Jerome Martinezavformat/mxfenc : fix stored/sampled/displayed width/height
According to MXF specs the Stored Rectangle corresponds to the data which is
passed to the compressor and received from the decompressor, so they should
contain the width / height extended to the macroblock boundary.In practice however width and height values rounded to the upper 16 multiples
are only seen when muxing MPEG formats. Therefore this patch changes stored
width and height values to unrounded for all non-MPEG formats, even macroblock
based ones.For DNXHD the specs (ST 2019-4) explicitly indicates to use 1080 for 1088p.
For ProRes the specs (RDD 44) only refer to to ST 377-1 without precision but
no known commercial implementations are using rounded values.
DV is not using 16x16 macroblocks, so 16 rounding makes no sense.The patch also fixes Sampled Width / Display Width to use unrounded values.
Signed-off-by : Marton Balint <cus@passwd.hu>
-
AAC bitstream not in ADTS format and extradata missing in MPEG-TS output
6 décembre 2022, par AntonioI am using ffmpeg 5.1.2 stable version, and fdk-aac v0.1.6 .
I am trying to encapsulate a LATM/LOAS in an MPEGTS DVB standard output, using this cmdline :


ffmpeg -i <source> -af volume=volume=1dB:precision=fixed -c:a libfdk_aac -latm 1 -b:a 128k -c:v libx264 -pix_fmt yuv420p -preset veryfast -x264-params "nal-hrd=cbr:keyint=50:min-keyint=50" -b:v 3200k -minrate 3200k -maxrate 3200k -bufsize 6400k -flush_packets 0 -f mpegts -mpegts_original_network_id 1 -mpegts_transport_stream_id 1 -mpegts_service_id 1 -mpegts_service_type '0x19' -mpegts_flags 'latm' -mpegts_flags 'system_b' -mpegts_flags 'nit' -muxrate 4000000 -metadata service_provider='MyRTV' -metadata service_name='My TV' -tables_version 0 'udp://238.0.0.1:6000?ttl=1&pkt_size=1316&bitrate=4000000'
</source>


It logs and error :


[mpegts @ 0x556dc3e6a840] AAC bitstream not in ADTS format and extradata missing



What am I missing ?
Thanks in advance and best regards


I am trying to encapsulate a LATM/LOAS in an MPEGTS DVB standard output, so expect to have a LOAS/LATM output, but I obtain an ADTS output.


-
fftools/ffmpeg : store forced keyframe pts in AV_TIME_BASE_Q
17 novembre 2022, par Anton Khirnovfftools/ffmpeg : store forced keyframe pts in AV_TIME_BASE_Q
Rather than the encoder timebase. Since the times are parsed as
microseconds, this will not reduce precision, except possibly when
chapter times are used and the chapter timebase happens to be better
aligned with the encoder timebase, which is unlikely.This will allow parsing the keyframe times earlier (before encoder
timebase is known) in future commits.