Recherche avancée

Médias (1)

Mot : - Tags -/biographie

Autres articles (49)

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

  • Support audio et vidéo HTML5

    10 avril 2011

    MediaSPIP utilise les balises HTML5 video et audio pour la lecture de documents multimedia en profitant des dernières innovations du W3C supportées par les navigateurs modernes.
    Pour les navigateurs plus anciens, le lecteur flash Flowplayer est utilisé.
    Le lecteur HTML5 utilisé a été spécifiquement créé pour MediaSPIP : il est complètement modifiable graphiquement pour correspondre à un thème choisi.
    Ces technologies permettent de distribuer vidéo et son à la fois sur des ordinateurs conventionnels (...)

  • De l’upload à la vidéo finale [version standalone]

    31 janvier 2010, par

    Le chemin d’un document audio ou vidéo dans SPIPMotion est divisé en trois étapes distinctes.
    Upload et récupération d’informations de la vidéo source
    Dans un premier temps, il est nécessaire de créer un article SPIP et de lui joindre le document vidéo "source".
    Au moment où ce document est joint à l’article, deux actions supplémentaires au comportement normal sont exécutées : La récupération des informations techniques des flux audio et video du fichier ; La génération d’une vignette : extraction d’une (...)

Sur d’autres sites (6126)

  • stop ffmpeg gently (to allow it to finish writing mp4 file) when streaming from udp

    22 juillet 2015, par user1913115

    i’m trying to receive a udp stream on a server and write it to an mp4 file. this works fine :

      ffmpeg -i udp://127.0.0.1:12345 -codec copy out.mp4

    if i press CTRL+C (or send SIGINT to the process) the ffmpeg quits and i have a working mp4 file.

    however, if the data stops coming in on the udp port (e.g. after 10 minutes of streaming) and i try to stop ffmpeg it requires 2 interrupt signals at which point ffmpeg exits abruptly and results in an unplayable mp4 file.

    does anyone know how to prevent ffmpeg from hanging when there’s no input data or to force it to write out the mp4 header ?

    i know i can specify a url option

     udp://127.0.0.1:12345?timeout=<microseconds>
    
</microseconds>

    however, i need to be able to ignore occasional (5-10 minute long) pauses during the process of recording and only quit at the end.
    so even if i set timeout=60000000 it will cause my app to wait for 10 minutes when i want to stop the stream (e.g. if there’s no data) and i need it to quit immediately when i send a SIGINT to it

  • stop ffmpeg gently (to allow it to finish writing mp4 file) when streaming from udp

    19 septembre 2023, par ierdna

    i'm trying to receive a udp stream on a server and write it to an mp4 file. this works fine :

    &#xA;&#xA;

      ffmpeg -i udp://127.0.0.1:12345 -codec copy out.mp4&#xA;

    &#xA;&#xA;

    if i press CTRL+C (or send SIGINT to the process) the ffmpeg quits and i have a working mp4 file.

    &#xA;&#xA;

    however, if the data stops coming in on the udp port (e.g. after 10 minutes of streaming) and i try to stop ffmpeg it requires 2 interrupt signals at which point ffmpeg exits abruptly and results in an unplayable mp4 file.

    &#xA;&#xA;

    does anyone know how to prevent ffmpeg from hanging when there's no input data or to force it to write out the mp4 header ?

    &#xA;&#xA;

    i know i can specify a url option

    &#xA;&#xA;

     udp://127.0.0.1:12345?timeout=<microseconds>&#xA;</microseconds>

    &#xA;&#xA;

    however, i need to be able to ignore occasional (5-10 minute long) pauses during the process of recording and only quit at the end. &#xA;so even if i set timeout=60000000 it will cause my app to wait for 10 minutes when i want to stop the stream (e.g. if there's no data) and i need it to quit immediately when i send a SIGINT to it

    &#xA;

  • FFMPEG : closing RTSP stream cleanly — av_read_frame crash on avformat_close_input

    29 novembre 2016, par braden

    I’m using KxMovie : https://github.com/kolyvan/kxmovie

    It appears to stop a stream and close the view controller one should use [pause] ;
    However, I’m trying to receive a stream from a version of gstreamer that has a memory leak if a stream isn’t closed properly (it’s just left hanging).

    So, just [pause]ing isn’t an option for me.

    I’m trying to use [closeFile] in the KxMovie decoder :

    -(void) closeFile
    
{
    

    
[self closeAudioStream];
    
[self closeVideoStream];
    
[self closeSubtitleStream];
    

    
_videoStreams = nil;
    
_audioStreams = nil;
    
_subtitleStreams = nil;
    

    
     if (_formatCtx) {
    
         _formatCtx->interrupt_callback.opaque = NULL;
    
         _formatCtx->interrupt_callback.callback = NULL;
    
         avformat_close_input(&amp;_formatCtx);
    
         _formatCtx = NULL;
    
     }
    
}

    However, I usually get a EXC_BAD_ACCESS from av_read_frame after [closeFile] issues avformat_close_input.

    Can anyone give me some advice on how to cleanly shutdown an RTSP stream using ffmpeg ?

    Thanks !

Navigation