Recherche avancée

Sur d’autres sites (6192)

• Discord.NET 1.0.2 sending voice to voice channel not working

  17 octobre 2018, par Sahar Ariel

  I did everything like the Discord.Net Documentation guide on voice -
  https://discord.foxbot.me/latest/guides/voice/sending-voice.html
  and it didn’t work the bot just joined the voice channel but it dont make any sound.
  and i have ffmpeg installed in PATH and ffmpeg.exe in my bot Directory along with opus.dll and libsodium.dll so i dont know what is the problem...

      public class gil : ModuleBase<socketcommandcontext>
  
  {
  
      [Command("join")]
  
      public async Task JoinChannel(IVoiceChannel channel = null)
  
      {
  
          // Get the audio channel
  
          channel = channel ?? (Context.Message.Author as IGuildUser)?.VoiceChannel;
  
          if (channel == null) { await Context.Message.Channel.SendMessageAsync("User must be in a voice channel, or a voice channel must be passed as an argument."); return; }
  
  
  
          // For the next step with transmitting audio, you would want to pass this Audio Client in to a service.
  
          var audioClient = await channel.ConnectAsync();
  
  
  
          await SendAsync(audioClient,"audio/hello.mp3");
  
      }
  
  
  
      private Process CreateStream(string path)
  
      {
  
          return Process.Start(new ProcessStartInfo
  
          {
  
              FileName = "ffmpeg.exe",
  
              Arguments = $"-hide_banner -loglevel panic -i \"{path}\" -ac 2 -f s16le -ar 48000 pipe:1",
  
              UseShellExecute = false,
  
              RedirectStandardOutput = true,
  
          });
  
      }
  
  
  
      private async Task SendAsync(IAudioClient client, string path)
  
      {
  
          // Create FFmpeg using the previous example
  
          using (var ffmpeg = CreateStream(path))
  
          using (var output = ffmpeg.StandardOutput.BaseStream)
  
          using (var discord = client.CreatePCMStream(AudioApplication.Mixed))
  
          {
  
              try { await output.CopyToAsync(discord); }
  
              finally { await discord.FlushAsync(); }
  
          }
  
      }
  
  }
  
  </socketcommandcontext>

  please help

• Ffmpeg hangs while transcoding HDHomerun Prime on channel change

  23 octobre 2017, par devo1929

  I’m using ffmpeg to transcode a live stream from a HDHomerun Prime. Everything is working beautifully. However, one ability that I would like, if possible, is the ability to change the channel on the HDHomerun without having to stop and restart the ffmpeg transcoding process.

  I start the ffmpeg process to begin reading the UDP feed from the HDHomerun. It writes the stream to a series of *.ts files with a m3u8 playlist.

  The second I use hdhomerun_config to change the channel on the device, ffmpeg immediately reports the following and hangs :

  [mpegts @ 0000018b4e05be60] New video stream 0:3 at pos:295211888 and DTS:40884.7s=108 drop=0 speed=1.02x
[mpegts @ 0000018b4e05be60] New audio stream 0:5 at pos:295279568 and DTS:40884.4s
frame= 4488 fps= 29 q=23.0 q=27.0 q=23.0 size=N/A time=00:02:28.94 bitrate=N/A dup=108 drop=0 speed=0.959x

  The command I am using to launch ffmpeg is :

  ffmpeg.exe -t 03:00:00 -i "udp://192.168.1.150:5000?fifo_size=1000000&overrun_nonfatal=1" -vf yadif=0:-1:1 -y -threads 4 -c:v libx264 -s 1280x720 -r 30 -b:v 4500k -force_key_frames expr:gte(t,n_forced*2) -profile:v high -preset fast -x264opts level=41 -c:a libfdk_aac -b:a 96k -ac 2 -hls_time 10 -hls_list_size 6 -hls_wrap 6 -hls_base_url /stream/ -hls_flags temp_file -hls_playlist_type event "C:\temp\streams\4500-stream.m3u8"

  Is there a specific command that I can pass to allow ffmpeg to "recover" from this ? Or, is there an arg that prevents this hang in the first place ? I’m using the latest version v3.4 of ffmpeg cross-compiled for Windows from Ubuntu. The issue also occurred using the stable version v3.4 of ffmpeg for Windows from ffmpeg.org.

  Edit :

  A new discovery to the issue, but still not yet resolved :
  If I change to the channel BACK to the original channel, Ffmpeg is able to continue writing the stream.

  Example : I start on channel X. Ffmpeg is recording to a file. I change to channel Y. Ffmpeg outputs a message similar to the one posted above and "hangs." I change back to channel X and ffmpeg picks up where it left off, no problem.

• Try out the latest Piwik 3.0.0 beta version : Piwik 3.0.0 is almost here !

  15 novembre 2016, par Matthieu Aubry — Uncategorized

  Dear Piwik community,

  We are excited today to announce our publicly available Piwik 3.0.0 beta 3 release. We have been been working hard behind the scenes on the new 3.0.0 release for almost one year now. We, the passionate team at Piwik, are dedicated to bringing you a new and improved Piwik experience and invite you to join our beta channel to switch to Piwik 3 today !

  Enable the beta release channel

  Ready to enjoy a much faster Piwik experience and the magic of a modern user interface ? Follow the instructions here and you can upgrade to Piwik 3.0.0 beta in just one click.

  Please note that beta versions have a risk of containing bugs so we don’t recommend to use on a production server. If you find and report a bug in a beta version, we will aim to fix it as quickly as possible.

  Premium plugins in Piwik 3

  In the Piwik Marketplace you can discover & download plugins to enrich the functionality of your Piwik, as well as themes to change the look and feel of your Piwik user interface. The Marketplace integration was much improved in this new release, most notably : you can now purchase and download Premium plugins within Piwik !

  Important changes

  The Piwik 3 upgrade comes with some important changes that may require your attention which we detail in this blog post and in the developer changelog.

  The full list of more than 150 changes can be found in the Piwik 3 beta changelogs : beta 1, beta 2, beta 3.

  What to do next

  When you use the Piwik beta channel and if you come across any issues in Piwik such as a bug, feature missing, regression… let us know on our tracker and create a new issue so we can get this sorted.

  As we are in the final days of Piwik 3 development, we are looking forward to your feedback and help testing !

  Welcome to the future of Piwik,

  Happy Analytics !