Recherche avancée

Sur d’autres sites (5743)

• building static ffmpeg library for Android under windows 7

  29 mai 2013, par Zhenya

  I know that this has been asked several times, but I've never found any clear step by step and conclusive answer.

  How can I compile ffmpeg for Android, under windows 7 ?
  What are the steps ? Is there a project or wiki on the internet where to find this ?

  All I've found are steps to run under Ubuntu, or purely linux, but nothing to generate a static library for android, to be build under windows 7.

  Thanks

• How would I assign multiple MMAP's from single file descriptor ?

  9 juin 2011, par Alex Stevens

  So, for my final year project, I'm using Video4Linux2 to pull YUV420 images from a camera, parse them through to x264 (which uses these images natively), and then send the encoded stream via Live555 to an RTP/RTCP compliant video player on a client over a wireless network. All of this I'm trying to do in real-time, so there'll be a control algorithm, but that's not the scope of this question. All of this - except Live555 - is being written in C. Currently, I'm near the end of encoding the video, but want to improve performance.

  To say the least, I've hit a snag... I'm trying to avoid User Space Pointers for V4L2 and use mmap(). I'm encoding video, but since it's YUV420, I've been malloc'ing new memory to hold the Y', U and V planes in three different variables for x264 to read upon. I would like to keep these variables as pointers to an mmap'ed piece of memory.

  However, the V4L2 device has one single file descriptor for the buffered stream, and I need to split the stream into three mmap'ed variables adhering to the YUV420 standard, like so...

  buffers[n_buffers].y_plane = mmap(NULL, (2 * width * height) / 3,
  
                                      PROT_READ | PROT_WRITE, MAP_SHARED,
  
                                      fd, buf.m.offset);
  
  buffers[n_buffers].u_plane = mmap(NULL, width * height / 6,
  
                                      PROT_READ | PROT_WRITE, MAP_SHARED,
  
                                      fd, buf.m.offset +
  
                                      ((2 * width * height) / 3 + 1) /
  
                                      sysconf(_SC_PAGE_SIZE));
  
  buffers[n_buffers].v_plane = mmap(NULL, width * height / 6,
  
                                      PROT_READ | PROT_WRITE, MAP_SHARED,
  
                                      fd, buf.m.offset +
  
                                      ((2 * width * height) / 3 + 
  
                                      width * height / 6 + 1) / 
  
                                      sysconf(_SC_PAGE_SIZE));

  Where "width" and "height" is the resolution of the video (eg. 640x480).

  From what I understand... MMAP seeks through a file, kind of like this (pseudoish-code) :

  fd = v4l2_open(...);
  
  lseek(fd, buf.m.offset + (2 * width * height) / 3);
  
  read(fd, buffers[n_buffers].u_plane, width * height / 6);

  My code is located in a Launchpad Repo here (for more background) :
  http://bazaar.launchpad.net/ alex-stevens/+junk/spyPanda/files (Revision 11)

  And the YUV420 format can be seen clearly from this Wiki illustration : http://en.wikipedia.org/wiki/File:Yuv420.svg (I essentially want to split up the Y, U, and V bytes into each mmap'ed memory)

  Anyone care to explain a way to mmap three variables to memory from the one file descriptor, or why I went wrong ? Or even hint at a better idea to parse the YUV420 buffer to x264 ? :P

  Cheers ! ^^

• The Fastest Way To Learn Assembly Language

  4 septembre 2011, par Multimedia Mike — Programming

  I saw an old StackOverflow thread linked from Hacker News asking how to whether it’s worthwhile to learn assembly language and how to go about doing so. I’d like to take a stab at the last question.

  The fastest way to learn an assembly language is to reverse engineer something. Seriously, start with something that you know (like a C program that you wrote yourself) and take it apart. The good news is that assembly language is very simple and you will get a lot of practice in a short amount of time with RE.

  So here’s how you do it :

  • Take a simple program in C and build it with your tool chain, whether GNU gcc on Linux, Xcode on Mac, or MSVC on Windows. Also, make sure to turn on debugging symbols during compilation (this will help annotate the disassembly).
  • On Linux, use objdump : objdump -d program_binary
  • On Mac, use otool : otool -tV program_binary
  • On Windows : I admit, I’m a bit fuzzy on this one– I’m quite certain there’s a standard MSVC tool that prints the assembly listing.

  Anyway, look at the disassembled code and find the main() function. Work from there. Whatever the first instruction is, look it up on Google. You’ll likely find various CPU manuals that will explain the simple operation of the instruction. Look up the next unfamiliar instruction, then the next. Trust me, you’ll become an ASM expert in no time.

  Good luck !