
Recherche avancée
Médias (1)
-
Revolution of Open-source and film making towards open film making
6 octobre 2011, par
Mis à jour : Juillet 2013
Langue : English
Type : Texte
Autres articles (55)
-
Submit bugs and patches
13 avril 2011Unfortunately a software is never perfect.
If you think you have found a bug, report it using our ticket system. Please to help us to fix it by providing the following information : the browser you are using, including the exact version as precise an explanation as possible of the problem if possible, the steps taken resulting in the problem a link to the site / page in question
If you think you have solved the bug, fill in a ticket and attach to it a corrective patch.
You may also (...) -
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 (...) -
De l’upload à la vidéo finale [version standalone]
31 janvier 2010, parLe chemin d’un document audio ou vidéo dans SPIPMotion est divisé en trois étapes distinctes.
Upload et récupération d’informations de la vidéo source
Dans un premier temps, il est nécessaire de créer un article SPIP et de lui joindre le document vidéo "source".
Au moment où ce document est joint à l’article, deux actions supplémentaires au comportement normal sont exécutées : La récupération des informations techniques des flux audio et video du fichier ; La génération d’une vignette : extraction d’une (...)
Sur d’autres sites (6760)
-
HEVC : Fetching the input width and height from input bin stream
1er juillet 2022, par ZaxI have created an elementary bin stream using
HM-12.0
reference code. So the out put is an HEVC encoded bin stream (say input.bin).


I have a task which involves reading the header of this elementary stream. That is i need to fetch information such a the stream width, height etc. from the
input.bin
file.


After seeing a lots of streams, i can conclude that all these bin streams starts from the sequence :



00 00 00 01




So whenever i see this sequence in any bin stream, i can say that this stream has to be decoded by HEVC decoder.



Further if i want to fetch the width, height, fps etc. from the input.bin (like ff_raw_video_read_header function in ffmpeg), that are the steps need to be performed to fetch this information ?



I have gone through the parsing section of the HEVC draft, but its very complicated for my level in video domain. Can anyone suggest a simple way to fetch the required information from the encoded bin file ?



Any suggestions will be really helpful to me. Thanks in advance.


-
HEVC : Fetching the input width and height from input bin stream
3 septembre 2014, par ZaxI have created an elementary bin stream using
HM-12.0
reference code. So the out put is an HEVC encoded bin stream (say input.bin).I have a task which involves reading the header of this elementary stream. That is i need to fetch information such a the stream width, height etc. from the
input.bin
file.After seeing a lots of streams, i can conclude that all these bin streams starts from the sequence :
00 00 00 01
So whenever i see this sequence in any bin stream, i can say that this stream has to be decoded by HEVC decoder.
Further if i want to fetch the width, height, fps etc. from the input.bin (like ff_raw_video_read_header function in ffmpeg), that are the steps need to be performed to fetch this information ?
I have gone through the parsing section of the HEVC draft, but its very complicated for my level in video domain. Can anyone suggest a simple way to fetch the required information from the encoded bin file ?
Any suggestions will be really helpful to me. Thanks in advance.
-
avcodec/ffv1enc : mark RGB48 support as non-experimental
5 janvier 2018, par Jérôme Martinezavcodec/ffv1enc : mark RGB48 support as non-experimental
Resulting bitstream was tested with a conformance checker
using the last draft of FFV1 specifications.Signed-off-by : Michael Niedermayer <michael@niedermayer.cc>
Also the files are already in the wild, and decoder support is
thus needed. And with decoders widely supporting it, there is no
advantage in not allowing it in the encoder.
The exact bitstream format may change in future versions of the
spec, if improvments are found.