Recherche avancée

Médias (1)

Mot : - Tags -/musée

Autres articles (104)

  • Keeping control of your media in your hands

    13 avril 2011, par

    The vocabulary used on this site and around MediaSPIP in general, aims to avoid reference to Web 2.0 and the companies that profit from media-sharing.
    While using MediaSPIP, you are invited to avoid using words like "Brand", "Cloud" and "Market".
    MediaSPIP is designed to facilitate the sharing of creative media online, while allowing authors to retain complete control of their work.
    MediaSPIP aims to be accessible to as many people as possible and development is based on expanding the (...)

  • 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

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

  • Is Replacing Dynamic Resolution with scale_amf in FFmpeg Command a Good Direction ?

    21 novembre 2024, par fred

    I'm working on a Lua script for MPV that processes 360-degree videos using FFmpeg's v360 filter. The original command dynamically calculates the output resolution based on a res variable, like this :

    


    mp.command_native_async({
    "no-osd", "vf", "add", 
    string.format(
        "@vrrev:v360=%s:%s:reset_rot=1:in_stereo=%s:out_stereo=2d:
id_fov=%s:d_fov=%.3f:yaw=%.3f:pitch=%s:roll=%.3f:
w=%s*192.0:h=%.3f*108.0:h_flip=%s:interp=%s",
        in_flip, inputProjection, outputProjection, in_stereo, idfov, dfov, yaw, pitch, roll, res, res, h_flip, scaling
    )
}, updateComplete)


    


    Change Proposal :

    


    I am considering replacing the dynamic width and height calculations with a scale_amf filter to handle scaling more efficiently and leverage GPU acceleration. The updated command would look like this :

    


    mp.command_native_async({
    "no-osd", "vf", "add", 
    string.format(
        "@vrrev:v360=%s:%s:reset_rot=1:in_stereo=%s:out_stereo=2d:
id_fov=%s:d_fov=%.3f:yaw=%.3f:pitch=%s:roll=%.3f,
%sscale_amf=w=%.0f:h=%.0f",
        inputProjection, outputProjection, in_stereo, idfov, dfov, yaw, pitch, roll, in_flip, res * 192.0, res * 108.0
    )


    


    Hardware Specifications :

    


    I am using an AMD Ryzen 5 5600G, no display card, 16GB RAM, Windows 10.

    


    Questions :

    


    Is using scale_amf for scaling a good direction in terms of performance and efficiency ?
Are there any potential drawbacks to this approach that I should be aware of ?
How does using scale_amf compare to the original dynamic resolution method in terms of output quality and processing speed ?
}, updateComplete)

    


    Any insights or experiences with this change would be greatly appreciated !

    


  • wmavoice : protect against zero-energy in adaptive gain control.

    21 décembre 2016, par Ronald S. Bultje
    wmavoice : protect against zero-energy in adaptive gain control.

    Otherwise the scale factor becomes NaN, resulting in corrupt output.
    
Fixes #5426.
    • [DH] libavcodec/wmavoice.c

  • Revision 1ec44505c9 : Bug fix for svc first pass rate control. 1. We didn't scale source image in low

    18 avril 2014, par Minghai Shang

    Changed Paths :
     Modify /vp9/encoder/vp9_firstpass.c


     Modify /vp9/encoder/vp9_onyx_if.c


     Modify /vp9/encoder/vp9_onyx_int.h



    Bug fix for svc first pass rate control.

    1. We didn’t scale source image in lower layers so that
    the stats are incorrect.
    2. We didn’t extend borders for re-constructed image.

    Change-Id : Ia8d7bafbdb695ffa7f504e171f9449812e7bb0a3

Navigation