Recherche avancée

Médias (91)

Autres articles (23)

  • Installation en mode ferme

    4 février 2011, par

    Le mode ferme permet d’héberger plusieurs sites de type MediaSPIP en n’installant qu’une seule fois son noyau fonctionnel.
    C’est la méthode que nous utilisons sur cette même plateforme.
    L’utilisation en mode ferme nécessite de connaïtre un peu le mécanisme de SPIP contrairement à la version standalone qui ne nécessite pas réellement de connaissances spécifique puisque l’espace privé habituel de SPIP n’est plus utilisé.
    Dans un premier temps, vous devez avoir installé les mêmes fichiers que l’installation (...)

  • Ajouter des informations spécifiques aux utilisateurs et autres modifications de comportement liées aux auteurs

    12 avril 2011, par

    La manière la plus simple d’ajouter des informations aux auteurs est d’installer le plugin Inscription3. Il permet également de modifier certains comportements liés aux utilisateurs (référez-vous à sa documentation pour plus d’informations).
    Il est également possible d’ajouter des champs aux auteurs en installant les plugins champs extras 2 et Interface pour champs extras.

  • 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 (5257)

  • Looking for a free alternative RTSP server for Node.js [closed]

    2 juin 2020, par Maoration

    I'm looking at running my node.js server as an RTSP streaming server, as well as an http server. the ability to get some ffmpeg video output to stream as rtsp to 'localhost' (which will be the server listening), and for multiple clients to request a stream from the server via the rtsp ://... protocol

    



    The most common online implementation is :
https://www.npmjs.com/package/rtsp-streaming-server

    



    However, this is licensed under GPL-3.0, meaning my product would have to be open-source, or I'll be violating the terms of use. I'm afraid thats not possible..

    



    Other common results when searching for a solution are :

    



    https://www.npmjs.com/package/rtsp-server
which just seems to wrap to lower level rtsp protocol messages.

    



    https://www.npmjs.com/package/node-media-server
which provides solutions to many use cases, but I couldnt figure out how to configure it as an RTSP server, or if this would even be possible.

    



    So, any alternatives ? other suggestions ?

    


  • Mixing audio stream into video stream using ffmpeg while retaining original audio from the video stream as background [duplicate]

    18 mars 2020, par Core7s

    I have a live video stream and a live audio stream. The audio stream has to get mixed into the video stream and the resulting stream is pushed to YouTube. I have this working ffmpeg -i videostream -i audiostream -map 0:1 -map 1:0 -shortest -c:a copy -c:v copy -f flv streamout-youtube;
    However I am losing the original audio in the videostream. I want to have the original audio playing at maybe 20% of the original volume.
    I looked around a lot and found maybe I can modify the above command to use -filter_complex to get ffmpeg -i videostream -i audiostream -filter_complex "volume=0.2" -map 0:1 -map 1:0 -shortest -c:a copy -c:v copy -f flv streamout-youtube;

    However, when I add the -filter_complex option, the stream goes dead meaning it doesn’t get pushed to youtube anymore. I have verified the stream keys are correct. This seems to be a rather simple thing but I can’t put my finger on what’s wrong.

    I am using rtmp module of nginx to receive, mix and push out streams.

  • dnxhddec : Decode and use interlace mb flag

    26 septembre 2015, par Christophe Gisquet
    dnxhddec : Decode and use interlace mb flag
    

    This bit is 1 in some samples, and seems to coincide with interlaced
    mbs and CID1260. 2008 specs do not know about it, and maintain qscale
    is 11 bits. This looks oversized, but may help larger bitdepths.

    Currently, it leads to an obviously incorrect qscale value, meaning
    its syntax is shifted by 1. However, reading 11 bits also leads to
    obviously incorrect decoding : qscale seems to be 10 bits.

    However, as most profiles still have 11bits qscale, the feature is
    restricted to the CID1260 profile (this flag is dependent on
    a higher-level flag located in the header).

    The encoder writes 12 bits of syntax, last and first bits always 0,
    which is now somewhat inconsistent with the decoder, but ends up with
    the same effect (progressive + reserved bit).

    Signed-off-by : Vittorio Giovara <vittorio.giovara@gmail.com>

    • [DH] libavcodec/dnxhddec.c