Recherche avancée

Sur d’autres sites (7237)

• Gallery of VP8 Encoding Naivete

  15 octobre 2010, par Multimedia Mike — VP8

  I’ve been toiling away as a multimedia technology generalist for so long that it’s easy for me to forget that not everyone is as versed in the minutiae of the domain as I am. But I recently experienced what it’s like to be such an outsider when I posted about my toy VP8 encoder, expressing that it’s one of the hardest things I have ever tried to do. I heard of from number of people who do have extensive experience in video encoding, particularly with the H.264 and VP8 codecs. Their reactions were predictable : What’s so hard ? Look, you might be a little too immersed in the area to really understand a relative beginner’s perspective.

  And to all the people who suggested that I should get the encoder into FFmpeg ASAP : Are you crazy ?! Did you see what the first pass of the encoder produced ? Do you have lower standards than even I do ?

  
  
  

  Not Giving Up
  I worked a little more on the toy encoder. Remember that the above image is what I’m hoping to encode somewhat faithfully for this experiment. In my first pass, I attempted vertical prediction for all planes. For my next pass, I forced the chroma planes to mid-level (which results in a greyscale image) and played with the 16×16 luma prediction modes. When implementing an extremely naive algorithm to decide which 16×16 prediction mode would be the best for a particular block, this is what the program produced :

  
  
  

  For fun, here is what the image encodes to when forcing various prediction modes :
  

  I think the DC-only prediction mode actually looks a little better than the image that the naive algorithm produced :

  
  
  

  Vertical 16×16 prediction, similar to the image from the last post (just in black and white) :
  

  
  
  

  Horizontal 16×16 prediction :
  

  
  
  

  This is the 16×16 prediction mode unique to VP8, the TrueMotion mode (based on On2/Duck’s very first video codec) :
  

  
  
  

  Wow, these encodings really bring down the cheerful tone of the original image.

  Next Steps
  I have little reason to believe that I am encoding and subsequently reconstructing the image correctly (i.e., error is likely propagating through the entire encoding). If I have time, the next step is to validate my reconstruction against the encoder. Then I need to get the entropy considerations correct so that I actually get some compression out of this format.

• Matomo’s new story : our stronger vision for the future

  31 octobre 2018, par Matthieu Aubry — Community

  

  Over the past year, the team here at Matomo have been working on a very exciting project we’d love to share with you.

  It’s to do with the impact we hope for Matomo to have.

  As you all know, the world changes at too fast a pace. New technologies, new phones, new everything in the blink of an eye. That’s not what will be happening here.

  Instead, we’d like to believe it’s a refresh. Taking stock of how far we’ve come, what we’ve achieved so far, and how far we still have to go.

  So we’re rebranding.

  The rebrand

  Like a caterpillar emerging from a cocoon, we hope to be a reborn analytics butterfly.

  As a result of some careful planning and reflection we’ll be updating our logo, website and reasserting our voice.

  It’s our chance to look at ourselves in a new light. We are a mighty analytics platform and it should be known we’re comparable to the likes of Google Analytics 360.

  Along with the refresh of imagery, we listened to your feedback about the confusion between our two identities, so we’re also taking this opportunity to unite both the business brand of Innocraft with the community brand Matomo into one website.

  It makes it easier for people from all walks of life, either as individuals or in large companies, to see us as being able to get down to business with a powerful analytics tool, as well as think on behalf of our community.

  We’re the same, but with slight changes in our appearance and a stronger vision for the future.

  How far we’ve come …

  When we started out, it was about building a community around a movement. From the beginning we were concerned about data ownership, privacy and all things that came with that.

  With the help of our community and contributors, we turned Matomo (formerly Piwik) into the trusted #1 open source analytics tool it is today. We’re committed to our community. But we also need to do more.

  We’ve been niche and happy staying small, but now we need to take action and start shouting far and wide about what we do.

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

  We believe we’ve done that, so we’ll take it one step further.

  A web analytics revolution has begun …

  Begun ?

  The line signifies a new beginning.

  This is us standing up and reasserting our voice.

  Our new chapter.

  The rebrand is our chance to show that, yes, the world is changing, but when it comes to privacy, there are matters meant to be sacred. Privacy is a human right.

  What makes it worse in this ever-changing landscape, with data breaches and stolen information, is that losing control of our data is scary, we have a right to know what’s going on with our information and this must start with us.

  We know we need to champion this cause for privacy and data ownership.

  We came together as a community and built something powerful, a free open-source analytics platform, that kept the integrity of the people using it.

  It’s important for us now to feel more empowered to believe in our right to privacy, information and our ability to act independently of large corporations.

  The time is here for us to speak up and take back control.

  Once more, we need to come together to build something even more powerful, a safer online society.

  Join us.

  Sincerely,
  Matthieu Aubry on behalf of the Matomo team

• PyArcade (Pyglet) python3 Help needed

  8 juillet 2024, par F4zi

  Python 3.8.1

  


  using python-arcade and linux manjaro os

  


  This project is a multiplayer game built with python arcade

  


  I get these errors while running :

  


  class Client(arcade.Window):

    def __init__(
        self, 
        width: int, 
        height: int, 
        title: str = 'Immortals'
    ) -> None:
        super().__init__(width, height, title=title)


  


  Traceback (most recent call last):&#xA;  File "/home/iddos/Documents/Github/Python/immortals/immortals/main.py", line 42, in <module>&#xA;    main(**config[&#x27;resolution&#x27;])&#xA;  File "/home/iddos/Documents/Github/Python/immortals/immortals/main.py", line 20, in main&#xA;    window = Immortals(*args, **kwargs)&#xA;  File "/home/iddos/Documents/Github/Python/immortals/immortals/core/client.py", line 40, in __init__&#xA;    super().__init__(width, height, title=title)&#xA;  File "/home/iddos/.local/share/virtualenvs/immortals-SS7Euna6/lib/python3.8/site-packages/arcade/application.py", line 70, in __init__&#xA;    super().__init__(width=width, height=height, caption=title,&#xA;  File "/home/iddos/.local/share/virtualenvs/immortals-SS7Euna6/lib/python3.8/site-packages/pyglet/window/xlib/__init__.py", line 171, in __init__&#xA;    super(XlibWindow, self).__init__(*args, **kwargs)&#xA;  File "/home/iddos/.local/share/virtualenvs/immortals-SS7Euna6/lib/python3.8/site-packages/pyglet/window/__init__.py", line 642, in __init__&#xA;    self._create()&#xA;  File "/home/iddos/.local/share/virtualenvs/immortals-SS7Euna6/lib/python3.8/site-packages/arcade/application.py", line 469, in _create&#xA;    super()._create()&#xA;  File "/home/iddos/.local/share/virtualenvs/immortals-SS7Euna6/lib/python3.8/site-packages/pyglet/window/xlib/__init__.py", line 352, in _create&#xA;    self.set_caption(self._caption)&#xA;  File "/home/iddos/.local/share/virtualenvs/immortals-SS7Euna6/lib/python3.8/site-packages/arcade/application.py", line 481, in set_caption&#xA;    super().set_caption(caption)&#xA;  File "/home/iddos/.local/share/virtualenvs/immortals-SS7Euna6/lib/python3.8/site-packages/pyglet/window/xlib/__init__.py", line 511, in set_caption&#xA;    self._set_text_property(&#x27;_NET_WM_NAME&#x27;, caption)&#xA;  File "/home/iddos/.local/share/virtualenvs/immortals-SS7Euna6/lib/python3.8/site-packages/pyglet/window/xlib/__init__.py", line 785, in _set_text_property&#xA;    raise XlibException(&#x27;Could not create UTF8 text property&#x27;)&#xA;pyglet.window.xlib.XlibException: Could not create UTF8 text property&#xA;</module>

  


  And also this ffmpeg not found error, altough ffmpeg is in /usr/bin/ffmpeg

  


  Unable to find match for ffmpeg sound library at expected location: /home/iddos/.local/share/virtualenvs/immortals-SS7Euna6/lib64/python3.8/site-packages/pyglet_ffmpeg2/linux_x86_64/libavfilter.so.7.


  


  I would love to get some help from you guys since i didn't find a solution for this yet.