Recherche avancée

Sur d’autres sites (9577)

• Need help transcoding Red5 RTMP stream to MPEG2-TS

  5 février 2014, par reyniraron

  Me and my friend are going to make live shows and for that purpose I have set up a Red5 server on my old 2006 Intel Core Duo Mac mini running Mac OS X Snow Leopard Server 10.6.8.

  I use Flash Media Live Encoder to broadcast to Red5's oflaDemo application and the stream works great, except for the fact that I want the stream to work with iOS.
  I am developing an app for it, but I still need to convert my stream to Apple's HTTP Live Streaming protocol for it to work.
  Can anybody help me convert the RTMP stream to MPEG2-TS, because that's the format that mediastreamsegmenter supports ? I already have Apple's HTTP Live Streaming Tools installed on the server, so the segmenter's not a problem.

  FFmpeg doesn't work, at least not with the code I found here. With it a always get an "Operation not permitted" error. Xuggler doesn't work, not even with a Linux box.
  Can anybody please help me ? I'd really, really appreciate it.

  -Reynir Aron

• How Akamei is packaging HLS and DASH videos ?

  27 décembre 2022, par Ahmed Mahmoud

  Latlert I've been trying to create my own simple streaming service which converts an mp4 video to HLS or DASH. For the sake of simplicity, let's focus on only HLS.

  


  Apple is the the one how created HLS (HTTP Live Streaming) which consists of a different resulotions playlist files, and each file consists of seperate sepemts (ts, mp4 or m4a) each segment is a time range of the original video.

  


  I've noticed the Akamei are using the same mp4 video and a query param range to range over the video segements.

  


  Example of a typical segments playlist :

  


  #EXTM3U
#EXT-X-TARGETDURATION:6
#EXT-X-VERSION:3
#EXT-X-MEDIA-SEQUENCE:1
#EXT-X-INDEPENDENT-SEGMENTS
#EXTINF:6.92,
240p_noaudio_dash1.ts

#EXT-X-ENDLIST


  


  Example of Akamei playlist :

  


  #EXTM3U
#EXT-X-VERSION:6
#EXT-X-MEDIA-SEQUENCE:0
#EXT-X-TARGETDURATION:6
#EXT-X-PLAYLIST-TYPE:VOD
#EXT-X-MAP:URI="../../../parcel/video/78619exa.mp4?r=dXMtd2VzdDE%3D&range=0-830"
#EXTINF:6.066667
../../../parcel/video/78619exa.mp4?r=dXMtd2VzdDE%3D&range=5975-2400598
#EXTINF:6.066667
../../../parcel/video/78619exa.mp4?r=dXMtd2VzdDE%3D&range=2400599-4512749
#EXTINF:6.033333
../../../parcel/video/78619exa.mp4?r=dXMtd2VzdDE%3D&range=4512750-6575755
#EXTINF:6.066667
../../../parcel/video/78619exa.mp4?r=dXMtd2VzdDE%3D&range=6575756-8651671
#EXT-X-ENDLIST


  


  How Akamei is gementing the same video on the fly to stream HLS and DASH ?

  


  I searched and read the HLS Specifications with no luck.

  


• Why does fluent-ffmpeg only work when it throws the error Output stream closed

  29 mars 2024, par volume one

  I am using fluent-ffmpeg to process a video file (and then upload that to Amazon S3). The code is very straightforward but it only works if :

  


  

  • pipe option {end: true} is set in .output()

  


  • which has a side-effect that causes the following console log output

  


  


  


  Processing : 19.261847354642416% done Processing :
32.365144874807335% done Processing : 48.80978326261429% done Processing : 78.35771917058617%
Processing : 91.49377493455148% done Processing :
99.91264359125745% done An error occurred : Output stream closed

  


  


  Despite that error, it seems the file is generated correctly and it gets uploaded to Amazon S3 fine.

  


  This is the fluent-ffmpeg code :

  


  import {PassThrough} from 'node:stream';
import FFMpeg from 'fluent-ffmpeg';

let PassThroughStream = new PassThrough();

             FFMpeg('/testvideo.mp4')
                    .videoCodec('libx264')
                    .audioCodec('libmp3lame')
                    .size(`640x480`)
                    // Stream output requires manually specifying output formats
                    .format('mp4')
                    .outputOptions('-movflags dash')
                    .on('progress', function (progress) {
                        console.log('Processing: ' + progress.percent + '% done');
                    })
                    .on('error', function (err) {
                        console.log('An error occurred: ' + err.message);
                    })
                    .on('end', function () {
                        console.log('FFMpeg Processing finished!');
                    })
                    .output(PassThroughStream, {end: true})
                    .run();

   // Now upload to S3
    try {
          await s3Upload({
              AWSS3Client: 'mys3client',
              Bucket: 'publicbucket,
              ACL: "public-read",
              ContentType: 'video/mp4',
              Key: 'whoever/whatever.mp4',
              Body: PassThroughStream
           });
    } catch (error) {
                    console.log(`s3Upload error`, error)
                }


  


  If I set the pipe output() option to {end: false} then there is no error from fluent-ffmpeg and I get "Processing: 100% done FFMpeg Processing finished!" as the final console log.

  


  BUT the problem is that the s3Upload() does not do anything. There are no errors. Just no activity.

  


  I feel very uncomfortable letting fluent-ffmpeg end in an error even if the code itself does the job intended. It will also cause testing to fail. What could be the issue ?

  


  The command line code is : ffmpeg -i https:/xxxbucket.s3.amazonaws.com/14555/file-example.mp4 -acodec libmp3lame -vcodec libx264 -filter:v scale=w=trunc(oh*a/2)*2:h=480 -f mp4 -movflags dash pipe:1