Recherche avancée

Sur d’autres sites (8737)

• ReSample RTP Audio data over Socket as PCM data using FFMPEG

  5 février 2020, par GJ.

  I want to receive a RTP Stream and send the raw data received in it over TCP / UDP socket. For this i am trying following commands.

  1. I am sending the RTP stream using following command.

     ffmpeg -re -i hello.wav -ar 8000 -f mulaw -f rtp rtp ://127.0.0.1:1234

  2. Receiver to re transmit the stream over TCP / UDP socket.

     ffmpeg -i rtp ://127.0.0.1:1234 -f mulaw tcp ://127.0.0.1:5555 -hide_banner

  3. A Player to play this Socket stream to verify.

     ffplay tcp ://127.0.0.1:5555 ?listen

  My second command shows that its receiving data and transmitting the data to tcp over 5555 port.

  Input #0, rtp, from 'rtp://127.0.0.1:1234':
  
    Duration: N/A, start: 0.000000, bitrate: 64 kb/s
  
      Stream #0:0: Audio: pcm_mulaw, 8000 Hz, mono, s16, 64 kb/s
  
  Stream mapping:
  
    Stream #0:0 -> #0:0 (pcm_mulaw (native) -> pcm_mulaw (native))
  
  Press [q] to stop, [?] for help
  
  Output #0, mulaw, to 'tcp://127.0.0.1:5555':
  
    Metadata:
  
      encoder         : Lavf58.29.100
  
      Stream #0:0: Audio: pcm_mulaw, 8000 Hz, mono, s16, 64 kb/s
  
      Metadata:
  
        encoder         : Lavc58.54.100 pcm_mulaw

  But the third command does not receive anything, even i tried dumping the response into a file using FFMPEG in command three but same results.

  What am i doing wrong, Please suggest the correct commands using FFMPEG.

• MPEG-DASH not working. MPD validation fails

  16 novembre 2017, par Marko36

  I am trying to serve video using MPEG-DASH. No success. I have tried the following :

  Following the instructions on webproject.org, using FFMPEG, I have created several variants of the original video and the DASH MPD manifest, containing metadata. However, the manifest does not validate using http://dashif.org/conformance.html. This validator itself is quite useless, as it provides unusable info about the error. I have found in a post from 2014, that one of the errors generated by FFMPEG is capital letters in some metadata (not a critical one, but could have been fixed for years !). Other errors detected, but not described. No tangible info from any of these other validators either : http://www-itec.uni-klu.ac.at/dash/?page_id=605 (produces rubbish info), https://github.com/Eyevinn/dash-validator-js (throws an exception)

  Following instructions on mozilla.org, produces the same non-working result, as the instructions are nearly identical (including same resolution*bitrate sets), except that Mozilla omits the use of dash.js, which is deemed necessary by the rest of the internet.

  This guide on Bitmovin, utilizing x264 and MP4Box does not work either. Going by the instructions, I have to recode the original x264 video twice. The final version of videos are in some cases twice the size of their intermediate versions and 720p video is actually larger than its 1080p, higher bitrate counterpart. No need to go further. (Yet, this is the only way that actually produced segments..)

  I have spent 3 days on the above, read about all there is on the web from the other frustrated adopters, and ran out of options. I would really apreciate some pro tips ! Thanks !

• Revision 4c05a051ab : Move qcoeff, dqcoeff from BLOCKD to per-plane data Start grouping data per-plan

  2 avril 2013, par John Koleszar

  Changed Paths : Modify /vp9/common/vp9_blockd.h Modify /vp9/common/vp9_invtrans.c Modify /vp9/common/vp9_mbpitch.c Modify /vp9/common/vp9_rtcd_defs.sh Modify /vp9/decoder/vp9_decodframe.c Modify /vp9/decoder/vp9_dequantize.c Modify /vp9/decoder/vp9_dequantize.h (...)