Recherche avancée

Sur d’autres sites (8984)

• While transcoding to mpegts ffmpeg creates the first frame after 1.48 seconds delay

  15 mars 2018, par Biraj B Choudhury

  I have transcoded a file to mpegts using the following command

   ./ffmpeg -y -i big_buck_bunny_720p_5mb.mp4  -vcodec libx264  -x264opts "keyint=48:min-keyint=48:no_scenecut" -r 23.976 -c:a copy  -f mpegts test.mpegts

  When I run ffprobe on it -

  ./ffprobe  -i  test.mpegts  -select_streams v -show_frames -of csv

  I see that the first frame starts at 1.48 seconds why is this so ?

  Input #0, mpegts, from 'test.mpegts':
  
    Duration: 00:00:29.61, start: 1.483422, bitrate: 1964 kb/s
  
    Program 1 
  
      Metadata:
  
        service_name    : Service01
  
        service_provider: FFmpeg
  
      Stream #0:0[0x100]: Video: h264 (High) ([27][0][0][0] / 0x001B), yuv420p(progressive), 1280x720 [SAR 1:1 DAR 16:9], 23.98 fps, 23.98 tbr, 90k tbn, 47.95 tbc
  
      Stream #0:1[0x101](und): Audio: aac (LC) ([15][0][0][0] / 0x000F), 48000 Hz, 5.1, fltp, 406 kb/s
  
  frame,video,0,1,133508,1.483422,133508,1.483422,133508,1.483422,3753,0.041700,564,112008,1280,720,yuv420p,1:1,I,0,0,0,0,0
  
  frame,video,0,0,137262,1.525133,137262,1.525133,137262,1.525133,3753,0.041700,125584,1110,1280,720,yuv420p,1:1,B,2,0,0,0,0

  After some research I added "muxdelay 0" to my command

  ./ffmpeg -y -i big_buck_bunny_720p_5mb.mp4  -vcodec libx264  -x264opts "keyint=48:min-keyint=48:no_scenecut" -r 23.976 -c:a copy  -muxdelay 0 -f mpegts test.mpegts

  And now I get the following in ffprobe

  Input #0, mpegts, from 'test.mpegts':
  
    Duration: 00:00:29.61, start: 0.083422, bitrate: 1987 kb/s
  
    Program 1 
  
      Metadata:
  
        service_name    : Service01
  
        service_provider: FFmpeg
  
      Stream #0:0[0x100]: Video: h264 (High) ([27][0][0][0] / 0x001B), yuv420p(progressive), 1280x720 [SAR 1:1 DAR 16:9], 23.98 fps, 23.98 tbr, 90k tbn, 47.95 tbc
  
      Stream #0:1[0x101](und): Audio: aac (LC) ([15][0][0][0] / 0x000F), 48000 Hz, 5.1, fltp, 406 kb/s
  
  frame,video,0,1,7508,0.083422,7508,0.083422,7508,0.083422,3753,0.041700,564,112008,1280,720,yuv420p,1:1,I,0,0,0,0,0
  
  frame,video,0,0,11262,0.125133,11262,0.125133,11262,0.125133,3753,0.041700,125584,1110,1280,720,yuv420p,1:1,B,2,0,0,0,0

  Can anybody help me understand what is this muxdelay that is contributing to 1.4 seconds of delay and what is contributing to the remaining 0.08 seconds of delay.

  The first frame is at 0.000 when the output is mp4 so this is something particular to mpegts.

• Revision 3265 : On passe un nouvel argument possible au formulaire permettant de lui ...

  18 avril 2010, par kent1 — Log

  On passe un nouvel argument possible au formulaire permettant de lui indiquer directement quel est le tri actuel Dans le cas d’une page recherche, on ajoute un critère de tri qui est points (pertinence)

• We are hiring engineers to build an awesome product and platform used by millions of people

  16 février 2016, par Piwik Core Team — Uncategorized

  Are you ready for a new challenge ? Or maybe you know someone who is looking for a change ? We have some exciting problems to solve and are looking for senior developers to work with us and our community on our open source Piwik Analytics platform. Piwik is used by more than one million websites all over the world. It is deployed on more than 300.000 servers and some users track more than 1 billion actions per month.

  What is it like to work on Piwik ?

  We develop this software using modern PHP, MySQL, Redis, AngularJS and more. We provide several kind of APIs and a plugin architecture to allow developers to extend and change Piwik to their needs. However, we would not be Piwik if we stopped at this point ! We want to turn Piwik into an even more awesome product and platform.
  You can imagine there is a lot to do and many challenges to face !

  While one part is to always make Piwik scale better and to improve UI and UX, we also want to provide simple APIs to make the life of developers as pleasant as possible. We aim to solve things the right way and our thousands of unit, integration, system, JavaScript and screenshot tests help us to innovate and to not be afraid of change. We like clean code and constant improvements.

  The Piwik team lives in New Zealand and Europe (Germany). We do the vast majority of our collaboration online. Our values include being open, transparent and sharing knowledge. For this we use tools like GitHub and Slack to communicate and Quake servers to take our minds off complex challenges. We are a small, flexible team, so when you come aboard, you will play an integral part in engineering and have a big impact on the product loved by so many people. You’ll help to create a welcoming environment for new contributors and set an example with your development practices and communications skills.

  Apply now, or spread the word !

  If you have strong skills in PHP send us an email with your CV and tell us a little about yourself and your experience in engineering complex applications.

  Apply for a job here http://piwik.org/jobs/ and if you’re maybe not the right candidate, contribute to the project by sharing this blog post and by sending it to your friends !