Recherche avancée

Sur d’autres sites (7741)

• Create a progresa bar in rails while converting a file with ffmpeg

  15 avril 2017, par Raxor

  How i can create a progress bar in my view that update with ffmpeg while is converting from a video file mkv to webm

  Im using the gem ’paperclip’ and ’paperclip-av-transcoder’

  The file is uploaded fine but i need to show to the user something that tell him how long he has to wait

  postController.rb

  def create
  
  
  
   @article = current_user.articles.create(params_article)
  
  
  
   if @article.valid?
  
      @article.save
  
      if !@article.video_file_name.nil?
  
          @article.change_name_video
  
          @article.save
  
          @article.destroy_video_original
  
          respond_to do |format|
  
              format.js {render :create}
  
          end
  
      end
  
   else
  
      render :new
  
   end
  
  end
  
  
  
    def params_article
  
      params.require(:article).permit(:title, :body, :cover, :video)
  
    end

  form

      =simple_form_for @article ,html:{ :"data-type" => "js", id: "form"}, :remote => true do |f|
  
          .progress-wrapper
  
              .progress
  
                  .progress-bar{role: "progressbar"}
  
                      0%
  
          = f.input :video
  
          = f.input :cover 
  
          =f.input  :title
  
          =f.input  :body 
  
          =f.button  :submit

• Evolution #4699 (Nouveau) : CVT multi-étapes : un moyen de forcer la validation finale (passer à t...

  22 mars 2021, par RastaPopoulos ♥

  Une personne sur IRC demandait comment faire un bouton pour aller à une étape précise. Ça c’est bien indiqué dans la doc :
  https://www.spip.net/fr_article5386.html#Les-squelettes-de-chaque-page

  name="_retour_etape_X"

  Mais en fait le but c’est pas d’aller à une des étapes qui est numérotée, mais bien de valider la toute fin, donc de passer à traiter(), en pouvant sauter certaines étapes qui sont facultatives !

  Si on fait un bouton submit basique : ça va uniquement passer à l’étape suivante (si on est à l’étape 2, ça va à l’étape 3).

  Mais donc comment faire si je suis à l’étape 2, pour valider complètement ?

  Est-ce qu’il y a un manque ? ou bien ça existe et faut compléter la doc ?

• How are ARM GPUs supported by Video display/decoding/encoding Programs ?

  7 juillet 2020, par John Allard

  I often see ARM-based chips advertising onboard GPUs, like the RPI3 that came with "Broadcom VideoCore IV @ 250 MHz" and the OdroidC2 that comes with a "Mali-450 GPU". These chips advertise stuff like "Decode 4k/30FPS, Encode 1080p,30FPS" as the capabilities of the GPU for encoding and decoding videos.

  


  My question is this - how does a program like Kodi, VLC, or FFMPEG come to make use of these GPUs for actual encoding and decoding ? When I do research on how to make use of the Mali-450 GPU, for example, I find some esoteric and poorly documented C-examples of sending compressed frames to the GPU and getting decoded frames back. If I were to use a device like the OdroidC2 and install VLC on it, how does VLC make use of the GPU ? Did someone have to write logic into VLC to use the specific encoding/decoding API exposed by the Mali GPU in order to use it or do these GPUs follow some sort of consistent API that is exposed by all GPUs and VLC/Kodi can just program against this system API ?

  


  The reason I ask this question is that VLC and Kodi tend to support these GPUs out of the Box, but a very popular program like FFMPEG that prides itself on supporting as many codecs and accelerators as possible has no support for decoding and encoding with the Mali GPU series. Why would VLC/Kodi support encoding/decoding and not FFMPEG ? Why do these manufacturers claim wild decoding and encoding support if these GPUs are difficult to program against and one must use their custom esoteric APIs instead of something like libavcodec ?

  


  I hope my question makes sense, I guess what I'm curious about is that GPUs on most systems whether it be the Intel HD Graphics, Nvidia cards, AMD cards, etc seem to be used automatically by most video players but when it comes to using something like FFMPEG against these devices the process becomes much more process and you need to custom compile the build and give special flags to use the device as intended. Is there something I'm missing here ? Is VLC programmed to make use of all of these different type of GPUs ? And why, in that case, does FFMEPG not support Mali GPUs out of the Box ?