Recherche avancée

Médias (1)

Mot : - Tags -/sintel

Autres articles (22)

  • Personnaliser en ajoutant son logo, sa bannière ou son image de fond

    5 septembre 2013, par

    Certains thèmes prennent en compte trois éléments de personnalisation : l’ajout d’un logo ; l’ajout d’une bannière l’ajout d’une image de fond ;

  • Ecrire une actualité

    21 juin 2013, par

    Présentez les changements dans votre MédiaSPIP ou les actualités de vos projets sur votre MédiaSPIP grâce à la rubrique actualités.
    Dans le thème par défaut spipeo de MédiaSPIP, les actualités sont affichées en bas de la page principale sous les éditoriaux.
    Vous pouvez personnaliser le formulaire de création d’une actualité.
    Formulaire de création d’une actualité Dans le cas d’un document de type actualité, les champs proposés par défaut sont : Date de publication ( personnaliser la date de publication ) (...)

  • Publier sur MédiaSpip

    13 juin 2013

    Puis-je poster des contenus à partir d’une tablette Ipad ?
    Oui, si votre Médiaspip installé est à la version 0.2 ou supérieure. Contacter au besoin l’administrateur de votre MédiaSpip pour le savoir

Sur d’autres sites (6247)

  • ffmpeg use gpu to encode mpeg4 to ts/m3u8 [closed]

    14 novembre 2024, par danielRICADO

    using ffmpeg I want to trim and transcode a mpeg4 from ts / m3u8

    


    std::string ffmpeg_command = "ffmpeg -hwaccel drm -i " + output_dir + input_file +
                         " -ss 00:00:00.00 -t 31 -c:v " + codec + " -b:v " + std::to_string(bitrate) +
                         " -vf scale=" + std::to_string(width) + "x" + std::to_string(height) +
                         " -hls_time " + std::to_string(30) + " -hls_list_size 0 -hls_segment_filename " +
                         ts_file_pattern + " -f hls " + m3u8_file;


    


    I wanted to choose between codecs based on the system, if gpu is avaiable I'd like to opt to use it, right now I just check if the codec is available

    


    bool is_h264_v4l2m2m_available() {
    std::string result = exec_command("ffmpeg -encoders 2>&1");
    return result.find("h264_v4l2m2m") != std::string::npos;
}


    


    if it is a I wanted to move that process over to the gpu, not just use libx264. Here is the error log. Studying hard on the solution but wold super apperciate any expert advice.

    


    other considerations are - runs in a docker container on a pi5, pibian on the host apline on in the container, container runs in privledged mode

    


    2024-11-14 15:18:41 [INFO]: assigned codec: h264_v4l2m2m
2024-11-14 15:18:41 ffmpeg version 6.1.1 Copyright (c) 2000-2023 the FFmpeg developers
2024-11-14 15:18:41   built with gcc 13.2.1 (Alpine 13.2.1_git20240309) 20240309
2024-11-14 15:18:41   configuration: --prefix=/usr --disable-librtmp --disable-lzma --disable-static --disable-stripping --enable-avfilter --enable-gpl --enable-ladspa --enable-libaom --enable-libass --enable-libbluray --enable-libdav1d --enable-libdrm --enable-libfontconfig --enable-libfreetype --enable-libfribidi --enable-libharfbuzz --enable-libmp3lame --enable-libopenmpt --enable-libopus --enable-libplacebo --enable-libpulse --enable-librav1e --enable-librist --enable-libsoxr --enable-libsrt --enable-libssh --enable-libtheora --enable-libv4l2 --enable-libvidstab --enable-libvorbis --enable-libvpx --enable-libwebp --enable-libx264 --enable-libx265 --enable-libxcb --enable-libxml2 --enable-libxvid --enable-libzimg --enable-libzmq --enable-lto=auto --enable-lv2 --enable-openssl --enable-pic --enable-postproc --enable-pthreads --enable-shared --enable-vaapi --enable-vdpau --enable-version3 --enable-vulkan --optflags=-O3 --enable-libjxl --enable-libsvtav1 --enable-libvpl
2024-11-14 15:18:41   libavutil      58. 29.100 / 58. 29.100
2024-11-14 15:18:41   libavcodec     60. 31.102 / 60. 31.102
2024-11-14 15:18:41   libavformat    60. 16.100 / 60. 16.100
2024-11-14 15:18:41   libavdevice    60.  3.100 / 60.  3.100
2024-11-14 15:18:41   libavfilter     9. 12.100 /  9. 12.100
2024-11-14 15:18:41   libswscale      7.  5.100 /  7.  5.100
2024-11-14 15:18:41   libswresample   4. 12.100 /  4. 12.100
2024-11-14 15:18:41   libpostproc    57.  3.100 / 57.  3.100
2024-11-14 15:18:42 Input #0, mov,mp4,m4a,3gp,3g2,mj2, from '/app/client-data/camera-output/7ea3cbef-4da0-11ed-bdcc-baf70a43c072/1731550687270.mp4':
2024-11-14 15:18:42   Metadata:
2024-11-14 15:18:42     major_brand     : isom
2024-11-14 15:18:42     minor_version   : 512
2024-11-14 15:18:42     compatible_brands: isomiso2avc1mp41
2024-11-14 15:18:42     encoder         : Lavf60.16.100
2024-11-14 15:18:42   Duration: 00:00:31.33, start: 0.000000, bitrate: 678 kb/s
2024-11-14 15:18:42   Stream #0:0[0x1](und): Video: h264 (High) (avc1 / 0x31637661), yuv420p(progressive), 1024x1024, 677 kb/s, 15 fps, 15 tbr, 15360 tbn (default)
2024-11-14 15:18:42     Metadata:
2024-11-14 15:18:42       handler_name    : VideoHandler
2024-11-14 15:18:42       vendor_id       : [0][0][0][0]
2024-11-14 15:18:42 [AVFormatContext @ 0x7f9254dcb4c0] Unable to choose an output format for '678000'; use a standard extension for the filename or specify the format manually.
2024-11-14 15:18:42 [out#0 @ 0x7f9254d70700] Error initializing the muxer for 678000: Invalid argument
2024-11-14 15:18:42 Error opening output file 678000.
2024-11-14 15:18:42 Error opening output files: Invalid argument
2024-11-14 15:18:42 [ERROR]: Failed to generate .ts file for: 1731550687270.mp4


    


  • Webcam - Publishing and Archiving on line video files

    11 novembre 2014, par Emmanuel Brunet

    I want to publish an ASF live video stream over the internet and also copy the backup to disk (without sound to spare disk space)

    I’m running debian 7.7 wheezy / ffmpeg 2.2 and ffserver 1.2.9.


    The IP camera video streams specifications are

    Input #0, asf, from 'http://account:password@webcam/videostream.asf':
     Duration: N/A, start: 0.000000, bitrate: 32 kb/s
       Stream #0:0: Video: mjpeg (MJPG / 0x47504A4D), yuvj422p(pc), 640x480, 50 tbr, 1k tbn, 1k tbc
       Stream #0:1: Audio: adpcm_ima_wav ([17][0][0][0] / 0x0011), 8000 Hz, 1 channels, s16p, 32 kb/s

    To achieve this I have set up a /etc/ffserver.conf configuration

    Port 11000

    BindAddress 0.0.0.0

    MaxClients 1000

    MaxBandwidth 40000

    CustomLog -

    <feed>
    File /tmp/feed1.ffm
    FileMaxSize 200K
    ACL allow localhost
    ACL allow 192.168.1.1 192.168.255.255

    </feed>


    # --------------------------- ASF ----------------------

    <stream>
    Feed feed1.ffm
    Format asf

    AVOptionVideo flags +global_header
    VideoFrameRate 25
    VideoSize 640x480
    VideoBitRate 1024
    VideoBufferSize 1024
    StartSendOnKey
    NoAudio
    </stream>

    # ------------ Server status -------------------

    <stream>
    Format status

    # Only allow local people to get the status
    ACL allow localhost
    ACL allow 192.168.0.0 192.168.255.255

    #FaviconURL http://pond1.gladstonefamily.net:8080/favicon.ico
    </stream>


    # ---------- Redirect --------------------

    <redirect>
    URL http://www.ffmpeg.org/
    </redirect>

    To connect the feed I run

    to start the ffserver

    ffserver -f /etc/ffserver.conf

    to collect the stream from the camera

    ffmpeg -i http://account:password@webcam/videostream.asf -c:v libx264 -an http://localhost:11000/feed1.ffm

    and all works like a charm.


    My questions are :

    • How in the same time having the stream saved to disk ?

    (as done by the command)

    ffmpeg -i http://account:password@webcam/videostream.asf -preset veryfast -t 00:60:00 -b:v 512K -c:v libx264 -pix_fmt yuv420p -an /var/backup/videos/YYY-MM-DD.mp4

    Note that the output .mp4 file names should rotate to get multiple timestamped output archives

    • How can I published video over RTSP ?

    I’ve found examples on the internet but none worked for me

    Thanks in advance

    regards

  • avdevice/xcbgrab : don't assume xserver endianness

    31 janvier 2021, par Andriy Gelman
    avdevice/xcbgrab : don't assume xserver endianness
    

    xserver defines the endianness of the grabbed images. Use this information
    to set the correct pixel format.

    This also fixes format selection in configuration depth=32/bpp=32 with
    xserver on a little endian machine. Before the patch, the big endian
    layout 0RGB was always selected which is incorrect because BGR0 should
    be used. RGB24 was also incorrectly assumed (but this format was removed
    in xserver 1.20).

    The big-endian settings can be tested using docker+qemu from a little-endian
    machine :

    $ docker run —rm —privileged multiarch/qemu-user-static —reset -p yes
    $ docker run —rm -it -v /tmp :/tmp powerpc64/debian /bin/bash

    In docker container
    $ apt-get update
    $ apt-get install xvfb
    $ apt-get install x11-apps

    To test AV_PIX_FMT_0RGB32
    $ Xvfb :2 -screen 0 720x480x24 &
    $ export DISPLAY=:2
    $ xclock -geometry 720x480 -bg green #test different colors

    On your host machine grab the frames using the following
    command. View output to check that colors are rendered correctly
    $ ./ffmpeg -y -f x11grab -i :2.0 -codec:v mpeg2video out.mp4

    Other pixel formats can be tested by modifying how Xvfb is started in the docker
    container :

    AV_PIX_FMT_RGB565
    $ Xvfb :2 -screen 0 720x480x16

    AV_PIX_FMT_RGB555
    $ Xvfb :2 -screen 0 720x480x15

    AV_PIX_FMT_BGR24 / AV_PIX_FMT_RGB24
    This is difficult to test because bpp=24 support was removed in xserver 1.20
    https://lists.x.org/archives/xorg-devel/2018-February/056175.html?hmsr=joyk.com&utm_source=joyk.com&utm_medium=referral
    However, I was able to run previous version of Xvfb (with some
    modifications to force 24bpp) to check that images are rendered correctly.

    Reviewed-by : Carl Eugen Hoyos <ceffmpeg@gmail.com>
    Signed-off-by : Andriy Gelman <andriy.gelman@gmail.com>

    • [DH] libavdevice/xcbgrab.c