Recherche avancée

Médias (2)

Mot : - Tags -/media

Autres articles (95)

  • MediaSPIP 0.1 Beta version

    25 avril 2011, par

    MediaSPIP 0.1 beta is the first version of MediaSPIP proclaimed as "usable".
    The zip file provided here only contains the sources of MediaSPIP in its standalone version.
    To get a working installation, you must manually install all-software dependencies on the server.
    If you want to use this archive for an installation in "farm mode", you will also need to proceed to other manual (...)

  • Multilang : améliorer l’interface pour les blocs multilingues

    18 février 2011, par

    Multilang est un plugin supplémentaire qui n’est pas activé par défaut lors de l’initialisation de MediaSPIP.
    Après son activation, une préconfiguration est mise en place automatiquement par MediaSPIP init permettant à la nouvelle fonctionnalité d’être automatiquement opérationnelle. Il n’est donc pas obligatoire de passer par une étape de configuration pour cela.

  • HTML5 audio and video support

    13 avril 2011, par

    MediaSPIP uses HTML5 video and audio tags to play multimedia files, taking advantage of the latest W3C innovations supported by modern browsers.
    The MediaSPIP player used has been created specifically for MediaSPIP and can be easily adapted to fit in with a specific theme.
    For older browsers the Flowplayer flash fallback is used.
    MediaSPIP allows for media playback on major mobile platforms with the above (...)

Sur d’autres sites (11146)

  • AAC bitstream not in ADTS format and extradata missing

    14 août 2014, par Boehmi

    With FFMPEG, I’m sending a stream from Computer A over to Computer B, via UDP.
    This is done over a MPEGTS stream, encoded with libx264 and aac.
    Computer B takes this stream with FFMPEG and puts it into an m3u8 playlist.

    After a random time (2-35 minutes), the message

    [mpegts @ 0533f000] AAC bitstream not in ADTS format and extradata missing
    av_interleaved_write_frame(): Invalid data found when processing input

    appears.
    What I figures is that the receiving FFMPEG can’t read the header file of the audio part for this particular package, and since it can’t put video and audio together anymore, it stops creating the .ts files and just stops running.

    Here’s the cmdline of the receiving stream :

    ffmpeg -i udp://address -vcodec copy -acodec copy -map 0 -f segment -segment_list playlist.m3u8 -analyzeduration 100000 -probesize 100000-segment_list_flags +lis-Þcache -segment_time 8 -segment_wrap 10 out%03d.ts

    Now I need to know the answer to either one of these 2 questions :

    1) Can I put something in my commandline in order to avoid this particular problem or

    2) Can I tell FFMPEG to just ignore it for this particular message, quite possibly creating weird audio or none at all, and to simply move on to the next one ?

  • FFmpeg 'setpts=PTS-STARTPTS' cannot work on Android(ARM)

    12 octobre 2017, par Jerikc XIONG

    I use the following command on Android :

    ffmpeg -loglevel 56 -i test.mp4 -vf [0:v]setpts=PTS-STARTPTS[fg] -c:a copy out.mp4 -y

    But it’s failed and I got the following logs :

    N:0 PTS:0 T:0.000000 POS:3848 INTERLACED:0 -> PTS:0 T:nan

    So i add some logs into static int filter_frame(AVFilterLink *inlink, AVFrame *frame) in the libavfilter/setpts.c :

    av_log(inlink->dst, AV_LOG_TRACE, " -> PTS%"PRId64", d:%s timebase:%f, AV_NOPTS_VALUE:%"PRId64 ", AV_NOPTS_VALUE==0?%d:, d == AV_NOPTS_VALUE?%d, TS2T:%f, :%f\n", frame->pts, d2istr(d), av_q2d(inlink->time_base), AV_NOPTS_VALUE, val == 0, d == AV_NOPTS_VALUE, d*av_q2d(inlink->time_base), (double)(0)*0.000078);

    I got the logs :

    -> PTS0, d:0 timebase:0.000011, AV_NOPTS_VALUE:-9223372036854775808, AV_NOPTS_VALUE==0?0:, d == AV_NOPTS_VALUE?0, TS2T:nan, :0.000000

    It’s weird. I always get nan by the TS2T.

    It’s OK on MacBook Pro (Retina, 13-inch, Early 2015) with 2.7 GHz Intel Core i5 when i build the same source code.

    PS :

    #define TS2T(ts, tb) ((ts) == AV_NOPTS_VALUE ? NAN : (double)(ts)*av_q2d(tb))

    I added the full log here.

  • ffmpeg spawned inside NodeJS doesn't output to a url

    31 août 2020, par New Dev

    I'm trying to run ffmpeg on Google Cloud (cloud functions) and I'm trying to have it output the files to a URL (of a Google Storage).

    


    I'm spawning ffmpeg in NodeJS like so :

    


    const { spawn } = require('child_process');

spawn('ffmpeg', [
        '-i', 'input.mp4',
        // ... other arguments
        '-f', 'mp4',
        '-movflags', 'frag_keyframe+empty_moov' // needed for a URL output
        '-headers', `'Authorization: Bearer ${token}'`
        'https://storage.googleapis.com/upload/storage/v1/b/...'])


    


    The problem is the file never gets uploaded, even though ffmpeg runs and exits with code 0.

    


    The weird part is that if I run the exact same command directly from the terminal, it uploads the file.

    


    ffmpeg -i input.mp4 -f mp4 -movflags frag_keyframe+empty_moov -headers 'Authorization: Bearer XXX' 'https://storage.googleapis.com/upload/storage/v1/b/...'


    


    This, I think, eliminates the possibility of any authentication issues or anything on the server-side.

    


    I don't see any difference in the in the output (stderr).

    


    Any idea why the Node-version doesn't upload the output and doesn't report any errors ?