Recherche avancée

Sur d’autres sites (8748)

• Normalise offsetX and offsetY on the event

  19 février 2014, par chriscbrock

  Normalise offsetX and offsetY on the event
  According to the W3C Working Draft, offsetX and offsetY should be
  
  relative to the padding edge of the target element. The only browser
  
  using this convention is IE. Webkit uses the border edge, Opera uses the
  
  content edge, and FireFox does not support the properties.
  Normalizing to the border edge is easiest to do.
  

• fatal error : libavcodec/avcodec.h : No such file or directory

  18 février 2014, par Piterwilson

  

  The tooltip is over the line

  #include <libavcodec></libavcodec>avcodec.h>

  I'm new to JNI development. After managing to compile FFMPEG i fail to be able to use it on a project.

  On the screenshot you can see that the folder with the libs and includes is referenced under includes (via Project/properties/C/C++ general/paths and symbols)

  To me it looks like it should find it but i get the error.

  What extra place do i have to specify this folder for the build to work ?

  Edit : contents of Android.mk

  LOCAL_PATH := $(call my-dir)
  
  
  
  include $(CLEAR_VARS)
  
  
  
  LOCAL_MODULE    := FFMpegTest
  
  LOCAL_SRC_FILES := FFMpegTest.cpp
  
  LOCAL_LDLIBS := -llog
  
  
  
  LOCAL_SHARED_LIBRARIES := libavformat libavcodec libswscale libavutil
  
  
  
  include $(BUILD_SHARED_LIBRARY)
  
  include $(call all-subdir-makefiles)

  Thanks

• How To Extract RTP Packet Specific Fields From Wireshark Capture ?

  5 novembre 2014, par Lane

  I have a PCAPNG file and I need to get the RTP packets from it. Specifically, one of my RTP packets looks like...

  Frame N : X bytes on wire...

  • Ethernet II, Src : ...
  • IPv4, Src : ...
  • TCP, Src Port : rstp ...
  • RTSP Interleaved Frame, Channel : 0x02, 163 bytes
  • Real-Time Transport Protocol

  ...and what I need from each packet is...

  1. The channel from the RTSP interleaved frame
  2. The length from the RTSP interleaved frame
  3. The payload from the RTP

  ...using this data, I will re-create an audio and video file to re-construct the full video from a local payload (playback is not streaming).

  I am able to successfully get the RTP packets using either...

  tshark -r my.pcap -R -T fields -e rtp.payload -w rtp.out

  or...

  tshark -r my.pcap -R -T fields -e rtp.payload > rtp.out

  ...but the problem I am having is that the first method will save everything I need, but for some reason it will add extra data (i.e. more than just the RTP payload and RTSP interleaved frame contents) in strange places... which is preventing me from writing a program to produce the data I need to test. I attempted to remove all the extra data using several regular expressions, but there are too many different scenarios that overlap onto other valid scenarios.

  The second method will provide only the RTP payload without the interleaved properties I need (it will produce the hex with a colon between each byte, but that is easily handled). Even if I could make another call to get all the RTSP interleaved frame properties, I am going to need to combine the 2 outputs by identifying each packet using a separator / delimiter, which I’d like to avoid (I couldn’t get tshark to do that either...).

  I looked into the tshark read filters, which seems like it should be able to do what I need, but so far I haven’t been able to figure it out. Note that I am only doing this to create sample data and write the logic that formats the data required for playback. Eventually one of my co-workers will modify the streaming client to capture the data in the appropriate format (so I can simply run the data through ffmpeg without modifying it). Any ideas of how I can create the format I need ?