
Recherche avancée
Médias (1)
-
Richard Stallman et le logiciel libre
19 octobre 2011, par
Mis à jour : Mai 2013
Langue : français
Type : Texte
Autres articles (47)
-
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" (...) -
Contribute to a better visual interface
13 avril 2011MediaSPIP is based on a system of themes and templates. Templates define the placement of information on the page, and can be adapted to a wide range of uses. Themes define the overall graphic appearance of the site.
Anyone can submit a new graphic theme or template and make it available to the MediaSPIP community.
Sur d’autres sites (7170)
-
Revision 73756 : #LISTE au lieu de #ARRAY
20 juin 2013, par kent1@… — Log#LISTE au lieu de #ARRAY
-
DirectX12 Video Encoding : output buffer population
6 janvier 2023, par mikeI'm attempting to implement DX12 video encoding.


- 

- To date I've been using the ffmpeg library so am not very clued up on very low level data.
- I'm using the simplest possible encoding I can think of, with GOP size of 1 and H264






I am struggling with the first part of defining the output structure
D3D12_VIDEO_ENCODER_ENCODEFRAME_OUTPUT_ARGUMENTS
, namely setting up the resourcepBuffer
inD3D12_VIDEO_ENCODER_COMPRESSED_BITSTREAM
:

typedef struct D3D12_VIDEO_ENCODER_COMPRESSED_BITSTREAM {
 ID3D12Resource *pBuffer;
 UINT64 FrameStartOffset;
} D3D12_VIDEO_ENCODER_COMPRESSED_BITSTREAM;



Regards pBuffer, the docs say :




"A pointer to a ID3D12Resource containing the compressed bitstream buffer".




- 

- So I guess I create a buffer at least the size of the input frame + room for header data, and make it writeable - seems like it should be straightforward, but am I missing something ? Should it be multi-planar for example, or be some multiple of input frame size ?




Then :




"The output bitstream is expected to contain the subregion headers, but not the picture, sequence, video or other headers. The host is responsible for coding those headers and generating the complete bitstream."




- 

- what do these subregion headers look like ? I am showing my lack of encoding knowledge here in general, is there a resource somewhere explaining how to calculate them ? (or have I misread this, and this is saying the output will contain them)
- do I just write them by copying into mapped memory and setting the FrameStartOffset to point after the header data ?
- I'm currently streaming
AVPacket
s fromffmpeg
usinglibdatachannel
, how would the content of the output (without my adding extra headers) compare to anAVPacket->data
?








-
Revision 6776 : On met un h3 au lieu de h4 pour ne pas casser l’imbrication de Hx dixit ...
5 juillet 2012, par kent1 — LogOn met un h3 au lieu de h4 pour ne pas casser l’imbrication de Hx dixit opquast
Si on a des métadatas, on permet de les ouvrir dans une popin