Recherche avancée

Médias (91)

Autres articles (21)

  • Use, discuss, criticize

    13 avril 2011, par

    Talk to people directly involved in MediaSPIP’s development, or to people around you who could use MediaSPIP to share, enhance or develop their creative projects.
    The bigger the community, the more MediaSPIP’s potential will be explored and the faster the software will evolve.
    A discussion list is available for all exchanges between users.

  • Contribute to a better visual interface

    13 avril 2011

    MediaSPIP is based on a system of themes and templates. Templates define the placement of information on the page, and can be adapted to a wide range of uses. Themes define the overall graphic appearance of the site.
    Anyone can submit a new graphic theme or template and make it available to the MediaSPIP community.

  • Contribute to translation

    13 avril 2011

    You can help us to improve the language used in the software interface to make MediaSPIP more accessible and user-friendly. You can also translate the interface into any language that allows it to spread to new linguistic communities.
    To do this, we use the translation interface of SPIP where the all the language modules of MediaSPIP are available. Just subscribe to the mailing list and request further informantion on translation.
    MediaSPIP is currently available in French and English (...)

Sur d’autres sites (5449)

  • FFMPEG - Scale video filter not providing expected results

    11 novembre 2011, par dpassera

    Apologies if this question has been asked. I couldn't find it, but if it has, please let me know and I'll close this out.

    I'm attempting a simple scale of a video whose original dimensions are 480x360 and whose target dimensions are 400x300. The video starts as an FLV and eventually needs to end up as an MPEG. I'm using the following command line to do this :

    ffmpeg -i user.flv -vf "scale=400:300" user_scaled.mpg

    When I play the scaled video in MPEG Streamclip, the scale is correct and the video info shows that the dimensions are 400x300. However, when I play the scaled video in Quicktime, the video is scaled to 478x359. More importantly, FFMPEG, itself, treats the video as being 478x359, so any future commands (trimming, conversion, overlaying, etc) executed on it result in a video of 478x359.

    The initial workflow required an FLV to MPEG conversion, but I've tried this with several different in and out formats (FLV -> FLV, FLV -> MPEG, MPEG -> MPEG, etc) all with the same results. As long as I can end up with an MPEG, though, I can deal with however many steps and conversions it would take to get this scaling working.

    I'll paste the command-line output below, and a sample input video is also linked below, if you'd like it. Thank you very much for any help.

    http://www.monkeydriver.com/dpassera/stack_flv.zip

    Command-line output :

    ffmpeg -i user.flv -vf "scale=400:300" user_scaled.mpg

    ffmpeg version 0.7-rc1, Copyright (c) 2000-2011 the FFmpeg developers
     built on May 21 2011 22:13:19 with gcc 4.1.2 20080704 (Red Hat 4.1.2-50)
     configuration: --prefix=/usr --libdir=/usr/lib64 --shlibdir=/usr/lib64
    --mandir=/usr/share/man --incdir=/usr/include --disable-avisynth
    --extra-cflags='-O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions
    -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic -fPIC'
    --enable-avfilter --enable-libdirac --enable-libgsm --enable-libmp3lame
    --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libx264
    --enable-gpl --enable-postproc --enable-pthreads --enable-shared
    --enable-swscale --enable-vdpau --enable-version3 --enable-x11grab
    --disable-yasm --enable-filters --enable-filter=movie

     libavutil    50. 40. 1 / 50. 40. 1
     libavcodec   52.120. 0 / 52.120. 0
     libavformat  52.108. 0 / 52.108. 0
     libavdevice  52.  4. 0 / 52.  4. 0
     libavfilter   1. 77. 0 /  1. 77. 0
     libswscale    0. 13. 0 /  0. 13. 0
     libpostproc  51.  2. 0 / 51.  2. 0

    [flv @ 0x11dd3b30] Estimating duration from bitrate, this may be inaccurate
    Input #0, flv, from 'user.flv':

     Metadata:
       duration        : 5
       videocodecid    : 2
       audiocodecid    : 6
       canSeekToEnd    : true
       createdby       : FMS 4.0
       creationdate    : Mon Oct 31 11:43:44 2011

     Duration: 00:00:04.62, start: 0.000000, bitrate: N/A
       Stream #0.0: Video: flv, yuv420p, 640x480, 1k tbr, 1k tbn, 1k tbc
       Stream #0.1: Audio: nellymoser, 44100 Hz, mono, s16

    [buffer @ 0x11ddc950] w:640 h:480 pixfmt:yuv420p

    [scale @ 0x11dda610] w:640 h:480 fmt:yuv420p -> w:400 h:300 fmt:yuv420p flags:0xa0000004

    [mpeg @ 0x11dd6bd0] VBV buffer size not set, muxing may fail

    Output #0, mpeg, to 'user_scaled.mpg':
     Metadata:
       duration        : 5
       videocodecid    : 2
       audiocodecid    : 6
       canSeekToEnd    : true
       createdby       : FMS 4.0
       creationdate    : Mon Oct 31 11:43:44 2011
       encoder         : Lavf52.108.0

       Stream #0.0: Video: mpeg1video, yuv420p, 400x300, q=2-31, 200 kb/s, 90k tbn, 60 tbc

       Stream #0.1: Audio: mp2, 44100 Hz, mono, s16, 64 kb/s

    Stream mapping:
    Stream #0.0 -> #0.0
    Stream #0.1 -> #0.1

    Press [q] to stop encoding
    frame=  230 fps=  0 q=10.2 size=     366kB time=3.82 bitrate= 785.6kbits/s dup=175 drop=0
    frame=  267 fps=  0 q=10.7 Lsize=     412kB time=4.43 bitrate= 761.3kbits/s dup=203 drop=0    

    video:370kB audio:36kB global headers:0kB muxing overhead 1.568959%
  • Rails 3 : How can I make Paperclip-FFMPEG work ?

    9 novembre 2011, par remino

    I have Rails 3.0.3 with these gems :

    • delayed_job 2.1.4
    • delayed_paperclip 0.7.1
    • paperclip 2.3.16
    • paperclip-ffmpeg 0.7.0

    (This combination is very specific. Some newer gems will not work with others.)

    Here's my Video model :

    class Video < Upload
     has_attached_file :file, :default_style => :view, :processors => [:ffmpeg],
       :url => '/system/:class/:attachment/:id/:style/:basename.:extension',
       :path => ':rails_root/public/system/:class/:attachment/:id/:style' \
         + '/:basename.:extension',
       :default_url => '/images/en/processing.png',
       :styles => {
         :mp4video => { :geometry => '520x390', :format => 'mp4',
           :convert_options => { :output => { :vcodec => 'libx264',
             :vpre => 'ipod640', :b => '250k', :bt => '50k',
             :acodec => 'libfaac', :ab => '56k', :ac => 2 } } },
         :oggvideo => { :geometry => '520x390', :format => 'ogg',
           :convert_options => { :output => { :vcodec => 'libtheora',
             :b => '250k', :bt => '50k', :acodec => 'libvorbis',
             :ab => '56k', :ac => 2 } } },
         :view => { :geometry => '520x390', :format => 'jpg', :time => 1 },
         :preview => { :geometry => '160x120', :format => 'jpg', :time => 1 }
       }
     validates_attachment_content_type :file, :content_type => VIDEOTYPES,
       :if => Proc.new { |upload| upload.file.file? }
     process_in_background :file
    end

    When creating a new Video object with attachment, the original is saved, but no conversion will be done. Even calling Video.last.file.reprocess! won't to a thing except returning true. (Not sure what "true" means in this case as it didn't work.)

    I tried hardcoding the path to ffmpeg in Paperclip::options[:command_path]. I even tried deleting the paperclip-ffmpeg.rb file and replacing it with a blank file. Really thinking I'd get an exception by doing the later, instead, I simply got "true" again.

    It feels like the paperclip-ffmpeg.rb is being loaded, because it is required by config/application.rb, but nothing is called in it when trying to generate a thumbnail or convert a video.

    Can anyone help me with this ? Thanks in advance !

  • Révision 19472 : inc/plugin.php : donner la possibilité d’installer un plugin sans tenir compte d...

    26 mai 2012, par denisb@a-working-class-hero-is-something-to.be

    déclarer dans mes_options.php : define(’_DEV_PLUGINS’, true) ; ceci peut être DANGEREUX ! à réserver aux phases de test et de développement.