Recherche avancée

Médias (0)

Mot : - Tags -/alertes

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

Autres articles (49)

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

  • avcodec/mediacodecdec : add workaround for buggy amlogic mpeg2 decoder

    26 avril 2018, par Aman Gupta
    avcodec/mediacodecdec : add workaround for buggy amlogic mpeg2 decoder

    I tested the previous mediacodec changes on seven different Android
    
TV devices, with both mpeg2 and h264 content. All except one worked
    
as expected. The exception was the MiBox3 running Android 6.0.1,
    
where playback would freeze on a frame every few seconds. I tested
    
two other AMLogic devices with newer Android versions that did not
    
show the same problem. H264 decoding on the MiBox3 was also not affected,
    
so this workaround applies only to OMX.amlogic.mpeg2.decoder.awesome
    
on Android API22.
    

    There is a rumor that Xiaomi is planning to release Android Oreo for
    
the MiBox3, so I will revisit in a few months to confirm whether this
    
is specific to os/driver version or the chipset used in that device.
    

    Signed-off-by : Aman Gupta <aman@tmm1.net>
    
Signed-off-by : Matthieu Bouron <matthieu.bouron@gmail.com>
    • [DH] libavcodec/mediacodecdec.c

  • Video recorded using Kurento is corrupted

    10 avril 2023, par Pranjal Lamba

    We are using Kurento media server v6.6.1 to record a video conference. The web app client which runs on Chrome(Windows, OSX, Android) is using a modified version of one-to-one-call-advanced Kurento sample and the second client is an Android native application which is using Nubomedia webrtcpeer v1.1.1. Nubomedia webrtcpeer uses LibJingle built by io.pristine v11139(released on December 2015). The video and audio is recorded in two separate recorder endpoints by Kurento.

    &#xA;

    Video conference recordings generated using web app client/s are working properly. But sometimes the video generated using native application contains all the frames within initial few seconds. Please find below download link for the problematic video generated by our Android native application,

    &#xA;

    https://drive.google.com/file/d/1vOVk8hPuP_iOlQfsmMoqZLhICy-Jpcee/view?usp=sharing

    &#xA;

    We are testing this feature on a range of Android devices, Nexus 5(Android 6.0.1), Nexus 6(Android 7.1.1), Sony Xperia Z Tablet(Android 6.0.1), Samsung Galaxy Tab A(Android 5.0), OnePlus 3(Android 7.1.1), Xiaomi A1(Android 7.1.1). The issue randomly starts occurring on a bunch of these devices while the others work properly and vice-versa.

    &#xA;

    We are recording the videos with the following constraints,

    &#xA;

    Web app client

    &#xA;

    Minimum video width : 32
    &#xA;Minimum video height : 32
    &#xA;Maximum video width : 320
    &#xA;Maximum video height : 320
    &#xA;Minimum framerate : 1
    &#xA;Maximum framerate : 15
    &#xA;Video container format : MP4
    &#xA;Video codec : H.264
    &#xA;Audio codec : AAC

    &#xA;

    Android native client

    &#xA;

    Minimum video width : 32
    &#xA;Minimum video height : 32
    &#xA;Maximum video width : 480
    &#xA;Maximum video height : 640
    &#xA;Minimum framerate : 1
    &#xA;Maximum framerate : 25
    &#xA;Video container format : MP4
    &#xA;Video codec : H.264
    &#xA;Audio codec : Opus

    &#xA;

  • use ffmpeg libs to control native video recording fps

    9 février 2015, par suitianshi

    I am recording video natively with help from Camera.setPreviewCallback and ffmpeg libs. I want to get a fixed fps(through AVCodecContext.time_base) mp4 video, say , the fps is 20 which means it will have 20 frames in one second.

    The problem is that on some device (my zte-u817) I only get about 10 frames within a second whereas on another device(XiaoMi-4) I could get 30 frames.

    As said above, it seems I have to find some way to add/drop frames based on current fps of camera preview callback.Dropping frames should be easy to implement. How about creating frames ? Appreciate if any example is provided

Navigation