Rémi Bernon (@rbernon) commented about dlls/mf/tests/mf.c:
HRESULT (WINAPI *pMFCreateDXGIDeviceManager)(UINT *token, IMFDXGIDeviceManager **manager); BOOL has_video_processor;
+const static BYTE test_h264_sequence_header[] = +{
- 0x00, 0x00, 0x01, 0x67, 0x64, 0x00, 0x14, 0xac, 0xd9, 0x46, 0x36, 0xc0,
- 0x5a, 0x83, 0x03, 0x03, 0x52, 0x80, 0x00, 0x00, 0x03, 0x00, 0x80, 0x00,
- 0x00, 0x03, 0x01, 0x47, 0x8a, 0x14, 0xcb, 0x00, 0x00, 0x01, 0x68, 0xeb,
- 0xec, 0xb2, 0x2c,
+};
+const static BYTE test_aac_codec_data[] = +{
- 0x00, 0x00, 0x29, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,
- 0x12, 0x08,
+};
Fwiw I think it's important to have an easy way to reconstruct these.
For the AAC codec data, and this was the reason I added the AAC encoder tests, you can get it from the enumerated encoder media types. Maybe it should be shared between `transform.c` and `mf.c`, in `mf_test.h`?
For the H264 sequence header, I can't find where it is coming from. Is there a similar way to get it, which does not involve manual extraction from an H264 file? We can maybe have some basic H264 encoder tests if that would allow us to get the magic sequence out of it.