Recherche avancée

Sur d’autres sites (9268)

• Xuggle build failed on ubuntu x64 ?

  3 avril 2012, par beginner

  After downloading the source code from GIT hub I setup the enviroment variables
  as Xuggle YouTube Video said so

     export XUGGLE_HOME=/usr/local
  
     export PATH=$XUGGLE_HOME/bin:$PATH
  
     export LD_LIBRARY_PATH=$XUGGLE_HOME

  Then I simply started the ant test by command

  ant run-tests

  Which gave me following output with error in the end ..

  compile-native-do:
  
       [exec] Making all in captive
  
       [exec] make[1]: Entering directory `/home/uroot/xuggle/build/native/x86_64-unknown-linux-gnu/captive'
  
       [exec] Making all in libvo-aacenc
  
       [exec] make[2]: Entering directory `/home/uroot/xuggle/build/native/x86_64-unknown-linux-gnu/captive/libvo-aacenc'
  
       [exec] Incarcerated package configured: ../../../../../captive/libvo-aacenc
  
       [exec] Incarcerating package ../../../../../captive/libvo-aacenc to fake DESTDIR=/home/uroot/xuggle/build/native/x86_64-unknown-linux-gnu/captive
  
       [exec] make[3]: Entering directory `/home/uroot/xuggle/build/native/x86_64-unknown-linux-gnu/captive/libvo-aacenc/csrc'
  
       [exec] make  all-am
  
       [exec] make[4]: Entering directory `/home/uroot/xuggle/build/native/x86_64-unknown-linux-gnu/captive/libvo-aacenc/csrc'
  
       [exec] make[4]: Leaving directory `/home/uroot/xuggle/build/native/x86_64-unknown-linux-gnu/captive/libvo-aacenc/csrc'
  
       [exec] make[3]: Leaving directory `/home/uroot/xuggle/build/native/x86_64-unknown-linux-gnu/captive/libvo-aacenc/csrc'
  
       [exec] Incarceration complete: ../../../../../captive/libvo-aacenc
  
       [exec] make[2]: Leaving directory `/home/uroot/xuggle/build/native/x86_64-unknown-linux-gnu/captive/libvo-aacenc'
  
       [exec] Making all in libopencore-amr
  
       [exec] make[2]: Entering directory `/home/uroot/xuggle/build/native/x86_64-unknown-linux-gnu/captive/libopencore-amr'
  
       [exec] Incarcerated package must be reconfigured; regenerating out of date captive Makefile from: ../../../../../captive/libopencore-amr/csrc/configure
  
       [exec] /bin/mkdir -p csrc
  
       [exec] cd csrc && sh ../incarcerate
  
       [exec] Creating release version of libopencore-amr: 
  
       [exec] Copying /home/uroot/xuggle/build/native/x86_64-unknown-linux-gnu/captive/../../../../captive/libopencore-amr/csrc to /home/uroot/xuggle/build/native/x86_64-unknown-linux-gnu/captive/libopencore-amr/csrc
  
       [exec] Configuring libopencore-amr with these options:  --enable-shared
  
       [exec] checking for a BSD-compatible install... /usr/bin/install -c
  
       [exec] checking whether build environment is sane... yes
  
       [exec] checking for a thread-safe mkdir -p... /bin/mkdir -p
  
       [exec] checking for gawk... no
  
       [exec] checking for mawk... mawk
  
       [exec] checking whether make sets $(MAKE)... yes
  
       [exec] checking how to create a ustar tar archive... gnutar
  
       [exec] checking whether to enable maintainer-specific portions of Makefiles... no
  
       [exec] checking build system type... x86_64-unknown-linux-gnu
  
       [exec] checking host system type... x86_64-unknown-linux-gnu
  
       [exec] checking for g++... no
  
       [exec] checking for c++... no
  
       [exec] checking for gpp... no
  
       [exec] checking for aCC... no
  
       [exec] checking for CC... no
  
       [exec] checking for cxx... no
  
       [exec] checking for cc++... no
  
       [exec] checking for cl.exe... no
  
       [exec] checking for FCC... no
  
       [exec] checking for KCC... no
  
       [exec] checking for RCC... no
  
       [exec] checking for xlC_r... no
  
       [exec] checking for xlC... no
  
       [exec] configure: error: in `/home/uroot/xuggle/build/native/x86_64-unknown-linux-gnu/captive/libopencore-amr/csrc':
  
       [exec] configure: error: C++ compiler cannot create executables
  
       [exec] See `config.log' for more details.
  
       [exec] make[2]: *** [/home/uroot/xuggle/build/native/x86_64-unknown-linux-gnu/captive/libopencore-amr/csrc/Makefile] Error 1
  
       [exec] make[1]: *** [all-recursive] Error 1
  
       [exec] make: *** [all-recursive] Error 1
  
       [exec] checking for C++ compiler default output file name... 
  
       [exec] Could not configure library: "/home/uroot/xuggle/build/native/x86_64-unknown-linux-gnu/captive/../../../../captive/libopencore-amr"; you may want to try disabling it or installing your own version
  
       [exec] make[2]: Leaving directory `/home/uroot/xuggle/build/native/x86_64-unknown-linux-gnu/captive/libopencore-amr'
  
       [exec] make[1]: Leaving directory `/home/uroot/xuggle/build/native/x86_64-unknown-linux-gnu/captive'
  
  
  
  BUILD FAILED
  
  /home/uroot/xuggle/mk/buildtools/buildhelper.xml:1149: exec returned: 2

• Merge commit ’971099ff5a85377579eb5b8d3620e283957f097e’

  19 décembre 2014, par Michael Niedermayer

  Merge commit ’971099ff5a85377579eb5b8d3620e283957f097e’
  * commit ’971099ff5a85377579eb5b8d3620e283957f097e’ :
  
    aacenc : correctly check returned value
  Merged-by : Michael Niedermayer <michaelni@gmx.at>
  

  • [DH] libavcodec/aacenc.c

• How to get the real, actual duration of an MP3 file (VBR or CBR) server-side

  25 septembre 2016, par SquareCat

  I used to calculate the duration of MP3 files server-side using ffmpeg - which seemed to work fine. Today i discovered that some of the calculations were wrong. Somehow, for some reason, ffmpeg will miscalculate the duration and it seems to happen with variable bit rate mp3 files only.

  When testing this locally, i noticed that ffmpeg printed two extra lines in green.

  Command used :

  ffmpeg -i song_9747c077aef8.mp3

  ffmpeg says :

  [mp3 @ 0x102052600] max_analyze_duration 5000000 reached at 5015510
  
  [mp3 @ 0x102052600] Estimating duration from bitrate, this may be inaccurate

  After a nice, warm google session, i discovered some posts on this, but no solution was found.

  I then tried to increase the maximum duration :

  ffmpeg -analyzeduration 999999999 -i song_9747c077aef8.mp3

  After this, ffmpeg returned only the second line :

  [mp3 @ 0x102052600] Estimating duration from bitrate, this may be inaccurate

  But in either case, the calculated duration was just plain wrong. Comparing it to VLC i noticed that there the duration is correct.

  After more research i stumbled over mp3info - which i installed and used.

  mp3info -p "%S" song_9747c077aef8.mp3

  mp3info then returned the CORRECT duration, but only as an integer, which i cannot use as i need a more accurate number here. The reason for this was explained in a comment below, by user blahdiblah - mp3info is simply pulling ID3 info from the file and not actually performing any calculations.

  I also tried using mplayer to retrieve the duration, but just as ffmpeg, mplayer is returning the wrong value.