Recherche avancée

Sur d’autres sites (7841)

• Discord.Py Opus Heroku Issues

  9 janvier 2019, par charguyy

  I’m having trouble setting up my music bot to work with Heroku. It works perfectly fine on my host machine, however, I get an "Opus Not Loaded" error when I run the bot in Heroku. I already have a ffmpeg buildpack(https://github.com/jonathanong/heroku-buildpack-ffmpeg-latest.git), an apt buildpack (https://github.com/jonathanong/heroku-buildpack-ffmpeg-latest.git) with the Aptfile fully setup (see below), and I have an opus buildpack (https://github.com/dubsmash/heroku-buildpack-opus.git). I also have youtube_dl and discord.py[voice] in my requirements.txt file

  Here is the contents of my Aptfile.

  build-essential
  
  unzip
  
  software-properties-common
  
  libopus-dev
  
  libffi-dev
  
  libsodium-dev

  Here is the contents of my requirements.txt file

  discord.py[voice]
  
  youtube_dl

  Any help is appreciated :)

• FFmpeg libraries on Windows - Undefined References

  26 novembre 2018, par Gomes

  I am trying to use FFmpeg libraries available from here under Windows 10 (64 bits). I downloaded version=20181126-90ac0e5, architecture=Windows-64, Linking=Dev. There are 3 folders inside that FFmpeg folder : examples, lib and include.
  To use these libraries I copied the contents of the "include" folder to the "include" folder of my MinGW installation. I also copied the contents of the "lib" folder to the "lib" folder of MinGW.
  I try to compile the decode_video.c example that comes inside the examples folder with the following way :

   gcc decode_video.c -o decode_video.exe -lavcodec -lavutil -lavformat -lm

  The compiler gives me these undefined references :

   undefined reference to `avcodec_send_packet'
  
   undefined reference to `avcodec_receive_frame'
  
   undefined reference to `av_packet_alloc'
  
   undefined reference to `avcodec_find_decoder'
  
   undefined reference to `av_parser_init'
  
   undefined reference to `avcodec_alloc_context3'
  
   undefined reference to `avcodec_open2'
  
   undefined reference to `av_frame_alloc'
  
   undefined reference to `av_parser_parse2'
  
   undefined reference to `av_parser_close'
  
   undefined reference to `avcodec_free_context'
  
   undefined reference to `av_frame_free'
  
   undefined reference to `av_packet_free'

  I would like to know what I am doing wrong here. Any guidance is very welcome.

• Sending periodic metadata in fragmented live MP4 stream ?

  20 septembre 2022, par El Sampsa

  As suggested by the topic, I'm wondering if it's possible to send metadata about the stream contents periodically in a fragmented MP4 live stream.

  



  I'm using the following command (1) to get fragmented MP4 :

  



  ffmpeg -i rtsp://admin:12345@192.168.0.157 -c:v copy -an -movflags empty_moov+omit_tfhd_offset+frag_keyframe+default_base_moof -f mp4 ...


  



  My main program reads the fragments from this command from either stdout or from a (unix domain) socket and gets :

  



  ftyp
moov
moof
mdat
moof
mdat
moof
mdat 
...


  



  So, the first fragments I get are ftyp and moov which are metadata and describe the stream contents.

  



  Now a client program connects at a later time to the main program. The problem is, that at that point, the ftype and moov fragments are long gone.

  



  Is there a way (=ffmpeg command option) to make this work similar to MPEGTS (aka mpeg transport stream), and resend metadata periodically with the stream ? Like this :

  



  ftyp
moov
moof
mdat
moof
mdat
moof
mdat 
ftyp
moov
moof
mdat
moof
mdat
moof
mdat 
...


  



  .. or is my only option to cache the ftyp and moov packets in my main program and re-send them to the client program when it requests the stream ?

  



  A related link : What exactly is Fragmented mp4(fMP4) ? How is it different from normal mp4 ?

  



  Caching and resending ftyp and moov each time a new client connects is not that straightforward either .. as it somehow brokes the stream (at least the browser MSE extensions don't like such a stream). There seems to be lots of sequence numbers and stuff in the moof packets that should be modified. (+)

  



  Another option is to pass the stream through another FFmpeg process that does the remuxing (and corrects moof packets). Things are further complicated by the fact that command (1) does not give cleanly-separated ftyp, moov, moof, etc. packets.

  



  Any thoughts / solutions appreciated.

  



  EDIT : regarding (+), MSE seems to have problems playing fragmented MP4 with gaps : https://bugs.chromium.org/p/chromium/issues/detail?id=516114