Recherche avancée

Sur d’autres sites (10117)

• Powerful Video Analytics and Audio Analytics for Piwik

  10 novembre 2016, par InnoCraft — Plugins, Press Releases

  Over the years, one of the most frequently requested feature by users was to be able to measure how videos and audios are watched and engaged with on your website. We are finally able to announce that it is here ! We are very excited to launch Media Analytics, which will help you understand and grow your audience.

  This article is a showcase of the new powerful video and audio analytics product built for Piwik.

  Why media analytics ?

  We all love media content such as videos as they can make our experiences on websites and apps so much more interesting. A growing number of websites now utilize media files in one form or another : a video presentation of a product or service, a video tutorial teaching you how to do something or interviews with key speakers. Also many creators and distributors are publishing audio files such as podcasts or music songs, and even broadcasting live video events such as music concerts or an entire conference online.

  Whenever you publish videos or audio media on your websites or applications, Media Analytics provides you with clear insights on how your audience interacts with your content. It helps you see what content works and why – so you can better understand and further grow your business !

  

  Valuable insights in Real time

  

  See where your audience comes from.

  How will Media Analytics help me grow ?

  • Better understand your audience : who are the users playing videos and for how long, how often, and where have they dropped off.
  • Gain quick insights into how interaction with your media changes over time with easy to use graphs and report overviews.
  • Get closer to your users by seeing every action of your visitors before and after they utilized your media.
  • View valuable insights in Real time : ‘most popular content right now’, your real time audience map, and more.
  • See where your audience comes from. Drill down right from continents to specifics such as cities.
  • Share and export media analytics reports with your colleagues by creating custom email reports.
  • Video and audio players are supported either automatically (for Youtube, Vimeo, HTML5…) or via a simple custom player integration.
  • No data limit and 100% privacy and data ownership.

  Best of all, it is easy to use and understand, and integrates perfectly with Piwik. Media Analytics complements other reports to give you a 360 degree view of how your users engage with your content.

  Learn more on the official website : www.media-analytics.net

  How do I get Media Analytics ?

  All premium plugins come with our 14 day money back guarantee and 1-click installation & updates. Customers get all product updates for free.

  Learn more about Media Analytics Get it now on the Marketplace

  Media Analytics is available for purchase and download on the Marketplace.

  If you are not using Piwik yet, you can also signup for a free trial of Piwik Cloud (including Media Analytics !).

  Have a question about this product ? Get in touch.

• constructing an ffmpeg script for use in Xcode/swift project

  21 octobre 2019, par NCrusher

  I’m going back to the drawing board with this post because I’ve been through so much trial and error over the last day with this issue that the information I posted earlier is no longer relevant.

  I’ve only been learning both Swift and FFmpeg for a few weeks, and I’ve just exhausted my ability to troubleshoot this.

  I’m maybe 90% certain this is a problem with my ffmpeg script, rather than with the Swift component. But I think it’s complicated by what characters need special formatting in Swift (particularly mathematical operatives.)

  I started off using a method in Xcode modeled after this post, which Xcode actually managed to guide me through updating for current versions of swift without breaking. Which left me with this :

  func ffmpegConvert(inputPath: String, filters: String, outputPath: String) {
  
      guard let launchPath = Bundle.main.path(forResource: "ffmpeg", ofType: "") else { return }
  
      do {
  
          let convertTask: Process = Process()
  
          convertTask.launchPath = launchPath
  
          convertTask.arguments = [
  
              "-i", inputPath,
  
              filters,
  
              outputPath
  
          ]
  
          convertTask.standardInput = FileHandle.nullDevice
  
          convertTask.launch()
  
          convertTask.waitUntilExit()
  
      }
  
  }

  I call this function when I click the "Start Conversion" button on my app. Like I said, that part seems to work fine. The problem is either in the way ffmpeg is being called by the app, or with the construction of the strings in my arguments array.

  The inputFilePath and outputFilePath strings are self-explanatory. Both of them are perfectly acceptably formatted filepath strings.

  The filters is a little tougher. My app has five conversion options and a different filter set for each one. One is as simple as -c copy and the most complex is -c:a libmp3lame -ac 1 -ar 22050 -q:a 9 (I’m working with audiobooks so I don’t need a lot of complexity in my arguments.

  The app appears to be launching ffmpeg perfectly. But the console keeps giving me errors. And the errors keep changing depending on what I try. Here’s what I’ve been through so far :

  var inputFilePath = "/Volumes/CSW External/ffmpeg/diamonds.aac"
  
  var ffmpegFilters = "-c copy"
  
  var outputFilePath = "/Volumes/CSW External/ffmpeg/diamonds.m4b"

  Result :

  Unrecognized option ’c copy’.
  Error splitting the argument list : Option not found

  Next attempt, I tried var ffmpegFilters = "--c copy". Result was the same error.

  Then I tried var ffmpegFilters = " -c copy" and it actually read the metadata from my file before throwing a different error at me :

  Unable to find a suitable output format for ’ -c copy’ -c copy :
  Invalid argument

  I’m assuming that the fact that it read the metadata before throwing a different error at me means I made...some form of progress ?

  I spent a few hours researching that particular error and why people might be getting it and couldn’t find a situation that was analogous to what I was trying to do. Mostly people were encountering it from the command line and/or other operating systems. So no help there.

  At that point, since I was just throwing things at the wall to see what might stick, I decided to throw the whole command, inputPath / ffMpegFilters / outputPath into a single string to see if I could make that work (under the logic that if it did, I could narrow the cause of my trouble down to the way the separate strings are being constructed by XCode.)

  I tried it both with the whitespace in the filepath and with the whitespace escaped out (using double \ as required by Swift.) The ffmpeg log came displayed a perfectly valid

  Doing so took me back to the first error I got :

  Unrecognized option ’-c copy’.
  Error splitting the argument list : Option not found

  So then I started researching THAT error. Some of the discussions I came across indicated that the problem was that the arguments couldn’t all be in a single string, they needed to be split up and put in an array. Which I could see for a longer argument, but -c copy shouldn’t need that.

  But I decided to give it a go. Formerly my method for constructing the string of arguments would have looked like this

  func conversionSelection() {
  
      if inputFileUrl != nil {
  
          let conversionChoice = conversionOptionsPopup.indexOfSelectedItem
  
          switch conversionChoice {
  
              case 1 :
  
                  outputExtension = ".mp3"
  
                  ffmpegFilters = "-c:a libmp3lame -ac 1 -ar 22050 -q:a 9"
  
              (...case 2, 3, 4, default, etc)
  
          }
  
      }
  
  }

  Now it looks more like this :

  func conversionSelection() {
  
      if inputFileUrl != nil {
  
          let conversionChoice = conversionOptionsPopup.indexOfSelectedItem
  
          switch conversionChoice {
  
              case 1 :
  
                  outputExtension = ".mp3"
  
                  ffmpegCodec = "-c:a libmp3lame"
  
                  ffmpegChannels = "-ac 1"
  
                  ffmpegSampling = "-ar 22050"
  
                  ffmpegBitrate = "-q:a 9"
  
              (case 2, case 3, case 4, default, etc)
  
          }
  
      }
  
  }

  Unfortunately, this just brought me full circle. If I try to use -c:a libmp3lame or --c:a libmp3lame I get the Error splitting the argument list: Option not found error. Interestingly, however, it gives the argument with relation to the ffmpegSampling argument, which is a slight difference.

  If I put a whitespace in front of it -c:a libmp3lame it will get far enough into the process to read the input file metadata, then I get this :

  Unable to find a suitable output format for ’ -c:a libmp3lame’ -c:a
  libmp3lame : Invalid argument

  I’m stumped. I thought this was going to be an easy fix, but I’ve been at it almost a full day with all the trial and error, and nothing is working, and I’ve exhausted my newbie understanding of both Swift and ffmpeg.

• Unable to 'make' android ndk project - build fails : [build-openh264-x86] Error 2

  18 décembre 2015, par NoobNinja

  I’ve attempted these two fixes I’ve found while researching the issue :

  android update project  --23 --/Users/ajswann/Downloads/android-sdk-macosx 
  
  
  
  make OS=android NDKROOT=/Users/ajswann/Downloads/android-sdk-macosx TARGET=android-19 ARCH=x86 clean

  ...however neither seems to resolve the issue.

  Any input/suggestions are appreciated.

  P.S.

  I’m running OSX - could this be an issue with attempting to run an x86 architecture on a 64 bit machine ?

  Error Message :

  chris-mini-mac:linphone-android ajswann$ sudo make
  
  ls: /opt/local/etc/openssl/certs: No such file or directory
  
  /Users/ajswann/Downloads/android-sdk-macosx/tools/android update project --path . --target android-23
  
  Updated project.properties
  
  Updated local.properties
  
  build.xml: Found version-tag: custom. File will not be updated.
  
  Updated file ./proguard-project.txt
  
  It seems that there are sub-projects. If you want to update them
  
  please use the --subprojects parameter.
  
  /Users/ajswann/Downloads/android-sdk-macosx/tools/android update test-project --path tests -m .
  
  Resolved location of main project to: /groupchat/linphone-android/tests
  
  Updated project.properties
  
  Updated local.properties
  
  Updated file tests/proguard-project.txt
  
  Updated ant.properties
  
  /Users/ajswann/Downloads/android-sdk-macosx/tools/android update project --path liblinphone_tester --target android-23
  
  Updated project.properties
  
  Updated local.properties
  
  Updated file liblinphone_tester/proguard-project.txt
  
  ant -e -S clean
  
  Buildfile: /groupchat/linphone-android/build.xml
  
  No sub-builds to iterate on
  
  mkdir -p /groupchat/linphone-android/submodules/externals/openh264/include/wels
  
  rsync -rvLpgoc --exclude ".git"  /groupchat/linphone-android/submodules/externals/openh264/codec/api/svc/* /groupchat/linphone-android/submodules/externals/openh264/include/wels/.
  
  building file list ... done
  
  
  
  sent 156 bytes  received 20 bytes  352.00 bytes/sec
  
  total size is 56216  speedup is 319.41
  
  mkdir -p /groupchat/linphone-android/submodules/externals/build/openh264
  
  mkdir -p /groupchat/linphone-android/submodules/externals/build/openh264/arm
  
  cd /groupchat/linphone-android/submodules/externals/build/openh264/arm \
  
      && rsync -rvLpgoc --exclude ".git"  /groupchat/linphone-android/submodules/externals/openh264/* .
  
  building file list ... done
  
  
  
  sent 18841 bytes  received 20 bytes  37722.00 bytes/sec
  
  total size is 48272799  speedup is 2559.40
  
  cd /groupchat/linphone-android/submodules/externals/build/openh264/arm && \
  
      make libraries -j4 OS=android ARCH=arm NDKROOT=/Users/ajswann/Downloads/android-ndk-r10e TARGET=android-19
  
  cd ./ && sh ./codec/common/generate_version.sh
  
  Keeping existing codec/common/inc/version_gen.h
  
  mkdir -p /groupchat/linphone-android/submodules/externals/build/openh264
  
  mkdir -p /groupchat/linphone-android/submodules/externals/build/openh264/x86
  
  cd /groupchat/linphone-android/submodules/externals/build/openh264/x86 \
  
      && rsync -rvLpgoc --exclude ".git"  /groupchat/linphone-android/submodules/externals/openh264/* .
  
  building file list ... done
  
  
  
  sent 18841 bytes  received 20 bytes  12574.00 bytes/sec
  
  total size is 48272799  speedup is 2559.40
  
  cd /groupchat/linphone-android/submodules/externals/build/openh264/x86 && \
  
      make libraries -j4 OS=android ARCH=x86 NDKROOT=/Users/ajswann/Downloads/android-ndk-r10e TARGET=android-19
  
  cd ./ && sh ./codec/common/generate_version.sh
  
  nasm -DX86_32 -f elf -I./codec/common/x86/   -o codec/decoder/core/x86/dct.o codec/decoder/core/x86/dct.asm
  
  codec/decoder/core/x86/dct.asm:1: error: label or instruction expected at start of line
  
  codec/decoder/core/x86/dct.asm:144: error: label or instruction expected at start of line
  
  codec/decoder/core/x86/dct.asm:234: error: symbol `IdctResAddPred_mmx' redefined
  
  codec/decoder/core/x86/dct.asm:262: error: symbol `WelsBlockZero16x16_sse2' redefined
  
  codec/decoder/core/x86/dct.asm:276: error: symbol `WelsBlockZero8x8_sse2' redefined
  
  codec/decoder/core/x86/dct.asm:287: error: label or instruction expected at start of line
  
  make[1]: *** [codec/decoder/core/x86/dct.o] Error 1
  
  make[1]: *** Waiting for unfinished jobs....
  
  Keeping existing codec/common/inc/version_gen.h
  
  make[1]: *** wait: No child processes.  Stop.
  
  make: *** [build-openh264-x86] Error 2

  Source Repository (I simply clone it, add the platform-tools and tools folder from my android-sdk and run ’make’ and I get this error) :

  https://github.com/TheBaobabTeam/linphone-android