Recherche avancée

Sur d’autres sites (5810)

• Rails : Encoder error when converting video using FFMPEG on Heroku

  2 janvier 2013, par andmcgregor

  I'm trying to upload a video and convert the file to mp4 and reduce the file size using the paperclip-ffmpeg and paperclip gems. Everything works fine running a local server and I'm only getting this problem on heroku. I have ffmpeg installed in vendor/ffmpeg/ (I followed these steps : https://gist.github.com/3963576). Here is the code I've got and the error I'm getting :

  models/video.rb :

  class Video < ActiveRecord::Base
  
    attr_accessible :content, :user_id, :video
  
    has_attached_file :video , :styles => { 
  
      :medium => { :geometry => "500x500", :format => 'mp4',
  
          :convert_options => { :output => { :vcodec => 'libx264',
  
          :b => '1000k', :bt => '200k',
  
          :acodec => 'libfaac', :ab => '56k', :ac => 2 } } }
  
    }, :processors => [:ffmpeg]
  
  
  
    belongs_to :user
  
  end

  when I run heroku logs :

  2013-01-02T00:38:20+00:00 app[web.1]: Started POST "/videos" for 101.170.255.251 at 2013-01-02 00:38:20 +0000
  
  2013-01-02T00:38:20+00:00 app[web.1]: Processing by VideosController#create as HTML
  
  2013-01-02T00:38:20+00:00 app[web.1]:   Parameters: {"utf8"=>"✓", "authenticity_token"=>"X0IKts46TF8aFvEb1I/szFo/28omlVBXIIyJ3APz3YA=", "video"=>{"content"=>"", "video"=>#quicktime\r\n", @tempfile=#tmp/RackMultipart20130102-2-1ch9zcp>>}, "commit"=>"Post"}
  
  2013-01-02T00:38:20+00:00 app[web.1]: [paperclip] [ffmpeg] ffmpeg -i "/tmp/sample20130102-2-4j5sgh.mov" 2>&1
  
  2013-01-02T00:38:20+00:00 app[web.1]: [paperclip] [ffmpeg] Resize
  
  2013-01-02T00:38:20+00:00 app[web.1]: [paperclip] [ffmpeg] Command Success
  
  2013-01-02T00:38:20+00:00 app[web.1]: [paperclip] [ffmpeg] Making...
  
  2013-01-02T00:38:20+00:00 app[web.1]: [paperclip] [ffmpeg] Building Destination File: 'sample20130102-2-4j5sgh' + 'mp4'
  
  2013-01-02T00:38:20+00:00 app[web.1]: [paperclip] [ffmpeg] Destination File Built
  
  2013-01-02T00:38:20+00:00 app[web.1]: [paperclip] [ffmpeg] Adding Source
  
  2013-01-02T00:38:20+00:00 app[web.1]: [paperclip] [ffmpeg] Adding Geometry
  
  2013-01-02T00:38:20+00:00 app[web.1]: [paperclip] [ffmpeg] Convert Options: 500x280
  
  2013-01-02T00:38:20+00:00 app[web.1]: [paperclip] [ffmpeg] Adding Format
  
  2013-01-02T00:38:20+00:00 app[web.1]: [paperclip] [ffmpeg] -i :source -y -vcodec libx264 -b 1000k -bt 200k -acodec libfaac -ab 56k -ac 2 -s 500x280 :dest
  
  2013-01-02T00:38:20+00:00 app[web.1]: [paperclip] [ffmpeg] Extracting Target Dimensions
  
  2013-01-02T00:38:20+00:00 app[web.1]: [paperclip] [ffmpeg] Building Parameters
  
  2013-01-02T00:38:20+00:00 app[web.1]: [paperclip] [ffmpeg] Target Size is Available
  
  2013-01-02T00:38:20+00:00 app[web.1]: [paperclip] [ffmpeg] Keeping Aspect Ratio
  
  2013-01-02T00:38:20+00:00 app[web.1]: Command :: ffmpeg -i '/tmp/sample20130102-2-4j5sgh.mov' -y -vcodec libx264 -b 1000k -bt 200k -acodec libfaac -ab 56k -ac 2 -s 500x280 '/tmp/sample20130102-2-4j5sgh20130102-2-1mr35ix.mp4'
  
  2013-01-02T00:38:20+00:00 app[web.1]: ffmpeg version git-2013-01-01-d079d1d Copyright (c) 2000-2012 the FFmpeg developers
  
  2013-01-02T00:38:20+00:00 app[web.1]:   built on Jan  1 2013 12:59:49 with gcc 4.4.3 (Ubuntu 4.4.3-4ubuntu5)
  
  2013-01-02T00:38:20+00:00 app[web.1]:   configuration: --enable-shared --disable-asm --prefix=/app/vendor/ffmpeg
  
  2013-01-02T00:38:20+00:00 app[web.1]:   libavfilter     3. 30.102 /  3. 30.102
  
  2013-01-02T00:38:20+00:00 app[web.1]:   libavcodec     54. 85.100 / 54. 85.100
  
  2013-01-02T00:38:20+00:00 app[web.1]:   libavdevice    54.  3.102 / 54.  3.102
  
  2013-01-02T00:38:20+00:00 app[web.1]:   libavutil      52. 13.100 / 52. 13.100
  
  2013-01-02T00:38:20+00:00 app[web.1]:   libswresample   0. 17.102 /  0. 17.102
  
  2013-01-02T00:38:20+00:00 app[web.1]:   libswscale      2.  1.103 /  2.  1.103
  
  2013-01-02T00:38:20+00:00 app[web.1]:   libavformat    54. 58.100 / 54. 58.100
  
  2013-01-02T00:38:21+00:00 app[web.1]:     creation_time   : 2013-01-02 00:36:58
  
  2013-01-02T00:38:21+00:00 app[web.1]:     minor_version   : 0
  
  2013-01-02T00:38:21+00:00 app[web.1]:     major_brand     : qt  
  
  2013-01-02T00:38:21+00:00 app[web.1]: Input #0, mov,mp4,m4a,3gp,3g2,mj2, from '/tmp/sample20130102-2-4j5sgh.mov':
  
  2013-01-02T00:38:21+00:00 app[web.1]:     model           : iPhone 4
  
  2013-01-02T00:38:21+00:00 app[web.1]:     compatible_brands: qt  
  
  2013-01-02T00:38:21+00:00 app[web.1]:     model-eng       : iPhone 4
  
  2013-01-02T00:38:21+00:00 app[web.1]:     make-eng        : Apple
  
  2013-01-02T00:38:21+00:00 app[web.1]:     date-eng        : 2012-12-28T00:39:34+1100
  
  2013-01-02T00:38:21+00:00 app[web.1]:     encoder         : 6.0
  
  2013-01-02T00:38:21+00:00 app[web.1]:     encoder-eng     : 6.0
  
  2013-01-02T00:38:21+00:00 app[web.1]:   Duration: 00:00:00.03, start: 0.000000, bitrate: 9465 kb/s
  
  2013-01-02T00:38:21+00:00 app[web.1]:     Stream #0:0(und): Audio: aac (mp4a / 0x6134706D), 44100 Hz, mono, fltp, 75 kb/s
  
  2013-01-02T00:38:21+00:00 app[web.1]:     date            : 2012-12-28T00:39:34+1100
  
  2013-01-02T00:38:21+00:00 app[web.1]:       creation_time   : 2013-01-02 00:36:58
  
  2013-01-02T00:38:21+00:00 app[web.1]:     make            : Apple
  
  2013-01-02T00:38:21+00:00 app[web.1]:   Metadata:
  
  2013-01-02T00:38:21+00:00 app[web.1]:     Metadata:
  
  2013-01-02T00:38:21+00:00 app[web.1]:       handler_name    : Core Media Data Handler
  
  2013-01-02T00:38:21+00:00 app[web.1]:     Stream #0:1(und): Video: h264 (Main) (avc1 / 0x31637661), yuv420p, 640x360 [SAR 1:1 DAR 16:9], 8605 kb/s, 30 fps, 30 tbr, 600 tbn, 1200 tbc
  
  2013-01-02T00:38:21+00:00 app[web.1]:     Metadata:
  
  2013-01-02T00:38:21+00:00 app[web.1]:       handler_name    : Core Media Data Handler
  
  2013-01-02T00:38:21+00:00 app[web.1]: Unknown encoder 'libx264'
  
  2013-01-02T00:38:21+00:00 app[web.1]: Please use -b:a or -b:v, -b is ambiguous
  
  2013-01-02T00:38:21+00:00 app[web.1]:       creation_time   : 2013-01-02 00:36:58
  
  2013-01-02T00:38:21+00:00 app[web.1]: [paperclip] An error was received while processing: #
  
  2013-01-02T00:38:21+00:00 app[web.1]:   Rendered videos/new.html.erb within layouts/application (3.2ms)
  
  2013-01-02T00:38:21+00:00 heroku[router]: at=info method=POST path=/videos host=stark-sea-5654.herokuapp.com fwd=101.170.255.251 dyno=web.1 queue=0 wait=0ms connect=3ms service=3685ms status=200 bytes=1878
  
  2013-01-02T00:38:21+00:00 app[web.1]:   Rendered layouts/_footer.html.erb (0.0ms)
  
  2013-01-02T00:38:21+00:00 app[web.1]: Completed 200 OK in 342ms (Views: 124.8ms | ActiveRecord: 10.4ms)
  
  2013-01-02T00:38:21+00:00 app[web.1]:   Rendered layouts/_header.html.erb (1.2ms)

  Everything works fine until the message Unknown encoder 'libx264' so I'm thinking it's something to do with ffmpeg perhaps ?

• Matomo’s new story : our stronger vision for the future

  31 octobre 2018, par Matthieu Aubry — Community

  

  Over the past year, the team here at Matomo have been working on a very exciting project we’d love to share with you.

  It’s to do with the impact we hope for Matomo to have.

  As you all know, the world changes at too fast a pace. New technologies, new phones, new everything in the blink of an eye. That’s not what will be happening here.

  Instead, we’d like to believe it’s a refresh. Taking stock of how far we’ve come, what we’ve achieved so far, and how far we still have to go.

  So we’re rebranding.

  The rebrand

  Like a caterpillar emerging from a cocoon, we hope to be a reborn analytics butterfly.

  As a result of some careful planning and reflection we’ll be updating our logo, website and reasserting our voice.

  It’s our chance to look at ourselves in a new light. We are a mighty analytics platform and it should be known we’re comparable to the likes of Google Analytics 360.

  Along with the refresh of imagery, we listened to your feedback about the confusion between our two identities, so we’re also taking this opportunity to unite both the business brand of Innocraft with the community brand Matomo into one website.

  It makes it easier for people from all walks of life, either as individuals or in large companies, to see us as being able to get down to business with a powerful analytics tool, as well as think on behalf of our community.

  We’re the same, but with slight changes in our appearance and a stronger vision for the future.

  How far we’ve come …

  When we started out, it was about building a community around a movement. From the beginning we were concerned about data ownership, privacy and all things that came with that.

  With the help of our community and contributors, we turned Matomo (formerly Piwik) into the trusted #1 open source analytics tool it is today. We’re committed to our community. But we also need to do more.

  We’ve been niche and happy staying small, but now we need to take action and start shouting far and wide about what we do.

  We once said we need : “To create, as a community, the leading international open source digital analytics platform, that gives every user full control of their data.”

  We believe we’ve done that, so we’ll take it one step further.

  A web analytics revolution has begun …

  Begun ?

  The line signifies a new beginning.

  This is us standing up and reasserting our voice.

  Our new chapter.

  The rebrand is our chance to show that, yes, the world is changing, but when it comes to privacy, there are matters meant to be sacred. Privacy is a human right.

  What makes it worse in this ever-changing landscape, with data breaches and stolen information, is that losing control of our data is scary, we have a right to know what’s going on with our information and this must start with us.

  We know we need to champion this cause for privacy and data ownership.

  We came together as a community and built something powerful, a free open-source analytics platform, that kept the integrity of the people using it.

  It’s important for us now to feel more empowered to believe in our right to privacy, information and our ability to act independently of large corporations.

  The time is here for us to speak up and take back control.

  Once more, we need to come together to build something even more powerful, a safer online society.

  Join us.

  Sincerely,
  Matthieu Aubry on behalf of the Matomo team

• Why is one ffmpeg webm dash stream much larger than the others ?

  5 janvier 2017, par ranvel

  Over the summer, I worked on putting together a script which took a x264 video/mp3 stream and broke it up into the different streams so that it would work via MSE-DASH. (Based heavily on the instructions on the webmproject.org website) Those same scripts have ceased to work, turning a 6GB video into several 25 Gb videos. I kept up with updates of ffmpeg and so I don’t know when it stopped working, but I am guessing it was due to the way that their DASH Webm implementation was updated.

  I found new method which works better, but still has a major problem with one stream. I was hoping someone could explain how this encoding works so that I could understand the underlying cause.

  #!/bin/bash
  
  COMMON_OPTS="-map 0:0 -an -threads 11 -cpu-used 4 -cmp chroma"
  
  WEBM_OPTS="-f webm -c:v vp9 -keyint_min 50 -g 50 -dash 1"
  
  
  
  ffmpeg -i $1 -vn -acodec libvorbis -ab 128k audio.webm &
  
  ffmpeg -i $1 $COMMON_OPTS $WEBM_OPTS -b:v 500k -vf scale=1280:720 -y vid-500k.webm &
  
  ffmpeg -i $1 $COMMON_OPTS $WEBM_OPTS -b:v 700k -vf scale=1280:720 -y vid-700k.webm & 
  
  ffmpeg -i $1 $COMMON_OPTS $WEBM_OPTS -b:v 1000k -vf scale=1280:720 -y vid-1000k.webm &
  
  ffmpeg -i $1 $COMMON_OPTS $WEBM_OPTS -b:v 1500k -vf scale=1280:720 -y vid-1500k.webm  

  The transcode is not yet complete, but you can see where this is headed :

  -rw-r--r--  1 user  staff    87M Jan  4 23:27 audio.webm
  
  -rw-r--r--  1 user  staff    27M Jan  4 23:42 vid-1000k.webm
  
  -rw-r--r--  1 user  staff   285M Jan  4 23:42 vid-1500k.webm
  
  -rw-r--r--  1 user  staff    15M Jan  4 23:42 vid-500k.webm
  
  -rw-r--r--  1 user  staff    20M Jan  4 23:42 vid-700k.webm

  The 1500k variant is disproportionately larger than the other streams.

  The other problem is that when I use a shorter video, lets say eight or nine minutes, the above configuration runs as expected and everything is perfect. I don’t know where the limit for this is since each test costs a lot of processing power and time, but if it’s less than ten minutes, it works and if its longer than an hour, it produces massive files.