Recherche avancée

Sur d’autres sites (7315)

• Revision 99981 : Sur Opera 40 sous Windows 10, ça provoquait un « Uncaught ReferenceError : ...

  20 octobre 2016, par real3t@… — Log

  Sur Opera 40 sous Windows 10, ça provoquait un « Uncaught ReferenceError ? : tableau_sites is not defined » qui rendait les boutons calculer inutiles.

• FFMPEG : Is defining a context for a codec compulsary ?

  28 novembre 2013, par sam

  I'm having a a decoder code. I'm trying to integrate it into ffmpeg framework.

  I'm referring to the HOW TO given here : http://wiki.multimedia.cx/index.php?title=FFmpeg_codec_howto

  According to that article i need to define a structure in my decoder_name.c file.

  The example structure is shown below :

  AVCodec sample_decoder =
  
  {
  
      .name           = "sample",
  
      .type           = AVCODEC_TYPE_VIDEO,
  
      .id             = AVCODEC_ID_SAMPLE,
  
     // .priv_data_size = sizeof(COOKContext),
  
      .init           = sample_decode_init,
  
      .close          = sample_decode_close,
  
      .decode         = sample_decode_frame,
  
  };

  Where,

  .name -> specifies the short name of my decoder.
  
  
  
  .type -> is used to specify that it is a video decoder.
  
  
  
  .id -> is an unique id that i'm assigning to my video decoder.
  
  
  
  .init -> is a function pointer to the function in my decoder code that performs decoder related initializations
  
  
  
  .decode -> is a function pointer to the function in my decoder code that decodes a single frame, given the input data (elementary stream).
  
  
  
  .close -> is a function pointer to the function in my decoder that frees all allocated memory i.e. the memory allocated in init.

  However, my doubt is according to the above mentioned article, there is another field called .priv_data_size which hold the size of some context.

  Is it compulsory to have this field .priv_data_size because according to the above article, i need not define all the parameters of the structure AVCodec. Further i do not possess any such context for my decoder.

  However, when i go through the code of other available decoders in libavcodec of ffmpeg, i find that every decoder has defined this. Will my decoder work if i do not specify this ? I'm unable to proceed because of this. please provide some guidance regrading the same.

  —Thanks in advance.

• FFMPEG or FFPLAY, catch FFT signal in real time as floats

  25 avril 2021, par NVRM

  Looking to extract in real time a FFT snapshot of waveforms data with ffplay, in the view of creating animations.

  


  This is exactly what I am looking to catch, but this demo is using JavaScript in a browser. (Source own post)

  


  


  


  const audio = document.getElementById('music');
audio.load();
audio.play();

const ctx = new AudioContext();
const audioSrc = ctx.createMediaElementSource(audio);
const analyser = ctx.createAnalyser();

audioSrc.connect(analyser);
analyser.connect(ctx.destination);

analyser.fftSize = 256;
const bufferLength = analyser.frequencyBinCount;
const frequencyData = new Uint8Array(bufferLength);

setInterval(() => {
   analyser.getByteFrequencyData(frequencyData);
   console.log(frequencyData);
}, 1000);

  


  <audio src="http://strm112.1.fm/reggae_mobile_mp3" crossorigin="use-URL-credentials" controls="true"></audio>

  


  


  



  ---

  


  I tried many variations around the method posted on https://trac.ffmpeg.org/wiki/Waveform .

  


  

  


  The problem is the output format for FFT is PCM (Pulse Code Modulation), and not real time.

  


  ---

  


  In a generic way, is there a simple way to do this, while the sound is playing, to retrieve this data ?

  


  ffplay -fft file.mp3 > fft.json


  


  ---

  


  Using C, same stuff : Apply FFT on pcm data and convert to a spectrogram

  


  FFMPEG waveform filter documentation