Recherche avancée

Médias (91)

Autres articles (26)

  • La file d’attente de SPIPmotion

    28 novembre 2010, par

    Une file d’attente stockée dans la base de donnée
    Lors de son installation, SPIPmotion crée une nouvelle table dans la base de donnée intitulée spip_spipmotion_attentes.
    Cette nouvelle table est constituée des champs suivants : id_spipmotion_attente, l’identifiant numérique unique de la tâche à traiter ; id_document, l’identifiant numérique du document original à encoder ; id_objet l’identifiant unique de l’objet auquel le document encodé devra être attaché automatiquement ; objet, le type d’objet auquel (...)

  • Contribute to documentation

    13 avril 2011

    Documentation is vital to the development of improved technical capabilities.
    MediaSPIP welcomes documentation by users as well as developers - including : critique of existing features and functions articles contributed by developers, administrators, content producers and editors screenshots to illustrate the above translations of existing documentation into other languages
    To contribute, register to the project users’ mailing (...)

  • Support de tous types de médias

    10 avril 2011

    Contrairement à beaucoup de logiciels et autres plate-formes modernes de partage de documents, MediaSPIP a l’ambition de gérer un maximum de formats de documents différents qu’ils soient de type : images (png, gif, jpg, bmp et autres...) ; audio (MP3, Ogg, Wav et autres...) ; vidéo (Avi, MP4, Ogv, mpg, mov, wmv et autres...) ; contenu textuel, code ou autres (open office, microsoft office (tableur, présentation), web (html, css), LaTeX, Google Earth) (...)

Sur d’autres sites (4245)

  • Having issues with kdenlive screen capture mode

    5 décembre 2018, par brianH

    Am running new repository install of kdenlive on ubuntu 18.04 after having similar problem on 16.04 but the problem persists "failed to start the capture application" when i start in screen capture mode. This problem was also present when I used kdenlive appImages.
    The current kdenlive version is 17.12.3 and i’ve tried changing kdenlive config settings, switching to default settings etc. also cleaned the /.cache/kdenlive file ..

    Ironically, when I use gdb kdenlive then run, the capture device works. Although then there is a separate issue of playing the video with the project monitor.

    On the previous 16.04 build had an addition log message that libvorbis was not recognized when the capture application failed.

    I had purged, autoremove packages and Resinstalled, also reinstalled ffmpeg and the installed libvorbis packages.
    Running ffmpeg gives :
    ffmpeg version 3.4.4-0ubuntu0.18.04.1 Copyright (c) 2000-2018 the FFmpeg developers
    built with gcc 7 (Ubuntu 7.3.0-16ubuntu3)
    configuration : —prefix=/usr —extra-version=0ubuntu0.18.04.1 —toolchain=hardened —libdir=/usr/lib/x86_64-linux-gnu —incdir=/usr/include/x86_64-linux-gnu —enable-gpl —disable-stripping —enable-avresample —enable-avisynth —enable-gnutls —enable-ladspa —enable-libass —enable-libbluray —enable-libbs2b —enable-libcaca —enable-libcdio —enable-libflite —enable-libfontconfig —enable-libfreetype —enable-libfribidi —enable-libgme —enable-libgsm —enable-libmp3lame —enable-libmysofa —enable-libopenjpeg —enable-libopenmpt —enable-libopus —enable-libpulse —enable-librubberband —enable-librsvg —enable-libshine —enable-libsnappy —enable-libsoxr —enable-libspeex —enable-libssh —enable-libtheora —enable-libtwolame —enable-libvorbis —enable-libvpx —enable-libwavpack —enable-libwebp —enable-libx265 —enable-libxml2 —enable-libxvid —enable-libzmq —enable-libzvbi —enable-omx —enable-openal —enable-opengl —enable-sdl2 —enable-libdc1394 —enable-libdrm —enable-libiec61883 —enable-chromaprint —enable-frei0r —enable-libopencv —enable-libx264 —enable-shared
    libavutil 55. 78.100 / 55. 78.100
    libavcodec 57.107.100 / 57.107.100
    libavformat 57. 83.100 / 57. 83.100
    libavdevice 57. 10.100 / 57. 10.100
    libavfilter 6.107.100 / 6.107.100
    libavresample 3. 7. 0 / 3. 7. 0
    libswscale 4. 8.100 / 4. 8.100
    libswresample 2. 9.100 / 2. 9.100
    libpostproc 54. 7.100 / 54. 7.100

    Any thoughts on this ?

  • ffmpeg not generating palettes

    2 décembre 2018, par sk84z

    I downloaded ffmpeg and ran the command found in the documentation to generate palettes :

    ffmpeg -i input.mkv -vf palettegen palette.png

    The only difference being my input was input.mp4 instead of input.mkv.

    No file gets generated. Here’s the console output from PowerShell :

    ffmpeg version 3.4 Copyright (c) 2000-2017 the FFmpeg developers  
    
  built with gcc 7.2.0 (GCC)
    
  configuration: --enable-gpl --enable-version3 --enable-sdl2 --enable-bzlib --enable-fontconfig --enable-gnutls --enable-iconv --enable-libass --enable-libbluray --enable-libfreetype --enable-libmp3lame --enable-libopenjpeg --enable-libopus --enable-libshine --enable-libsnappy --enable-libsoxr --enable-libtheora --enable-libtwolame --enable-libvpx --enable-libwavpack --enable-libwebp --enable-libx264 --enable-libx265 --enable-libxml2 --enable-libzimg --enable-lzma --enable-zlib --enable-gmp --enable-libvidstab --enable-libvorbis --enable-cuda --enable-cuvid --enable-d3d11va --enable-nvenc --enable-dxva2 --enable-avisynth --enable-libmfx
    
  libavutil      55. 78.100 / 55. 78.100
    
  libavcodec     57.107.100 / 57.107.100
    
  libavformat    57. 83.100 / 57. 83.100
    
  libavdevice    57. 10.100 / 57. 10.100
    
  libavfilter     6.107.100 /  6.107.100
    
  libswscale      4.  8.100 /  4.  8.100
    
  libswresample   2.  9.100 /  2.  9.100
    
  libpostproc    54.  7.100 / 54.  7.100
    
Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'input.mp4':
    
  Metadata:
    
    major_brand     : mp42
    
    minor_version   : 0
    
    compatible_brands: mp41isom
    
    creation_time   : 2018-11-23T23:27:38.000000Z
    
  Duration: 00:00:09.98, start: 0.000000, bitrate: 2784 kb/s
    
    Stream #0:0(und): Video: h264 (Main) (avc1 / 0x31637661), yuv420p, 580x328 [SAR 1:1 DAR 145:82], 2699 kb/s, 30 fps, 30 tbr, 30k tbn, 60 tbc (default)
    
    Metadata:
    
      creation_time   : 2018-11-23T23:27:38.000000Z
    
      handler_name    : VideoHandler
    
      encoder         : AVC Coding
    
    Stream #0:1(und): Audio: aac (LC) (mp4a / 0x6134706D), 44100 Hz, mono, fltp, 79 kb/s (default)
    
    Metadata:
    
      creation_time   : 2018-11-23T23:27:38.000000Z
    
      handler_name    : SoundHandler
    
Stream mapping:
    
  Stream #0:0 -> #0:0 (h264 (native) -> png (native))
    
Press [q] to stop, [?] for help
    
Output #0, image2, to 'palette.png':
    
  Metadata:
    
    major_brand     : mp42
    
    minor_version   : 0
    
    compatible_brands: mp41isom
    
    encoder         : Lavf57.83.100
    
    Stream #0:0(und): Video: png, rgba, 16x16 [SAR 1:1 DAR 1:1], q=2-31, 200 kb/s, 30 fps, 30 tbn, 30 tbc (default)
    
    Metadata:
    
      creation_time   : 2018-11-23T23:27:38.000000Z
    
      handler_name    : VideoHandler
    
      encoder         : Lavc57.107.100 png
    
[Parsed_palettegen_0 @ 00000296510def00] 255(+1) colors generated out of 285516 colors; ratio=0.000893
    
[Parsed_palettegen_0 @ 00000296510def00] Dupped color: FF000001

    Any ideas ?

  • Using ffmpeg to scale app preview videos for the AppStore

    1er décembre 2018, par Felipe Ferri

    I’m generating an app preview video to send to the AppStore. Depending on the device type, the AppStore requires certain video resolutions.

    I have a main video, with resolution 1920x1080, which I was able to upload.

    I need to generate another video with the resolution 1920x886 for supporting 6.5" devices, so I used the following command to perform the scaling :

    ffmpeg -i video_1920_1080.mp4 -vf scale=1920:886 -c:a copy video_1920_886.mp4

    If I get the info for the generated video using ffmpeg -i I get the following result :

    ffmpeg -i video_1920_886.mp4
    

    
ffmpeg version 3.4.2 Copyright (c) 2000-2018 the FFmpeg developers
    
  built with Apple LLVM version 9.0.0 (clang-900.0.39.2)
    
  configuration: --prefix=/usr/local/Cellar/ffmpeg/3.4.2 --enable-shared --enable-pthreads --enable-version3 --enable-hardcoded-tables --enable-avresample --cc=clang --host-cflags= --host-ldflags= --disable-jack --enable-gpl --enable-libmp3lame --enable-libx264 --enable-libxvid --enable-opencl --enable-videotoolbox --disable-lzma
    
  libavutil      55. 78.100 / 55. 78.100
    
  libavcodec     57.107.100 / 57.107.100
    
  libavformat    57. 83.100 / 57. 83.100
    
  libavdevice    57. 10.100 / 57. 10.100
    
  libavfilter     6.107.100 /  6.107.100
    
  libavresample   3.  7.  0 /  3.  7.  0
    
  libswscale      4.  8.100 /  4.  8.100
    
  libswresample   2.  9.100 /  2.  9.100
    
  libpostproc    54.  7.100 / 54.  7.100
    
Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'hittin_1920_886.mp4':
    
  Metadata:
    
    major_brand     : isom
    
    minor_version   : 512
    
    compatible_brands: isomiso2avc1mp41
    
    encoder         : Lavf57.83.100
    
  Duration: 00:00:29.13, start: 0.000000, bitrate: 705 kb/s
    
    Stream #0:0(eng): Video: h264 (High) (avc1 / 0x31637661), yuv420p, 1920x886 [SAR 443:540 DAR 16:9], 694 kb/s, 30 fps, 30 tbr, 15360 tbn, 60 tbc (default)
    
    Metadata:
    
      handler_name    : VideoHandler
    
      timecode        : 00:00:10:20
    
    Stream #0:1(und): Audio: aac (LC) (mp4a / 0x6134706D), 44100 Hz, stereo, fltp, 2 kb/s (default)
    
    Metadata:
    
      handler_name    : SoundHandler
    
    Stream #0:2(eng): Data: none (tmcd / 0x64636D74), 0 kb/s
    
    Metadata:
    
      handler_name    : TimeCodeHandler
    
      timecode        : 00:00:10:20

    Ok, so it seems the output video is in the correct 1920x886 resolution.

    However, when I try to upload this video the AppStore complains that the video is in the incorrect resolution.

    If I open the file properties window on macos, the following information appears for the same video :

    Properties of video_1920_886.mp4

    And, if I open the same video on VLC, I can see the following info on the Media Info screen :

    Codec Details on VLC

    So :

    1. ffmpeg -i tells me the video is in the resolution 1920x886.
    2. macos file properties tells me the video is in the resolution 1575x886.
    3. VLC tells me the video has a Resolution of 1920x898 and a Display Resolution of 1920x886.

    Why are there three different resolutions ? How can I change each one of them ? I suppose the appstoreconnect website expects the file properties resolution to be 1920x886. How can I change that ?

Navigation