Recherche avancée

Médias (5)

Mot : - Tags -/open film making

Autres articles (97)

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

  • ANNEXE : Les plugins utilisés spécifiquement pour la ferme

    5 mars 2010, par

    Le site central/maître de la ferme a besoin d’utiliser plusieurs plugins supplémentaires vis à vis des canaux pour son bon fonctionnement. le plugin Gestion de la mutualisation ; le plugin inscription3 pour gérer les inscriptions et les demandes de création d’instance de mutualisation dès l’inscription des utilisateurs ; le plugin verifier qui fournit une API de vérification des champs (utilisé par inscription3) ; le plugin champs extras v2 nécessité par inscription3 (...)

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

  • Enormous, constant memory consumption using VP9 codec in FFMPEG C++

    17 décembre 2017, par Sebastian Schon

    Using :
    https://github.com/ash3D/VideoRecorder
    Wrapped with :
    https://github.com/ash3D/UEVideoRecorder

    I added the VP9 codec to the "FindEncoder" function of the CVideoRecorder (part of the VideoRecorder repository). Using VP9 codec works generally, however the memory consumption is enormous and within a good 30 seconds, the memory usage goes up from 3GB to 6GB, upon which (round about) FFMPEG throws out of memory errors and aborts the encoding process. I started up the Diagnostics Tool of Visual Studio and it told me that avcodec.dll is holding all the memory, which is not released until the encoding is terminated (peacefully). The function within which the allocating call is executed is the CVideoRecorder::Encode() function, which inside it calls avcodec_send_frame().

    H264 and HVENC work fine with a constant memory consumption of around 300MB.

    I tried setting various settings on the VP9 codec like the bitrate, cfr and quality, none of which changed the behavior in any to me recognizable way.

  • FFmpeg : Get better encoding out of my function

    31 octobre 2019, par A Person

    I needed some assistance on my task.

    I am using FFmpeg to burn time and the channel name onto the video.

    My goal is to record a stream that is html5 compatible with the following settings :

    Video wrapper MP4

    Video codec H.264

    Bitrate 1Mbps

    Audio codec AAC

    Audio bitrate 128Kbps

    And GPU encoding.

    This is what I am using :

    ffmpeg -hwaccel cuvid -y -i {udp} -vf "drawtext=fontfile=calibrib.tff:fontsize=25:text='{ChannelName} %{localtime}': x=10: y=10: fontcolor=white: box=1: boxcolor=0x000000" -pix_fmt yuv420p -vsync 1 -c:v h264_nvenc -r 25 -threads 0  -b:v 1M -profile:v main -minrate 1M -maxrate 1M -bufsize 10M -sc_threshold 0 -c:a aac -b:a 128k -ac 2 -ar 44100 -af "aresample=async=1:min_hard_comp=0.100000:first_pts=0" -bsf:v h264_mp4toannexb -t 00:30:00 {output}\{ChannelName}\{ChannelName}_{year}_{monthno}_{day}__{Hours}_{Minutes}_{Seconds}.mp4

    {ChannelName}_{year}_{monthno}_{day}__{Hours}_{Minutes}_{Seconds} are all variable holding information.

    {udp} holds the UDP stream link.

    I have done it this way as I have multiple UDP stream recording.

    Although this works, is there a better way for me to do this keeping in the -vf as I need the time and channel name.

    Currently, this uses between 0.8% to 1.9% GPU on my Quadro P4000. I don’t want to use more than this as I have more than 30 streams.

  • avformat/matroskaenc : Don't use size of inexistent Cluster

    22 janvier 2020, par Andreas Rheinhardt
    avformat/matroskaenc : Don't use size of inexistent Cluster
    

    In order to determine whether the current Cluster needs to be closed
    because of the limits on clustersize and clustertime,
    mkv_write_packet() would first get the size of the current Cluster by
    applying avio_tell() on the dynamic buffer holding the current Cluster.
    It did this without checking whether there is a dynamic buffer for
    writing Clusters open right now.

    In this case (which happens when writing the first packet)
    avio_tell() returned AVERROR(EINVAL) ; yet it is not good to rely on
    avio_tell() (or actually, avio_seek()) to handle the situation
    gracefully.

    Fixing this is easy : Only check whether a Cluster needs to be closed
    if a Cluster is in fact open.

    Signed-off-by : Andreas Rheinhardt <andreas.rheinhardt@gmail.com>

    • [DH] libavformat/matroskaenc.c