Recherche avancée

Sur d’autres sites (3924)

• Convert mp3 to AAC with mpeg-2 container (FFMPEG)

  18 mars 2016, par jsurf

  I’m trying to convert an mp3 audio file to an AAC file with FFMPEG, and I need the audio to be wrapped in an MPEG-2 container.
  The resulting AAC file needs to be AAC-LC (Low Complexity), 1-channel, CBR mode, 44100 sample rate, and 48kb/s bitrate, so I use this command :

  ffmpeg -y -i input.mp3 -ar 44100 -ab 48k -acodec libfdk_aac -ac 1 output.aac

  But when I examine the ADTS headers, the audio file is always being wrapped in an MPEG-4 container. I have tried all the codecs listed here but I still end up with an mpeg-4 container wrapped around the audio : http://trac.ffmpeg.org/wiki/AACEncodingGuide.

  Here are the headers I get when examining the AAC output file :

  mpeg_type : ’MPEG4’,
  profile : 2,
  profile_name : ’AAC LC’,
  sample_freq : 44100,
  channel_config : 1,
  channels : 1,
  frame_length : 139,
  buffer_fullness : 157,
  number_of_frames : 1,
  frames_per_sec : 43.06640625

  Any ideas as to why ffmpeg wraps an mp4 container around the audio ? Can I get around this somehow ? Are there any other encoders I can try aside from FFMPEG ? I was giving FAAC encoder a shot and it gives me the proper encoding and ADTS headers, but alas it does not support mp3, only WAV.

• Compiling FFMPEG on CentOS DigitalOcean

  29 juillet 2015, par coder_uk

  I set up a DigitalOcean instance running CentOS 6.5 and successfully followed the guide to compile FFMPEG (https://trac.ffmpeg.org/wiki/CompilationGuide/Centos). Hurrah !

  But of course I realised that by default, DigitalOcean creates a root user and so ffmpeg now lives in /root/bin/ffmpeg. Which isn’t ideal because when I want to exec the ffmpeg bin from nginx, I would have to run nginx as root for it to have permission.

  Questions ...

  1) Long-shot, but presumably if I change the owner of the ffmpeg binary to nginx, it still won’t work, because nginx won’t be able to access the /root folder it is in. Correct ?

  2) I could run nginx as root (’user root’). But this seems like a very bad idea. Correct ?

  3) Which leaves me with the option of creating a new user, and then compiling ffmpeg into its home folder. But : which user ? EC2 creates ’ec2-user’, so should I make my own equivalent for DO ? But then won’t I have to run nginx as that user, else I’ll run into the same problem ?

  Or should I compile ffmpeg into the ’nginx’ home folder, if indeed it has one ? Is that how it is supposed to be done ?

  Since compiling ffmpeg takes ages, I don’t want to keep doing it, and the static files all seem very out of date. Thanks

• SRT protocol not found - Raspbery Pi 4 via ffmpeg

  12 août 2021, par Tim Martin

  We tried to stream from a rasp Pi 4 via SRT, but we got a error : "protocol not found". Our command line is :

  


  ffplay srt://127.0.0.1:9500?mode=listener&latency=20000


  


  We tried the following guides :
https://trac.ffmpeg.org/wiki/CompilationGuide/Ubuntu
how to compile ffmpeg with enabling libsrt
https://www.undergroundnews.dk/index.php/item/107-rtmp-eller-srt-streaming

  


  Those guides worked so far and compiled but we still got the error message.

  


  Do you have any ideas how to get the srt protocol working on a pi via ffmpeg ?