Sur d’autres sites (5342)

• How to create a spectrogram image from an audio file in Python just like how FFMPEG does ?

  2 mai 2020, par hamandishe Mk

  My code :

  



  import matplotlib.pyplot as plt
from matplotlib.pyplot import specgram
import librosa
import librosa.display
import numpy as np
import io
from PIL import Image

samples, sample_rate = librosa.load('thabo.wav')
fig = plt.figure(figsize=[4, 4])
ax = fig.add_subplot(111)
ax.axes.get_xaxis().set_visible(False)
ax.axes.get_yaxis().set_visible(False)
ax.set_frame_on(False)
S = librosa.feature.melspectrogram(y=samples, sr=sample_rate)
librosa.display.specshow(librosa.power_to_db(S, ref=np.max))
buf = io.BytesIO()
plt.savefig(buf,  bbox_inches='tight',pad_inches=0)

# plt.close('all')
buf.seek(0)
im = Image.open(buf)
# im = Image.open(buf).convert('L')
im.show()
buf.close()


  



  Spectrogram produced

  



  

  



  Using FFMPEG

  



  ffmpeg -i thabo.wav -lavfi showspectrumpic=s=224x224:mode=separate:legend=disabled spectrogram.png

  



  Spectrogram produced

  



  

  



  Please help, i want a spectrogram that is exactly the same as the one produced by FFMPEG, for use with a speech recognition model exported from google's teachable machine.
Offline recognition

  


• Odd X server error with ffmpeg

  4 novembre 2013, par jhc

  I am building a weather data acquisition system. One of the things I would like to do would be to animate the satellite data that is arriving every 15 minutes. In fact, I have already devised a script (called animate) that successfully joins eight hours worth of PNG images into an AVI video file. This runs fine when run manually from the terminal.

  Unfortunately, the same cannot be said when run from my (as in my user, not root) crontab.

  Below is the cron job that I mentioned :

  1,16,31,46 * * * * /home/daniella/bin/anim_all > /home/daniella/logs/anim_all.log 2>&1

  anim_all simply calls animate for each distinct data product :

  #!/bin/bash
  
  set -x
  
  cd /home/daniella/data/imager
  
  
  
  rm -rf HRIT_MSG3_*.avi
  
  
  
  animate HRIT_MSG3_CTT
  
  animate HRIT_MSG3_IR108
  
  animate HRIT_MSG3_VIS006
  
  animate HRIT_MSG3_WV062

  And animate itself calls ffmpeg.

  #!/bin/bash
  
  
  
  set -x
  
  cd /home/daniella/data/imager
  
  product=$1
  
  hl="$product.8hl"
  
  
  
  declare -i i=0
  
  for file in $(cat $hl); do
  
      link=$(printf "images%02d.png" $i)
  
      ln -sf $file $link
  
      i=$((i+1))
  
      echo $i
  
  done
  
  
  
  ffmpeg -sameq -r 15 -i images%02d.png $product.avi
  
  rm -rf images*.png

  Just to be clear, the .8hl file is simply a list of PNG file paths that refer to that last 8 hours of data. Since there is new data every 15 minutes, that is a text file with 32 lines. Finally, this is the error that is returned when examining anim_all.log (referred in the crontab) file.

  + animate HRIT_MSG3_CTT
  
  animate: unable to open X server `' @ animate.c/AnimateImageCommand/365.
  
  + animate HRIT_MSG3_IR108
  
  animate: unable to open X server `' @ animate.c/AnimateImageCommand/365.
  
  + animate HRIT_MSG3_VIS006
  
  animate: unable to open X server `' @ animate.c/AnimateImageCommand/365.
  
  + animate HRIT_MSG3_WV062
  
  animate: unable to open X server `' @ animate.c/AnimateImageCommand/365.

  Please note that anim_all works fine, when called manually from the terminal. This error exists only when called by cron. I would imagine that this has to do with environment variables, but I have sourced my .bashrc inside the script to no prevail.

  EDIT -
  Investigating the animate.c file itself (see the full code here), at lines 365-368, there is this :

  if (display == (Display *) NULL)
  
      ThrowAnimateException(XServerError,"UnableToOpenXServer",
  
      XDisplayName(server_name));
  
  (void) XSetErrorHandler(XError);

  In response, I have attempted to export the $DISPLAY variable to 127.0.0.0:0 in the animate script, but this has not worked.

• Evolution #4146 (Fermé) : Invalideur lors de la publication : facultatif

  26 septembre 2018, par cedric -

  Bon pour commencer la ligne pointée est pas la bonne :)
  https://core.spip.net/projects/spip/repository/entry/spip/ecrire/action/editer_objet.php#L118 dit que si on modifie un objet déjà publié, ça invalide le cache, et c’est normal !

  C’est dans https://core.spip.net/projects/spip/repository/entry/spip/ecrire/action/editer_objet.php#L409 que l’on invalide le cache au moment de la publication.

  Et je ne pense vraiment pas qu’il faille changer ça en y mettant des dérogations.
  Par contre, si dans formidable les réponses sont juste stockées en base pour utilisation dans le back-office sans publication côté public, pourquoi leur donner le statut ’publie’ ? Appelons un chat un chat ! Le statut "publie" ça veut bien dire "à caractère publique, affichable sur le site public".

  Dans le cas présent, si tes données ne sont pas publiques, tu les mets en ’modération a priori’ dans la configuration de formidable et elles seront en statut ’proposée’ ce qui corrige tout tes problèmes sans gérer de cas particulier et en gardant la cohérence de tout le fonctionnement de SPIP