Search Results

Search found 5 results on 1 pages for 'marue'.

Page 1/1 | 1 

• Why isn't sox able to convert to mp3?

  - by marue

  I installed Sox, i installed lame-398, but sox is not able to convert any file to mp3. It fails with the messages: ./../sox FAIL util: Unable to load LAME encoder library (libmp3lame). ./../sox FAIL formats: can't open output file `funktech.mp3': How can i check if lame has been installed correct? How can i get sox to find the mp3Library? edit: I did not install sox at all, it works without installing directly from the commandline. Lame was installed by following the instructions on their site: ./configure make make install which results in the following files being found in /usr/local/lib/ : libmp3lame.dylib, libmp3lame.la, libmp3lame.a Maybe symlinking libmp3lame.la, which is marked as executable, to /usr/bin would help?

  Read the article

• Why isn't sox able to convert to mp3?

  - by marue

  I installed Sox, i installed lame-398, but sox is not able to convert any file to mp3. It fails with the messages: ./../sox FAIL util: Unable to load LAME encoder library (libmp3lame). ./../sox FAIL formats: can't open output file `funktech.mp3': How can i check if lame has been installed correct? How can i get sox to find the mp3Library? edit: I did not install sox at all, it works without installing directly from the commandline. Lame was installed by following the instructions on their site: ./configure make make install which results in the following files being found in /usr/local/lib/ : libmp3lame.dylib, libmp3lame.la, libmp3lame.a Maybe symlinking libmp3lame.la, which is marked as executable, to /usr/bin would help?

  Read the article

• Suddenly get "apt-get: symbol lookup error" when using apt-get

  - by marue

  I have no idea what has gone wrong here. I have installed the audiotool sox, then tried to install the library libsox-fmt-all and all of a sudden apt-get refused to work. I cannot use it now, neither to update nor to install anything. Could somebody suggest what i could do to get it back to work? Here is the complete message it throws: apt-get: symbol lookup error: /usr/lib/libstdc++.so.6: undefined symbol: _ZNSt7num_getIcSt19istreambuf_iteratorIcSt11char_traitsIcEEE2idE, version GLIBCXX_3.4

  Read the article

• Is ffmpeg incorrectly interpreting .aif files?

  - by marue

  Being on an Ubuntu 10.04 server i installed the ffmpeg packages with apt. ffmpeg is working afterwards, and doing as it should. Almost. For testing purposes i uploaded a few audiofiles. One of them, an aif file, is not being correctly interpreted. While on my workhorse (Mac SnowLeopard) ffmpeg tells the format as Stream #0.0: Audio: pcm_s24be, 44100 Hz, 2 channels, s32, 2116 kb/s my Ubuntu server says it is: Stream #0.0: Audio: pcm_s24be, 44100 Hz, stereo, s16, 2116 kb/s which is the wrong bitdepth. Ubuntu then fails to convert the file with the error message [pcm_s24be @ 0xcd4b580]invalid PCM packet Error while decoding stream #0.0 which certainly is not true. The file is perfectly valid. Are there any know issues for ffmpeg interpreting the aif format? How can i find out which version of the aif-codec ffmpeg is using? Any ideas how to approach this issue? ffprobe output: FFprobe version SVN-r20090707, Copyright (c) 2007-2009 Stefano Sabatini libavutil 49.15. 0 / 49.15. 0 libavcodec 52.20. 0 / 52.20. 1 libavformat 52.31. 0 / 52.31. 0 built on Jan 20 2010 00:13:01, gcc: 4.4.3 20100116 (prerelease) Input #0, aiff, from 'testfile.aif': Duration: 00:00:04.00, start: 0.000000, bitrate: 2117 kb/s Stream #0.0: Audio: pcm_s24be, 44100 Hz, stereo, s16, 2116 kb/s update 2: Forcing the conversion with -sample_fmt s32 doesn't change anything. Strange thing is: Even without using -sample_fmt s32 i just realized that the conversion is working and creates valid audiofiles. There just is the error message from above.

  Read the article

• How can i use a commandlinetool (ie. sox) via subprocess.Popen with mod_wsgi?

  - by marue

  I have a custom django filefield that makes use of sox, a commandline audiotool. This works pretty well as long as i use the django development server. But as soon as i switch to the production server, using apache2 and mod_wsgi, mod_wsgi catches every output to stdout. This makes it impossible to use the commandline tool to evaluate the file, for example use it to check if the uploaded file really is an audio file like this: filetype=subprocess.Popen([sox,'--i','-t','%s'%self.path], shell=False,\ stdout=subprocess.PIPE, stderr=subprocess.PIPE) (filetype,error)=filetype.communicate() if error: raise EnvironmentError((1,'AudioFile error while determining audioformat: %s'%error)) Is there a way to workaround for this? edit the error i get is "missing filename". I am using mod_wsgi 2.5, standard with ubuntu 8.04. edit2 What exactly happens, when i call subprocess.Popen from within django in mod_wsgi? Shouldn't subprocess stdin/stdout be independent from django stdin/stdout? In that case mod_wsgi should not affect programms called via subprocess... I'm really confused right now, because the file i am trying to access is a temporary file, created via a filenamevariable that i pass to the file creation and the subprocess command. That file is being written to /tmp, where the rights are 777, so it can't be a rights issue. And the error message is not "file does not exist", but "missing filename", which suggests i am not passing a filename as parameter to the commandlinetool.

  Read the article

1