Recherche avancée

Sur d’autres sites (4251)

• Cannot play audio from a link using a Discord Bot

  2 mars 2020, par Guilhermeffable

  I’m trying to code a bot so me and my friends can hear the local radio on our Discord Server but I’m having this error.

  This is part of my code, it’s the play.js file that handles the playback stuff.

  module.exports = (client,message) => {
  
  
  
  const voiceChannel = message.member.voiceChannel;
  
  const idChannel = voiceChannel.id;
  
  
  
  console.log(idChannel)
  
      //vê se o user está numa sala de voz
  
  if(!voiceChannel) {
  
      return message.channel.send("Precisas de estar num voice channel para usar este comando.")
  
  }
  
  const permissions = voiceChannel.permissionsFor(message.client.user);
  
  
  
   //vê se tem permissões para entrar na sala
  
  if(!permissions.has('CONNECT') || !permissions.has('SPEAK')) {
  
      return message.channel.send("Não tenho permissões para entrar nessa sala.")
  
  }
  
  
  
  voiceChannel.join()
  
      .then(connection => {
  
          console.log("Successfully connected.");
  
          connection.playStream('http://centova.radios.pt:8401/stream.mp3/1')
  
  }).catch(e =>{
  
      console.error(e);
  
  
  
  });

  }

  And this is the error I’m getting :

  TypeError [ERR_INVALID_ARG_TYPE]: The "file" argument must be of type string. Received an instance of         
  
  Object
  
  at validateString (internal/validators.js:117:11)
  
  at normalizeSpawnArguments (child_process.js:406:3)
  
  at Object.spawn (child_process.js:542:16)
  
  at new FfmpegProcess (C:\Users\guilh\desktop\BOT\orbitalbot\node_modules\prism-media\src\transcoders\ffmpeg\FfmpegProcess.js:14:33)
  
  at FfmpegTranscoder.transcode (C:\Users\guilh\desktop\BOT\orbitalbot\node_modules\prism-media\src\transcoders\ffmpeg\Ffmpeg.js:34:18)
  
  at MediaTranscoder.transcode (C:\Users\guilh\desktop\BOT\orbitalbot\node_modules\prism-media\src\transcoders\MediaTranscoder.js:27:31)
  
  at Prism.transcode (C:\Users\guilh\desktop\BOT\orbitalbot\node_modules\prism-media\src\Prism.js:13:28)
  
  at AudioPlayer.playUnknownStream (C:\Users\guilh\desktop\BOT\orbitalbot\node_modules\discord.js\src\client\voice\player\AudioPlayer.js:97:35)
  
  at VoiceConnection.playStream (C:\Users\guilh\desktop\BOT\orbitalbot\node_modules\discord.js\src\client\voice\VoiceConnection.js:546:24)
  
  at C:\Users\guilh\desktop\BOT\orbitalbot\commands\play.js:24:24 {
  
    code: 'ERR_INVALID_ARG_TYPE'

• ffmpeg segment naming of rtsp surveillance stream HikVisions

  20 juillet 2022, par kenneth558

  I need to ensure unique segment names : Apparent POE cable defects, etc. around campus cause HikVision camera streams to require their ffmpeg daemons re-started once or twice or more times/day. (I am miles away from this campus for the most part, so I prefer a command line fix until the hardware fixes get applied.) When ffmpeg has to be restarted for a camera (by background bash script), I need the names of the new .mp4 segments positively not to be the same as any previous names.

  


  Background bash process currently does fine to specify an acceptable ddHHMM style new starting name for the first segment after ffmpeg restart BUT after the first or sometime second or third segment is made, ffmpeg insists on future naming to default to an unacceptable YYYmmdd style and thus start to overwrite previous segments. I use "$(date +%d%H%M)" to obtain my acceptable date style.

  


  I've tried a lot of different combinations of date codes and date embedding and both ssegment and segment muxers ; also I know very little of the very complex realm that ffmpeg is normally used in outside of simple rtsp stream copy to .mp4 files.

  


  ffmpeg command that is launched from inside bash script :
bash -c 'nohup ffmpeg -nostdin -stimeout 10000000 -rtsp_transport udp -i "rtsp://192.168.0.11:6554/Streaming/channels/101" -reconnect 1 -reconnect_at_eof 1 -reconnect_streamed 1 -c:v libx264 -f ssegment -strftime 0 -segment_time 180 -segment_format_options movflags=+faststart -reset_timestamps 0 -increment_tc 1 -avoid_negative_ts 1 -c copy -flags +global_header /var/www/camera_streams/camera_east_driveway/"$(date +%d%H%M)"_%3d.mp4 > /dev/null 2>/dev/null & '

  


  Can the segment naming pattern be carried forward indefinitely like I want ? Honestly, I wonder if ffmpeg does not allow for my specific use case naming need ?

  


  (Yes, I know changing from udp to tcp can help, but I don't consider it to be the specific solid naming fix I'm hoping for right now. And I mention HikVision in case there is known frame encoding differences for them than other cameras)

  


• How can I write to file with video state while paused in ffplay

  26 août 2014, par pixelearth

  Can anyone recommend a way to do what I need : I need to go through 2000+ videos and choose an accurate thumbnail frame down to the .xx decimal place.
  Ffplay works great for this, but it’s tedious to manually copy paste this value from the terminal into my database. It would be great if I could hit a key sequence or somehow trigger an event that would write information about ffplay’s current state (filename, location) to a file.

  Is there a way once the video is paused to somehow write to a file with the filename and location ?