Recherche avancée

Sur d’autres sites (6139)

• libx264 not found when compiling 64 bit ffmpg

  11 juillet 2017, par Tamilraj

  export PLATFORM=$NDK_BASE/platforms/android-21/arch-arm64
  
  export PREBUILT=$NDK_BASE/toolchains/aarch64-linux-android-4.9/prebuilt
  
  export PREFIX=/android-lib/arm64
  
  
  
  ./configure --cross-prefix=$PREBUILT/windows-x86_64/bin/aarch64-linux-android- \
  
  --sysroot=$PLATFORM \
  
  --host=aarch64-linux \
  
  --enable-pic \
  
  --enable-static \
  
  --extra-cflags="-fPIE -pie" \
  
  --extra-ldflags="-fPIE -pie" \
  
  --disable-cli \
  
  --disable-asm \
  
  --prefix=$X264_OUT_PATH/arm64 \

  This is my setup_x264_arm64.sh and when i compile it does not show any error and compiled successfully.But when compile

    export PLATFORM=$NDK_BASE/platforms/android-21/arch-arm64
  
  export PREBUILT=$NDK_BASE/toolchains/aarch64-linux-android-4.9/prebuilt
  
  export PREFIX=../android-lib/arm64
  
  
  
  echo $X264_OUT_PATH/arm64/include
  
  sh configure --prefix=$FFMPEG_OUT_PATH/arm64 \
  
  $DEBUG_FLAG \
  
  --arch=arm64 \
  
  --cpu=cortex-a53 \
  
  --target-os=linux \
  
  --enable-runtime-cpudetect \
  
  --enable-pic \
  
  --enable-shared \
  
  --enable-nonfree \
  
  --enable-cross-compile \
  
  --enable-static \
  
  --cross-prefix=$PREBUILT/windows-x86_64/bin/aarch64-linux-android- \
  
  --sysroot=$PLATFORM \
  
  --extra-cflags="-I$X264_OUT_PATH/arm64/include -Wno-deprecated-declarations -Wno-format-extra-args -Wno-pointer-sign -Wno-implicit-function-declaration -Wno-parentheses  -Wno-format-extra-args -Wno-unused-result -Wno-traditional -fPIE -pie" \
  
  --extra-ldflags="-L$X264_OUT_PATH/arm64/lib" \
  
  \
  
  --enable-version3 \
  
  --enable-gpl \
  
  --disable-opencl \
  
  \
  
  --disable-doc \
  
  --enable-yasm \
  
  \
  
  --enable-decoders \
  
  --enable-encoders \
  
  --enable-muxers \
  
  --enable-demuxers \
  
  --enable-parsers \
  
  --enable-protocols \
  
  --enable-filters \
  
  --enable-avresample \
  
  --disable-libfreetype \
  
  \
  
  --disable-indevs \
  
  --disable-indev=lavfi \
  
  --disable-outdevs \
  
  \
  
  --enable-hwaccels \
  
  \
  
  --disable-ffmpeg \
  
  --disable-ffplay \
  
  --disable-ffprobe \
  
  --disable-ffserver \
  
  --disable-network \
  
  \
  
  --enable-thumb \
  
  --enable-encoder=libx264 \
  
  --enable-libx264 \
  
  --disable-muxer=md5
  
  
  
  
  
  popd; popd

  this one i got libx264 not found error .Can anyone pls help me .Thanks in advance

• 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.

• How to extract small video chunk with ffmpeg ?

  3 décembre 2017, par Édouard Lopez

  I’m writing a script to split a video in multiple small files based on subtitles timing. Each chunk illustrated how to sign a word LSF (French Sign Language).

  However, some file are blank once extracted and when converted to webm they are 0kb.

  Timing data

  I extract the timing from a .ass file to get this kind of file

  0:00:01.01 0:00:04.07
  
  0:00:04.09 0:00:07.00
  
  0:00:07.00 0:00:10.36
  
  0:00:10.36 0:00:13.28

  First column is start_time, second is end_time

  Extraction

  extract_word_chunk() {
  
    ffmpeg \
  
      -i "$INPUT_FILE" \
  
      -ss "$start" \
  
      -to "$end" \
  
      -vcodec copy \
  
      -acodec copy \
  
      -loglevel error \
  
      "$chunk" < /dev/null
  
  }

  Conversion to webm

  convert_to_webm() {
  
    ffmpeg \
  
      -y \
  
      -i "$chunk" \
  
      -acodec libvorbis \
  
      -codec:v libvpx \
  
      -b:v 192k \
  
      -b:a 96k \
  
      -minrate 128k \
  
      -maxrate 256k \
  
      -bufsize 192k \
  
      -quality good \
  
      -cpu-used 2 \
  
      -deadline best \
  
      -loglevel error \
  
    "$chunk.webm" < /dev/null
  
  }

  Output

  # extract_word_chunk
  
  ffmpeg \
  
    -i 'assets/raw/partie 1: Apprendre 300 mots du quotidien en LSF.jauvert laura.mkv' \
  
    -ss 0:00:01.01 \
  
    -to 0:00:04.07 \
  
    -vcodec copy \
  
    -acodec copy \
  
    -loglevel error \
  
    assets/raw/0:00:01.01.mkv
  
  
  
  # convert_to_webm
  
  ffmpeg -y \
  
    -i assets/raw/0:00:01.01.mkv \
  
    -acodec libvorbis \
  
    -codec:v libvpx \
  
    -b:v 192k \
  
    -b:a 96k \
  
    -minrate 128k \
  
    -maxrate 256k \
  
    -bufsize 192k \
  
    -quality good \
  
    -cpu-used 2 \
  
    -deadline best \
  
    -loglevel error \
  
    assets/raw/0:00:01.01.mkv.webm

  Error

  [buffer @ 0x16d8be0] Unable to parse option value "-1" as pixel format
  
      Last message repeated 1 times
  
  [buffer @ 0x16d8be0] Error setting option pix_fmt to value -1.
  
  [graph 0 input from stream 0:0 @ 0x16e6fc0] Error applying options to the filter.

  Question

  Only some chunk are blank/empty.

  How do I prevent my video to be blank/empty ?