Recherche avancée

Sur d’autres sites (6982)

• Exactly what parameters are needed by libva/VAAPI to decode an H.264 video frame ?

  12 juillet 2022, par Synthetix

  I've got a basic Linux app running on supported Intel hardware that uses Intel's libva (VAAPI) to decode H.264 frames from an MP4 file. I have the entire thing working except the part where the frame gets submitted to the GPU/decoder. What's unclear is exactly what information to submit, when, and it what order. I don't see any official documentation on this, either. Here's the point in the code I'm referring to :

  


  vaBeginPicture(...)
vaRenderPicture(...)
vaEndPicture(...)


  


  The functions vaBeginPicture and vaEndPicture are self-explanatory, but my issue is with vaRenderPicture. I would expect to need to send the SPS and PPS (out of the AVCC atom in the MP4 file), then each frame, or slice of frames to the decoder via vaRenderPicture(). But this isn't mentioned anywhere other than in code examples I've found online. From some of these examples, I've surmised the following :

  


  vaRenderPicture() // call 1/4: VAPictureParameterBufferH264: Send picture params? e.g. frame size and SPS/PPS?
vaRenderPicture() // call 2/4: VAIQMatrixBufferH264: Send inverse matrix? Where do I get this?
vaRenderPicture() // call 3/4: VASliceParameterBufferH264: Parameters of the next slice of H.264 picture data?
vaRenderPicture() // call 4/4: Slice Data? The actual compressed H.264 data from the file?


  


  I have a very rudimentary understanding of how H.264 data is arranged in an MP4. But the libva documentation, as far as I can tell, does not explain exactly what is needed and in what order to successfully decode a frame. Furthermore, the buffer structures submitted to the decoder have an extensive amount of fields, which implies I need to know a ton of information about the frames before I submit them. In other video APIs I've used, none of this is needed. Why so complex ?

  


  Any pointers to documentation on exactly what parameters, data and how to arrange it all before submitting to the VAAPI decoder would be much appreciated.

  


• opencv3.1 python VideoCapture black screen

  3 mai 2017, par alex

  i’m trying to use opencv3.1 with python3.5
  following this official)tutorial
  http://docs.opencv.org/3.0-beta/doc/py_tutorials/py_gui/py_video_display/py_video_display.html#display-video

  the camera led is "on" but the window doesn’t show any image (black)

  my current enviroment :
   windows 10
   python 3.5.2 (32bit)
   numpy 1.12.0b1 (32bit) binaries downloaded from : http://www.lfd.uci.edu/ gohlke/pythonlibs/
   opencv 3.1.0 (32bit) binaries downloaded from : http://www.lfd.uci.edu/ gohlke/pythonlibs/

  they seem installed correctly !

  as the tutorial says :

  Note Make sure proper versions of ffmpeg or gstreamer is installed. Sometimes, it is a headache to work with Video Capture mostly due to wrong installation of ffmpeg/gstreamer.

  i’ve no ffmpeg installed !!! so i suppose this is the cause of my problem
  so the questions are :
  1) which version of ffmpeg is needed ?
  2) how install ffmpeg on windows ? it seems a setup doesn’t exist(there is a binary section with a zip file ? how to use it after unzipped ?)
  3) is possible to see(in some way) if the opencv binaries(that i’ve downloaded) were compiled with ffmpeg support(flag ?)

  PS : i’ve tried to add the ffmpeg folder path the the PATH enviroment variable but nothing change

• Tele-Arena Lives On

  25 février 2011, par Multimedia Mike — Game Hacking

  Readers know I have a peculiar interest in taking apart video games and that I would rather study a game’s inner workings than actually play it. I take an interest on others’ efforts in this same area. It’s still in my backlog to take a closer look at Clone2727’s body of work. But I wanted to highlight my friend’s work on re-implementing a game called Tele-Arena.

  
  
  

  Back In The Day
  As some of you are likely aware, there was a dark age of online communication that predated the era of widespread internet access. This was known as "The BBS Age". People dialed into these BBSes using modems that operated at abysmal transfer speeds and would communicate with other users, upload and download files, and play an occasional game.

  BBS software evolved and perhaps the ultimate (and final) evolution was Galacticomm’s MajorBBS (MBBS). There were assorted games that plugged into the MBBS, all rendered in glorious color ANSI graphics. One of the most famous of these games was Tele-Arena (TA). TA was a multiplayer fantasy-themed text adventure game. Perhaps you could think of it as World of Warcraft, only rendered as interactive fiction instead of a rich 3D landscape. (Disclaimer : I might not be qualified to make that comparison since I have never experienced WoW firsthand, though I did play TA on and off about 17 years ago).

  TA was often compared to multi-user dungeons — or MUDs — that were played by telneting into internet servers hosting games. Such comparisons were usually unfavorable as people who had experience with both TA and MUDs were sniffy elitists with internet access who thought they were sooooo much better than those filthy, BBS-dialing serfs.

  Sorry, didn’t mean to open old wounds.

  Modern Retelling of A Classic Tale
  Anyway, my friend Ron Kinney is perhaps the world’s biggest fan of TA. So much so that he has re-implemented the engine in Java under the project name Ether. He’s in a similar situation as the ScummVM project in that, while the independent, open source engine is fair game for redistribution, it would be questionable to redistribute the original data files. That’s why he created an AreaBuilder application that generates independent game data files.

  Ironically, you can also telnet into a server on which Ron hosts an instance of Tele-Arena (ironic in the sense that the internet/BBS conflict gets a little blurry).

  I hope that one day Ron will regale us with the strangest tales from the classic TA days. My personal favorite was "Wrath of a Sysop."