Recherche avancée

Sur d’autres sites (5787)

• DCT coefficients and MV extraction in ffmpeg Mpeg-4 encoding

  30 juin 2017, par Giacomo Calvigioni

  I’m using ffmpeg and libx264 to encode a video and I want to extract the DCT coefficients and motion vector of each frame during the encoding process.

  What is the best way to do this ?

  I read in the ffmpeg manual that is possible to use the debug mode with some flags to extract these values. I tried ffmpeg -debug dct_coeff to output the dct coefficients but this option doesn’t work for me ; is it deprecated or related to a specific ffmpeg version ?

  Another option would be to modify and recompile ffmpeg source code but I don’t know in which part of the code DCT and MV are calculated.

  Any help with the debug mode or code modification suggestions would be appreciated.

• How to send libmmpeg AVPacket through WebRTC (using libdatachannel)

  29 mars 2022, par mike

  I'm encoding a video frame with the ffmpeg libraries, generating an AVPacket with compressed data.

  


  Thanks to some recent advice here on S/O, I am trying to send that frame over a network using the WebRTC library libdatachannel, specifically by adapting the example here :

  


  https://github.com/paullouisageneau/libdatachannel/tree/master/examples/streamer

  


  I am seeing problems inside h264rtppacketizer.cpp (part of the library, not the example) which are almost certainly to do with how I'm providing the sample data.
(I don't think that this is anything to do with libdatachannel specifically, it will be an issue with what I'm sending)

  


  The example code reads each encoded frame from a file, and populates a sample by setting the content of the file to the contents of the file :

  


  sample = *reinterpret_cast *>(&fileContents);

  


  sample is just a std::vector<byte>;</byte>

  


  I have naively copied the contents of an AVPacket->data pointer into the sample vector :

  


  sample.resize(pkt->size);
memcpy(sample.data(), pkt->data, pkt->size * sizeof(std::byte));    


  


  but the packetizer is falling over when trying to get length values out of that data.
Specifically, in the following code, the first iteration gets a length of 1, but the second, looking up index 5, gives 1119887324. This is way too big for my data, which is only 3526 bytes (the whole frame is a single colour so likely to be small once encoded) :

  


  while (index &lt; message->size()) {&#xA;assert(index &#x2B; 4 &lt; message->size());&#xA;auto lengthPtr = (uint32_t *)(message->data() &#x2B; index);&#xA;uint32_t length = ntohl(*lengthPtr);&#xA;auto naluStartIndex = index &#x2B; 4;&#xA;auto naluEndIndex = naluStartIndex &#x2B; length;&#xA;assert(naluEndIndex &lt;= message->size());    &#xA;        &#xA;auto begin = message->begin() &#x2B; naluStartIndex;&#xA;auto end = message->begin() &#x2B; naluEndIndex;&#xA;nalus->push_back(std::make_shared<nalunit>(begin, end));&#xA;index = naluEndIndex;&#xA;}&#xA;</nalunit>

  


  Here is a dump of

  


  uint32_t length = ntohl(*lengthPtr);


  


  for the first few elements of the message (*lengthPtr in parentheses) :

  


  [2022-03-29 15:12:01.182] [info] index 0: 1  (16777216)
[2022-03-29 15:12:01.183] [info] index 1: 359  (1728118784)
[2022-03-29 15:12:01.184] [info] index 2: 91970  (1114046720)
[2022-03-29 15:12:01.186] [info] index 3: 23544512  (3225577217)
[2022-03-29 15:12:01.186] [info] index 4: 1732427807  (532693607)
[2022-03-29 15:12:01.187] [info] index 5: 1119887324  (3693068354)
[2022-03-29 15:12:01.188] [info] index 6: 3223313413  (98312128)
[2022-03-29 15:12:01.188] [info] index 7: 534512896  (384031)
[2022-03-29 15:12:01.188] [info] index 8: 3691315291  (1526728156)
[2022-03-29 15:12:01.189] [info] index 9: 83909537  (2707095557)
[2022-03-29 15:12:01.189] [info] index 10: 6004992  (10574592)
[2022-03-29 15:12:01.190] [info] index 11: 1537277952  (41307)
[2022-03-29 15:12:01.190] [info] index 12: 2701131779  (50331809)
[2022-03-29 15:12:01.192] [info] index 13: 768  (196608)


  


  (I know I should post a complete sample, I am working on it)

  


  


  • I am fairly sure I am just missing something basic. E.g. am I supposed to do something with the AVPacket side_data, does AVPacket have or miss some header info ?

    


  


  • If I just fwrite the pkt->data for a single frame to disk, I can read the codec information with ffprobe :

    


  


  


  Input #0, h264, from 'encodedOut.h264':
Duration: N/A, bitrate: N/A
Stream #0:0: Video: h264 (Constrained Baseline), yuv420p(progressive), 1280x720, 30 tbr, 1200k tbn


  


  

  • whereas the same for the example input files (again a single frame) gives the following :

  


  


  [h264 @ 000001c88d1135c0] Format h264 detected only with low score of 1, misdetection possible!
[h264 @ 000001c88f337400] missing picture in access unit with size 85306
[extract_extradata @ 000001c88d11ee40] No start code is found.
sample-0.h264: Invalid data found when processing input


  


• Air and ffmpeg with NativeProcess

  16 mai 2013, par Pierre

  I´trying to create an Air application that can generate a movie file via ffmpeg. I´m using NativeProcess and it all works fine if (and only if) I add an ffmpeg that is compiled on my computer to the native installer. Whenever I try to use a precompiled build the process fails like this :

  NSTask : Task create for path 'mypathto/ffmpeg' failed : 22, "Invalid argument". Terminating temporary process.

  If I was the only user I wouldn´t have a problem. But I want other people to use my application so I really need to bundle the ffmpeg with my native installer.

  I have tried several different builds with the same result. Here is the argument string before I put in the process arguments Vector : "-y -f image2 -i seq%04d.png movie.mpg".

  Please help !