Recherche avancée

Sur d’autres sites (8816)

• Video Failed to transcode with FFmpeg with Rails app in my localhost

  25 avril 2017, par Takor

  I ve tried to upload videos using Carrierwave-video & FFmpeg. I’ve installed FFmpeg and there is no problem with installation. I have made configurations from ’ http://blog.41studio.com/upload-videos-using-carrierwave-ffmpeg/ ’ .But when I tried to upload video (.mov file), I have an error.

  Error

   Video Failed to transcode with FFmpeg. Check ffmpeg install and verify video is not corrupt or cut short. Original error: Failed encoding.Errors: encoded file is invalid. Full output: ffmpeg version 2.8.3 Copyright (c) 2000-2015 the FFmpeg developers built with Apple LLVM version 7.0.0 (clang-700.1.76) configuration: --prefix=/usr/local/Cellar/ffmpeg/2.8.3 --enable-shared --enable-pthreads --enable-gpl --enable-version3 --enable-hardcoded-tables --enable-avresample --cc=clang --host-cflags= --host-ldflags= --enable-opencl --enable-libx264 --enable-libmp3lame --enable-libvo-aacenc --enable-libxvid --enable-libfaac --enable-nonfree --enable-vda libavutil 54. 31.100 / 54. 31.100 libavcodec 56. 60.100 / 56. 60.100 libavformat 56. 40.101 / 56. 40.101 libavdevice 56. 4.100 / 56. 4.100 libavfilter 5. 40.101 / 5. 40.101 libavresample 2. 1. 0 / 2. 1. 0 libswscale 3. 1.101 / 3. 1.101 libswresample 1. 2.101 / 1. 2.101 libpostproc 53. 3.100 / 53. 3.100 Input #0, mov,mp4,m4a,3gp,3g2,mj2, from '/Users/tanerkoroglu/Desktop/Wishpere2/public/uploads/tmp/1449435556-7186-2107/IMG_1756.MOV': Metadata: major_brand : qt minor_version : 0 compatible_brands: qt creation_time : 2015-10-17 12:19:27 Duration: 00:01:04.24, start: 0.000000, bitrate: 17176 kb/s Stream #0:0(und): Video: h264 (High) (avc1 / 0x31637661), yuv420p(tv, bt709), 1920x1080, 17082 kb/s, 29.98 fps, 29.97 tbr, 600 tbn, 1200 tbc (default) Metadata: creation_time : 2015-10-17 12:19:27 handler_name : Core Media Data Handler encoder : H.264 Stream #0:1(und): Audio: aac (LC) (mp4a / 0x6134706D), 44100 Hz, mono, fltp, 85 kb/s (default) Metadata: creation_time : 2015-10-17 12:19:27 handler_name : Core Media Data Handler Stream #0:2(und): Data: none (mebx / 0x7862656D), 0 kb/s (default) Metadata: creation_time : 2015-10-17 12:19:27 handler_name : Core Media Data Handler Stream #0:3(und): Data: none (mebx / 0x7862656D), 0 kb/s (default) Metadata: creation_time : 2015-10-17 12:19:27 handler_name : Core Media Data Handler Please use -q:a or -q:v, -qscale is ambiguous [Parsed_movie_0 @ 0x7feb6bf00100] Failed to avformat_open_input '/Users/tanerkoroglu/Desktop/Wishpere2/app/assets/images/logo.png' [AVFilterGraph @ 0x7feb6bc09240] Error initializing filter 'movie' with args '/Users/tanerkoroglu/Desktop/Wishpere2/app/assets/images/logo.png' Error opening filters! 

  video_uploader.rb

  class VideoUploader < CarrierWave::Uploader::Base  
  
      include CarrierWave::Video
  
      process :encode
  
       def encode
  
         encode_video(:mp4, watermark: {path: File.join(Rails.root, "app/assets/images/logo.png")})
  
       end
  
  
  
     version :mp4 do
  
       def full_filename(for_file)
  
          super.chomp(File.extname(super)) + '.mp4'
  
       end
  
     end
  
   end 

  Gemfile

   gem 'carrierwave',             '0.10.0'
  
   gem 'carrierwave-video' 
  
   gem 'streamio-ffmpeg'

• ffmpeg build from source fails in docker container ?

  24 mars 2016, par John Allard

  I’m trying to make some changes to the ffmpeg source code (yes, I’m a masochist), and to start I booted an Arch Linux docker container, installed the requirements, downloaded ffmpeg source code, and tried to compile, but I’m getting some extremely odd errors.

  compile command :

  ./configure --bindidr=~/ffmpeg_build --enable-gpl --enable-libass --enable-libfdk-aac --enable-libfreetype --enable-libmp3lame --enable-libopus --enable-libtheora --enable-libvorbis --enable-libx264 --enable-nonfree

  Output :

  ./configure:unset:3338: no such has table element: mktemp
  
  pr: /tmp/ffconf.uQI7CeV.c: No such file or directory.
  
  pr: /tmp/ffconf.uQI7CeV.c: No such file or directory.
  
  pr: /tmp/ffconf.uQI7CeV.c: No such file or directory.
  
  pr: /tmp/ffconf.uQI7CeV.c: No such file or directory.
  
  ... (24 times)
  
  pr: /tmp/ffconf.uQI7CeV.c: No such file or directory.
  
  pr: /tmp/ffconf.r547UgWy.m: No such file or directory.
  
  ./configure:53378: parse error near '}'
  
  ==> ERROR" A failure occured in build()
  
      Aborting...
  
  The build failed.

  This doesn’t seem to be a problem with ffmpeg, more a problem with the container. If I check find /tmp -name ffconf\* I see that the files do exist and they contain

  extern int getrusage();
  
  int main(void){ getrusage(); }

  what in the hell is going on ? hash tabled ? mktemp not working ? files not being found ?

  edit-

  here is what is on the line numbers in the files that give the errors

  3338:configure - unset -f mktemp
  
  5338:configure - check_builtin gmtime_r time.g "time_t * time; strict tm*; gmtime_r(time, tm)"

  edit2 - Here’s the dockerfile (cloned from here https://hub.docker.com/r/greyltc/archlinux/ /dockerfile/)

  # Arch Linux baseline docker container
  
  # Generated on Sat Mar 19 14:26:28 GMT 2016 using code in this GitHub repo:
  
  # https://github.com/greyltc/docker-archlinux
  
  FROM scratch
  
  MAINTAINER Grey Christoforo <grey@christoforo.net>
  
  
  
  # copy in super minimal root filesystem archive
  
  ADD archlinux.tar.xz /
  
  
  
  # perform initial container setup tasks
  
  RUN setup-arch-docker-container
  
  
  
  # this allows the system profile to be sourced at every shell
  
  ENV ENV /etc/profile

• Help us to improve Piwik by sending anonymous usage data (and get usage data yourself)

  22 octobre 2015, par Thomas Steur — Community, Plugins

  At Piwik we have developed a new plugin named AnonymousPiwikUsageMeasurement. The opt-in and anonymised usage tracking information will be used by us to build a better product and a great user experience. The plugin can be installed via the Piwik Marketplace with just a few clicks in your Piwik installation. As a Super User simply go to the Administration and select Marketplace in the left menu. There you will find the plugin and can install it with just one click.

  The plugin allows you to track usage data into up to three Piwik installations :

  • demo-anonymous.piwik.org (enabled by default, can be disabled).
  • your own Piwik (can be configured optionally)
  • a custom Piwik (can be configured optionally)

  The usage data that is sent to Piwik can be publicly viewed by anyone under demo-anonymous.piwik.org.

  What are the advantages by tracking the data into my own installation ?

  You can see how your Piwik installation is used and how well your Piwik performs by checking the average generation time of pages and API calls. Use the Row Evolution feature to see how your Piwik is performing over time.

  What is Piwik doing to make sure the data is anonymized ?

  We are very careful in what we track and we make sure to anonymize data that could contain user data.

  • We overwrite the page title as the title could contain the name of the viewed website
  • We remove any referrer information
  • We replace URL paramaters with a predefined value apart from a few whitelisted ones to make sure no actual token_auth, CSRF token or user defined value will be tracked
  • On demo-anonymous.piwik.org 3 bytes of the IP are anonymised (eg when IP is 192.168.1.1 we track only 192.0.0.0). We do not track nor collect your location and provider information.
  • We do not track clicks on outlinks or downloads

  When should I not install this plugin ?

  If you have developed a custom Piwik plugin that contains for example the name of your business in any of the following names we recommend to not install this plugin as it might be tracked :

  • name of a plugin
  • name of a controller action
  • name of a report
  • name of a widget
  • name of an API method

  Plugins that are installed via the Marketplace should not pose a problem as their names don't contain any user specific information such as the name of your business.

  The data is tracked as efficiently as possible as to not slow down your Piwik server. If you already have some performance challenges with your Piwik, we recommend not to install this plugin.

  Which data is tracked ?

  When the plugin is activated, the following data will be tracked :

  • The pages and reports that are viewed
  • The visitors' software and devices data like the used browser and the resolution
  • Some clicks or interactions with certain selectors or buttons. For example we track an event when a segment is selected (but we do not track the actual segment name or value).
  • In a daily task we track the following data :
    • Piwik version
    • PHP version
    • Number of websites
    • Number of users
    • Number of segments
    • How often which API method was called (only plugin name and method name but no parameters) and how long the API calls took on average.

  Are there any prerequisites ?

  • If sending usage data to Piwik is enabled, the Piwik installation must be connected to the internet
  • If tracking to a custom Piwik installation is enabled, your Piwik installation and your Piwik users must be able to connect to this instance

  Where can I report any issues with the plugin ?

  If you experience any issues with the plugin please create a new issue. The source code is available under GPL v3+ on GitHub. We always appreciate pull requests and suggestions to improve this plugin.