Recherche avancée

Médias (1)

Mot : - Tags -/biomaping

Autres articles (46)

  • Gestion de la ferme

    2 mars 2010, par

    La ferme est gérée dans son ensemble par des "super admins".
    Certains réglages peuvent être fais afin de réguler les besoins des différents canaux.
    Dans un premier temps il utilise le plugin "Gestion de mutualisation"

  • Contribute to translation

    13 avril 2011

    You can help us to improve the language used in the software interface to make MediaSPIP more accessible and user-friendly. You can also translate the interface into any language that allows it to spread to new linguistic communities.
    To do this, we use the translation interface of SPIP where the all the language modules of MediaSPIP are available. Just subscribe to the mailing list and request further informantion on translation.
    MediaSPIP is currently available in French and English (...)

  • Création définitive du canal

    12 mars 2010, par

    Lorsque votre demande est validée, vous pouvez alors procéder à la création proprement dite du canal. Chaque canal est un site à part entière placé sous votre responsabilité. Les administrateurs de la plateforme n’y ont aucun accès.
    A la validation, vous recevez un email vous invitant donc à créer votre canal.
    Pour ce faire il vous suffit de vous rendre à son adresse, dans notre exemple "http://votre_sous_domaine.mediaspip.net".
    A ce moment là un mot de passe vous est demandé, il vous suffit d’y (...)

Sur d’autres sites (5467)

  • Live Streaming using CloudFront and FFMPEG having delay issue

    22 avril 2021, par jitendra-gautam

    Live Streaming using CloudFront and FFMPEG having delay issue
I am using the NodeJS server with FFMPEG and live streaming to CloudFront, which is then consumed by many people via CloudFront.
Below is the data received at the user's end.

    


    #EXTM3U
#EXT-X-VERSION:3
#EXT-X-MEDIA-SEQUENCE:1317
#EXT-X-ALLOW-CACHE:NO
#EXT-X-TARGETDURATION:1
#EXTINF:0.833333,
1317.ts
#EXTINF:0.833333,
1318.ts
#EXTINF:0.833333,
1319.ts


    


    The problem is the next .ts file that is 1320.ts is taking time to create on the server, thus the user is seeing the loading sign, and when this 1320.ts is created on the server, thereafter only the user is able to see the next live stream frame.
How can the streaming be continuous ??
Below is the FFMPEG command that is being used :

    


    process = child_process.spawn('ffmpeg', commandArgs);


    


    let commandArgs = [
  '-loglevel',
  'debug',
  '-protocol_whitelist',
  'pipe,udp,rtp,rtmp,http,https,tcp',
  '-fflags',
  '+genpts',
  '-f',
  'sdp',
  '-i',
  'pipe:0',
  '-c:v',
  'libx264',
  '-crf',
  '21',
  '-preset',
  'veryfast',
  '-g',
  '25',
  '-sc_threshold',
  '0',
  '-c:a',
  'aac',
  '-b:a',
  '128k',
  '-ac',
  '2',
  '-hls_flags',
  'delete_segments+append_list',
  '-f',
  'segment',
  '-segment_list_flags',
  'live',
  '-segment_time',
  '1',
  '-segment_list_size',
  '3',
  '-segment_format',
  'mpegts',
  '-segment_list',
  `${RECORD_FILE_LOCATION_PATH}/${fileName}.m3u8`,
  `-segment_list_type`,
  'm3u8',
  `${RECORD_FILE_LOCATION_PATH}/%d.ts`
];


    


  • ffmpeg crashes in electron on mac apple store ; no suitable image found file system sandbox blocked open() of 'libass'

    20 février 2021, par Martin

    I am trying to release an electron app on the Mac Apple Store (mas), my electron app uses ffmpeg to render videos. In order to release my app on the mac apple store, It needs to be sandboxed, and by default ffmpeg makes calls to external libraries so I need to statically build ffmpeg and package it with my app. I have successfully built my app, submitted it to the app store, had it approved, and downloaded/used it but my ffmpeg fails with this errir :

    


    Uncaught (in promise) Error: Command was killed with SIGABRT (Aborted): /Users/martinbarker/Documents/projects/digify-new/dist/mas/Digify.app/Contents/Resources/ffmpeg -i /Users/martinbarker/Downloads/Steve Leach With The Crystal Grass Orchestra – Ocean Potion/9. Get Out In The Sun.flac -i /Users/martinbarker/Downloads/Steve Leach With The Crystal Grass Orchestra – Ocean Potion/10. Golden Hues.flac -y -filter_complex concat=n=2:v=0:a=1 -c:a libmp3lame -b:a 320k /Users/martinbarker/Downloads/Steve Leach With The Crystal Grass Orchestra – Ocean Potion/output-261020.mp3
dyld: Library not loaded: /usr/local/opt/libass/lib/libass.9.dylib
  Referenced from: /Users/martinbarker/Documents/projects/digify-new/dist/mas/Digify.app/Contents/Resources/ffmpeg
  Reason: no suitable image found.  Did find:
    file system sandbox blocked open() of '/usr/local/opt/libass/lib/libass.9.dylib'
    /usr/local/opt/libass/lib/libass.9.dylib: stat() failed with errno=1
    file system sandbox blocked open() of '/usr/local/lib/libass.9.dylib'
    file system sandbox blocked open() of '/usr/local/Cellar/libass/0.15.0/lib/libass.9.dylib'
    at makeError (/Users/martinbarker/…eca/lib/error.js:59)
    at handlePromise (/Users/martinbarker/…/execa/index.js:114)
    at async file:/Users/ma…js/newindex.js:1151


    


    I think this line is important ; file system sandbox blocked open() of '/usr/local/opt/libass/lib/libass.9.dylib' but I'm not sure what I should change with my static ffmpeg build so that it works in production and so that I can avoid the above error.

    


    My code is available on the branch mas-attempt-after-redesign here : https://github.com/MartinBarker/digify/tree/mas-attempt-after-redesign

    


    Inside my package.json I have the command download-ffmpeg which clones the ffmpeg repo, runs a configure command with some flags, and then builds ffmpeg into a folder called 'ffmpeg-mac', this folder gets packaged with the app for the mac apple store build.

    


    git clone https://git.ffmpeg.org/ffmpeg.git ffmpeg-mac && cd ffmpeg-mac && ./configure pkg_config='pkg-config --static' --pkg-config-flags='--static' --libdir=/usr/local/lib --extra-version=ntd_20150128 --disable-shared --disable-lzma --enable-gpl --enable-pthreads --enable-nonfree --enable-libass --enable-libfdk-aac  --enable-libmp3lame  --enable-libx264 --enable-static --enable-filters --enable-runtime-cpudetect && make && cd ..


    


    You can see in the above ffmpeg command the flag --enable-libass, but even though I have that flag included, after I build and sign my mac apple store build by running sudo rm -rf dist/mas/ && npm run build-mas && sh mas-sign-script.sh, the production build (once approved) fails with the above included error.

    


  • Live Streaming over HTTP using CloudFront and FFMPEG having delay issue

    23 avril 2021, par jitendra-gautam

    Live Streaming using CloudFront and FFMPEG having delay issue I am using the NodeJS server with FFMPEG and live streaming to CloudFront, which is then consumed by many people via CloudFront. Below is the data received at the user's end.

    


    #EXTM3U
#EXT-X-VERSION:3
#EXT-X-MEDIA-SEQUENCE:1317
#EXT-X-ALLOW-CACHE:NO
#EXT-X-TARGETDURATION:1
#EXTINF:0.833333,
1317.ts
#EXTINF:0.833333,
1318.ts
#EXTINF:0.833333,
1319.ts


    


    The problem is the next .ts file that is 1320.ts is taking time to create on the server, thus the user is seeing the loading sign, and when this 1320.ts is created on the server, thereafter only the user is able to see the next live stream frame. How can the streaming be continuous ?? Below is the FFMPEG command that is being used :

    


    process = child_process.spawn('ffmpeg', commandArgs);



    


    let commandArgs = [
  '-loglevel',
  'debug',
  '-protocol_whitelist',
  'pipe,udp,rtp,rtmp,http,https,tcp',
  '-fflags',
  '+genpts',
  '-f',
  'sdp',
  '-i',
  'pipe:0',
  '-c:v',
  'libx264',
  '-crf',
  '21',
  '-preset',
  'veryfast',
  '-g',
  '25',
  '-sc_threshold',
  '0',
  '-c:a',
  'aac',
  '-b:a',
  '128k',
  '-ac',
  '2',
  '-hls_flags',
  'delete_segments+append_list',
  '-f',
  'segment',
  '-segment_list_flags',
  'live',
  '-segment_time',
  '1',
  '-segment_list_size',
  '3',
  '-segment_format',
  'mpegts',
  '-segment_list',
  `${RECORD_FILE_LOCATION_PATH}/${fileName}.m3u8`,
  `-segment_list_type`,
  'm3u8',
  `${RECORD_FILE_LOCATION_PATH}/%d.ts`
];