Sur d’autres sites (5403)

• ffmpeg h264 interesting bright video fail ?

  23 novembre 2019, par Max Paython

  I am trying streaming with ffmpeg using the information I found here.

  • Server

    ffmpeg -f dshow -i video="john":audio="doe" -vcodec libx264
    
    -preset ultrafast -tune zerolatency -acodec aac -f mpegts udp://localhost:1234

  • Client

    ffmpeg -i udp://localhost:1234?listen test.mp4

  The client will actually live stream the video, but for testing purposes I am writing the output to a file for now.

  Here comes the interesting part. I began the stream(video and audio) in a dark room, everything is fine. I turn on the room’s lights and the client cries with many errors. I later checked the output, it is very corrupted indeed on the light turned-on parts. What could be the reason behind this ? I am posting the errors here if it could be of assistance.

  Some of the errors :

  udp://localhost:1234?listen: corrupt decoded frame in stream 0trate= 845.6kbits/s dup=1250 drop=0 speed=1.08x
  
      Last message repeated 1 times
  
  [h264 @ 0000026c4af69400] Invalid NAL unit 1, skipping.7.61 bitrate= 864.7kbits/s dup=1441 drop=0 speed=1.07x
  
  [h264 @ 0000026c4af69400] Invalid level prefix
  
  [h264 @ 0000026c4af69400] error while decoding MB 18 8
  
  [h264 @ 0000026c4af69400] concealing 911 DC, 911 AC, 911 MV errors in P frame
  
  [h264 @ 0000026c4af4b780] Invalid NAL unit 1, skipping.
  
  [h264 @ 0000026c4af4b780] negative number of zero coeffs at 10 14
  
  [h264 @ 0000026c4af4b780] error while decoding MB 10 14
  
  [h264 @ 0000026c4af4b780] concealing 679 DC, 679 AC, 679 MV errors in P frame
  
  udp://localhost:1234?listen: corrupt decoded frame in stream 0
  
      Last message repeated 1 times
  
  [h264 @ 0000026c4ba1e1c0] Invalid NAL unit 1, skipping.8.21 bitrate= 858.0kbits/s dup=1460 drop=0 speed=1.07x
  
  [h264 @ 0000026c4ba1e1c0] out of range intra chroma pred mode
  
  [h264 @ 0000026c4ba1e1c0] error while decoding MB 34 18
  
  [h264 @ 0000026c4ba1e1c0] concealing 495 DC, 495 AC, 495 MV errors in P frame
  
  [h264 @ 0000026c4bb16840] top block unavailable for requested intra mode
  
  [h264 @ 0000026c4bb16840] error while decoding MB 10 0
  
  [h264 @ 0000026c4bb16840] concealing 160 DC, 160 AC, 160 MV errors in P frame
  
  udp://localhost:1234?listen: corrupt decoded frame in stream 0
  
  [h264 @ 0000026c4bb16cc0] Invalid NAL unit 0, skipping.8.58 bitrate= 853.9kbits/s dup=1463 drop=0 speed=1.06x
  
  [h264 @ 0000026c4bb16cc0] corrupted macroblock 16 28 (total_coeff=-1)
  
  [h264 @ 0000026c4bb16cc0] error while decoding MB 16 28
  
  [h264 @ 0000026c4bb16cc0] concealing 113 DC, 113 AC, 113 MV errors in P frame
  
  [h264 @ 0000026c4bb17140] cbp too large (84) at 12 0
  
  [h264 @ 0000026c4bb17140] error while decoding MB 12 0
  
  [h264 @ 0000026c4bb17140] concealing 160 DC, 160 AC, 160 MV errors in P frame
  
  [mpegts @ 0000026c4aeb8d80] PES packet size mismatch

  Edit : As suggestion, I added these parameters to the server.

  -b:v 1M -bufsize 2M

  Now the errors are mostly gone. Except one time where it seemed like it occured just as I was turning off the lights, although I could not reproduce it after trying 4-5 times.

  Errors :

  [h264 @ 000002646f0d2f80] cbp too large (118) at 23 1422.25 bitrate= 659.5kbits/s dup=368 drop=0 speed=1.33x
  
  [h264 @ 000002646f0d2f80] error while decoding MB 23 14
  
  [mpegts @ 000002646e578d80] PES packet size mismatch
  
  [h264 @ 000002646f0d2f80] concealing 666 DC, 666 AC, 666 MV errors in P frame
  
  [h264 @ 000002646f0d0f80] concealing 160 DC, 160 AC, 160 MV errors in P frame
  
  [aac @ 000002646e64d640] Number of bands (59) exceeds limit (43).
  
  Error while decoding stream #0:1: Invalid data found when processing input
  
  [aac @ 000002646e64d640] Multiple frames in a packet.
  
  [aac @ 000002646e64d640] Reserved bit set.
  
  [aac @ 000002646e64d640] Number of bands (31) exceeds limit (29).
  
  Error while decoding stream #0:1: Invalid data found when processing input
  
  [h264 @ 000002646e5e11c0] concealing 160 DC, 160 AC, 160 MV errors in P frame
  
  udp://localhost:1234?listen: corrupt decoded frame in stream 0trate= 633.1kbits/s dup=368 drop=0 speed=1.35x
  
      Last message repeated 2 times

  The errors decreased because I increased the bitrate ? (I don’t know the default bitrate by the way). Bright decoding fails because it carries more information, data ? (same in raw video, but maybe file is heavier encoded bright frames)

• Piwik is now Matomo – Announcement

  
  9 janvier 2018, par Matomo Core Team

  You may be surprised to read this announcement, but no stress, take a deep breath, nothing big is going to happen, it is just our name that is changing and here are the reasons why.

  

  Why are we changing from Piwik to Matomo ?

  “After an epic 10 year journey creating and perfecting the best open digital analytics solution, we felt it was a good time to refresh our brand to reflect how far we have come and to reaffirm our vision :
  To create, as a community, the leading international open source digital analytics platform, that gives every user full control of their data.”

  Matthieu Aubry, creator of Piwik

  As projects evolve, so do names. After 10 years of Piwik and the amazing achievement of building the top open source analytics software that gives every user full control of their data, we are now looking forward to the next chapter. Thus, Piwik, the community project, will now become Matomo. The only change is our name, everything else stays the same.

  This will allow users to take a fresh look at what we’ve become today and acknowledging all of the community’s hard work over the past 10 years. In addition, we also want our name to be unique, ensuring that it is not shared with any other company to remove any possible confusion or affiliations. Piwik is already used on over 1 million websites and with Matomo, we hope to reach our maximum potential.

  With the strong focus on privacy worldwide and the upcoming privacy regulations about to be legislated in Europe, it is clear that we were on the right mission from the very beginning. With the upcoming big release Matomo 4.0 planned for this year, new privacy protections will bring users the tools to be compliant with the GDPR privacy laws. And Matomo will grow in line with these regulations, with a very clear and focused vision.

  Changing our name is an exciting opportunity for us, and we hope you love the name Matomo as much as we do.

  Matomo FAQs

  So what is going to change for me ?

  Well, basically nothing, the name will change but the values stay the same : Matomo (Piwik) will continue to be free and always will be.

  Also the same people stay behind the project. We are motivated more than ever to take this project to the next level.

  Why not keep the name Piwik ?

  For a few reasons, one of which is to ensure that Matomo does not/will not share its name with any other businesses unlike Piwik. We also want to protect the Matomo brand and for it to remain the open source community project name forever.

  Where does the name Matomo come from ?

  We loved the name Piwik and were looking for something that sounded just as good ! Initially we wanted to have an acronym based on key terms, such as Free, Open Source and Privacy, but none really fit us perfectly.

  Until we found Matomo ! Easily pronounced in all languages. Short enough to remember. Concise. And best of all… Matomo means honesty in Japanese. Which aligns with one of our key values – transparency.

  We love the name Matomo and hope you do too.

  What is the vision of Matomo ?

  

  We have come a long way in those 10 years ! However, our mission statement remains the same :

  “To create, as a community, the leading international open source digital analytics platform, that gives every user full control of their data.”

  Matomo provides a range of amazing and innovative features, allowing you to get a 360 view of your visitors. These insights are invaluable to help understand behavior, keep track of goals, and increase conversion rates and revenue.

  Who will deliver Matomo professional services ?

  Any company who wishes to. The only exception is that no companies will be allowed to have the name Matomo.

  Our company providing professional services is and will remain InnoCraft.

  Where can I follow the Matomo project ?

  Our new website will be matomo.org (automatically redirected from Piwik.org)

  Follow our new Twitter : twitter.com/matomo_org

  Github : github.com/matomo-org

  Facebook : facebook.com/Matomo.org

  Linkedin : linkedin.com/company/matomo/

  If you are already following us on social media, you will be kept up to date with Matomo automatically as all social media accounts will be redirected.

  How should I pronounce Matomo ?

  If you’re wondering how to say ‘Matomo’, you can find out by clicking play :

  Where can I see a demo of Matomo ?

  On demo.matomo.org

  Where can I download Matomo first release ?

  On matomo.org/download

  (Matomo 3.3.0 will be released in the next few days)

  What is the new logo ?

  Check it out below.

  

  Matomo trademark Policy

  Matomo is an internationally registered trademark of Matthieu Aubry, Founder of Piwik (now Matomo).

  Information about how to use the name Matomo (and logo) can be found here : matomo.org/trademark/

  What are the next big steps ?

  We will keep it simple for our valued users. As it is just a name change, the only thing you will notice is that the Piwik brand will gradually be replaced on the websites you are used to seeing the name on. The first version of Matomo will be available in just a few days for download. The software version numbers stay the same : the next release after Piwik 3.2.1 will be Matomo 3.3.0.

  All our public HTTP APIs and Tracking SDKs will continue working normally. As you can imagine, there is a lot of work and complexity behind slowly updating all the SDKs and keeping backwards compatibility, so our renaming project will take a few weeks to complete.

  The Matomo trademark will later be transferred into the Matomo foundation, a non-profit that will be dedicated to promoting and ensuring access to Matomo and our related open source projects in perpetuity.

  ---

  Thank you

  Thank you for continuing to support our project, alongside our 20+ Matomo core team members and more than 500 contributors.

  Please help to spread the word about this announcement by sharing it with friends or or colleagues who may benefit from using Matomo Analytics !

  The post Piwik is now Matomo – Announcement appeared first on Analytics Platform - Matomo.

• ffmpeg have unmet dependencies (Ubuntu20) [closed]

  10 août 2024, par mojiang

  when installing ffmpeg with ubuntu20(fosal), it have conflict dependencies :

  


  # sudo apt-get install ffmpeg
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 ffmpeg : Depends: libavdevice58 (= 7:4.2.7-0ubuntu0.1) but it is not going to be installed
          Depends: libavfilter7 (= 7:4.2.7-0ubuntu0.1)
          Depends: libavformat58 (= 7:4.2.7-0ubuntu0.1) but it is not going to be installed
E: Unable to correct problems, you have held broken packages.


  


  I solved it by install the reason of conflit library with a specific version, may be someone will need the solution.

  


  step 1. fix-broken

  


  sudo apt --fix-broken install
Reading package lists... Done
Building dependency tree       
Reading state information... Done


  


  step2. find the reason of unmet dependencies :

  


  # sudo apt install libavdevice58=7:4.2.7-0ubuntu0.1 libavfilter7=7:4.2.7-0ubuntu0.1 libavformat58=7:4.2.7-0ubuntu0.1
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 libavformat58 : Depends: libchromaprint1 (>= 1.3.2) but it is not going to be installed
E: Unable to correct problems, you have held broken packages.


  


  Here the problem is from libchromaprint1

  


  step3. find candidate versions of libchromaprint1(conflict reason)

  


  # apt-cache policy libchromaprint1
libchromaprint1:
  Installed: (none)
  Candidate: 1.5.1-1~20.04.sav0
  Version table:
     1.5.1-1~20.04.sav0 500
        500 http://ppa.launchpad.net/savoury1/multimedia/ubuntu focal/main amd64 Packages
     1.4.3-3build1 500
        500 http://mirrors.cloud.aliyuncs.com/ubuntu focal/universe amd64 Packages
        500 http://archive.ubuntu.com/ubuntu focal/universe amd64 Packages


  


  step4. install the old version of libchromaprint1 to solve the conflicts

  


  # sudo apt install libchromaprint1=1.4.3-3build1
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following NEW packages will be installed:
  libchromaprint1
0 upgraded, 1 newly installed, 0 to remove and 223 not upgraded.
Need to get 37.6 kB of archives.


  


  step5. reinstall ffmpeg

  


  # sudo apt install ffmpeg
Reading package lists... Done
Building dependency tree       
Reading state information... Done


  


  Done. the reason of conflict is that the latest version of libraries have conflict, by install old version of the conflicted ones to solve it.