Recherche avancée

Sur d’autres sites (13334)

• PHP : Convert file with FFMPEG and upload to S3 using shell_exec() and aws cli tools

  18 septembre 2017, par andreaem

  I need a script that handle the upload of a video file from dropzone.js, convert to m4v then generate 5 thumbnails using the name of file appending -(number) to each jpg file (eg : file-1.jpg, file-2.jpg, file-3.jpgetc) and finally upload to s3 using shell_script (or maybe if there is a better way to do this).

  Recap

  1. Upload file in a temp dir
  2. Convert file to .m4v
  3. Generate 5 thumbnails from video
  4. Upload the converted video to Amazon S3
  5. Delete local video file

  Here is my code, at the moment I don’t know where the file goes and nothing seems to be uploaded to Amazon S3 (doing the upload in command-line works, so the credentials are ok).

  Dropzone.js

  $("#dZUpload").dropzone({
  
       url: "/ajax/admin/admin.acceptVideo.php",
  
       maxFilesize: 200,
  
       renameFile: new Date,
  
       acceptedFiles: "video/*",
  
       addRemoveLinks: true,
  
       success: function (file, response) {
  
            var imgName = response;                              file.previewElement.classList.add("dz-success");
  
            console.log("Successfully uploaded :" + imgName);
  
            $('#form_video').val(file);
  
       },
  
       error: function (file, response) {file.previewElement.classList.add("dz-error");
  
       }
  
   }).autoDiscover = false;
  
      Dropzone.prototype.defaultOptions.dictRemoveFile = "Rimuovi file";
  
      Dropzone.on("addedfile", function(file) {
  
          var cancelLink = Dropzone.createElement('<a>Cancel upload</a>');
  
       file.previewElement.appendChild(cancelLink);
  
       cancelLink.addEventListener("click", function(e) {
  
       e.preventDefault();
  
       myDropzone.cancelUpload(file);
  
   });
  
  });

  PHP

  $target_dir = "/var/www/html/example.com/web/temp/";
  
  $target_file = $target_dir . basename($_FILES["file"]["name"]);
  
  $uploadOk = 1;
  
  $imageFileType = pathinfo($target_file,PATHINFO_EXTENSION);
  
  // Check if image file is a actual image or fake image
  
  if(isset($_POST["submit"])) {
  
      $check = getimagesize($_FILES["file"]["tmp_name"]);
  
      if($check !== false) {
  
          echo "File is a video - " . $check["mime"] . ".";
  
          $uploadOk = 1;
  
      } else {
  
          echo "File is not an image.";
  
          $uploadOk = 0;
  
      }
  
  }
  
  // Check if file already exists
  
  if (file_exists($target_file)) {
  
      echo "Sorry, file already exists.";
  
      $uploadOk = 0;
  
  }
  
  // Check file size
  
  if ($_FILES["fileToUpload"]["size"] > 200000000) {
  
      echo "Sorry, your file is too large.";
  
      $uploadOk = 0;
  
  }
  
  // Allow certain file formats
  
  if($imageFileType != "mp4" && $imageFileType != "mov" && $imageFileType != "avi" && $imageFileType != "m4v" ) {
  
      echo "Sorry, only MP4 MOV AVI M4V files are allowed.";
  
      $uploadOk = 0;
  
  }
  
  // Check if $uploadOk is set to 0 by an error
  
  if ($uploadOk == 0) {
  
      echo "Sorry, your file was not uploaded.";
  
  // if everything is ok, try to upload file
  
  } else {
  
      if (move_uploaded_file($_FILES["file"]["tmp_name"], $target_file)) {
  
          S3Up(VideoConvert(basename( $_FILES["file"]["name"]),random_int('1','9999')));
  
          echo "The file ". basename( $_FILES["file"]["name"]). " has been uploaded.";
  
      } else {
  
          echo "Sorry, there was an error uploading your file.";
  
      }
  
  }
  
  
  
  function VideoConvert($video, $id) {
  
      shell_exec('ffmpeg -i ' . $video . ' /var/www/html/example.com/web/temp/' . $id . '.m4v');
  
      for ($i=0;$i <= 5;$i++) {
  
          shell_exec('ffmpeg -i ' . $video .' -vf "select=gte(n\,' . $i .'00)" -vframes 1 ' .$id . '-' . $i. '.jpg');
  
      }
  
  
  
      return '/var/www/html/example.com/web/temp/' . $id . '.m4v';
  
  }
  
  
  
  function S3Up($video) {
  
      shell_exec('aws s3 cp ' . $video .' s3://example-video/ --grants read=uri=http://acs.amazonaws.com/groups/global/AllUsers');
  
      sleep(1);
  
      //shell_exec('rm '. $video);
  
  }

  Here is my error.log line relating to s3 upload :

  error.log

  example.mp4: No such file or directory
  
  Traceback (most recent call last):
  
    File "/usr/local/bin/aws", line 19, in <module>
  
      import awscli.clidriver
  
    File "/usr/local/lib/python2.7/dist-packages/awscli/clidriver.py", line 17, in <module>
  
      import botocore.session
  
    File "/usr/local/lib/python2.7/dist-packages/botocore/session.py", line 26, in <module>
  
      import botocore.credentials
  
    File "/usr/local/lib/python2.7/dist-packages/botocore/credentials.py", line 22, in <module>
  
      from dateutil.parser import parse
  
  ImportError: No module named dateutil.parser
  
  </module></module></module></module>

  How can I improve this ? I’ve tried using aws php api but got some problems with credentials, cli tools don’t have.

  Behavior

  At the moment dropzone.js stop uploading at 50% if I put a file of 8 MB, php maxUploadSize directive is set to 201M, php upload temp folder is inside the site root directory and permissions set to 7777. File where uploaded if I put a smallest file of 200Kb but don’t convert and make a 0 byte file.

• checkasm : updated tests for sw_scale

  13 août 2022, par Swinney, Jonathan

  checkasm : updated tests for sw_scale
  Change the reference to exactly match the C reference in swscale,
  
  instead of exactly matching the x86 SIMD implementations (which
  
  differs slightly). Test with and without SWS_ACCURATE_RND - if this
  
  flag isn't set, the output must match the C reference exactly,
  
  otherwise it is allowed to be off by 2.
  Mark a couple x86 functions as unavailable when SWS_ACCURATE_RND
  
  is set - apparently this discrepancy hasn't been noticed in other
  
  exact tests before.
  Add a test for yuv2plane1.
  Signed-off-by : Jonathan Swinney <jswinney@amazon.com>
  
  Signed-off-by : Martin Storsjö <martin@martin.st>
  

  • [DH] libswscale/x86/swscale.c
  • [DH] tests/checkasm/sw_scale.c

• Introducing Crash Analytics for Matomo

  30 août 2023, par Erin — Community, Plugins

  Bugs and development go hand in hand. As code matures, it contends with new browser iterations, clashes with ad blockers and other software quirks, resulting in the inevitable emergence of bugs. In fact, a staggering 13% of all pageviews come with lurking JavaScript errors.

  Monitoring for crashes becomes an unrelenting task. Amidst this never-ending effort to remove bugs, a SurveyMonkey study unveils a shared reality : a resounding 66% of individuals have encountered bug-ridden websites.

  These bugs lead to problems like malfunctioning shopping carts, glitchy checkout procedures and contact forms that just won’t cooperate. But they’re not just minor annoyances – they pose a real danger to your conversion rates and revenue.

  According to a study, 58% of visitors are inclined to abandon purchases as a result of bugs, while an astonishing 75% are driven to completely abandon websites due to these frustrating experiences.

  Imagine a website earning approximately 25,000 EUR per month. Now, factor in errors occurring in 13% of all pageviews. The result ? A potential monthly loss of 1,885 EUR.

  Meet Crash Analytics

  Driven by our vision to create an empowering analytics product, we’re excited to introduce Crash Analytics, an innovative plugin for Matomo On-Premise that automatically tracks bugs on your website.

  

  By offering insights into the precise bug location and the user’s interactions that triggered it, along with details about their device type, browser and more, Crash Analytics empowers you to swiftly address crashes, leading to an improved user experience, higher conversion rates and revenue growth.

  Soon, Crash Analytics will become available to Matomo Cloud users as well, so stay tuned for further updates and announcements.

  Say goodbye to lost revenue – never miss a bug again

  Even if you put your website through the toughest tests, it’s hard to predict every little hiccup that can pop up across different browsers, setups and situations. Factors such as ad blockers, varying internet speeds for visitors and browser updates can add an extra layer of complexity.

  When these crashes happen, you want to know immediately. However, according to a study, only 29% of surveyed respondents would report the existence of the site bug to the website operator. These bugs that go unnoticed can really hurt your bottom line and conversion rates, causing you to lose out on revenue and leaving your users frustrated and disappointed.

  

  Crash Analytics is here to bridge this gap. Armed with scheduled reporting (via email or texts) and automated alert functionalities, you gain the power to instantly detect bugs as they occur on your site. This proactive approach ensures that even the subtlest of issues are brought to your attention promptly. 

  With automated reports and alerts, you can also opt to receive notifications when crashes increase or ignore specific crashes that you deem insignificant. This keeps you in the loop with only the issues that truly matter, helping you cut out the noise and take immediate action.

  

  Easily forward crash data to developers and synchronise the efforts of technical teams and marketing experts. Track emerging, disappearing and recurring errors, ensuring that crash data is efficiently relayed to developers to prioritise fixes that matter.

  

  Plus, your finger is always on the pulse with real-time reports that offer a live view of crashes happening at the moment, an especially helpful feature after deploying changes. Use annotations to mark deploys and correlate them with crash data, enabling you to quickly identify if a new bug is linked to recent updates or modifications.

  

  And with our mobile app, you can effortlessly stay connected to your website’s performance, conveniently accessing crash information anytime and anywhere. This ensures you’re in complete control of your site’s health, even when you’re on the move.

  Streamline bug resolution with combined web and crash analytics

  Crash Analytics for Matomo doesn’t just stop at pinpointing bug locations ; it goes a step further by providing you with a holistic perspective of user interactions. Seamlessly combining Matomo’s traditional and behavioural web analytics features—like segments, session recordings and visitor logs—with crash data, this integrated approach unveils a wealth of insights so you can quickly resolve bugs. 

  For instance, let’s say a user encounters a bug while attempting to complete a purchase on your e-commerce website. Crash Analytics reveals the exact point of failure, but to truly grasp the situation, you delve into the session recordings. These recordings offer a front-row seat to the user’s journey—every click and interaction that led to the bug. Session recordings are especially helpful when you are struggling to reproduce an issue.

  

  Additionally, the combination of visitor logs with crash data offers a comprehensive timeline of a user’s engagement. This helps you understand their activity leading up to the bug, such as pages visited, actions taken and devices used. Armed with these multifaceted insights, you can confidently pinpoint the root causes and address the crash immediately.

  With segments, you have the ability to dissect the data and compare experiences among distinct user groups. For example, you can compare mobile visitors to desktop visitors to determine if the issue is isolated or widespread and what impact the issue is having on the user experience of different user groups. 

  The combination of crash data with Matomo’s comprehensive web analytics equips you with the tools needed to elevate user experiences and ultimately drive revenue growth.

  Start in seconds, shape as needed : Your path to a 100% reliable website

  Crash Analytics makes the path to a reliable website simple. You don’t have to deal with intricate setups—crash detection starts without any configuration. 

  Plus, Crash Analytics excels in cross-stack proficiency, seamlessly extending its capabilities beyond automatically tracking JavaScript errors to covering server-side crashes as well, whether they occur in PHP, Android, iOS, Java or other frameworks. This versatile approach ensures that Crash Analytics comprehensively supports your website’s health and performance across various technological landscapes.

  Elevate your website with Crash Analytics

  Experience the seamless convergence of bug tracking and web analytics, allowing you to delve into user interactions, session recordings and visitor logs. With the flexibility of customising real-time alerts and scheduled reports, alongside cross-stack proficiency, Crash Analytics becomes your trusted ally in enhancing your website’s reliability and user satisfaction to increase conversions and drive revenue growth. Equip yourself to swiftly address issues and create a website where user experiences take precedence.

  Start your 30-day free trial of our Crash Analytics plugin today, and stay tuned for its availability on Matomo Cloud.