Sur d’autres sites (5624)

• Updating SDL yuv Texture

  15 juin 2015, par madprogrammer2015

  I am receiving an H.264 video stream and successfully decoding it with FFMPEG. It can display the first frame of data but then after that the screen never updates. It just appears to become a static image. I am using YUV pixel format, and I am receiving it in that format as well. Also I am using SDL_UpdateYUVTexture().

  Here is my code :

  int main()
  
  {
  
      WORD wVersionRequested;
  
      WSADATA wsaData;
  
      int wsaerr;
  
  
  
      if (SDL_Init(SDL_INIT_EVERYTHING)) {
  
          fprintf(stderr, "Could not initialize SDL - %s\n", SDL_GetError());
  
          exit(1);
  
      }
  
  
  
      // Using MAKEWORD macro, Winsock version request 2.2
  
      wVersionRequested = MAKEWORD(2, 2);
  
  
  
      wsaerr = WSAStartup(wVersionRequested, &wsaData);
  
  
  
      if (wsaerr != 0)
  
      {
  
          /* Tell the user that we could not find a usable */
  
          /* WinSock DLL.*/
  
          printf("The Winsock dll not found!\n");
  
          return 0;
  
      }
  
      else
  
      {
  
          printf("The Winsock dll found!\n");
  
          printf("The status: %s.\n", wsaData.szSystemStatus);
  
      }
  
  
  
      /* Confirm that the WinSock DLL supports 2.2.*/
  
      /* Note that if the DLL supports versions greater    */
  
      /* than 2.2 in addition to 2.2, it will still return */
  
      /* 2.2 in wVersion since that is the version we      */
  
      /* requested.                                        */
  
      if (LOBYTE(wsaData.wVersion) != 2 || HIBYTE(wsaData.wVersion) != 2)
  
      {
  
          /* Tell the user that we could not find a usable */
  
          /* WinSock DLL.*/
  
          printf("The dll do not support the Winsock version %u.%u!\n", LOBYTE(wsaData.wVersion), HIBYTE(wsaData.wVersion));
  
          WSACleanup();
  
          return 0;
  
      }
  
      else
  
      {
  
          printf("The dll supports the Winsock version %u.%u!\n", LOBYTE(wsaData.wVersion), HIBYTE(wsaData.wVersion));
  
          printf("The highest version this dll can support: %u.%u\n", LOBYTE(wsaData.wHighVersion), HIBYTE(wsaData.wHighVersion));
  
      }
  
  
  
      ULONG              localif;
  
      /*INT Ret;
  
      HANDLE ThreadHandle;
  
      DWORD ThreadId;
  
      WSAEVENT AcceptEvent;
  
      char               buf[1024];
  
      int                buflen = 1024, rc, err;*/
  
  
  
      SOCKET s;
  
      SOCKET ns;
  
      SOCKADDR_IN        multi, safrom;
  
      int fromlen;
  
  
  
      int totalSize = 0;
  
  
  
      AVCodec *codec;
  
      AVCodecContext *codecContext;
  
      int frame;
  
      int got_picture;
  
      AVFrame *picture;
  
      AVPacket packet;
  
      SwsContext* convertContext;
  
      uint16_t i = 1;
  
      //std::queue<madproto> queue;
  
      //std::list<madproto> list;
  
      AVCodecParserContext *parser;
  
      std::vector buffer;
  
      //moodycamel::ConcurrentQueue<madproto> protoQueue;
  
  
  
      SDL_Window *window;
  
      SDL_Renderer *renderer;
  
      SDL_Texture *bmp;
  
      SDL_Rect rect;
  
  
  
      file.open("log.txt");
  
  
  
      s = socket(AF_INET, SOCK_STREAM, IPPROTO_RM);
  
  
  
      multi.sin_family = AF_INET;
  
      multi.sin_port = htons(5150);
  
      multi.sin_addr.s_addr = inet_addr("234.5.6.7");
  
      int bindResult = bind(s, (PSOCKADDR)&amp;multi, sizeof(multi));
  
  
  
      if (bindResult &lt; 0)
  
      {
  
          std::cout &lt;&lt; "bindResult: " &lt;&lt; WSAGetLastError() &lt;&lt; std::endl;
  
      }
  
  
  
      listen(s, 10);
  
  
  
      //if ((AcceptEvent = WSACreateEvent()) == WSA_INVALID_EVENT)
  
      //{
  
      //  printf("WSACreateEvent() failed with error %d\n", WSAGetLastError());
  
      //  return 1;
  
      //}
  
      //else
  
      //  printf("WSACreateEvent() is OK!\n");
  
  
  
      //// Create a worker thread to service completed I/O requests
  
      //if ((ThreadHandle = CreateThread(NULL, 0, WorkerThread, (LPVOID)AcceptEvent, 0, &amp;ThreadId)) == NULL)
  
      //{
  
      //  printf("CreateThread() failed with error %d\n", GetLastError());
  
      //  return 1;
  
      //}
  
      //else
  
      //  printf("CreateThread() should be fine!\n");
  
  
  
      localif = inet_addr("192.168.1.2");
  
      setsockopt(s, IPPROTO_RM, RM_ADD_RECEIVE_IF, (char *)&amp;localif, sizeof(localif));
  
  
  
      fromlen = sizeof(safrom);
  
      ns = accept(s, (SOCKADDR *)&amp;safrom, &amp;fromlen);
  
  
  
      closesocket(s);  // Don't need to listen anymore
  
  
  
      std::string received;
  
  
  
      av_register_all();
  
  
  
      int horizontal = 0;
  
      int vertical = 0;
  
  
  
      GetDesktopResolution(horizontal, vertical);
  
  
  
      codec = avcodec_find_decoder(CODEC_ID_H264);
  
      if (!codec) {
  
          std::cout &lt;&lt; "codec not found" &lt;&lt; std::endl;
  
          std::cin.get();
  
      }
  
  
  
      codecContext = avcodec_alloc_context3(codec);
  
  
  
      /*if (codec->capabilities &amp; CODEC_CAP_TRUNCATED)
  
          codecContext->flags |= CODEC_FLAG_TRUNCATED;*/
  
  
  
      //codecContext->flags |= CODEC_FLAG_LOW_DELAY;
  
      codecContext->flags2 |= CODEC_FLAG2_CHUNKS;
  
  
  
      codecContext->width = horizontal;
  
      codecContext->height = vertical;
  
      codecContext->codec_id = CODEC_ID_H264;
  
      codecContext->codec_type = AVMEDIA_TYPE_VIDEO;
  
      codecContext->pix_fmt = PIX_FMT_YUV420P;
  
      codecContext->thread_type = 0;
  
  
  
      if (avcodec_open2(codecContext, codec, NULL) &lt; 0) {
  
          std::cout &lt;&lt; "could not open codec" &lt;&lt; std::endl;
  
          std::cin.get();
  
      }
  
  
  
      convertContext = sws_getContext(
  
          codecContext->width,
  
          codecContext->height,
  
          PIX_FMT_RGB32,
  
          codecContext->width,
  
          codecContext->height,
  
          PIX_FMT_YUV420P,
  
          SWS_BICUBIC,
  
          NULL,
  
          NULL,
  
          NULL
  
          );
  
  
  
      parser = av_parser_init(CODEC_ID_H264);
  
  
  
      picture = av_frame_alloc();
  
  
  
      if (ns == INVALID_SOCKET)
  
      {
  
          std::cout &lt;&lt; "accept didn't work!" &lt;&lt; std::endl;
  
          std::cin.get();
  
      }
  
  
  
      /*if (WSASetEvent(AcceptEvent) == FALSE)
  
      {
  
          printf("WSASetEvent() failed with error %d\n", WSAGetLastError());
  
          return 1;
  
      }
  
      else
  
          printf("WSASetEvent() should be working!\n");*/
  
  
  
      window = SDL_CreateWindow("YUV", SDL_WINDOWPOS_UNDEFINED, SDL_WINDOWPOS_UNDEFINED, codecContext->width, codecContext->height, SDL_WINDOW_SHOWN);
  
      renderer = SDL_CreateRenderer(window, -1, 0);
  
      bmp = SDL_CreateTexture(renderer, SDL_PIXELFORMAT_IYUV, SDL_TEXTUREACCESS_STREAMING, codecContext->width, codecContext->height);
  
  
  
      //receive = SDL_CreateThread(receiveThread, "ReceiveThread", (void *)NULL);
  
      bool quit = false;
  
  
  
      rect.x = 0;
  
      rect.y = 0;
  
      rect.w = codecContext->width;
  
      rect.h = codecContext->height;
  
  
  
      while (!quit)
  
      {
  
          while (true)
  
          {
  
              MadProto proto;
  
              int result = recvfrom(ns, (char *)&amp;proto, sizeof(MadProto), 0, (struct sockaddr *)&amp;multi, &amp;fromlen);
  
  
  
              if (result &lt; 0)
  
              {
  
                  std::cout &lt;&lt; "receive failed! error: " &lt;&lt; WSAGetLastError() &lt;&lt; std::endl;
  
                  break;
  
              }
  
              else
  
              {
  
                  std::cout &lt;&lt; "receive successful, received " &lt;&lt; result &lt;&lt; " bytes" &lt;&lt; std::endl;
  
  
  
                  if (ntohs(proto.frame_end) == 1)
  
                  {
  
                      uint8_t *outbuffer = NULL;
  
                      int outBufSize = 0;
  
                      int rc = av_parser_parse2(parser, codecContext, &amp;outbuffer, &amp;outBufSize, buffer.data(), buffer.size(), 0, 0, 0);
  
  
  
                      if (outBufSize &lt;= 0)
  
                      {
  
                          std::cout &lt;&lt; "parsing failed!" &lt;&lt; std::endl;
  
                          std::cout &lt;&lt; "outBufSize: " &lt;&lt; outBufSize &lt;&lt; std::endl;
  
                          break;
  
                      }
  
  
  
                      if (rc)
  
                      {
  
                          std::cout &lt;&lt; "rc: " &lt;&lt; rc &lt;&lt; std::endl;
  
                          std::cout &lt;&lt; "parsing successful!" &lt;&lt; std::endl;
  
                          //std::cin.get();
  
  
  
                          av_init_packet(&amp;packet);
  
                          packet.size = outBufSize;
  
                          packet.data = outbuffer;
  
  
  
                          frame = avcodec_decode_video2(codecContext, picture, &amp;got_picture, &amp;packet);
  
  
  
                          if (frame &lt; 0)
  
                          {
  
                              std::cout &lt;&lt; "decoding was unsuccessful!" &lt;&lt; std::endl;
  
                              break;
  
                          }
  
  
  
                          if (got_picture)
  
                          {
  
                              std::cout &lt;&lt; "decoding was successful!" &lt;&lt; std::endl;
  
                              std::cout &lt;&lt; "decoded length was: " &lt;&lt; frame &lt;&lt; std::endl;
  
                              buffer.empty();
  
  
  
                              //std::cin.get();
  
                              int code = SDL_UpdateYUVTexture(bmp, NULL, picture->data[0], picture->linesize[0],
  
                                  picture->data[1], picture->linesize[1],
  
                                  picture->data[2], picture->linesize[2]);
  
  
  
                              if (code &lt; 0)
  
                              {
  
                                  std::cout &lt;&lt; "unable to update texture " &lt;&lt; SDL_GetError() &lt;&lt; std::endl;
  
                                  std::cin.get();
  
                              }
  
  
  
                              code = SDL_RenderClear(renderer);
  
  
  
                              if (code &lt; 0)
  
                              {
  
                                  std::cout &lt;&lt; "renderer clear failed " &lt;&lt; SDL_GetError() &lt;&lt; std::endl;
  
                                  std::cin.get();
  
                              }
  
  
  
                              code = SDL_RenderCopy(renderer, bmp, NULL, &amp;rect);
  
  
  
                              if (code &lt; 0)
  
                              {
  
                                  std::cout &lt;&lt; "renderer copy failed " &lt;&lt; SDL_GetError() &lt;&lt; std::endl;
  
                                  std::cin.get();
  
                              }
  
  
  
                              SDL_RenderPresent(renderer);
  
  
  
                              SDL_Delay(40);
  
                          }
  
  
  
                          av_free_packet(&amp;packet);
  
                      }
  
                  }
  
                  else
  
                  {
  
                      std::copy(proto.payload, proto.payload + ntohs(proto.nal_length), std::back_inserter(buffer));
  
                      std::cout &lt;&lt; "frame is continuing!" &lt;&lt; std::endl;
  
  
  
                      //queue.push(proto);
  
                      //list.push_front(proto);
  
                  }
  
              }
  
          }
  
  
  
          SDL_WaitEvent(&amp;event);
  
          switch (event.type)
  
          {
  
          case SDL_QUIT:
  
              quit = true;
  
              break;
  
          }
  
      }
  
  
  
      std::cout &lt;&lt; "closing everything!" &lt;&lt; std::endl;
  
      av_frame_free(&amp;picture);
  
      closesocket(ns);
  
      fclose(f);
  
      std::cin.get();
  
      return 0;
  
  }
  
  </madproto></madproto></madproto>

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

• Vedanti and Max Sound vs. Google

  14 août 2014, par Multimedia Mike — Legal/Ethical

  Vedanti Systems Limited (VSL) and Max Sound Coporation filed a lawsuit against Google recently. Ordinarily, I wouldn’t care about corporate legal battles. However, this one interests me because it’s multimedia-related. I’m curious to know how coding technology patents might hold up in a real court case.

  Here’s the most entertaining complaint in the lawsuit :

  Despite Google’s well-publicized Code of Conduct — “Don’t be Evil” — which it explains is “about doing the right thing,” “following the law,” and “acting honorably,” Google, in fact, has an established pattern of conduct which is the exact opposite of its claimed piety.

  I wonder if this is the first known case in which Google has been sued over its long-obsoleted “Don’t be evil” mantra ?

  Researching The Plaintiffs
  
  I think I made a mistake by assuming this lawsuit might have merit. My first order of business was to see what the plaintiff organizations have produced. I have a strong feeling that these might be run of the mill patent trolls.

  VSL currently has a blank web page. Further, the Wayback Machine only has pages reaching back to 2011. The earliest page lists these claims against a plain black background (I’ve highlighted some of the more boisterous claims and the passages that make it appear that Vedanti doesn’t actually produce anything but is strictly an IP organization) :

  The inventions key :
  The patent and software reduced any data content, without compressing, up to a 97% total reduction of the data which also produces a lossless result. This physics based invention is often called the Holy Grail.

  Vedanti Systems Intellectual Property
  Our strategic IP portfolio is granted in all of the world’s largest technology development and use countries. A major value indemnification of our licensee products is the early date of invention filing and subsequent Issue. Vedanti IP has an intrinsic 20 year patent protection and valuation in royalties and licensing. The original data transmission art has no prior art against it.

  Vedanti Systems invented among other firsts, The Slice and Partitioning of Macroblocks within a RGB Tri level region in a frame to select or not, the pixel.

  Vedanti Systems invention is used in nearly every wireless chipset and handset in the world

  Our original pixel selection system revolutionized wireless handset communications. An example of this system “Slice” and “Macroblock Partitioning” is used throughout Satellite channel expansion, Wireless partitioning, Telecom – Video Conferencing, Surveillance Cameras, and 2010 developing Media applications.

  Vedanti Systems is a Semiconductor based software, applications, and IP Continuations Intellectual Property company.

  Let’s move onto the other plaintiff, Max Sound. They have a significantly more substantive website. They also have an Android app named Spins HD Audio, which appears to be little more than a music player based on the screenshots.

  Max Sound also has a stock ticker symbol : MAXD. Something clicked into place when I looked up their ticker symbol : While worth only a few pennies, it was worth a few more pennies after this lawsuit was announced, which might be one of the motivations behind the lawsuit.

  Here’s a trick I learned when I was looking for a new tech job last year : When I first look at a company’s website and am trying to figure out what they really do, I head straight to their jobs/careers page. A lot of corporate websites have way too much blathering corporatese that can be tough to cut through. But when I see what mix of talent and specific skills they are hoping to hire, that gives me a much better portrait of what the company does.

  The reason I bring this up is because this tech company doesn’t seem to have jobs/careers page.

  The Lawsuit
  The core complaint centers around Patent 7974339 : Optimized data transmission system and method. It was filed in July 2004 (or possibly as early as January 2002), issued in July 2011, and assigned (purchased ?) by Vedanti in May 2012. The lawsuit alleges that nearly everything Google has ever produced (or, more accurately, purchased) leverages the patented technology.

  The patent itself has 5 drawings. If you’ve ever seen a multimedia codec patent, or any whitepaper on a multimedia codec, you’ve seen these graphs before. E.g., “Raw pixels come in here -> some analysis happens here -> more analysis happens over here -> entropy coding -> final bitstream”. The text of a patent document isn’t meant to be particularly useful. I’ve tried to understand this stuff before and it never goes well. Skimming the text, I just see a blur of the words data, transmission, pixel, and matrix.

  So I read the complaint to try to figure out what this is all about. To summarize the storyline as narrated by the lawsuit, some inventors were unhappy with the state of video compression in 2001 and endeavored to create something better. So they did, and called it the VSL codec. This codec is so far undocumented on the MultimediaWiki, so it probably has yet to be seen “in the wild”. Good luck finding hard technical data on it now since searches for “VSL codec” are overwhelmed by articles about this lawsuit. Also, the original codec probably wasn’t called VSL because VSL is apparently an IP organization formed much later.

  Then, the protagonists of the lawsuit patented the codec. Then, years later, Google wanted to purchase a video codec that they could open source and use to supplant H.264.

  The complaint goes on to allege that in 2010, Google specifically contacted VSL to possibly license or acquire this mysterious VSL technology. Google was allegedly allowed to study the technology, eventually decided not to continue discussions, and shipped back the proprietary materials.

  Here’s where things get weird. When Google shipped back the materials, they allegedly shipped back a bunch of Post-It notes. The notes are alleged to contain a ton of incriminating evidence. The lawsuit claims that the notes contained such tidbits as :

  • Google was concerned that its infringement could be considered “recklessness” (the standard applicable to willful infringement) ;
  • Google personnel should “try” to destroy incriminating emails ;
  • Google should consider a “design around” because it was facing a “risk of litigation.”

  Actually, given Google’s acquisition of On2, I can totally believe that last one (On2’s codecs have famously contained a lot of weirdness which is commonly suspected to be attributable to designing around known patents).

  Anyway, a lot of this case seems to hinge on the authenticity of these Post-It notes :

  “65. The Post-It notes are unequivocal evidence of Google’s knowledge of the ’339 Patent and infringement by Defendants”

  I wish I could find a stock photo of a stack of Post-It notes in an evidence bag.

  I’ve worked at big technology companies. Big tech companies these days are very diligent about indoctrinating employees about IP liability issues. The reason this Post-It situation strikes me as odd is because the alleged contents of the notes basically outline everything the corporate lawyers tell you NOT to do.

  Analysis
  I’m trying to determine what specific algorithms and coding techniques. I guess I was expecting to see a specific claim that, “Our patent outlines this specific coding technique and here is unequivocal proof that Google A) uses the same technique, and B) specifically did so after looking at our patent.” I didn’t find that (well, a bit of part B, c.f., the Post-It note debacle), but maybe that’s not how these patent lawsuits operate. I’ve never kept up before.

  Maybe it’s just a patent troll. Maybe it’s for the stock bump. I’m expecting to see pump-n-dump stock spam featuring the stock symbol MAXD anytime now.

  I’ve never been interested in following a lawsuit case carefully before. I suddenly find myself wondering if I can subscribe to the RSS feed for this case ? Too much to hope for. But I found this item through Pando and maybe they’ll stay on top of it.