Recherche avancée

Sur d’autres sites (7649)

• ffplay cannot play more than one song

  5 février 2020, par Bernie gach

  i have taken ffplay.c file from http://ffmpeg.org/doxygen/trunk/ffplay_8c-source.html and re edited it to a cpp file to embed in my win32 gui application . i have made the following changes to it.

  1. made the int main function into a local function as follows, i can pass the HWND to embedd the player

  void Ffplay::play_song(string file, HWND parent, bool* successfull)
  
  {
  
      int flags;
  
      VideoState* is;
  
      input_filename = file; 
  
      /* register all codecs, demux and protocols */
  
  #if CONFIG_AVDEVICE
  
      avdevice_register_all();
  
  #endif
  
      //avformat_network_init();
  
      //check whether the filename is valid
  
      if (input_filename.empty())
  
      {
  
          logger.log(logger.LEVEL_ERROR, "filename %s is not valid\n", file);
  
          return;
  
      }
  
      if (display_disable)
  
      {
  
          video_disable = 1;
  
      }
  
      flags = SDL_INIT_VIDEO | SDL_INIT_AUDIO | SDL_INIT_TIMER;
  
      if (audio_disable)
  
          flags &= ~SDL_INIT_AUDIO;
  
      else
  
      {
  
          /* Try to work around an occasional ALSA buffer underflow issue when the
  
           * period size is NPOT due to ALSA resampling by forcing the buffer size. */
  
          if (!SDL_getenv("SDL_AUDIO_ALSA_SET_BUFFER_SIZE"))
  
              SDL_setenv("SDL_AUDIO_ALSA_SET_BUFFER_SIZE", "1", 1);
  
      }
  
      if (display_disable)
  
          flags &= ~SDL_INIT_VIDEO;
  
      SDL_SetMainReady();
  
      if (SDL_Init(flags))
  
      {
  
          logger.log(logger.LEVEL_ERROR, "Could not initialize SDL - %s\n", SDL_GetError());
  
          logger.log(logger.LEVEL_ERROR, "(Did you set the DISPLAY variable?)\n");
  
          return;
  
      }
  
      //Initialize optional fields of a packet with default values.
  
      //Note, this does not touch the data and size members, which have to be initialized separately.
  
      av_init_packet(&flush_pkt);
  
      flush_pkt.data = (uint8_t*)&flush_pkt;
  
  
  
      if (!display_disable)
  
      {
  
          int flags = SDL_WINDOW_HIDDEN;
  
          if (alwaysontop)
  
  #if SDL_VERSION_ATLEAST(2,0,5)
  
              flags |= SDL_WINDOW_ALWAYS_ON_TOP;
  
  #else
  
              logger.log(logger.LEVEL_INFO, "SDL version doesn't support SDL_WINDOW_ALWAYS_ON_TOP. Feature will be inactive.\n");
  
  #endif
  
          if (borderless)
  
              flags |= SDL_WINDOW_BORDERLESS;
  
          else
  
              flags |= SDL_WINDOW_RESIZABLE;
  
          SDL_InitSubSystem(flags);
  
          ShowWindow(parent, true);
  
          //window = SDL_CreateWindow(program_name, SDL_WINDOWPOS_UNDEFINED, SDL_WINDOWPOS_UNDEFINED, default_width, default_height, flags);
  
          window = SDL_CreateWindowFrom(parent);
  
          SDL_SetHint(SDL_HINT_RENDER_SCALE_QUALITY, "linear");
  
          if (window) {
  
              renderer = SDL_CreateRenderer(window, -1, SDL_RENDERER_ACCELERATED | SDL_RENDERER_PRESENTVSYNC);
  
              if (!renderer)
  
              {
  
                  logger.log(logger.LEVEL_ERROR, "Failed to initialize a hardware accelerated renderer: %s\n", SDL_GetError());
  
                  renderer = SDL_CreateRenderer(window, -1, 0);
  
              }
  
              if (renderer)
  
              {
  
                  if (!SDL_GetRendererInfo(renderer, &renderer_info))
  
                  {
  
                      logger.log(logger.LEVEL_INFO, "Initialized %s renderer.\n", renderer_info.name);
  
                  }
  
              }
  
          }
  
          if (!window || !renderer || !renderer_info.num_texture_formats)
  
          {
  
              logger.log(logger.LEVEL_ERROR, "Failed to create window or renderer: %s\n", SDL_GetError());
  
              return;
  
          }
  
      }
  
  
  
      is = stream_open(input_filename.c_str(), file_iformat);
  
      if (!is)
  
      {
  
          logger.log(logger.LEVEL_ERROR, "Failed to initialize VideoState!\n");
  
          return;
  
      }
  
      //the song is playing now
  
      *successfull = true;
  
      event_loop(is);
  
      //the song has quit;
  
      *successfull = false;
  
  }

  2. changed the callback functions as the static ones couldn’t be used by c++ eg,

  void Ffplay::static_sdl_audio_callback(void* opaque, Uint8* stream, int len)
  
  {
  
      static_cast(opaque)->sdl_audio_callback(opaque, stream, len);
  
  }

  closing doesn’t change from the main file to close the audio and sdl framework

  void Ffplay::do_exit(VideoState* is)
  
  {
  
      abort = true;
  
      if(is)
  
      {
  
          stream_close(is);
  
      }
  
      if (renderer)
  
          SDL_DestroyRenderer(renderer);
  
      if (window)
  
           SDL_DestroyWindow(window);
  
  #if CONFIG_AVFILTER
  
      av_freep(&vfilters_list);
  
  #endif
  
      avformat_network_deinit();
  
      SDL_Quit();
  
  
  
  }

  i call the functions as follows from main gui

  ft=std::async(launch::async, &Menu::play_song, this, songs_to_play.at(0));

  the menu::play_song function is :

  void Menu::play_song(wstring song_path)
  
  {
  
      ready_to_play_song = false;
  
      OutputDebugString(L"\nbefore song\n");
  
      using std::future;
  
      using std::async;
  
      using std::launch;
  
  
  
      string input{ song_path.begin(),song_path.end() };
  
      Ffplay ffplay;
  
      ffplay.play_song(input, h_sdl_window, &song_opened);
  
  
  
      OutputDebugString(L"\nafter song\n");
  
      ready_to_play_song = true;
  
  }

  THE PROBLEM is i can only play one song . if i call the menu::play_song function again the sound is missing and the video/art cover is occasionally missing also. it seems some resources are not been released or something like that.

  i have localised the proble to this function

  int Ffplay::packet_queue_get(PacketQueue* q, AVPacket* pkt, int block, int* serial)
  
  {
  
  
  
      MyAVPacketList* pkt1;
  
      int ret;
  
      int count=0;
  
      SDL_LockMutex(q->mutex);
  
  
  
      for (;;) 
  
      {
  
  
  
  
  
          if (q->abort_request)
  
          {
  
              ret = -1;
  
              break;
  
          }
  
  
  
          pkt1 = q->first_pkt;
  
          if (pkt1) {
  
              q->first_pkt = pkt1->next;
  
              if (!q->first_pkt)
  
                  q->last_pkt = NULL;
  
              q->nb_packets--;
  
              q->size -= pkt1->pkt.size + sizeof(*pkt1);
  
              q->duration -= pkt1->pkt.duration;
  
              *pkt = pkt1->pkt;
  
              if (serial)
  
                  *serial = pkt1->serial;
  
              av_free(pkt1);
  
              ret = 1;
  
              break;
  
          }
  
          else if (!block) {
  
              ret = 0;
  
              break;
  
          }
  
          else 
  
          {
  
              logger.log(logger.LEVEL_INFO, "packet_queue before");
  
              SDL_CondWait(q->cond, q->mutex);
  
              logger.log(logger.LEVEL_INFO, "packet_queue after");
  
  
  
          }
  
      }
  
      SDL_UnlockMutex(q->mutex);
  
      return ret;
  
  }

  the call to SDL_CondWait(q->cond, q->mutex); never returns

• Matomo SSO options and why is it useful ?

  8 novembre 2017, par Matomo Core Team — Plugins

  Bored with typing again and again different logins and passwords for each service you have access to ? Would you like to add hundreds or thousands of users with different roles to your Matomo (Piwik) at once ? Would you like to save time and effort of managing your users while increasing the security in your business ? Guess what, Matomo has come up with great features to do just that.

  But what is a SSO ?

  Before introducing you to new Matomo (Piwik) features, let me explain what a SSO is.
  SSO is the acronym for Single Sign On. As its name suggests this authentication process allows a user to access multiple applications with one set of login credentials.

  Advantages of using a SSO are numerous :

  • improving security, for example when an employee is leaving your company, how can you check that all his credentials have been removed ?
  • reducing employees time-wasters such as having to enter logins/passwords each time.
  • providing a centralized database for administrators. They can then easily manage permissions of all employees saving them heaps of time.
  • reduces support costs related to authentication / accounts management.

  In order to provide SSO options, two Matomo (Piwik) plugins have been developed and are available on the marketplace :

  • SAML
  • LDAP

  SAML

  

  SAML stands for “Security Assertion Markup Language”, it is a standard in order to exchange authentication and authorization between an identity provider (OneLogin, Okta, Ping Identity, ADFS, Google, Salesforce, SharePoint…) and a service provider.
  An identity provider is an online service that authenticates users on the Internet by using security tokens.

  Are you wondering if your business or organization is using any of these providers ? We recommend to ask your operations team or sysadmin.

  At InnoCraft, we developed a plugin in order to allow SSO with SAML for Matomo (Piwik). It can ensure consistent access control across the enterprise and external providers, potentially reducing support costs related to authentication and accounts management.

  The installation process is straightforward. All you need is to get the SAML premium feature from the marketplace. Once installed, you will access the SAML configuration interface through the admin where you can configure various settings :

  • SAML Status
  • Identity Provider (Entity ID, SSO endpoint info, Public x509 certificate)
  • Just-in-time provisioning and Mapping attributes
  • Access Synchronization
  • Advanced settings

  

  From there you will need to follow our detailed documentation to have it up and running :
  https://matomo.org/docs/login-saml/.
  Once finished, you will then be able to use SAML to authenticate to your Matomo (Piwik) account :

  

  As all premium features, SAML is eligible to a 30-day period money back guarantee, so do not hesitate to have it a try.

  LDAP

  

  LDAP stands for Lightweight Directory Access Protocol. As its names implies LDAP is a directory, hosted on a server, which organizes the data about people in your company.
  Thanks to the LDAP plugin, Matomo (Piwik) can be connected to your LDAP infrastructure and then use all its power in order to give each individual an access with different rights according to their needs.

  Let’s say that you have 1,000 employees within a company and they all need right now an access to the analytics reports in Matomo (Piwik) with different roles. This is what LDAP can do.

  Moreover if your business or organization is already using LDAP, we recommend using the LDAP connector for Matomo (Piwik) for better security, to stop wasting time of your users and sysadmins, and to reduce the costs related to account management.

  You understood it well. LDAP is a plugin which saves a LOT of time within an organization. Here is a preview of the settings part :

  

  LDAP has been developed by the Matomo (Piwik) core team and is available as a Free plugin on the marketplace.

  Try it now within the marketplace

  If you are surprised by the possibilities that Matomo (Piwik) is offering in terms of plugins, the good news is that many other plugins are waiting for you on the marketplace. Check out our premium marketplace which offers state-of-the-art plugins to get the most out of Matomo.

  And if you are a developer feel free to create your own plugin, a detailed documentation is available at : https://developer.matomo.org/guides/getting-started-part-1.

• Piwik SSO options and why is it useful ?

  8 novembre 2017, par Piwik Core Team — Plugins

  Bored with typing again and again different logins and passwords for each service you have access to ? Would you like to add hundreds or thousands of users with different roles to your Piwik at once ? Would you like to save time and effort of managing your users while increasing the security in your business ? Guess what, Piwik has come up with great features to do just that.

  But what is a SSO ?

  Before introducing you to new Piwik features, let me explain what a SSO is.
  SSO is the acronym for Single Sign On. As its name suggests this authentication process allows a user to access multiple applications with one set of login credentials.

  Advantages of using a SSO are numerous :

  • improving security, for example when an employee is leaving your company, how can you check that all his credentials have been removed ?
  • reducing employees time-wasters such as having to enter logins/passwords each time.
  • providing a centralized database for administrators. They can then easily manage permissions of all employees saving them heaps of time.
  • reduces support costs related to authentication / accounts management.

  In order to provide SSO options, two Piwik plugins have been developed and are available on the marketplace :

  • SAML
  • LDAP

  SAML

  

  SAML stands for “Security Assertion Markup Language”, it is a standard in order to exchange authentication and authorization between an identity provider (OneLogin, Okta, Ping Identity, ADFS, Google, Salesforce, SharePoint…) and a service provider.
  An identity provider is an online service that authenticates users on the Internet by using security tokens.

  Are you wondering if your business or organization is using any of these providers ? We recommend to ask your operations team or sysadmin.

  At InnoCraft, we developed a plugin in order to allow SSO with SAML for Piwik. It can ensure consistent access control across the enterprise and external providers, potentially reducing support costs related to authentication and accounts management.

  The installation process is straightforward. All you need is to get the SAML premium feature from the marketplace. Once installed, you will access the SAML configuration interface through the admin where you can configure various settings :

  • SAML Status
  • Identity Provider (Entity ID, SSO endpoint info, Public x509 certificate)
  • Just-in-time provisioning and Mapping attributes
  • Access Synchronization
  • Advanced settings

  

  From there you will need to follow our detailed documentation to have it up and running :
  https://piwik.org/docs/login-saml/.
  Once finished, you will then be able to use SAML to authenticate to your Piwik account :

  

  As all premium features, SAML is eligible to a 30-day period money back guarantee, so do not hesitate to have it a try.

  LDAP

  

  LDAP stands for Lightweight Directory Access Protocol. As its names implies LDAP is a directory, hosted on a server, which organizes the data about people in your company.
  Thanks to the LDAP plugin, Piwik can be connected to your LDAP infrastructure and then use all its power in order to give each individual an access with different rights according to their needs.

  Let’s say that you have 1,000 employees within a company and they all need right now an access to the analytics reports in Piwik with different roles. This is what LDAP can do.

  Moreover if your business or organization is already using LDAP, we recommend using the LDAP connector for Piwik for better security, to stop wasting time of your users and sysadmins, and to reduce the costs related to account management.

  You understood it well. LDAP is a plugin which saves a LOT of time within an organization. Here is a preview of the settings part :

  

  LDAP has been developed by the Piwik core team and is available as a Free plugin on the marketplace.

  Try it now within the marketplace

  If you are surprised by the possibilities that Piwik is offering in terms of plugins, the good news is that many other plugins are waiting for you on the marketplace. Check out our premium marketplace which offers state-of-the-art plugins to get the most out of Piwik.

  And if you are a developer feel free to create your own plugin, a detailed documentation is available at : https://developer.piwik.org/guides/getting-started-part-1.