Recherche avancée

Médias (91)

Autres articles (55)

  • Other interesting software

    13 avril 2011, par

    We don’t claim to be the only ones doing what we do ... and especially not to assert claims to be the best either ... What we do, we just try to do it well and getting better ...
    The following list represents softwares that tend to be more or less as MediaSPIP or that MediaSPIP tries more or less to do the same, whatever ...
    We don’t know them, we didn’t try them, but you can take a peek.
    Videopress
    Website : http://videopress.com/
    License : GNU/GPL v2
    Source code : (...)

  • Personnaliser en ajoutant son logo, sa bannière ou son image de fond

    5 septembre 2013, par

    Certains thèmes prennent en compte trois éléments de personnalisation : l’ajout d’un logo ; l’ajout d’une bannière l’ajout d’une image de fond ;

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

  • Anomalie #3051 : Perte de config des documents lors de màj 2.1.23 vers 3.0.11

    23 septembre 2013, par b b

    Hop, ok je vois qu’on activait pas les docs sur les articles en 2.1, mais je pense tout de même que cela devrait être actif par défaut en 3.0. Donc oui pour un autre ticket à ce sujet :)

  • Converting AAC stream to DASH MP4 with high fragment length precision

    5 mars 2017, par vdudouyt

    For my HTML5 project I need to create a fragmented MP4 file with a single audio stream (no video), each fragment of which has a duration of exactly 0.1 second.

    Accordingly to ffmpeg docs, you can accomplish that by passing a value in microseconds with ’-frag_duration’ - which I found to be working and playable with HTML5 MediaSource API :

    $ ffmpeg -y -i input.aac -c:a libfdk_aac -b:a 64k -level:v 13 -r 25 -strict experimental -movflags empty_moov+default_base_moof -frag_duration 100000 output.mp4

    As we have a 210 second audio split up by 0.1s fragments, I expect that in output.mp4 we’d have 2100 fragments, hence 2100 moof atoms. But, upon inspecting it I’ve figured out that we only have 1811 moof atoms - which means that some (or maybe even all) fragments are bigger than expected :

    $ python ~/git/mp4viewer/src/showboxes.py output.mp4 |grep moof|wc -l
    
1811

    Could anybody tell me what’s wrong, and how could I accomplish what I want ?

    Right now my assumption is that during an encoding I have AAC frame length which is not a multiple of 0.1s, hence ffmpeg has no chance to produce the fragments that are strictly equal to 0.1s but I’m not sure. If somebody can confirm that - and let me know a way to explicitly set AAC frame_size in FFMPEG (I couldn’t find anything like that in the docs), or completely disprove this - it would be also highly appreciated.

  • FFmpeg.AutoGen decoding an image using av_image_copy_to_buffer

    28 juin 2022, par Steve

    I try to use FFmpeg.AutoGen.av_image_copy_to_buffer to get decoded data into my application defined frame_buffer like so :

    


    bytes_decoded = ffmpeg.av_image_copy_to_buffer(frame_data, buffer_size, frame->data, frame->linesize, 
                                               codCtx->pix_fmt, codCtx->width, codCtx->height, 1);


    


    However the type of the parameter frame->data is of type FFmpeg.AutoGen.byte_ptrArray8, but the interface expects FFmpeg.AutoGen.byte_ptrArray4.
Does anyone know how to convert this parameter, so that I can pass it to the interface ? VS complains with the following error message :
https://docs.microsoft.com/en-us/dotnet/csharp/misc/cs1503?f1url=%3FappId%3Droslyn%26k%3Dk(CS1503)

    


    Thanks in advance for any help on this issue.

    


Navigation