Recherche avancée

Médias (0)

Mot : - Tags -/xmp

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

Autres articles (84)

  • 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 ;

  • List of compatible distributions

    26 avril 2011, par

    The table below is the list of Linux distributions compatible with the automated installation script of MediaSPIP. Distribution nameVersion nameVersion number Debian Squeeze 6.x.x Debian Weezy 7.x.x Debian Jessie 8.x.x Ubuntu The Precise Pangolin 12.04 LTS Ubuntu The Trusty Tahr 14.04
    If you want to help us improve this list, you can provide us access to a machine whose distribution is not mentioned above or send the necessary fixes to add (...)

  • (Dés)Activation de fonctionnalités (plugins)

    18 février 2011, par

    Pour gérer l’ajout et la suppression de fonctionnalités supplémentaires (ou plugins), MediaSPIP utilise à partir de la version 0.2 SVP.
    SVP permet l’activation facile de plugins depuis l’espace de configuration de MediaSPIP.
    Pour y accéder, il suffit de se rendre dans l’espace de configuration puis de se rendre sur la page "Gestion des plugins".
    MediaSPIP est fourni par défaut avec l’ensemble des plugins dits "compatibles", ils ont été testés et intégrés afin de fonctionner parfaitement avec chaque (...)

Sur d’autres sites (12421)

  • lavfi/delogo : take SAR into account

    1er juillet 2013, par Jean Delvare
    lavfi/delogo : take SAR into account
    

    When interpolating, weights are based on relative distances, which
    assume square pixels. If a non-1:1 sample aspect ratio is used, it
    should be taken into account when comparing distances, because the
    human eye and brain care about the picture as it is displayed, not
    stored.

    Signed-off-by : Jean Delvare <khali@linux-fr.org>
    Signed-off-by : Michael Niedermayer <michaelni@gmx.at>

    • [DH] libavfilter/vf_delogo.c
  • ffmpeg transcode to hls and multiple aac audio tracks

    23 août 2023, par Aquarius

    I'm trying to transcode h264 mp4 file to HLS format with multiple AAC audio tracks. On Windows browsers everythins works like a shine. There's an option to switch audio track

    &#xA;

    audio track switcher

    &#xA;

    It doesn't work on Android devices or TV. On Android Opera browser video works with sound, but screen stuck while seeking and there's no option to switch audio track. On TV browser video works, it doesn't stuck when seeking but also no option to switch audio track

    &#xA;

    Using video.js player on site. Below code for transcode and produced manifest file

    &#xA;

    ffmpeg -i "file.mp4" -i PL-6ch.aac -i EN-6ch.aac -map 0:v -map 1:a -map 2:a -c:v copy -c:a:0 aac -ac:a:0 6 -af channelmap=channel_layout=5.1 -c:a:1 aac -ac:a:1 6 -af channelmap=channel_layout=5.1 -tag:v:0 h264 -b:v:0 2500k -tag:a:0 aac -b:a:0 384k -tag:a:1 aac -b:a:1 384k -f hls -hls_time 10 -hls_playlist_type vod -hls_list_size 0 -master_pl_name file.m3u8 -var_stream_map "v:0,agroup:AAC a:0,agroup:AAC,language:pl a:1,agroup:AAC,language:en" file_%v_.m3u8&#xA;

    &#xA;

    #EXTM3U&#xA;#EXT-X-VERSION:3&#xA;#EXT-X-INDEPENDENT-SEGMENTS&#xA;#EXT-X-MEDIA:TYPE=AUDIO,GROUP-ID="AAC",NAME="Polish",AUTOSELECT=YES,DEFAULT=YES,LANGUAGE="pl",URI="file_1_.m3u8"&#xA;#EXT-X-MEDIA:TYPE=AUDIO,GROUP-ID="AAC",NAME="English",AUTOSELECT=YES,DEFAULT=NO,LANGUAGE="en",URI="file_2_.m3u8"&#xA;#EXT-X-STREAM-INF:PROGRAM-ID=1,BANDWIDTH=3172400,RESOLUTION=1920x872,CODECS="avc1.640029,mp4a.40.2",AUDIO="AAC" &#xA;file_0_.m3u8&#xA;&#xA;#EXT-X-STREAM-INF:BANDWIDTH=422400,CODECS="mp4a.40.2",AUDIO="AAC"&#xA;file_1_.m3u8&#xA;&#xA;#EXT-X-STREAM-INF:BANDWIDTH=422400,CODECS="mp4a.40.2",AUDIO="AAC"&#xA;file_2_.m3u8&#xA;

    &#xA;

    Any clues what's wrong ?

    &#xA;

  • Pointers returned by xlib don't match any existing window IDs

    1er septembre 2022, par Kroltan

    I'm using some X11 bindings to query some window information and later pass it to FFmpeg. FFmpeg expects a "window ID" given in hexadecimal notation.

    &#xA;

    This notation seems somewhat standard, as it is returned by programs like xwininfo or wmctrl. I haven't found much information about it, but it seems to just be the hexadecimal representation of the window pointer ? If I take the ID string given by these programs and give it to FFmpeg, it is able to capture the window correctly :

    &#xA;

    $ xwininfo&#xA;&#xA;xwininfo: Please select the window about which you&#xA;          would like information by clicking the&#xA;          mouse in that window.&#xA;&#xA;xwininfo: Window id: 0x2800014 "Desktop — Plasma"&#xA;&#xA;$ ffmpeg -f x11grab -window_id 0x2800014 -i :0&#x2B;0,0 -f apng -vframes 1 out.png&#xA;# works fine&#xA;

    &#xA;

    However, if I try listing all the windows in code :

    &#xA;

    var root = Window.None;&#xA;var parent = Window.None;&#xA;Xlib.XQueryTree(_display, Xlib.XDefaultRootWindow(_display), ref root, ref parent, out var children);&#xA;&#xA;var ids = children&#xA;    .Select(ptr => $"0x{(ulong) ptr:x}")&#xA;    .ToArray();&#xA;

    &#xA;

    I don't see 0x2800014 in the results (even disregardingleading zeroes), and if I try running FFmpeg on one of those results, it fails terribly :

    &#xA;

    $ ffmpeg -f x11grab -window_id 0x4400003 -i :0&#x2B;0,0 -f apng -vframes 1&#xA;&#xA;# snipped for brevity&#xA;&#xA;Trailing option(s) found in the command: may be ignored.&#xA;[x11grab @ 0x55b811a8da40] Cannot get the image data event_error: response_type:0 error_code:8 sequence:10 resource_id:167772160 minor_code:4 major_code:130.&#xA;[x11grab @ 0x55b811a8da40] Continuing without shared memory.&#xA;[x11grab @ 0x55b811a8da40] Cannot get the image data event_error: response_type:0 error_code:8 sequence:11 resource_id:71303171 minor_code:0 major_code:73.&#xA;Input #0, x11grab, from &#x27;:0&#x2B;0,0&#x27;:&#xA;  Duration: N/A, bitrate: 38361 kb/s&#xA;  Stream #0:0: Video: rawvideo (BGR[0] / 0x524742), bgr0, 200x200, 38361 kb/s, 29.97 fps, 1000k tbr, 1000k tbn&#xA;At least one output file must be specified&#xA;

    &#xA;

    So I must conclude my guess that they are hex pointers is incorrect, or that the Window type is not the pointer itself, but then the question stands, how can I get the actual window IDs so I can pass them to FFmpeg ?

    &#xA;