Recherche avancée

Médias (0)

Mot : - Tags -/flash

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

Autres articles (103)

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

  • Participer à sa traduction

    10 avril 2011

    Vous pouvez nous aider à améliorer les locutions utilisées dans le logiciel ou à traduire celui-ci dans n’importe qu’elle nouvelle langue permettant sa diffusion à de nouvelles communautés linguistiques.
    Pour ce faire, on utilise l’interface de traduction de SPIP où l’ensemble des modules de langue de MediaSPIP sont à disposition. ll vous suffit de vous inscrire sur la liste de discussion des traducteurs pour demander plus d’informations.
    Actuellement MediaSPIP n’est disponible qu’en français et (...)

Sur d’autres sites (13819)

  • dash.js four channels audio stream not working

    19 juillet 2016, par Carlos Chacon

    Does dash.js supports 4 channels in the audio stream ?

    I’m using webm, mp4 container : h254 and acc audio stream.

    For the case that the acc audio stream is 2 channels it works fine, both video and audio play correctly.

    I’m using FFMPEG to create the files and WOWZA to setup the DASH streaming.

    For the case that the acc audio stream is 4 channels I get the following error :

    Video can't be played because the file is corrupt.

    Command line to generate the 2-channels file :

    ffmpeg -i video_in.mp4 -i audio_in_4ch.wav -c:v copy -c:a aac -ac 2 output_2channels.mp4

    Command line to generate the 4-channels file :

    ffmpeg -i video_in.mp4 -i audio_in_4ch.wav -c:v copy -c:a aac -ac 4 output_4channels.mp4

    This is the fmmpeg -i information printed for each file :

    2 Channels output file details :

    Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'output_2channels.mp4':
     Metadata:
       major_brand     : isom
       minor_version   : 512
       compatible_brands: isomiso2avc1mp41
       encoder         : Lavf57.37.101
     Duration: 00:00:17.59, start: 0.000000, bitrate: 901 kb/s
       Stream #0:0(eng): Video: h264 (Constrained Baseline) (avc1 / 0x31637661), yuv420p, 1024x512 [SAR 1:1 DAR 2:1], 894 kb/s, 29.97 fps, 29.97 tbr, 30k tbn, 59.94 tbc (default)
       Metadata:
         handler_name    : VideoHandler
       Stream #0:1(und): Audio: aac (LC) (mp4a / 0x6134706D), 48000 Hz, stereo, fltp, 129 kb/s (default)
       Metadata:
         handler_name    : SoundHandler

    4 Channels output file details :

    Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'output_4channels.mp4':
     Metadata:
       major_brand     : isom
       minor_version   : 512
       compatible_brands: isomiso2avc1mp41
       encoder         : Lavf57.37.101
     Duration: 00:00:17.59, start: 0.000000, bitrate: 1038 kb/s
       Stream #0:0(eng): Video: h264 (Constrained Baseline) (avc1 / 0x31637661), yuv420p, 1024x512 [SAR 1:1 DAR 2:1], 894 kb/s, 29.97 fps, 29.97 tbr, 30k tbn, 59.94 tbc (default)
       Metadata:
         handler_name    : VideoHandler
       Stream #0:1(und): Audio: aac (LC) (mp4a / 0x6134706D), 48000 Hz, 4.0, fltp, 265 kb/s (default)
       Metadata:
         handler_name    : SoundHandler
  • Failing to push mpeg dash segment to webdav server using method PUT

    18 avril 2020, par Safwan Sada

    I am trying to push mpeg dash segments to webdav server.

    



    Here is the command :

    



    ffmpeg -loglevel verbose -re -i /home/SAFWAN/URI.mp4 -codec copy -sc_threshold 0 -b_strategy 0 -use_timeline 0 -use_template 1 -window_size 10 -init_seg_name init-$RepresentationID$.mp4 -strict -2 -f dash -segment_list_flags +live -min_seg_duration 2000000 -method PUT http://192.168.22.112/webdav/SAFWAN5/manifest.mpd

    



    But I am able to push hls segments using sample ffmpeg command :
ffmpeg -loglevel verbose -re -i /home/SAFWAN/URI.mp4 -codec copy -method PUT -f hls http://192.168.22.112/webdav/SAFWAN5/master.m3u8

    



    Here is the apache2 access log :
183.82.0.170 - - [18/Apr/2020:10:32:28 -0400] "POST /webdav/SAFWAN5/manifest.mpd HTTP/1.1" 200 292 "-" "Lavf/57.83.100"
183.82.0.170 - - [18/Apr/2020:10:32:38 -0400] "POST /webdav/SAFWAN5/chunk-stream0-00004.m4s HTTP/1.1" 404 498 "-" "Lavf/57.83.100"
183.82.0.170 - - [18/Apr/2020:10:32:38 -0400] "POST /webdav/SAFWAN5/chunk-stream1-00004.m4s HTTP/1.1" 404 498 "-" "Lavf/57.83.100"
183.82.0.170 - - [18/Apr/2020:10:32:39 -0400] "POST /webdav/SAFWAN5/manifest.mpd HTTP/1.1" 200 292 "-" "Lavf/57.83.100"
183.82.0.170 - - [18/Apr/2020:10:32:48 -0400] "POST /webdav/SAFWAN5/chunk-stream0-00005.m4s HTTP/1.1" 404 498 "-" "Lavf/57.83.100"
183.82.0.170 - - [18/Apr/2020:10:32:48 -0400] "POST /webdav/SAFWAN5/chunk-stream1-00005.m4s HTTP/1.1" 404 498 "-" "Lavf/57.83.100"
183.82.0.170 - - [18/Apr/2020:10:32:49 -0400] "POST /webdav/SAFWAN5/manifest.mpd HTTP/1.1" 200 292 "-" "Lavf/57.83.100"
183.82.0.170 - - [18/Apr/2020:10:32:53 -0400] "POST /webdav/SAFWAN5/chunk-stream0-00006.m4s HTTP/1.1" 404 498 "-" "Lavf/57.83.100"
183.82.0.170 - - [18/Apr/2020:10:32:53 -0400] "POST /webdav/SAFWAN5/chunk-stream1-00006.m4s HTTP/1.1" 404 498 "-" "Lavf/57.83.100"
183.82.0.170 - - [18/Apr/2020:10:32:53 -0400] "POST /webdav/SAFWAN5/manifest.mpd HTTP/1.1" 200 292 "-" "Lavf/57.83.100"
183.82.0.170 - - [18/Apr/2020:10:32:57 -0400] "POST /webdav/SAFWAN5/chunk-stream0-00007.m4s HTTP/1.1" 404 498 "-" "Lavf/57.83.100"
183.82.0.170 - - [18/Apr/2020:10:32:57 -0400] "POST /webdav/SAFWAN5/chunk-stream1-00007.m4s HTTP/1.1" 404 498 "-" "Lavf/57.83.100"
183.82.0.170 - - [18/Apr/2020:10:32:57 -0400] "POST /webdav/SAFWAN5/manifest.mpd HTTP/1.1" 200 292 "-" "Lavf/57.83.100"
183.82.0.170 - - [18/Apr/2020:10:33:00 -0400] "POST /webdav/SAFWAN5/chunk-stream0-00008.m4s HTTP/1.1" 404 498 "-" "Lavf/57.83.100"
183.82.0.170 - - [18/Apr/2020:10:33:00 -0400] "POST /webdav/SAFWAN5/chunk-stream1-00008.m4s HTTP/1.1" 404 498 "-" "Lavf/57.83.100"
183.82.0.170 - - [18/Apr/2020:10:33:01 -0400] "POST /webdav/SAFWAN5/manifest.mpd HTTP/1.1" 200 292 "-" "Lavf/57.83.100"

    



    Please let me know why the dash segments is failing to push to webdav server ?

    


  • Why does ffmpeg generate a mpeg-dash mpd with long timeShiftBufferDepth even with window_size of one minute ? [closed]

    1er février 2024, par igorblima

    I'm having a problem with ffmpeg when i try to create a dynamic mpd from rtmp livestream. The vídeo integrity its ok and works fine, but the only problem is with the timeShiftBufferDepth. The command specifies how much window_size to have, but for some reason the timeShiftBufferDepth generated by ffmpeg doesn't respect that. I specified 1 minute of window_size, but for some reason unknown to me, the timeShiftBufferDepth is generated as 8 minutes

    


    the command :

    


    ffmpeg -i rtmp://localhost:1935/live/stream -c:v libx264 -b:v 1000k -c:a aac -b:a 128k -strict experimental -f dash -window_size 60 -utc_timing_url https://time.akamai.com/?ms -seg_duration 5 -remove_at_exit 1 -dash_segment_type mp4 h264.mpd


    


    result :

    


    timeShiftBufferDepth="PT8M19.9S"


    


    how i say previously, the mpd works fine in the player. The only issue is with that incorrect timeShiftBufferDepth

    


    i read the ffmpeg documentation https://ffmpeg.org/ffmpeg-formats.html#Options-19