Recherche avancée

Sur d’autres sites (10279)

• Icecast status page not showing Server Name, Server Description, Stream Name, or Stream Description

  28 novembre 2024, par Daniel Torridon

  I have PHP streaming MP3 files listed in playlist.txt to Icecast using FFMpeg.

  


  $ffmpeg_command = "ffmpeg -re -f concat -safe 0 -stream_loop -1 -i /var/www/html/media/radio/playlist.txt -c:a libmp3lame -b:a 128k -f mp3 -ice_name \"My Name\" -ice_description \"My Description\" -metadata title=\"My Title\" -metadata artist=\"My Artist\" -metadata genre=\"My Genre\" -headers \"Icy-MetaData: 1\" icecast://source:Password@99.99.99.99:8000/stream > /dev/null 2>&1 &";


  


  The stream plays correctly, but the Admin and Public status pages for Icecast show the Server Name, Server Description, Stream Name, and Stream Description as "Unspecified".

  


  I've checked my Icecast XML file. It seems to have all the relevant sections as follows...

  


  <icecast>     &#xA;My Server Name&#xA;My Server Description&#xA;...&#xA;10&#xA;...&#xA;<limits>&#xA;    ...&#xA;    <metadata>1limits>&#xA;...&#xA;<mount>&#xA;   /stream&#xA;   <name>My Name</name>&#xA;   <description>My Description</description>&#xA;   <genre>My Genre</genre>    &#xA;   ...&#xA;   <public>1</public>&#xA;</mount>&#xA;...&#xA;<fileserve>1</fileserve>&#xA;...&#xA;</metadata></limits></icecast>&#xA;

  


  The genre tag is passed from the XML file to the Admin and Public status pages. But the server-name and server-description tags in the global icecast tag are not.

  


  -ice_name, -ice_description and -metadata tags are not being passed from FFMpeg to the Icecast status pages, despite me including them along with -headers "Icy-MetaData : 1" in the FFMpeg command.

  


  metadata-update-interval and metadata tags are present in the Icecast XML file.

  


  What am I doing wrong ?

  


• Streaming from google cloud run to youtube

  29 mars 2021, par Robin to Roxel

  When I stream to YouTube with ffmpeg from within a container on google cloud run, I get a connection timeout. But the same container successfully streams from google cloud build to YouTube during the container build process (which I accidentally found out). Also, the same container successfully streams to YouTube when I run it locally.

  


  The ffmpeg command is ffmpeg -hide_banner -loglevel error -re -i test.flv -c copy -f flv rtmp://a.rtmp.youtube.com/live2/key. The dockerfile is

  


  FROM python:3.8-slim-buster

RUN apt update; apt install ffmpeg -y
RUN apt-get update; apt-get install git -y

RUN git clone "url/to/github/repository"
RUN pip install flask

EXPOSE 8080

CMD cd test_dir; python3 test_script.py


  


• Google Speech to Text on WAV file gives

  7 janvier 2021, par Darth.Vader

  I am using the Google Speech to Text API to convert a WAV file to text. When I play the WAV file, it works fine but when I run the Google Speech To Text API I get this error :

  


  WAV header indicates an unsupported format.


  


  When I try to analyze the file using ffmpeg tool, it get the following error :

  


  Output #0, wav, to '/home/shubham/workspace/intent-service/scripts/audio2.tmp.wav':
Metadata:
  ISFT            : Lavf57.83.100
  Stream #0:0: Audio: pcm_s16le ([1][0][0][0] / 0x0001), 8000 Hz, mono, s16, 128 kb/s
  Metadata:
    encoder         : Lavc57.107.100 pcm_s16le
[gsm_ms @ 0x55d4c255cd20] Packet is too small
Error while decoding stream #0:0: Invalid data found when processing input size=7924kB time=00:08:27.16 bitrate= 128.0kbits/s speed=3.72e+03x    
video:0kB audio:7924kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: 0.000961%


  


  What am I missing ?