Recherche avancée

Sur d’autres sites (15334)

• 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 !

• Saving H264 RTP Packets In Useful Form

  14 novembre 2014, par Nick Lima

  I know that it is possible to save RTP h264 streams using Wireshark and VLC. But in order to learn more about video streaming I am trying to do it myself. There are several related questions that make for good reading on this topic :

  How to process raw UDP packets so that they can be decoded by a decoder filter in a directshow source filter

  Problem to Decode H264 video over RTP with ffmpeg (libavcodec)

  How to convert H.264 UDP packets to playable media stream or file (defragmentation)

  With those as background, this is where I am currently :

  • I can receive RTP packets over UTP.
  • I parse packets as discussed in the questions above.
  • I write the packets to a file, separated by \x000001 and add the NAL byte again according to the above guides.
  • At the beginning of the file I put the SPS and PPS which I got from my code’s RTSP conversation with the server (again seperated by the correct bytes).

  I end up with a file of supposedly a lot of NAL frames. I then try to run ffmpeg on the .264 file to create a .mp4. This brings up several errors :

  [h264 @ 0x15257a0] decode_slice_header error

  [h264 @ 0x15257a0] no frame !

  [h264 @ 0x15257a0] non-existing PPS referenced

  [h264 @ 0x15257a0] non-existing PPS 0 referenced

  [buffer @ 0x15e16a0] Invalid pixel format string ’-1’

  I am essentially at a standstill until I can figure out this problem. I have thouroughly read the questions I linked to above, and the stream is definitely viewable because I can connect and watch it via VLC and the incoming packets are definitely H264 RTP packets according to wireshark. If VLC can do it why can’t I ! I would greatly appreciate any insight into my errors and possible a summary of the three linked questions that resolves the disagreements between them.

• Pushing data while downloading to ffmpeg

  5 avril 2019, par Nguyễn Thành Đạt

  I have try to relivestream video to facebook with source from youtube.

  I use the ytdl to download video from youtube.
  I want to during the video download process, i will livestream

  When i run my source in blow by nodejs then the error appears :

  var url = 'https://www.youtube.com/watch?v=CTL_5dqDOyc';
  
  var ffmpeg = spawn('ffmpeg', ['-re', '-i', 'pipe:0', '-i', 'logo.png',' acodec', 'libmp3lame',  '-ar', '44100', '-b:a', '128k', '-profile:v', 'baseline', '-s', '854x480', '-bufsize', '6000k', '-vcodec', 'libx264', '-preset', 'veryfast', '-g', '30', '-r', '30', '-f', 'flv', 'rpmt link']);
  
  ytdl(url).pipe(ffmpeg.stdin);