Recherche avancée

Sur d’autres sites (4577)

• 24kHz audio file problem : unsupported bitrate 64000

  28 novembre 2018, par R. Vait

  I use alexa audio tags a lot. I know that now audio tags support 24kHz audio files so tried converting my audio files from 16kHz. I used the provided command in the docs to do so :

  ffmpeg -i  -ac 2 -codec:a libmp3lame -b:a 48k -ar 24000 

  But when I try to play this file, I get an invalid response error, saying : Error: The audio is of an unsupported bitrate 64000. By looking into file details I clearly see, that bitrate is 48kbps and sample rate is 24kHz. I don’t see any value where it would say 64 or anything close to it.

  If I encode my file back to 16kHz it plays fine again.

  It seems that there is a problem with this command, because if I encode my files using audacity, they work with 24kHz. I still would prefer to use ffmpeg, because I need to encode a lot of files.

  I am asking, not about file format, format is correct. I need files in 24kHz sample rate and that is what causes issues. I saw another question about similar problem and others having the discussion there about sample rates, but no one was able to encode file to be 24kHz using ffmpeg.

  Did anyone had any luck on encoding files to 24kHz using ffmpeg ?

• opencv installation ffmpeg error

  22 avril 2016, par tGeek

  I have been trying to install opencv for a long time in my fedora 20 32 bit system.I followed the instructions from http://docs.opencv.org/trunk/doc/py_tutorials/py_setup/py_setup_in_fedora/py_setup_in_fedora.html#install-opencv-python-in-fedora
  But after all cmake commands when I m trying to make it I am getting an error again and again.

      scanning dependencies of target opencv_createsamples
  
       [100%] Building CXX object    apps/haartraining/CMakeFiles/opencv_createsamples.dir/createsamples.cpp.o
  
      Linking CXX executable ../../bin/opencv_createsamples
  
     /lib/libavcodec.so.55: undefined reference to `vpx_codec_vp9_dx_algo'
  
      /lib/libavcodec.so.55: undefined reference to `vpx_codec_vp9_cx_algo'
  
      collect2: error: ld returned 1 exit status
  
      make[2]: *** [bin/opencv_createsamples] Error 1
  
     make[1]: *** [apps/haartraining/CMakeFiles/opencv_createsamples.dir/all] Error 2
  
      make: *** [all] Error 2

  I have followed so many articles about the ffmpeg versions and updating stuff but did understand a little. but when I tried

  $ sudo yum update ffmpeg

  I got the error as

  >Package(s) ffmpeg available, but not installed.
  
  No packages marked for update

  What should I do ?

• Is there a set of working P/Invoke declarations for FFMpeg, libavutil, libavformat and libavcodec in .NET ?

  30 août 2011, par casperOne

  I'm currently looking to access libavutil, libavformat and libavcodec (all part of FFMpeg) from .NET.

  Currently, I'm getting the libraries from the automated builds of the shared FFMpeg package performed every night for Windows 32-bit.

  I am also using the code from the ffmpeg-sharp project. In that project, I have removed a number of classes that were not compiling (they are wrapper classes not the P/Invoke declarations).

  The code compiles fine, but I am running into a few issues.

  First, it appears that the build of av*.dll uses the cdecl calling convention, as I was receiving a number of PInvokeStackImbalanceException when trying to call av_open_input_file. This was easy enough to change to get it to work right. The AVFormatContext structure is populated.

  After that, I want to call av_find_stream_info to get information about the streams in the file. However, when calling that with the AVFormatContext retrieved from the call to av_open_input_file, an AccessViolationException is thrown indicating that I am trying to read or write from protected memory.

  Has anyone used P/Invoke to access the libavutil, libavformat and libavcodec dll libraries through P/Invoke and have gotten it to work ?

  I should mention that working with the command-line version of FFMpeg, while a solution, is not a viable solution in this case, access needs to occur through the libraries. The reason for this is that I'd have to thrash the disk way too much to do what I need to do (I have to do a frame-by-frame analysis of some very high definition video) and I want to avoid the disk as much as possible.