Recherche avancée

Sur d’autres sites (3886)

• lavc/vaapi_encode : Separate reference frame into previous/future list

  11 septembre 2023, par Fei Wang

  lavc/vaapi_encode : Separate reference frame into previous/future list
  To support more reference frames from different directions.
  Signed-off-by : Fei Wang <fei.w.wang@intel.com>
  
  Reviewed-by : Neal Gompa <ngompa13@gmail.com>
  

  • [DH] libavcodec/vaapi_encode.c
  • [DH] libavcodec/vaapi_encode.h
  • [DH] libavcodec/vaapi_encode_h264.c
  • [DH] libavcodec/vaapi_encode_h265.c
  • [DH] libavcodec/vaapi_encode_mpeg2.c
  • [DH] libavcodec/vaapi_encode_vp8.c
  • [DH] libavcodec/vaapi_encode_vp9.c

• PC Video Conferencing in the Year 1999

  21 juin 2011, par Multimedia Mike — General

  Remember Intel’s custom flavor of H.263 cleverly named I.263 ? I think I have finally found an application that used it thanks to a recent thrift shop raid— Intel Video Phone :

  
  
  

  The root directory of the disc has 2 copies of an intro.avi video. One copy uses Intel Indeo 3 video and PCM audio. The other uses I.263 video and an undetermined (presumably Intel-proprietary) audio codec — RIFF id 0x0402 at a bitrate of 88 kbits/sec for stereo, 22 kHz audio. The latter video looks awful but is significantly smaller (like 4 MB vs. 25 MB).

  This is the disc marked as "Send it to a friend...". Here’s the way this concept was supposed to operate :

  • You buy an Intel Video Phone Camera Pack (forgotten page courtesy of the Internet Archive) which includes a camera and 2 CDs.
  • You install the camera and video phone software on your computer.
  • You send the other CD to the person whom you want to be able to see your face when you’re teleconferencing with them.
  • The other party installs the software.
  • The 2 of you may make an internet phone call presumably using commodity PC microphones for the voice component ; the person who doesn’t have a camera is able to see the person who does have a camera.
  • In a cunning viral/network marketing strategy, Intel encourages the other party to buy the physical hardware as well so that they may broadcast their own visage back to the other person.

  If you need further explanation, the intro lady does a great job :

  
  
  

  I suspect I.263 was the video codec driving this since Indeo 3 would probably be inappropriate for real time video applications due to its vector quantizing algorithm.

• Decoding RIMM streaming file format

  1er août 2019, par ThomasRS

  I want to decode the video (visual) frames within a Blackberry RIMM file. So far I have a parser, and some corresponding container documentation from RIM. 

  The video codec is H264 and is explicitly set on the device using one of the video.encodings properties. However, FFMPEG is not able to decode the frames and this is driving me nuts.

  Edit 1 : The issues seems to be lack of SPS and PPS in the frames, and artificially inserting them have proven unsuccessful so far (all grey image). Blackberry 9700 sends

  0x00 0x00 0x ?? 0x ?? 0xType

  where Type is according to table 7-1 in the H264 spec (I and P frames). We believe the 0x ?? 0x ?? represent the size of the frame, however the size does not always correspond to the size found by the parser (the parser seems to be working correctly).

  I have a windows decoder codec from blackberry, called mc_demux_mp2_ds.ax, and can play some MPEG-4 files captured the same way, but it is a binary for windows. And the H264 files will not play either way. I am aware of previous attempts. The capture url for javax.microedition.media.Manager is

  encoding=video-3gpp_width=176_height=144_video_codec=H264_audio_codec=AAC

  and I am writing to an output stream. Some example files here.

  Edit 2 :Turns out that about 3-4 of the 12-15 available video capture modes are flat out failing and refusing to output data, even in the simplest of test applications. So any working solution should implement MPEG-4, H264 and H263 in both AMR and AAC, in so getting fallback alternatives when one sound codec and/or resolution fails. Reboots, hangs and what not litters the Blackberry video implementation and vary from firmware to firmware ; total suckage.