Recherche avancée

Sur d’autres sites (9925)

• Piwik is now using Github issues as our Issue Tracker !

  9 juillet 2014, par Matthieu Aubry — Community, Development

  This is an announcement regarding the Issue Tracker used for the Piwik project. We are excited to announce that Piwik has migrated from Trac to now using Github issues for managing our issues !

  More than 5,400 tickets and 20,000+ comments from 1,000+ users were migrated to Github. Read on for more information.

  Where do I find Piwik Issue Tracker ?

  • Piwik main project issue tracker (piwik/piwik)
  • Piwik Mobile issues (piwik/mobile2)
  • Device Detector issues (piwik/device-detector)
  • Piwik iOS SDK (piwik/piwik-sdk-ios)
  • See other repositories at github.com/piwik

  Benefits of using Github Issues for the Piwik project

  There are several advantages of moving to Github issues :

  • Faster and responsive user interface
  • Better cross-project referencing of issues
  • Ability to notify people with the @username functionality
  • No spam
  • Integration with Pull requests and our Git repository

  How do I get notifications for all Piwik tickets ?

  To receive notifications for new tickets or new comments in the Piwik project, go to github.com/piwik/piwik, then click the Watch button at the top of the page.

  

  In Github, watching a repository lets you follow new commits, pull requests, and issues that are created.

  How do I report a bug in Piwik ?
  See Submitting a bug report.

  How do I suggest a new feature ?
  See Submitting a feature request.

  Next steps

  At Piwik we care a lot about Data ownership. For this reason we need to have an up to date copy of all our tickets and comments out of github.com servers. Our next step will be to create and release as open source a tool to let anyone create a Mirror of their Github issues. See #5299.

  For more information about the Trac->migration, see #5273.

  We look forward to reading your issues on Github !

• ffmpeg : RTP missed many packets

  29 juin 2020, par Yves

  I have an mp4 file named test.mp4, and I'm using VLC player as an RTSP server to convert the file test.mp4 to the RTSP stream and send it to the client.

  


  Here is how I configure my VLC to become a RTSP server : https://www.youtube.com/watch?v=kfCKSIrIGlY

  


  Then I login remotely my Linux machine, which is the client to receive the RTSP stream. To do so, I execute the below command on my Linux machine :

  


  ffmpeg -i rtsp://192.168.120.157:5544/stream -c copy -f segment -segment_time 100 out_%d.mp4


  


  After executing the command, I got two mp4 files. It seems that everything works as expected, except that I got many warnings :

  


  [rtsp @ 0x5a48580] max delay reached. need to consume packet=N/A speed=1.02x
[rtsp @ 0x5a48580] RTP: missed 40 packets
[rtsp @ 0x5a48580] max delay reached. need to consume packet=N/A speed=1.02x
[rtsp @ 0x5a48580] RTP: missed 6 packets
[rtsp @ 0x5a48580] max delay reached. need to consume packet
[rtsp @ 0x5a48580] RTP: missed 3 packets
[rtsp @ 0x5a48580] max delay reached. need to consume packet=N/A speed=1.02x
[rtsp @ 0x5a48580] RTP: missed 45 packets
[rtsp @ 0x5a48580] max delay reached. need to consume packet
[rtsp @ 0x5a48580] RTP: missed 5 packets
[rtsp @ 0x5a48580] max delay reached. need to consume packet=N/A speed=1.02x
[rtsp @ 0x5a48580] RTP: missed 22 packets
[rtsp @ 0x5a48580] max delay reached. need to consume packet
...
...


  


  Is this normal ? How can I solve these warnings ?

  


• Serving live stream by using ffmpeg via rtmp protocol

  28 janvier 2019, par Yusufu

  I have been trying to serve my rtmp stream to web, struggling with videojs
  I am able to serve my static video or live stream from android screen by using ffmpeg via this command :

  ffmpeg -i video7.mp4 -c:v libx264 -g 25 -preset fast -b:v 4096k -c:a libfdk_aac -ar 44100 -f flv rtmp://127.0.0.1/media_server/video.flv

  So can connect it via ffplay. This part works like a charm.

  ffplay  rtmp://127.0.0.1/media_server/video.flv

  But couldnt watch in web. My html file here. Copied from videojs offical example

  1. question : Being able to watch via ffplay on rtmp means my nginx rtmp module works well ?

  2. I have been serving httml via http-server and rtmp on rtmp ://127.0.0.1 without port caused problem ?

  3. Any other videoplayer advice ? I have already tried hls it works but in my case creating m3u8 manifest file not desired because I am streaming live video from mobile screen record so creating new ts files nut not updated m3u8 file not for me I guess ?

  4. What else I can try as a protocol ? instead of rtmp

  I can share about my screenrecord and ffmpeg commands to help me or you. Thanks