Recherche avancée

Médias (1)

Mot : - Tags -/belgique

Autres articles (48)

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

  • Submit enhancements and plugins

    13 avril 2011

    If you have developed a new extension to add one or more useful features to MediaSPIP, let us know and its integration into the core MedisSPIP functionality will be considered.
    You can use the development discussion list to request for help with creating a plugin. As MediaSPIP is based on SPIP - or you can use the SPIP discussion list SPIP-Zone.

  • Les autorisations surchargées par les plugins

    27 avril 2010, par

    Mediaspip core
    autoriser_auteur_modifier() afin que les visiteurs soient capables de modifier leurs informations sur la page d’auteurs

Sur d’autres sites (6264)

  • How do I calculate optimal dimensions and bitrate for displaying a video on an iPhone ?

    6 février 2020, par wachutu

    I’m currently developing a mobile app that will have a library of 2-5 minute videos (approx 100 in total) and going through the process of determining which versions of the videos to have ready to serve to different mobile devices. In my research, I have noticed that there is a lot of room to play with video settings such as dimensions and bitrate.

    As a first test, I am attempting to find the minimum video size I can deliver to an iPhone XS with dimensions 1125x2436 without losing any noticeable quality. I started by scaling the video to 1125x2436 and creating versions with 5 different bitrates ranging from 500kbps-4400kbps. I noticed that at 1500kbps, the video looks great and the size is cut 1/3 so that was a good start.

    Then after doing some reading, I saw that in adaptive bitrate scenarios Apple recommends delivering video of lower bitrate AND lower resolution. So in my next test I just cut both in half - scaled to 562x1218 and bitrate at 750kbps and noticed the video also looked great on the iPhone. So 1125x2436 at 750kbps looks bad, but 562x1218 at 750kbps looks great on the same device. To some extent this makes sense to me as you need less bits to fill a smaller screen but what I’m not understanding is how the scaling plays a factor. Shouldn’t it essentially pixelate because the resolution is 1/2 of the iPhone dimensions ? And at a higher level, is there a somewhat concrete way to figure out this optimal resolution / bitrate balance given the dimensions of a device ? We want to most modern smartphones (iPhone 6 and later, Samsung Galaxy, etc.) so we need to be prepared for a range of dimensions (aspect ratios 9:16 or 6:13).

  • ffserver : Clear avio context after closing it

    1er novembre 2015, par Michael Niedermayer
    ffserver : Clear avio context after closing it
    

    Fixes : ==13287== Invalid read of size 4
    ==13287== at 0x45161A : flush_buffer (aviobuf.c:143)
    ==13287== by 0x451971 : avio_flush (aviobuf.c:200)
    ==13287== by 0x512CCF : av_write_trailer (mux.c:1016)
    ==13287== by 0x41A5E0 : close_connection (ffserver.c:853)
    ==13287== by 0x421EDC : rtsp_cmd_interrupt (ffserver.c:3245)
    ==13287== by 0x420B9C : rtsp_parse_request (ffserver.c:2854)
    ==13287== by 0x41A9C2 : handle_connection (ffserver.c:930)
    ==13287== by 0x41A04B : http_server (ffserver.c:700)
    ==13287== by 0x423A60 : main (ffserver.c:3897)
    ==13287== Address 0xb6cd258 is 88 bytes inside a block of size 192 free’d
    ==13287== at 0x4C2B5D9 : free (vg_replace_malloc.c:446)
    ==13287== by 0x1004DAC : av_free (mem.c:239)
    ==13287== by 0x454835 : avio_close_dyn_buf (aviobuf.c:1170)
    ==13287== by 0x41F385 : http_prepare_data (ffserver.c:2368)
    ==13287== by 0x41F59B : http_send_data (ffserver.c:2416)
    ==13287== by 0x41ABE2 : handle_connection (ffserver.c:986)
    ==13287== by 0x41A04B : http_server (ffserver.c:700)
    ==13287== by 0x423A60 : main (ffserver.c:3897)

    Reviewed-by : "Reynaldo H. Verdejo Pinochet" <reynaldo@osg.samsung.com>
    Signed-off-by : Michael Niedermayer <michael@niedermayer.cc>

    • [DH] ffserver.c
  • How to Play Smooth 4K Video with FFplay ? [closed]

    14 mai 2020, par Matan Marciano

    Im trying to play 4K video with ffplay and the video is not smooth.

    &#xA;&#xA;

    Video File :

    &#xA;&#xA;

    &#xA;&#xA;

    Hardware :

    &#xA;&#xA;

      &#xA;
    • Dell OptiPlex 7070 Micro (8 Cores, 8GB RAM, GPU : Intel Corporation UHD Graphics 630)
    • &#xA;

    • Samsung U28E590D, 4K Screen
    • &#xA;

    • DisplayPort to HDMI Cable
    • &#xA;

    &#xA;&#xA;

    Software :

    &#xA;&#xA;

    &#xA;&#xA;

    The FFplay command I used is : ffplay -vcodec h264_qsv -i input.ts

    &#xA;&#xA;

      &#xA;
    • Notes :
    • &#xA;

    • During the playing, my CPU usage is around 25% (according to 'top' command)
    • &#xA;

    • FFplay logs indicate on many frame drops
    • &#xA;

    • I also tried VLC and MPV player's- VLC looks bad also. MPV player looks better but still not smooth.
    • &#xA;

    &#xA;&#xA;

    So, its looks like my hardware is good enough for 4K playing. What am I missing ?&#xA;How can I play smooth 4K video via FFplay ?

    &#xA;