Recherche avancée

Sur d’autres sites (12059)

• KeyError :

  26 juin 2022, par Leon Warta

  So i get the "KeyError: " error, in my code for a music bot (Discord). it says the problems lays in this part : url2 = info['format'][0]['url']

  


  this is the code ;

  


  @client.command()
async def play(ctx, url):
    ctx.voice_client.stop()
    FFPEG_OPTIONS = {'before_options': '-reconnect 1 -reconnect_streamed 1 -reconnect_delay_max 5', 'options': '-vn'}
    YDL_OPTIONS = {'format': 'bestaudio', 'default-search': "ytdlsearch"}
    vc = ctx.voice_client

    with youtube_dl.YoutubeDL(YDL_OPTIONS) as ydl:
        info = ydl.extract_info(url, download=False)
        url2 = info['format'][0]['url']
        source = await discord.FFmpegOpusAudio.from_probe(url2, **FFPEG_OPTIONS)

        vc.play(source)


  


  edit ; im new to coding so if you explain, just use easy words.
edit ; thnx to Infinity ! you're a legend ! I was struggling with this code for 2 days, bc i missed one "s" in my code.....

  


• “only position independent executables (PIE) are supported”

  3 juin 2015, par Karthikeyan

  I am using FFMPEG support library to convert bunch of images to video. It works fine on earlier version of the lollipop. But in the lollipop it generates the following error. ***error: only position independent executables (PIE) are supported.*** I know the PIE Security restrictions has been changed in lollipop, but i don’t know how to fix it.

  From my knowledge it may have two possible solutions,

  either

  we need to relocate the FFMPEG library assets to the SDCard and we have to refer them from our coding, if this is the answer what are all the steps to be followed ?

  or

  Is there any update in the FFMPEG library for android lollipop.

  If both are wrong can you provide me with the proper solution.

  Many thanks...

  Here is my code

     try {
  
              String[] ffmpegCommand = {"/data/data/com.mobvcasting.mjpegffmpeg/ffmpeg", "-r", ""+p.getPreviewFrameRate(), "-b", "1000000", "-vcodec", "mjpeg", "-i", 
  
                      Environment.getExternalStorageDirectory().getPath() + "/req_images/frame_%05d.jpg", Environment.getExternalStorageDirectory().getPath() + "/req_images/video.mov"};
  
  
  
              ffmpegProcess = new ProcessBuilder(ffmpegCommand).redirectErrorStream(true).start();            
  
  
  
              OutputStream ffmpegOutStream = ffmpegProcess.getOutputStream();
  
              BufferedReader reader = new BufferedReader(new InputStreamReader(ffmpegProcess.getInputStream()));
  
  
  
              String line;
  
  
  
              Log.v(LOGTAG,"***Starting FFMPEG***");
  
              while ((line = reader.readLine()) != null)
  
              {
  
                  Log.v(LOGTAG,"***"+line+"***");
  
              }
  
              Log.v(LOGTAG,"***Ending FFMPEG***");
  
  
  
  
  
          } catch (IOException e) {
  
              e.printStackTrace();
  
          }
  
  
  
          if (ffmpegProcess != null) {
  
              ffmpegProcess.destroy();        
  
          }

• avutil/threadmessage : split the pthread condition in two

  1er décembre 2015, par Clément Bœsch

  avutil/threadmessage : split the pthread condition in two
  Fix a dead lock under certain conditions. Let’s assume we have a queue of 1
  
  message max, 2 senders, and 1 receiver.
  Scenario (real record obtained with debug added) :
  
      [...]
  
      SENDER #0 : acquired lock
  
      SENDER #0 : queue is full, wait
  
      SENDER #1 : acquired lock
  
      SENDER #1 : queue is full, wait
  
      RECEIVER : acquired lock
  
      RECEIVER : reading a msg from the queue
  
      RECEIVER : signal the cond
  
      RECEIVER : acquired lock
  
      RECEIVER : queue is empty, wait
  
      SENDER #0 : writing a msg the queue
  
      SENDER #0 : signal the cond
  
      SENDER #0 : acquired lock
  
      SENDER #0 : queue is full, wait
  
      SENDER #1 : queue is full, wait
  Translated :
  
   - initially the queue contains 1/1 message with 2 senders blocking on
  
     it, waiting to push another message.
  
   - Meanwhile the receiver is obtaining the lock, read the message,
  
     signal & release the lock. For some reason it is able to acquire the
  
     lock again before the signal wakes up one of the sender. Since it
  
     just emptied the queue, the reader waits for the queue to fill up
  
     again.
  
   - The signal finally reaches one of the sender, which writes a message
  
     and then signal the condition. Unfortunately, instead of waking up
  
     the reader, it actually wakes up the other worker (signal = notify
  
     the condition just for 1 waiter), who can’t push another message in
  
     the queue because it’s full.
  
   - Meanwhile, the receiver is still waiting. Deadlock.
  This scenario can be triggered with for example :
  
      tests/api/api-threadmessage-test 1 2 100 100 1 1000 1000
  One working solution is to make av_thread_message_queue_send,recv()
  
  call pthread_cond_broadcast() instead of pthread_cond_signal() so both
  
  senders and receivers are unlocked when work is done (be it reading or
  
  writing).
  This second solution replaces the condition with two : one to notify the
  
  senders, and one to notify the receivers. This prevents senders from
  
  notifying other senders instead of a reader, and the other way around.
  
  It also avoid broadcasting to everyone like the first solution, and is,
  
  as a result in theory more optimized.
  

  • [DH] libavutil/threadmessage.c