Recherche avancée

Sur d’autres sites (6955)

• Why rtp streaming of a .avi video file fails to be received ?

  14 juillet 2016, par user1914692

  In ffmpeg streamingGuide, it writes :

  ffmpeg -re -f lavfi -i aevalsrc="sin(400*2*PI*t)" -ar 8000 -f mulaw -f rtp rtp://127.0.0.1:1234 &
  
  ffplay rtp://127.0.0.1:1234

  I want to use a real video file to replace the artificial signal.
  Then I write the below at terminal A :

  ffmpeg -re -i outputFile.avi -f mulaw -f rtp rtp://127.0.0.1:1234

  it seems it is working :
  The frame information is counting. Here are information on the terminal A at the end :

  frame=  309 fps= 29 q=31.0 Lsize=     931kB time=00:00:10.30 bitrate= 740.8kbits/s     video:922kB audio:0kB subtitle:0 global headers:0kB muxing overhead 1.030813%

  When the frame at terminal A is still counting (not finished), I type the below at terminal B :

  ffplay rtp://127.0.0.1:1234

  But it does not work :
  The error information is :

  [udp @ 0x7fb370001500] bind failed: Address already in useB f=0/0   
  
  rtp://127.0.0.1:1234: Input/output error

  Why ?

  [Update 1] Following the instruction from Camille Goudeseune
  I used the foo.sdp
  The input for the ffmpeg terminal is :

  ffmpeg -re -i out.avi -f mulaw -f rtp rtp ://127.0.0.1:1235

  The terminal for ffplay is :

  ffplay -i foo.sdp

  The ffplay terminal shows a lot of error, without images.

    libpostproc    52.  2.100 / 52.  2.100
  
  [sdp @ 0x7fafdc0008c0] Undefined type (30)    0KB sq=    0B f=0/0   
  
  [sdp @ 0x7fafdc0008c0] nal size exceeds length: 25453 86 0B f=0/0   
  
  [sdp @ 0x7fafdc0008c0] Consumed more bytes than we got! (-25367)
  
  [sdp @ 0x7fafdc0008c0] nal size exceeds length: 25453 86
  
  [sdp @ 0x7fafdc0008c0] Consumed more bytes than we got! (-25367)
  
  [sdp @ 0x7fafdc0008c0] Unhandled type (27) (See RFC for implementation details
  
  [sdp @ 0x7fafdc0008c0] Undefined type (31)    0KB sq=    0B f=0/0   
  
  [sdp @ 0x7fafdc0008c0] Unhandled type (27) (See RFC for implementation details
  
  [sdp @ 0x7fafdc0008c0] nal size exceeds length: 62414 6130B f=0/0   
  
  [sdp @ 0x7fafdc0008c0] Consumed more bytes than we got! (-61801)
  
  [sdp @ 0x7fafdc0008c0] nal size exceeds length: 62414 613
  
  [sdp @ 0x7fafdc0008c0] Consumed more bytes than we got! (-61801)
  
  [h264 @ 0x7fafdc003020] non-existing PPS referencedq=    0B f=0/0   
  
  [h264 @ 0x7fafdc003020] non-existing PPS 0 referenced
  
  [h264 @ 0x7fafdc003020] decode_slice_header error
  
  [h264 @ 0x7fafdc003020] Invalid mix of idr and non-idr slices
  
  [sdp @ 0x7fafdc0008c0] Undefined type (31)    0KB sq=    0B f=0/0   
  
  [sdp @ 0x7fafdc0008c0] Unhandled type (29) (See RFC for implementation details
  
  [sdp @ 0x7fafdc0008c0] Unhandled type (26) (See RFC for implementation details
  
  [sdp @ 0x7fafdc0008c0] Unhandled type (27) (See RFC for implementation details
  
      Last message repeated 2 times  0KB vq=    0KB sq=    0B f=0/0   
  
  [sdp @ 0x7fafdc0008c0] Undefined type (31)
  
  [sdp @ 0x7fafdc0008c0] Unhandled type (26) (See RFC for implementation details
  
  [sdp @ 0x7fafdc0008c0] Unhandled type (25) (See RFC for implementation details
  
  [h264 @ 0x7fafdc003020] insane cropping not completely supported, this could look slightly wrong ... (left: 2, top: 2)
  
  [h264 @ 0x7fafdc003020] illegal aspect ratio
  
  [h264 @ 0x7fafdc003020] missing picture in access unit with size 84589
  
  [h264 @ 0x7fafdc003020] Partitioned H.264 support is incomplete
  
  [h264 @ 0x7fafdc003020] insane cropping not completely supported, this could look slightly wrong ... (left: 2, top: 2)
  
  [h264 @ 0x7fafdc003020] illegal aspect ratio
  
  [h264 @ 0x7fafdc003020] insane cropping not completely supported, this could look slightly wrong ... (left: 2, top: 2)
  
  [h264 @ 0x7fafdc003020] illegal aspect ratio
  
  [h264 @ 0x7fafdc003020] no frame!
  
  [h264 @ 0x7fafdc003020] RTP: missed 2563 packetsB sq=    0B f=0/0   
  
  [sdp @ 0x7fafdc0008c0] Undefined type (30)
  
      Last message repeated 1 times
  
  [sdp @ 0x7fafdc0008c0] Undefined type (31)

• Revision 5724b7e292 : yv12extend : name variables consistently - s|source -> src - dest -> dst - use v

  23 août 2013, par James Zern

  Changed Paths :
   Modify /vpx_scale/generic/yv12extend.c

  
  
  yv12extend : name variables consistently

   s|source -> src
   dest -> dst
   use verbose names in extend_plane dropping the redundant comments

  + light cosmetics :
   join a few lines / assignments
   drop some unnecessary comments & includes

  Change-Id : I6d979a85a0223a0a79a22f79a6d9c7512fd04532

• Struggling with where to start with creating a x264 .Net Wrapper [closed]

  3 août 2013, par Rob ElCalvo Perry

  I have a compiled libx264-129.dll for Windows and its functions are clearly visible in DLL Viewer. However, I havent got a clue where to start to create a .NET wrapper for it. The ultimate aim is to create a piece of screen recording software with x264 as the codec..

  Can anyone shed some light on where to start (I understand about P/Invoke etc) What I'm looking for is the fundamentals needed to wrap the library and encode bitmaps from .NET..

  I know that x264_param_t plays a part in creating the encoder object but with no knowledge of C, I'm totally stuck really :-s