Recherche avancée

Sur d’autres sites (10661)

• /bin/sh : ffmpeg : command not found while merge audio with with using ffmpeg aws lamda [duplicate]

  1er mai 2023, par bhavesh kaila

  I am trying to merge audio with video using the below command in AWS lambda using Python but the getting and below error.

  


  ffmpeg Command

  


  cmd = 'ffmpeg  -stream_loop -1 -i mayur.mp4 -i audio.mp3 -shortest -map 0:v:0 -map 1:a:0 -y out/output.mp4'
subprocess.call(cmd, shell=True) 


  


  Aws Lambda Error

  


  2023-05-01T16:08:18.591+05:30   INIT_START Runtime Version: python:3.10.v2 Runtime Version ARN: arn:aws:lambda:eu-north-1::runtime:7764dc7f3ff1fc45718f596be4cd03d7bca223f0586f3bfa5fe6584d6af81cd8

2023-05-01T16:08:19.631+05:30   START RequestId: 4557a174-e12c-4924-971a-ef8f852b106b Version: $LATEST

2023-05-01T16:08:22.286+05:30

Copy
/bin/sh: ffmpeg: command not found
/bin/sh: ffmpeg: command not found

2023-05-01T16:08:23.926+05:30   [ERROR] FileNotFoundError: [Errno 2] No such file or directory: '/tmp/output.mp4' Traceback (most recent call last):   File "/var/task/lambda_function.py", line 65, in lambda_handler     s3_upload_response = s3.put_object(Bucket=bucket, Body=open('/tmp/output.mp4', 'rb'), Key =filename)

2023-05-01T16:08:23.929+05:30   END RequestId: 4557a174-e12c-4924-971a-ef8f852b106b


  


  Full Code snippet

  


  import json
from gtts import gTTS
import openpyxl
import boto3
import base64
import openai
import os
import random
import ffmpeg
import subprocess

# os.system("cp -ra bin/ffmpeg /tmp/")
# os.system("chmod -R 775 /tmp")

#from botocore.vendored import requests
language = 'en'
def lambda_handler(event, context):
    input1 = event["queryStringParameters"]['question']
    outputText=""
    
    # Define variable to load the dataframe
    dataframe = openpyxl.load_workbook('QNA/Book1.xlsx')
    
      #accesskey and secretkey for the S3 bucket
    accesskey = os.getenv("access_key")
    secretkey = os.getenv("secret_key")
    
    # Define variable to read sheet
    ws = dataframe['Sheet1']
    
    for row in ws.iter_rows(0,dataframe.active.max_row):
        for cell in row:
          #print(cell.value)
          if input1 in str(cell.value):
            outputText=row[1].value
  
    
    
      #Save Audio File
    audio = gTTS(text=outputText, lang=language, slow=False)
    audio.save("/tmp/audio.mp3")
    
    cmd='ffmpeg -stream_loop -1 -i QNA/mayur.mp4 -i tmp/audio.mp3 -shortest -map 0:v:0 -map 1:a:0 -y tmp/output.mp4'
    subprocess.run(cmd, shell=True)


  


  Note : I Download the static library from Here and added it to the python folder and generate python.zip with other dependencies and upload it on the aws layer and the AWS layer is linked with the python function.

  


  Note : Above code is working fine with google codelab and is able to generate a merged video working fine.

  


  Any help would be appriciated

  


• How to track single-page websites and web applications using Piwik Analytics

  21 février 2017, par InnoCraft — Community, Development

  Single-page websites and web applications have become a standard over the last years. Getting the tracking of such websites and apps right is crucial to your success as you need to ensure the measured data is meaningful and correct. That’s why we, at InnoCraft, help our clients setting up their web tracking and measurement strategy. Some challenges our clients face are the tracking of single-page websites and web applications. We will cover this challenge in this post with a complete example at the bottom.

  Embedding the Tracking Code

  First you need to embed your JavaScript tracking code into your single-page website or web application as usual. To do this go to “Administration” in the top right in your Piwik, click on “Tracking Code” and adjust the tracking code to your needs.

  Tracking a New Page View

  The challenge begins when you need to track a new page view. A single-page app is different from a usual website as there is no regular new page load and Piwik cannot detect automatically when a new page is viewed. This means you need to let Piwik know whenever the URL and the page title changes. You can do this using the methods setCustomUrl and setDocumentTitle like this :

  window.addEventListener('hashchange', function() {
  
          _paq.push(['setCustomUrl', '/' + window.location.hash.substr(1)']);
  
          _paq.push(['setDocumentTitle', 'My New Title']);
  
          _paq.push(['trackPageView']);
  
  }

  Resetting previously set custom variables

  If you have set any Custom Variables in scope “page”, you need to make sure to delete these custom variables again as they would be attributed to the new page view as well otherwise. The following code requires Piwik 3.0.2 :

  _paq.push(['deleteCustomVariables', 'page']);      
  
  _paq.push(['trackPageView']);

  Updating the generation time

  Next you need to update the generation time before tracking a new page view. Otherwise, the initial page generation time will be attributed to all of your subsequent pageviews.

  If you don’t load new content from the server when the page changes, simply set the value to zero :

  _paq.push(['setGenerationTimeMs', 0]);
  
  _paq.push(['trackPageView']);

  In case you load new content from the server, we recommend to measure the time it took to load this content (in milliseconds) and set the needed time :

  _paq.push(['setGenerationTimeMs', timeItTookToLoadPage]);
  
  _paq.push(['trackPageView']);

  Updating the referrer

  Depending on whether you want to track the previous page as a referrer for the new page view, you should update the referrer URL by setting it to the previous page URL :

  _paq.push(['setReferrerUrl', previousPageUrl]);
  
  _paq.push(['trackPageView']);

  Making Piwik Aware of New Content

  When you show a new page, your single-page DOM might change as well. For example, you might replace parts of your page with new content that you loaded from your server via Ajax. This means you need to instruct Piwik to scan the DOM for new content. We’ll now go over various content types (Videos & Audio, Forms, Links and Downloads, Content tracking).

  Video and Audio tracking

  If you use the Media Analytics feature to track your videos and audios, whenever a new page is displayed you need to call the following method :

  _paq.push(['MediaAnalytics::scanForMedia', documentOrElement]);

  When you don’t pass any parameter, it will scan the entire DOM for new media. Alternatively, you can pass an element to scan only a certain area of your website or app for new media.

  Form tracking

  If you use the Form Analytics feature to measure the performance of your online forms, whenever a new page is displayed you need to call the following method :

  _paq.push(['FormAnalytics::scanForForms', docuemntOrElement]);

  Where documentOrElement points either to document to re-scan the entire DOM (the default when no parameter is set) or you can pass an element to restrict the re-scan to a specific area.

  Link tracking

  Supposing that you use the link tracking feature to measure outlinks and downloads, Piwik needs to re-scan the entire DOM for newly added links whenever your DOM changes. To make sure Piwik will track such links, call this method :

  _paq.push(['enableLinkTracking']);

  Content tracking

  If you use the Content Tracking feature, whenever a new page is displayed and some parts of your DOM changes, you need to call this method :

  _paq.push(['trackContentImpressionsWithinNode', documentOrElement]);

  Where documentOrElement points either to document or an element similar to the other methods. Piwik will then scan the page for newly added content blocks.

  Measuring Single-Page Apps : Complete Example

  In this example we show how everything works together assuming you want to track a new page whenever a hash changes :

  var currentUrl = location.href;
  
  window.addEventListener('hashchange', function() {
  
      _paq.push(['setReferrerUrl', currentUrl]);
  
       currentUrl = '' + window.location.hash.substr(1);
  
      _paq.push(['setCustomUrl', currentUrl]);
  
      _paq.push(['setDocumentTitle', 'My New Title']);
  
  
  
      // remove all previously assigned custom variables, requires Piwik 3.0.2
  
      _paq.push(['deleteCustomVariables', 'page']); 
  
      _paq.push(['setGenerationTimeMs', 0]);
  
      _paq.push(['trackPageView']);
  
      
  
      // make Piwik aware of newly added content
  
      var content = document.getElementById('content');
  
      _paq.push(['MediaAnalytics::scanForMedia', content]);
  
      _paq.push(['FormAnalytics::scanForForms', content]);
  
      _paq.push(['trackContentImpressionsWithinNode', content]);
  
      _paq.push(['enableLinkTracking']);
  
  });

  Questions ?

  If you have any questions or need help, please get in touch with us. You can find more information about the Piwik JavaScript tracker on the Piwik Developer Zone.

• The complete guide on tracking your websites and web apps into multiple Piwiks and how to do it easily & efficiently

  23 février 2017, par InnoCraft — Community, Development

  Getting the tracking of your website and apps right is crucial to your success as you need to ensure the measured data is meaningful and correct. That’s why we, at InnoCraft, help our clients setting up their web tracking and digital measurement strategy. Some challenges include tracking your analytics data into multiple Piwik services as well as the tracking of single-page websites and web applications (covered in a previous article). In this blog post, we explain how to track your data into multiple Piwik websites correctly.

  Embedding the tracking code

  First of all you need to embed your JavaScript tracking code into your website or app as usual. If you haven’t done this yet : Log in to your Piwik, click on “Administration” in the top right and go to “Tracking Code”. There you have various options to adjust your tracking code to your needs.

  Tracking the same data into different websites

  Let’s assume you have set up the regular JavaScript tracking code and you want to track the same data into a second Piwik website. This second Piwik website can be either on the same Piwik installation or on a different Piwik. To do this, add the following line to your tracking code :

  _paq.push(['addTracker', 'https://$yourPiwikDomain/piwik.php', idSite]);

  It should look like this :

  var u = '//$yourPiwikDomain';
  
  _paq.push(['addTracker', u + '/piwik.php', var idSite = 2]); // adds an additional tracker
  
  _paq.push(['setSiteId', '1']); // configures your regular Piwik tracker
  
  _paq.push(['setTrackerUrl', u + 'piwik.php']);

  This will track the same data into website 1 and website 2 of your Piwik installation. You can also change the domain in addTracker to point it to a different Piwik installation :

  _paq.push(['addTracker', '//$differentPiwikDomain/piwik.php', var idSite = 2]);

  All Piwik tracker methods that you call afterwards will be applied to all trackers. Say you call _paq.push(['disableCookies']); _paq.push(['trackPageView']);, then both methods will be called on all tracker instances assuring they will behave the same and will track the same data into both Piwik websites.

  Tracking different data into different websites

  If you want to track only certain data into one website, and different data into an additional website, you need to configure the trackers differently. For example, you want to enable link tracking only for one tracker, but not for the other. The problem is that calling _paq.push(['enableLinkTracking']); enables link tracking on all of your trackers. To workaround this limitation, you can configure your trackers differently like this :

  window.piwikAsyncInit = function () {
  
      Piwik.on('TrackerSetup', function (tracker) {
  
        if (tracker.getSiteId() == 2 
  
           || tracker.getTrackerUrl() === '//$yourPiwikDomain/piwik.php') {
  
            tracker.enableLinkTracking();
  
          }
  
      });
  
  };

  Now it enables link tracking only for the tracker that is configured for a certain website ID or Piwik domain.

  Accessing a previously generated tracker instance

  When you configure a tracker via _paq.push, you create a so called “Async tracker” because Piwik will be loaded asynchronously and create the tracker instance as soon as it is loaded. If you need to get the instance of such a tracker, you can use the method Piwik.getAsyncTracker(trackerUrl, idSite). This can be useful if you have a single-page website and want to track different data into different websites :

  window.addEventListener('hashchange', function() {
  
      if ('undefined' === typeof Piwik) {
  
          // Piwik might not be loaded yet
  
          return;
  
      }
  
      var tracker1 = Piwik.getAsyncTracker('//$yourPiwikDomain/piwik.php', var idSite = 1);
  
      var tracker2 = Piwik.getAsyncTracker('//$yourPiwikDomain/piwik.php', var idSite = 2);
  
      tracker1.setCurrentUrl('/' + window.location.hash.substr(1));
  
      tracker2.setCurrentUrl('/mywebsite/' + window.location.hash.substr(1));
  
  });

  Tracking different data into multiple Piwik installations without using “_paq”

  Some users prefer to not use _paq.push and instead directly create tracker instances themselves using the method Piwik.getTracker(trackerUrl, idSite) like this :

  window.piwikAsyncInit = function () {
  
      var tracker1 = Piwik.getTracker('//$yourPiwikdomain/piwik.php', var idSite = 1);
  
      tracker1.disableCookies();
  
      var tracker2 = Piwik.getTracker('//$yourPiwikdomain/piwik.php', var idSite = 2);
  
      tracker2.enableLinkTracking();
  
  
  
      tracker1.trackPageView();
  
      tracker2.trackPageView();
  
  };

  We usually don’t recommend creating trackers manually as it is more complicated and you need to make sure to configure trackers in the right order. For example to prevent the setting of any cookies, it is recommended to call disableCookies before calling any other methods. If you want to create your trackers manually and you use any of the following methods, make sure to call them in this order :

  disableCookies(), setAPIUrl(), enableCrossDomainLinking(), setCookiePath(), setCookieDomain(), setDomains(), setUserId(), enableLinkTracking()

  Roll-Up Reporting – the easy and efficient way

  Often users track data into multiple websites because they need aggregated data over all their websites. They want to see all statistics for a single website, but also which pages were viewed across all their websites, or how much traffic they got from a specific website or search engine across all websites. This means they add a second tracker to all their websites and track data not only into the regular Piwik website, but also into one additional website that gives them statistics over all websites. This has several disadvantages :

  • Complexity in getting the tracking code right and the time needed to integrate and maintain it
  • Slower website performance because everything needs to be tracked into several websites. This can decrease your conversions and sales
  • Slower Piwik performance because it has to handle twice as much traffic. This means tracking becomes slower, generating the report becomes slower, and the database gets twice as big

  Luckily, there is a better solution called Roll-Up Reporting. With Roll-Up Reporting, you can get aggregated data over all websites and / or for a group of websites without any of these disadvantages. It lets you create as many Roll-Ups as you wish and you can choose which websites’ data should be aggregated together into a new website.

  We had customers who were able to remove one Piwik tracker because of this feature which resulted in less server costs, a faster website, and a faster Piwik. On top of all these advantages, it also lets you view the Visitor Log, Real-time Map, and other widgets and reports across several websites.

  Questions ?

  If you got any questions, please let us know and get in touch with us. You can find more information about the Piwik JavaScript tracker on the Piwik Developer Zone. There is a section dedicated to Multiple Piwik Trackers.