Recherche avancée

Médias (0)

Mot : - Tags -/signalement

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

Autres articles (38)

  • Contribute to documentation

    13 avril 2011

    Documentation is vital to the development of improved technical capabilities.
    MediaSPIP welcomes documentation by users as well as developers - including : critique of existing features and functions articles contributed by developers, administrators, content producers and editors screenshots to illustrate the above translations of existing documentation into other languages
    To contribute, register to the project users’ mailing (...)

  • Selection of projects using MediaSPIP

    2 mai 2011, par

    The examples below are representative elements of MediaSPIP specific uses for specific projects.
    MediaSPIP farm @ Infini
    The non profit organizationInfini develops hospitality activities, internet access point, training, realizing innovative projects in the field of information and communication technologies and Communication, and hosting of websites. It plays a unique and prominent role in the Brest (France) area, at the national level, among the half-dozen such association. Its members (...)

  • Use, discuss, criticize

    13 avril 2011, par

    Talk to people directly involved in MediaSPIP’s development, or to people around you who could use MediaSPIP to share, enhance or develop their creative projects.
    The bigger the community, the more MediaSPIP’s potential will be explored and the faster the software will evolve.
    A discussion list is available for all exchanges between users.

Sur d’autres sites (7955)

  • libavutil/mem : use size_t for the length in av_strdup()

    10 mai 2015, par Michael Niedermayer
    libavutil/mem : use size_t for the length in av_strdup()

    the string length is not constrained to INT_MAX
    

    Signed-off-by : Michael Niedermayer <michaelni@gmx.at>
    • [DH] libavutil/mem.c

  • ffmpeg : video from images - handling a zero length image file

    29 septembre 2021, par Buadhai

    I have a shell script which uses ffmpeg to crate a time-lapse video from webcam images. Normally, it works just fine :

    &#xA;

    /usr/bin/ffmpeg -loglevel info  -framerate 4 \&#xA;     -pattern_type glob -i $ipath/&#x27;*.jpg&#x27; \&#xA;    -c:v libx264 -crf 30 -y -pix_fmt yuv420p $temp &amp;>>$log&#xA;

    &#xA;

    But this chokes if the image is a zero-length file :

    &#xA;

    -rw-r--r-- 1 pi pi  156636 Sep 29 04:35 image_022.jpg&#xA;-rw-r--r-- 1 pi pi  156533 Sep 29 04:35 image_023.jpg&#xA;-rw-r--r-- 1 pi pi  159302 Sep 29 04:35 image_024.jpg&#xA;-rw-r--r-- 1 pi pi       0 Sep 29 04:35 image_025.jpg&#xA;-rw-r--r-- 1 pi pi  157055 Sep 29 04:35 image_026.jpg&#xA;-rw-r--r-- 1 pi pi  156851 Sep 29 04:35 image_027.jpg&#xA;-rw-r--r-- 1 pi pi  155793 Sep 29 04:35 image_028.jpg&#xA;-rw-r--r-- 1 pi pi  160647 Sep 29 04:35 image_029.jpg&#xA;

    &#xA;

    In this case the video only included frames up to the zero length JPEG.

    &#xA;

    I realize I can test the file length of every webcam image, but there must be an easier, more efficient way.

    &#xA;

    Is there ?

    &#xA;

  • swscale : Take the destination range into account for yuv->rgb->yuv conversions

    18 février 2022, par Martin Storsjö
    swscale : Take the destination range into account for yuv->rgb->yuv conversions

    The range parameters need to be set up before calling
    
sws_init_context (which selects which fastpaths can be used ;
    
this gets called by sws_getContext) ; solely passing them via
    
sws_setColorspaceDetails isn't enough.
    

    This fixes producing full range YUV range output when doing
    
YUV->YUV conversions between different YUV color spaces.
    

    Signed-off-by : Martin Storsjö <martin@martin.st>
    • [DH] libswscale/utils.c
    • [DH] tests/fate/libswscale.mak
    • [DH] tests/ref/fate/sws-yuv-colorspace
    • [DH] tests/ref/fate/sws-yuv-range

Navigation