Recherche avancée

Médias (16)

Mot : - Tags -/mp3

Autres articles (99)

  • MediaSPIP 0.1 Beta version

    25 avril 2011, par

    MediaSPIP 0.1 beta is the first version of MediaSPIP proclaimed as "usable".
    The zip file provided here only contains the sources of MediaSPIP in its standalone version.
    To get a working installation, you must manually install all-software dependencies on the server.
    If you want to use this archive for an installation in "farm mode", you will also need to proceed to other manual (...)

  • Installation en mode standalone

    4 février 2011, par

    L’installation de la distribution MediaSPIP se fait en plusieurs étapes : la récupération des fichiers nécessaires. À ce moment là deux méthodes sont possibles : en installant l’archive ZIP contenant l’ensemble de la distribution ; via SVN en récupérant les sources de chaque modules séparément ; la préconfiguration ; l’installation définitive ;
    [mediaspip_zip]Installation de l’archive ZIP de MediaSPIP
    Ce mode d’installation est la méthode la plus simple afin d’installer l’ensemble de la distribution (...)

  • Les autorisations surchargées par les plugins

    27 avril 2010, par

    Mediaspip core
    autoriser_auteur_modifier() afin que les visiteurs soient capables de modifier leurs informations sur la page d’auteurs

Sur d’autres sites (7849)

  • swresample/arm : remove unintentional relocation.

    19 avril 2018, par Rahul Chaudhry
    swresample/arm : remove unintentional relocation.
    

    Branch to global symbol results in reference to PLT, and when compiling
    for THUMB-2 - in a R_ARM_THM_JUMP19 relocation. Some linkers don't
    support this relocation (ld.gold), while others can end up truncating
    the relocation to fit (ld.bfd).

    Convert this branch through PLT into a direct branch that the assembler
    can resolve locally.

    See https://github.com/android-ndk/ndk/issues/337 for background.

    The current workaround is to disable neon during gstreamer build,
    which is not optimal and can be reverted after this patch :
    https://github.com/freedesktop/gstreamer-cerbero/commit/41556c415739fbc3a72c7eaee7e70a565b719b2f

    Signed-off-by : Michael Niedermayer <michael@niedermayer.cc>

    • [DH] libswresample/arm/audio_convert_neon.S
  • FFmpeg create directory hierarchy for strftime

    23 avril 2017, par David

    Recently bought an ip-cam which outputs a RTSP stream. I’m using the segment option of FFmpeg to create 30 minute long recordings.

    I want FFmpeg to write the files to a directory based on Year/Month/Date, and write to a file Hour-Minute.mp4 For example :
    /raid1/homes/share/public/recordings/queue/bedroom/2017/04/23/13-05.mp4 for a recording started on 23 april 2017, 13:05.

    Unfortunately FFmpeg seems to not create the directory hierarchy. FFmpeg quits since the directory can not be found.

    Input #0, rtsp, from 'rtsp://192.168.1.240/unicast':
     Metadata:
       title           : LIVE555 Streaming Media v2014.07.04
       comment         : LIVE555 Streaming Media v2014.07.04
     Duration: N/A, start: 0.000750, bitrate: N/A
       Stream #0:0: Video: h264 (High), yuv420p, 1920x1080, 90k tbr, 90k tbn, 180k tbc
       Stream #0:1: Audio: pcm_alaw, 8000 Hz, 1 channels, s16, 64 kb/s
    [segment @ 0x2557300] Using AVStream.codec to pass codec parameters to muxers is deprecated, use AVStream.codecpar instead.
    [segment @ 0x2557300] Failed to open segment '/raid1/homes/share/public/recordings/queue/bedroom/2017/04/23/14-19.mp4'
    Output #0, segment, to '/raid1/homes/share/public/recordings/queue/bedroom/%Y/%m/%d/%H-%M.mp4':
     Metadata:
       title           : LIVE555 Streaming Media v2014.07.04
       comment         : LIVE555 Streaming Media v2014.07.04
       encoder         : Lavf57.41.100
       Stream #0:0: Video: h264, yuv420p, 1920x1080, q=2-31, 90k tbr, 90k tbn, 90k tbc
    Stream mapping:
     Stream #0:0 -> #0:0 (copy)
    Could not write header for output file #0 (incorrect codec parameters ?): No such file or directory

    record.sh is as follows :

    #!/bin/sh
    ffmpeg -stimeout 600\
    -rtsp_transport udp \
    -i rtsp://192.168.1.240/unicast \
    -c copy \
    -map 0:0 \
    -f segment \
    -segment_time 3600 \
    -segment_wrap 100 \
    -segment_format mov \
    -strftime 1 \
    -reset_timestamps 1 \
    "/raid1/homes/share/public/recordings/queue/bedroom/%Y/%m/%d/%H-%M.mp4"

    I’ve tried not using a directory hierachy : "/raid1/homes/share/public/recordings/queue/bedroom/%Y-%m-%d_%H-%M.mp4". This works fine.

    $ ffmpeg -version
    ffmpeg version N-80901-gfebc862 Copyright (c) 2000-2016 the FFmpeg developers
    built with gcc 4.8 (Ubuntu 4.8.4-2ubuntu1~14.04.3)
    configuration: --extra-libs=-ldl --prefix=/opt/ffmpeg --mandir=/usr/share/man --enable-avresample --disable-debug --enable-nonfree --enable-gpl --enable-version3 --enable-libopencore-amrnb --enable-libopencore-amrwb --disable-decoder=amrnb --disable-decoder=amrwb --enable-libpulse --enable-libfreetype --enable-gnutls --enable-libx264 --enable-libx265 --enable-libfdk-aac --enable-libvorbis --enable-libmp3lame --enable-libopus --enable-libvpx --enable-libspeex --enable-libass --enable-avisynth --enable-libsoxr --enable-libxvid --enable-libvidstab
    libavutil      55. 28.100 / 55. 28.100
    libavcodec     57. 48.101 / 57. 48.101
    libavformat    57. 41.100 / 57. 41.100
    libavdevice    57.  0.102 / 57.  0.102
    libavfilter     6. 47.100 /  6. 47.100
    libavresample   3.  0.  0 /  3.  0.  0
    libswscale      4.  1.100 /  4.  1.100
    libswresample   2.  1.100 /  2.  1.100
    libpostproc    54.  0.100 / 54.  0.100

    Can FFmpeg create output directories on the go ?

  • Patching FFmpeg to extract more detailed MV information

    13 février 2018, par helmo

    I am new to video compression and in the past one month I have been studying and reading a lot on this topic. My main aim as of now is to be able to extract in a meaningful way, motion vectors data into a text file.

    Some may write about ffmpeg’s extract_mvs.c but I have already explored this example file and is not returning the complete information I would like to get, for instance, the output of this file does not tell the frame type nor whether a backward or forward motion vector was used for a particular frame number.

    I saw here on SO a similar post that had as answers to explore ’patch’ of FFMpeg to get more meaningful information, that’s a reply from Ronald.

    Is there anyone in the community who can help in expanding this file and get more out of ffmpeg ? Does anyone know about this patch and what it means/entails ?

    Thanks in advance.