Recherche avancée

Médias (0)

Mot : - Tags -/xmlrpc

Aucun média correspondant à vos critères n’est disponible sur le site.

Autres articles (94)

  • Gestion des droits de création et d’édition des objets

    8 février 2011, par

    Par défaut, beaucoup de fonctionnalités sont limitées aux administrateurs mais restent configurables indépendamment pour modifier leur statut minimal d’utilisation notamment : la rédaction de contenus sur le site modifiables dans la gestion des templates de formulaires ; l’ajout de notes aux articles ; l’ajout de légendes et d’annotations sur les images ;

  • Supporting all media types

    13 avril 2011, par

    Unlike most software and media-sharing platforms, MediaSPIP aims to manage as many different media types as possible. The following are just a few examples from an ever-expanding list of supported formats : images : png, gif, jpg, bmp and more audio : MP3, Ogg, Wav and more video : AVI, MP4, OGV, mpg, mov, wmv and more text, code and other data : OpenOffice, Microsoft Office (Word, PowerPoint, Excel), web (html, CSS), LaTeX, Google Earth and (...)

  • Dépôt de média et thèmes par FTP

    31 mai 2013, par

    L’outil MédiaSPIP traite aussi les média transférés par la voie FTP. Si vous préférez déposer par cette voie, récupérez les identifiants d’accès vers votre site MédiaSPIP et utilisez votre client FTP favori.
    Vous trouverez dès le départ les dossiers suivants dans votre espace FTP : config/ : dossier de configuration du site IMG/ : dossier des média déjà traités et en ligne sur le site local/ : répertoire cache du site web themes/ : les thèmes ou les feuilles de style personnalisées tmp/ : dossier de travail (...)

Sur d’autres sites (11477)

  • What type file to pass to FFMPEG::Movie.new(file) in the gem ffmpeg (heroku)

    31 août 2020, par AlbertMunichMar

    I have a Rails app hosted in Heroku. I am using the gem ffmpeg to record screenshots.

    


    I get a video from a React App in my controller :

    


    video = params[:video].tempfile
# #tmp/RackMultipart20200831-4-zgw094.mp4>


    


    I try to pass this object, but does not work :

    


    Errno::ENOENT (No such file or directory - the ffprobe binary could not be found in /app/vendor/bundle/ruby/2.5.0/bin:/app/bin:/app/vendor/bundle/bin:/usr/local/bin:/usr/bin:/bin):


    


    I thought it should worked, since FFMPEG::Movie.new(file) is asking for the path, and I am providing it :

    


    Parameters: {"video"=>#, @original_filename="89.mp4", @content_type="video/mp4", @headers="Content-Disposition: form-data; name=\"video\"; filename=\"89.mp4\"\r\nContent-Type: video/mp4\r\n">}


    


    see : tmp/RackMultipart20200831-4-q2yi74.mp4>. This is the temp path right ?

    


    Maybe it's looking for the file in the wrong path, but how can I specify it ?

    


    I also tried :

    


    File.open(video, 'r') do |file|
  FFMPEG::Movie.new(file.path)
end


    


    But also wrong path. Could someone help me ?

    


    Buildpack is installed in heroku.

    


    I used the CLI installation :

    


    heroku create --buildpack https://github.com/FFmpeg/FFmpeg.git


    


    With following output :

    


    remote: -----> ffmpeg app detected
remote: -----> Install ffmpeg
remote:        DOWNLOAD_URL =  https://johnvansickle.com/ffmpeg/builds/ffmpeg-git-amd64-static.tar.xz
remote:        exporting PATH
remote: -----> Discovering process types
remote:        Procfile declares types -> (none)


    


    It seems to be installed.

    


    But I keep getting this error :

    


    2020-08-31T15:56:24.157721+00:00 heroku[router]: at=error code=H14 desc="No web processes running" method=POST path="/nodes" host=wikisalsaapi.herokuapp.com request_id=35e23352-005a-4178-bda1-0bed65885c0d fwd="46.128.35.112" dyno= connect= service= status=503 bytes= protocol=https
2020-08-31T15:57:08.000000+00:00 app[api]: Build started by user albert.montolio@gmail.com
2020-08-31T15:57:31.843422+00:00 app[api]: Deploy 038e1b47 by user albert.montolio@gmail.com
2020-08-31T15:57:31.843422+00:00 app[api]: Release v76 created by user albert.montolio@gmail.com
2020-08-31T15:57:34.000000+00:00 app[api]: Build succeeded
2020-08-31T15:58:37.767157+00:00 heroku[router]: at=error code=H14 desc="No web processes running" method=POST path="/nodes" host=wikisalsaapi.herokuapp.com request_id=365fe1a2-091e-479a-b9b6-02c0b70ed754 fwd="46.128.35.112" dyno= connect= service= status=503 bytes= protocol=https


    


  • FFmpeg proccess killed while converting .mov file

    10 novembre 2020, par Vala Khosravi

    I'm using FFmpeg to reduce my videos file size when I give a .mov file as an input with this command :

    


    ffmpeg -i in.mov -c:a copy -crf 20 out.mov


    


    program start working and after a while, it gets killed. here are the last lines of the log that I get :

    


    Output #0, mov, to '/home/ubuntu/test.mov':
  Metadata:
    major_brand     : qt
    minor_version   : 0
    compatible_brands: qt
    com.apple.quicktime.creationdate: 2020-08-29T15:03:17+0430
    com.apple.quicktime.make: Apple
    com.apple.quicktime.model: MacBookPro14,1
    com.apple.quicktime.software: Mac OS X 10.15.1 (19B88)
    encoder         : Lavf57.83.100
    Stream #0:0(und): Video: h264 (libx264) (avc1 / 0x31637661), yuv420p, 2866x1716 [SAR 1:1 DAR 1433:858], q=-1--1, 60 fps, 15360 tbn, 60 tbc (default)
    Metadata:
      creation_time   : 2020-11-10T09:04:43.000000Z
      handler_name    : Core Media Data Handler
      encoder         : Lavc57.107.100 libx264
    Side data:
      cpb: bitrate max/min/avg: 0/0/0 buffer size: 0 vbv_delay: -1
    Stream #0:1(und): Audio: aac (LC) (mp4a / 0x6134706D), 44100 Hz, stereo, fltp, 207 kb/s (default)
    Metadata:
      creation_time   : 2020-11-10T09:04:43.000000Z
      handler_name    : Core Media Data Handler
Killed   23 fps=3.6 q=0.0 size=       0kB time=00:00:01.34 bitrate=   0.0kbits/s dup=1 drop=0 speed=0.21x


    


    I tried so many different flags for FFmpeg but still getting the same error.

    


    What's the solution ?
here is my input video file

    


  • ffmpeg options for encoding a video mpeg2video but with .mov extension

    20 septembre 2020, par Selene

    I just finished a project, and need to produce an output in the specific format, should be exactly the same as the format of the video I received.
The best way for me to identify the source format was to use ffprobe. Here was the output of that :

    


    Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'input.mov':
  Metadata:
    creation_time   : 2020-02-27T04:15:23.000000Z
  Duration: 00:00:22.13, start: 0.000000, bitrate: 111320 kb/s
    Stream #0:0(eng): Video: mpeg2video (4:2:2) (xd5c / 0x63356478), yuv422p(tv, bt709, top coded first (swapped)), 1920x1080 [SAR 1:1 DAR 16:9], 109779 kb/s, 54.94 fps, 54.94 tbr, 5494 tbn, 50 tbc (default)
    Metadata:
      creation_time   : 2020-02-27T04:15:23.000000Z
      handler_name    : Gestor de contenido de v?deo Apple
      encoder         : XDCAM HD422 1080i50 (50 Mb/s)
    Stream #0:1(eng): Audio: pcm_s16be (twos / 0x736F7774), 48000 Hz, 2 channels, s16, 1536 kb/s (default)
    Metadata:
      creation_time   : 2020-02-27T04:15:23.000000Z
      handler_name    : Gestor de contenido de sonido Apple


    


    I did a lot of video work on the above file, and as part of my pipeline, I converted the file to ProRes4444. Now I need to get this video into the same format as above.

    


    Couple of questions on the format, if I understand it correctly, mpeg2video is mpeg2, this would not normally appear as .mov file, but the source is as mov container. Why ?

    


    Does the encoder from the input format matter ? specifically the XDCAM ?

    


    Alternative to solving my problem would be to use media encoder, but even that application doesn't seem to give me options at mov + mpeg2, and if it is mov, it almost forces to use Apple ProRes to keep high resolution. Also, none of the options allow me to set fps at the source level, which is 54.94, and the closest option I have is 59.94.

    


    Please help,