Recherche avancée

Sur d’autres sites (7540)

• what is the good function php to deal with ffmpeg and progress bar [duplicate]

  17 mai 2014, par Abed Soliman

  This question already has an answer here :

  • ffmpeg Progress Bar - Encoding Percentage in PHP
    
    2 answers
    

  I ask about ffmpeg and progressbar

  I used exec function with ffmpeg and output the result to txt file

  and using some of code I found here to

  <center>
  
  
  
  
  
  
  
      &lt;?php 
  
  
  
      define('RAPIDLEECH', 'yes');
  
      define('CONFIG_DIR', 'configs/');
  
      require_once('configs/config.php');
  
      define ( 'TEMPLATE_DIR', 'templates/'.$options['template_used'].'/' );
  
      // Include other useful functions
  
      require_once('classes/other.php');
  
      error_reporting(0);
  
  
  
      login_check();
  
  
  
      include(TEMPLATE_DIR.'header.php');
  
  
  
      echo ('<br /><br /><br /><b>AudioXtractor</b>, un complemento <br /> que te permite extraer el audio de tus videos.<br /><br /><br />');
  
  
  
      putenv('GDFONTPATH=' . realpath('.')); ?>
  
  
  
      <br />
  
  
  
      <form method="post"><center>
  
      <table>
  
        <td>Movie:
  
      <select>
  
  
  
      &lt;?php
  
      $exts=array(".ac3", ".avi", ".f4v", ".flv", ".mkv", ".mov", ".mp4", ".mpg", ".mpeg", ".rmvb", ".srt", ".swf", ".wav", ".wmv");
  
      $ext="";
  
      function vidlist($dir) 
  
      {
  
      $results = array();
  
      $handler = opendir($dir);
  
      while ($file = readdir($handler)) 
  
      {
  
      if (strrchr($file,'.')!="")
  
      {
  
      $ext=strtolower(strrchr($file,'.'));
  
      }
  
      if ($file != '.' &amp;&amp; $file != '..' &amp;&amp; in_array($ext,$GLOBALS["exts"]))
  
      {
  
      $results[] = $file;
  
      }
  
      }
  
      closedir($handler);
  
      sort($results);
  
      return $results;
  
      }
  
      function Output($command) {
  
      $output = array($command);
  
      exec($command.' 2>&amp;1', $output);
  
      return ($output);
  
      }
  
      $files = vidlist("./files/");
  
      foreach($files as $file)
  
      {
  
          echo '<option value="'.$file.'">'.$file.'</option>';
  
      }
  
  
  
      ?>
  
  
  
  
  
      </select></td></table>
  
  
  
      <br /> >
  
      New MP3's name: 
  
      <input type="text" value="nuevoaudio" /> 
  
      <br /> >
  
      <br />
  
      <br />
  
  
  
      <center><input type="submit" style="font-size:16px; font-weight:bold; cursor:pointer;" value="Extract" />
  
      
  
  
  
      </center></center></form>
  
  
  
  
  
      &lt;?php
  
      if ($_POST['video']!="")
  
  
  
          $video = 'files/';
  
          $video=array();     
  
          $video[0] = $_POST['video'];
  
  
  
      if ($_POST['nvdo']!="")
  
  
  
          $nvdo = 'files/';
  
          $nvdo=array();      
  
          $nvdo[0] = $_POST['nvdo'];
  
  
  
  
  
  
  
      foreach ($video as $vdo)
  
      foreach ($nvdo as $nvd)
  
  
  
      if (isset($_POST["analize"])) {
  
  
  
          exec("ffmpeg -i files/$vdo -ab 192k files/$nvd.mp3 -y 2> files/$nvd.txt");
  
  
  
          $ext=strtolower(strrchr($vdo,'.'));
  
  
  
      /////////////////////////////////////////////////////my code //////////////////////////////////////////
  
  
  
      $content = @file_get_contents("files/$nvd.txt");
  
  
  
  
  
          //get duration of source
  
          preg_match("/Duration: (.*?), start:/", $content, $matches);
  
  
  
          $rawDuration = $matches[1];
  
  
  
          //rawDuration is in 00:00:00.00 format. This converts it to seconds.
  
          $ar = array_reverse(explode(":", $rawDuration));
  
          $duration = floatval($ar[0]);
  
          if (!empty($ar[1])) $duration += intval($ar[1]) * 60;
  
          if (!empty($ar[2])) $duration += intval($ar[2]) * 60 * 60;
  
  
  
          //get the time in the file that is already encoded
  
          preg_match_all("/time=(.*?) bitrate/", $content, $matches);
  
  
  
          $rawTime = array_pop($matches);
  
  
  
          //this is needed if there is more than one match
  
          if (is_array($rawTime)){$rawTime = array_pop($rawTime);}
  
  
  
          //rawTime is in 00:00:00.00 format. This converts it to seconds.
  
          $ar = array_reverse(explode(":", $rawTime));
  
          $time = floatval($ar[0]);
  
          if (!empty($ar[1])) $time += intval($ar[1]) * 60;
  
          if (!empty($ar[2])) $time += intval($ar[2]) * 60 * 60;
  
  
  
          //calculate the progress
  
          $progress = round(($time/$duration) * 100);
  
  
  
  
  
  
  
  
  
          echo '<br /><br />¡Su video fue convertido correctamente! <br /><br />Link al archivo:';
  
  
  
          echo ' <a href="http://stackoverflow.com/feeds/tag/files/'.$nvd.'.mp3">'.$nvd.'.mp3</a><br />' . "<br />";
  
          echo "Duration: " . $duration . "<br />";
  
          echo "Current Time: " . $time . "<br />";
  
          echo "Progress: " . $progress . "%" . "<br />";
  
  
  
      //////////////////////////////////////my coed //////////////////////////////////////////////
  
      }
  
  
  
      ?>
  
      <br /><br /><a href="http://stackoverflow.com/feeds/tag/index.php">Volver al RapidLeech</a>
  
  
  
      <br /><br /><br />Formatos Aceptados: <br /><b>.ac3, .avi, .f4v, .flv, .mkv, .mov, .mp3,<br /> .mp4, .mpg, .mpeg, .rmvb, .srt, .swf, .wav, .wmv</b>
  
      <br /><br />
  
      </center>
  
  
  
      &lt;?php
  
  
  
  
  
  
  
      ?>

  so i ask some one he told me the exec stop php script and never give me

  You can't get the progress directly if you are using exec, because the php script is stopped until ffmpeg closes. (Because exec returns the whole execution output)
  
  
  
  You should use popen, for being able to get the output from the process in real time (without reading any file) for parse and show the progressbar
  
  
  
  Here is a example for get the output: 
  
  
  
  When you get the progress info from ffmpeg, you can use your code for parse it and show your progressbar

  this is my popen script

  <?php 
  
  
  
  $handle = popen ("ffmpeg.exe -i files/fz.mp4 -ab 192k files/vdf.mp3 2>&1 ", 'r');
  
  $handles = (string)$handle;
  
  $line = "";
  
  
  
  while (false !== ($char = fgetc($handle)))
  
  {
  
    if ($char == "\r")
  
    {
  
      // You could now parse the $line for status information.
  
      echo "$line\n";
  
      $line = "";
  
    } else {
  
      $line .= $char;
  
    }
  
    ob_flush();
  
    flush();
  
  }
  
  pclose ($handle);
  
  
  
  
  
      //get duration of source
  
      preg_match("/Duration: (.*?), start:/", $handles, $matches);
  
  
  
      $rawDuration = $matches[1];
  
  
  
      //rawDuration is in 00:00:00.00 format. This converts it to seconds.
  
      $ar = array_reverse(explode(":", $rawDuration));
  
      $duration = floatval($ar[0]);
  
      if (!empty($ar[1])) $duration += intval($ar[1]) * 60;
  
      if (!empty($ar[2])) $duration += intval($ar[2]) * 60 * 60;
  
  
  
      //get the time in the file that is already encoded
  
      preg_match_all("/time=(.*?) bitrate/", $handles, $matches);
  
  
  
      $rawTime = array_pop($matches);
  
  
  
      //this is needed if there is more than one match
  
      if (is_array($rawTime)){$rawTime = array_pop($rawTime);}
  
  
  
      //rawTime is in 00:00:00.00 format. This converts it to seconds.
  
      $ar = array_reverse(explode(":", $rawTime));
  
      $time = floatval($ar[0]);
  
      if (!empty($ar[1])) $time += intval($ar[1]) * 60;
  
      if (!empty($ar[2])) $time += intval($ar[2]) * 60 * 60;
  
  
  
      //calculate the progress
  
      $progress = round(($time/$duration) * 100);
  
  
  
  
  
  
  
  
  
      echo '<br /><br />¡Su video fue convertido correctamente! <br /><br />Link al archivo:';
  
  
  
  
  
      echo "Duration: " . $duration . "<br />";
  
      echo "Current Time: " . $time . "<br />";
  
      echo "Progress: " . $progress . "%" . "<br />";
  
  
  
  //////////////////////////////////////my coed //////////////////////////////////////////////
  
  
  
  ?>

  so i dont under stand what is good for ffmpeg progressbAR

  is exec or popen

  so please give me hints for ffmpeg real time progressbar

  what is good for progressbar

  is html5 progress bar

  or javascript progress bar

• Your guide to cookies, web analytics, and GDPR compliance

  25 février 2020, par Joselyn Khor — Analytics Tips, Privacy, Security
  It’s been almost two years since the GDPR came into effect and turned the online world on its head. Confusion around cookies/cookie consent/cookie compliance remains till today. So we’d like to take this chance to talk more about the supposed “big bad” of the latest century. 

  Online cookies seem to have a bad reputation, but are they as bad as they seem ?

  To start, what are cookies on the internet ?

  An internet cookie a.k.a. an HTTP cookie, is a small piece of data sent from websites that is stored on your computer or mobile when you visit that site.

  Are all cookies bad ?

  No. Cookies themselves are usually harmless as they can’t infect computers with malware. 

  They can also be helpful for both websites who use them and individuals visiting those websites. For example, when online shopping, cookies on ecommerce sites keep track of what you’re shopping for. If you didn’t have that tracking, your cart would be empty every time you moved away from that site.

  For businesses/websites, cookies can be used for authentication (logins) and tracking website user experience. For example, tracking multiple visits to the same site in order to provide better experiences to customers visiting their website.

  

  The not-so-sweet types of cookies :

  Cookies that contain personal data

  Another example of a bad cookie is when cookies contain personal data directly in the cookie itself. For example, when websites store demographics or your name in a cookie ; or when a website stores survey results in a cookie. Use of cookies in these ways is considered bad practice nowadays.

  Third-party cookies
  

  They can be used by websites to learn about your visit and activity across multiple websites. Cookies can enter harmful territory when employed for “big brother” types of tracking i.e. when they’re used to build a virtual fingerprint of individuals after their activity is tracked from website to website. For example most advertising networks create third party cookies in your browser when you view an ad, which lets these advertisers track users across these websites and let companies buy more targeted ads.

  Why does Matomo use cookies ?

  

  For accurate reporting of new and returning visitors. Matomo uses cookies to store some information about visitors between visits. We also use cookies to remember if someone gave consent to tracking, or opted out of tracking. 

  Types of cookies Matomo uses :

  • Matomo by default uses first-party cookies, set on the domain of your site.
  • Cookies created by Matomo start with : _pk_ref, _pk_cvar, _pk_id, _pk_ses. See a list of all Matomo cookies : https://matomo.org/faq/general/faq_146/

  Cookie-less tracking - disable cookies and ensure cookie compliance :

  It’s possible to disable tracking cookies in Matomo by adding a line on the javascript code. When cookies are disabled, Matomo data will become slightly less accurate. Also, when cookies are disabled, there may still be a few cookies created in specific cases.

  If you disable cookies, Matomo tries to detect unique visitors by a fingerprint based on a few browser attributes : operating system, browser, browser plugins, IP address and browser language.

  By disabling tracking cookies, you may also use Matomo without needing to display a cookie consent screen. You can also keep tracking when they reject cookie consent by keeping cookies disabled.

  Cookies and the GDPR

  In some countries and according to the GDPR, websites need to provide a way for users to opt-out of all tracking, in particular tracking cookies.

  The GDPR regulates the use of cookies when they compromise an individual’s privacy. When cookies can identify an individual, it is considered personal data.

  

  Cookie compliance and the GDPR

  To be GDPR compliant you must :

  • Receive user consent before using any cookies (except strictly necessary cookies). Read more on cookies that are “clearly exempt from consent”.
  • Provide accurate and specific information about the data each cookie tracks and its purpose in plain language before consent is received.
  • Document and store consent received from users.
  • Allow users to access your service even if they refuse to allow the use of certain cookies
  • Make it as easy for users to withdraw their consent as it was for them to give their consent in the first place.

  Source : https://gdpr.eu/cookies/

  When does GDPR require cookie consent ?

  The purpose of the GDPR is to give individuals control over their personal data. As such this regulation has provisions and requirements which regulate the processing of personal data to protect the privacy of individuals. 

  This means in order to use cookies, you will sometimes need explicit consent from those individuals.

  When does GDPR not require cookie consent ?

  Then there are many cookies that generally do NOT require consent (Source : https://wikis.ec.europa.eu/display/WEBGUIDE/04.+Cookies). 

  These are :

  • user input cookies, for the duration of a session
  • authentication cookies, for the duration of a session
  • user-centric security cookies, used to detect authentication abuses and linked to the functionality explicitly requested by the user, for a limited persistent duration
  • multimedia content player session cookies, such as flash player cookies, for the duration of a session
  • load balancing session cookies and other technical cookies, for the duration of session
  • user interface customisation cookies, for a browser session or a few hours, when additional information in a prominent location is provided (e.g. “uses cookies” written next to the customisation feature)

  Tracking cookies and consent vs legitimate interest

  

  User consent is not always required :

  We understand that whenever you collect and process personal data, you need – almost always – to ask for their consent. However, there are instances where you have to process data under “legitimate interests”. The GDPR states that processing of personal data is lawful “if processing is necessary for the purposes of the legitimate interests”. This means if you have “legitimate interests” you can avoid asking for consent for collecting and processing personal information. Learn more : https://cookieinformation.com/resources/blog/what-is-legitimate-interest-under-the-gdpr 

  A lawful basis for processing personal data (proceeding with caution) :

  We’ve also written about having a lawful basis for processing personal data under GDPR with Matomo. The caveat here is you need to have a strong argument for legitimate interests. If you are processing personal data which may represent a risk to the final user, then getting consent is, for us, still the right lawful basis. If you are not sure, at the time of writing ICO is providing a tool in order to help you make this decision.

  How is Matomo Analytics GDPR compliant ?

  Matomo can be configured to automatically anonymise data so you don’t process any personal data. This allows you to completely avoid GDPR. If you decide to process personal data, Matomo provides you with 12 steps to easily comply with the GDPR guidelines.

  New developments on cookies and the GDPR

  In the early days of the GDPR, a spate of cookie management platforms (CMPs) popped up to help websites and people comply with GDPR rules around cookies.

  These have become problematic in recent years. Europe’s highest court ruled pre-checked box for cookie boxes does not give enough consent. 

  As well as that, new research suggests most cookie consent pop-ups in the EU fall short of GDPR. A new study called, ‘Dark Patterns after the GDPR’ from MIT, UCL and Aarhus University found that a vast majority of websites aren’t following GDPR rules around cookies. The study found most cookie consent pop-ups in the EU to be undermining the GDPR by finding sneaky ways to convince website visitors to click ‘accept’.

  Disclaimer

  We are not lawyers and don’t claim to be. The information provided here is to help give an introduction to issues you may encounter when dealing cookies. We encourage every business and website to take data privacy seriously and discuss these issues with your lawyer if you have any concerns. 

  Additional resources :

  • How do the cookie rules relate to the GDPR ? 
  • Cookies, the GDPR, and the ePrivacy Directive

• Announcing Matomo 4 : More security, privacy and better performance

  17 novembre 2020, par Matomo Core Team — Community, Development, Privacy, Security
  The moment we’ve all been waiting for is here … Matomo Analytics 4 has launched !! We’re incredibly grateful for all community members and contributors who’ve helped with improvements, and our awesome team for all the fixes. 

  We can’t wait for you to gain greater security, privacy protection, and be able to boost your website performance. Now who’s ready ?

  Minimise your business’ web data security risk

  We’ve made Matomo even more secure to meet our users’ ever increasing security needs. Matomo 4 has certainly delivered on these expectations with a wide range of security enhancements and fixes across the platform :

  • Support for app specific API tokens. [#6559]
  • API tokens and session ids are now stored hashed in the database which means if someone can access your database they wouldn’t be able to get the actual token.
  • A more secure host validation. [#16169]
  • By default, you no longer can embed widgets through tokens with higher privileges. [#16264]
  • Plenty of other minor security fixes.

  More protection of your customer’s personal data

  Matomo 4 ensures you’re compliant with data privacy laws and provides you with more ways to keep your customer’s personal data private, such as :

  • The ability to automatically anonymise the referrer to avoid tracking personal data by accident. [#15426]
  • The option to enforce the disabling of cookies. [#16258]
  • Possibility in JavaScript tracker to turn cookies on and off at any time. [#13056]
  • The option to not store any IP address at all. [#16377]
  • Easily disable visits log and visitor profile feature if needed for privacy compliance [#16259]
  • New segment to separate visitors who gave consent vs visitors who didn’t give consent. [#16192]

  Matomo now offers PHP 8 support to users. Want to know more ? Get a detailed list of over 300 fixes and improvements in the Matomo 4 changelog.

  Increased conversion rates with a focus on page performance

  Our new Page Performance feature in Matomo 4 can help you increase conversion rates by showing you exactly how fast or slow your website is going, and WHY. An Akamai Online Retail Study in 2017 found that a 100-millisecond delay in website load time could underperform website conversion rates by up to 7%. 

  By using this new feature you can quickly identify slow pages and fix page speed issues as soon as they arise, meaning you never miss out on those valuable new sales opportunities.

  Improve your Google search rankings in 2021

  According to moz.com, Google’s bringing in a new ranking factor into their algorithm named Core Web Vitals, which will place greater emphasis on load speed (favouring websites that load faster). This means the slower your page loads, the worse it will rank in Google. With Matomo’s new feature, you’ll be able to optimise your pages to rank better according to the Core Web Vitals ranking factor. 

  Read more on how you can use this new feature : https://matomo.org/faq/how-to/how-do-i-see-page-performance-reports/

  Need help upgrading Matomo ?

  Read the Updating Matomo user guide or contact the Matomo experts. 

  Please note : It may take a while for you to receive a notice to update to Matomo 4.