Recherche avancée

Médias (91)

Autres articles (51)

  • Websites made ​​with MediaSPIP

    2 mai 2011, par

    This page lists some websites based on MediaSPIP.

  • Creating farms of unique websites

    13 avril 2011, par

    MediaSPIP platforms can be installed as a farm, with a single "core" hosted on a dedicated server and used by multiple websites.
    This allows (among other things) : implementation costs to be shared between several different projects / individuals rapid deployment of multiple unique sites creation of groups of like-minded sites, making it possible to browse media in a more controlled and selective environment than the major "open" (...)

  • Submit bugs and patches

    13 avril 2011

    Unfortunately a software is never perfect.
    If you think you have found a bug, report it using our ticket system. Please to help us to fix it by providing the following information : the browser you are using, including the exact version as precise an explanation as possible of the problem if possible, the steps taken resulting in the problem a link to the site / page in question
    If you think you have solved the bug, fill in a ticket and attach to it a corrective patch.
    You may also (...)

Sur d’autres sites (8969)

  • avfilter/vf_libplacebo : don't force dovi frames to bt.2020-ncl

    30 octobre 2023, par Niklas Haas
    avfilter/vf_libplacebo : don't force dovi frames to bt.2020-ncl

    This is at odds with the YUV matrix negotiation API, in which such
    
dynamic changes in YUV encoding are no longer easily possible. There is
    
also no really strong motivating reason to do this, since the choice of
    
YUV matrix is essentially arbitrary and not actually related to the
    
Dolby Vision decoding process.
    • [DH] libavfilter/vf_libplacebo.c

  • Anomalie #2020 : Rendre optionnelles les extensions

    8 mai 2012, par cedric -

    Work in progress, à finir dans la 3.1

  • How to limit cpu usage for a terminal command that works on m1 mac and macOS Monterey ?

    18 juin 2024, par mcaay

    I have a m1 macbook pro and I regularly need to do some heave processing with ffmpeg. When I do it, all my 8 cores go at it 100% and my cpu temperature goes to 92°C, which I don't feel comfortable about.

    


    I don't really need 100% speed, I'd much rather see 80°C and wait 5x longer for it to finish.

    


    I use Macs Fan Control which sets my fan at 100% at 75°C, so this helps definitely, but is not enough.

    


    I tried ffmpeg -threads 1 parameter but it doesn't make a difference in compressing speed nor temperature, so I assume it just doesn't work.

    


    I tried cpulimit -l 60 -i ffmpeg ... and it doesn't change a thing, so I assume it also doesn't work. cpulimit -l value gives 100% for every core, so cpulimit -l 800 should be 100%, -l 400 should be 50% and -l 60 should be 7.5%.

    


    I tried nice and it is not for my use case. Even with the lowest priority the task uses all available cpu, resulting in 92°C.

    


    Did anybody figure it out for m1 macs already ?

    


Navigation