Recherche avancée

Médias (91)

Autres articles (67)

  • 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

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

  • FFMPEG with -vf yadif on progressive file produces incorrect 'Original Frame Rate' metadata double

    28 septembre 2020, par hedgehog90

    I've got an ffmpeg command that I often use, I incorporate the yadif argument for content that may or may not be interlaced :

    


    ffmpeg -i input.mkv -c copy -c:v hevc_nvenc -c:a:0 aac -b:a 192k -vf yadif=mode=1:deint=1 output.mkv

    


    This means if input.mkv is an interlaced video, I get double the frame rate and the footage is deinterlaced, and if it's progressive it remains so and the frame rate doesn't change, exactly as I want it.

    


    However, I've just noticed in Mediainfo that progressive videos processed by this command, it adds this mysterious "Original Frame Rate" tag (I assume it's just metadata)

    


    enter image description here

    


    It doesn't appear to affect playback in VLC or MPV, however it is recognized in MPV as 'framerate (Specified)'...

    


    How do I prevent ffmpeg from generating this tag when using the yadif filter ?

    


  • Cross origin issue in html 5 player

    2 septembre 2020, par Danish Abdul Hamid

    Hey Guys i am new this field i encoded video through ffmpeg and for packaging used bento 4 for output single file in ts below the command i used

    


    mp4hls —hls-version 4 —output-single-file —segment-duration 6 input_7000kb.mp4 input_5000kb.mp4 input_3500kb.mp4

    


    and this is output file http://stream.simpaisa.com/output/master.m3u8 when i open this url in html 5 player its showing error "not allowed by Access-Control-Allow-Headers in preflight response" but in android and vlc this url is working. server already have .htaccess file for cross origin allow .

    


    when i used this command mp4hls —hls-version 4 input_7000kb.mp4 input_5000kb.mp4 input_3500kb.mp4

    


    the output file is http://stream.simpaisa.com/new/output/master.m3u8 and this file is working in html 5 player no cross origin issue

    


    Please tell me whats the issue

    


    this is .htaccess file configuration

    


    Header set Access-Control-Allow-Origin "*"
Header set Access-Control-Allow-Credentials "true"
Header set Access-Control-Allow-Methods "GET,HEAD,OPTIONS,POST,PUT"
Header set Access-Control-Allow-Headers "Access-Control-Allow-Headers, Origin,Accept, X-Requested-With, Content-Type, Access-Control-Request-Method, Access-Control-Request-Headers"
RewriteEngine On

    


    RewriteCond %REQUEST_FILENAME !-f
RewriteRule ^(.*)$ index.php [QSA,L]

    


  • avfilter/af_amix : Fix double-free of AVFilterChannelLayouts on error

    7 août 2020, par Andreas Rheinhardt
    avfilter/af_amix : Fix double-free of AVFilterChannelLayouts on error
    

    The query_formats function of the amix filter tries to allocate a list
    of channel layouts which are attached to more permanent objects
    (an AVFilter's links) for storage afterwards on success. If attaching
    a list to a link succeeds, the link becomes one of the common owners
    of the list. Yet if a list has been successfully attached to links (or if
    there were no links to attach it to in which case
    ff_set_common_channel_layouts() already frees the list) and an error
    happens lateron, the list was manually freed, which is wrong, because
    the list has either already been freed or it is owned by its links in
    which case these links' pointers to their list will become dangling and
    there will be double-frees/uses-after-free when these links are cleaned
    up automatically.

    This commit fixes this by removing the custom freeing code ; this is made
    possible by using the list in ff_set_common_channel_layouts() directly
    after its allocation (without anything that can fail in between).

    Notice that ff_set_common_channel_layouts() is buggy itself which can
    lead to double-frees on error. This is not fixed in this commit.

    Reviewed-by : Nicolas George <george@nsup.org>
    Signed-off-by : Andreas Rheinhardt <andreas.rheinhardt@gmail.com>

    • [DH] libavfilter/af_amix.c