Recherche avancée

Sur d’autres sites (10382)

• can someone explain this difference between H.264 and H.265 ?

  19 janvier 2017, par Muhammad Abu bakr

  I have studied this in a research paper :

  "The off-the-shelf video codecs like H.264 handle all the movements equally. In our case there are some non moving region that lies in region of interest and need to be encode in high quality and there are some moving regions which don’t need such requirements. H.265 can help us in such circumstances."

  How H.265 deals with movements differently ?

• how to upload a video to google driver use paperclip or carriwave

  14 janvier 2016, par bách trần nguyên

  i want to upload video to google driver.
  code models
  video model

  class Video < ActiveRecord::Base
  
    has_attached_file :video,
  
     :storage => :google_drive,
  
     :google_drive_credentials => {:client_id => AppConfig.gg_drive.client_id,
  
                                :client_secret => AppConfig.gg_drive.client_secret,
  
                                :refresh_token => AppConfig.gg_drive.refresh_token,
  
                                :scope => AppConfig.gg_drive.scope,
  
                                :access_token => Token.cache_access_token_google_drive
  
                                },
  
    :styles => {
  
      :medium => {
  
        :geometry => "640x480",
  
        :format => 'mp4'
  
      },
  
      :thumb => { :geometry => "160x120", :format => 'jpeg', :time => 10} 
  
    },# hello 123
  
    :processors => [:transcoder],
  
    :google_drive_options => {
  
      :path => proc { |style| "#{style}_#{id}_#{image.original_filename}" },
  
      :public_folder_id => '0B0VNyOkzIwUZZFFGeVhycFk0dnc'
  
    }
  
  end

  in Gemfile

  gem 'google-api-client'
  
  gem 'paperclip'
  
  gem 'paperclip-googledrive'
  
  gem 'paperclip-av-transcoder'
  
  gem "paperclip-ffmpeg"

  in controller

  def create
  
      if params[:videos]
  
        params[:videos].each { |video| Video.create(video: video) }
  
      end
  
  end

  when i run , this display error

  [AV] Running command : if command -v avprobe 2>/dev/null ; then echo "true" ; else echo "false" ; fi
  [AV] Running command : if command -v ffmpeg 2>/dev/null ; then echo "true" ; else echo "false" ; fi
  Av::UnableToDetect in AlbumsController#create
  Unable to detect any supported library

  pls. how to fix this errors

• FFmpeg java.lang.UnsatisfiedLinkError dlopen failed : library "libavutil.so" not found in Vivo model device

  9 février 2024, par sejn

  Facing a lot of crashes in the Android Vivo devices with the above error. Can I restrict this to the Vivo models in Android.

  


  I'm using the implementation 'com.arthenica:mobile-ffmpeg-full:4.4'

  


  Fatal Exception: java.lang.UnsatisfiedLinkError dlopen failed: library "libavutil.so" not found

init {
    try{
        System.loadLibrary("avutil")
        System.loadLibrary("avcodec")
        System.loadLibrary("avformat")
        System.loadLibrary("swscale")
        System.loadLibrary("avfilter")
    }
    catch (e:Exception){
        Log.i("error","${e.message}")
    }
}


  


  In app/build.gradle

  


  


  ndk 
abiFilters 'armeabi-v7a','arm64-v8a','x86','x86_64'

  


  


  Note : If I migrate to the latest version ffmpeg-kit-full:6.0-2

  


  Clarifications :

  


  

  1. Shall I need to add this below in the code as well if I use the FFmpeg-kit

  


  2. If I did not need to use means, does it make any issues in the app ?.(i.e) if I removed

  


  3. Shall I need to add any additional loadlibrary in the init ?

  


  4. Is there any simple fix for the above error for Oppo alone without migrating ?

  


  5. Shall I need to add these architectures in ndk of my app ?

  


  


  


  arm-v7a, arm-v7a-neon, arm64-v8a, x86 and x86_64 architectures

  


  


   init {
        try{
            System.loadLibrary("avutil")
            System.loadLibrary("avcodec")
            System.loadLibrary("avformat")
            System.loadLibrary("swscale")
            System.loadLibrary("avfilter")
        }
        catch (e:Exception){
            Log.i("error","${e.message}")
        }
    }