Recherche avancée

Sur d’autres sites (1988)

• Evolution #3892 (Nouveau) : Différence de tri entre {id_patate IN ...} et {id_patate ?}

  24 janvier 2017, par tcharlss (*´_ゝ｀)

  Avec un critère {id_patate IN ...}, le compilateur ajoute un ORDER BY FIELD(id_patate,...) à la requête, du coup les résultats sont triés dans l’ordre du IN : joie.
  En revanche, avec un critère optionnel {id_patate?} et un array dans l’environnement, ça fait bien un IN dans la requête par contre il n’y a pas ORDER BY et on perd l’ordre de tri : tristesse.

  Dans les 2 cas, on devrait avoir cet ORDER BY FIELD fort pratique.

  Exemples :

  
  

  SELECT articles.id_article, articles.lang, articles.titre
  FROM spip_articles AS `articles`
  WHERE (articles.statut = ’publie’)
      AND ((articles.id_article  IN (3,1,2)))
  ORDER BY FIELD(articles.id_article,3,1,2)
  

  SELECT articles.id_article, articles.lang, articles.titre
  FROM spip_articles AS `articles`
  WHERE (articles.statut = ’publie’)
      AND ((articles.id_article  IN (3,1,2)))
  

  Testé en SPIP 3.1.3

• FFMPEG Increment filename past 1000 and reset from 1

  15 avril 2019, par Eric Gao

  From the documentation :

  ffmpeg -i video.webm image-%03d.png

  This will extract 25 images per second from the file video.webm and save them as image-000.png, image-001.png, image-002.png up to image-999.png. If there are more than 1000 frames then the last image will be overwritten with the remaining frames leaving only the last frame.

  Is there any way to increment this number past 1000, and can I also have this restart from 1 so that we’re not just overwriting the last frame ?

  I have a script that analyzes these images as they come in so I use locally stored images as a buffer/queue. It’s also useful for me to have more images stored so I can go back and debug anything, so being able to do the above would be quite helpful for me.

• FFmpeg : Re-Streaming RTSP to RTMP (via Nginx) crash randomly with "Connection reset by peer" Error

  5 octobre 2023, par Xav

  I try to Re-stream a RTSP stream from my local network to a RTMP stream (using Nginx), using the following command :

  


  ffmpeg -re -rtsp_transport tcp -i "rtsp://some_ip/Streaming/Channels/101" -vcodec libx264 -f flv -filter:v fps=5 rtmp://127.0.0.1:3500/live/stream


  


  It always starts well and I can watch the resulting stream

  


  But after some random time, it crashes with this output :

  


  av_interleaved_write_frame(): Connection reset by peer49.40 bitrate=6002.5kbits/s speed=0.755x                                        
[flv @ 0x55b00cbd7140] Failed to update header with correct duration.                                                                 
[flv @ 0x55b00cbd7140] Failed to update header with correct filesize.                                                                 Error writing trailer of rtmp://127.0.0.1:3500/live/stream: Connection reset by peer  


  


  Most of time it crashes after 'a few' frames (400 - 800), but some times only after 10 minutes or a day.

  


  I have tried a lot of things found on several forums

  


  The original prompt was

  


  ffmpeg -re -i "rtsp://some_ip/Streaming/Channels/101" -f hevc -filter:v fps=5 rtmp://127.0.0.1:3500/live/stream


  


  with the same error, but at every try and never more than 200 frames.

  


  

  • I added -rtsp_transport tcp -> Same error , but some warnings disappear

  


  • I changed the video codec from hevc to flv (I read somewhere hevc was not well supported by rtmp) -> I have seen some improvement. It seems to prevent crashes, but not all the time.

  


  


  Thank you for your help