Recherche avancée

Sur d’autres sites (5373)

• Live streaming Rmtp node-media-server real server not creating video files but wont fail (OBS)

  3 octobre 2020, par Orgil

  I have made a live streaming server with node-media-server and it works well in local but when i put it on a real server (ubuntu, nginx) its just creating the folder but not creating video files and no errors given OBS the streaming sofware not failing. is it something to do with ffmpeg ? maybe needed packages didnt install or ? idk whats going on :D

  


  Cofig of node-media-server :

  


  rtmp_server: {
    rtmp: {
        port: 1935,
        chunk_size: 60000,
        gop_cache: false,
        ping: 60,
        ping_timeout: 30
    },
    http: {
        port: 8088,
        mediaroot: '/home/ubuntu/projects/amjilt_media/media',
        allow_origin: '*'
    },
    trans: {
        ffmpeg: '/usr/bin/ffmpeg',
        // ffmpeg: 'C:/Users/User/Desktop/ffmpeg/bin/ffmpeg.exe',
        tasks: [
            {
                app: 'live',
                hls: true,
                hlsFlags: '[hls_time=2:hls_list_size=3:hls_flags=delete_segments]',
                dash: true,
                dashFlags: '[f=dash:window_size=3:extra_window_size=5]'
            }
        ]
    }
}


  


• How to process and upload large video files directly to cloud with ffmpeg but without fragmented MP4 ?

  9 avril 2024, par volume one

  I am using ffmpeg via fluent-ffpmeg for Node.js to process videos uploaded by users.

  


  The problem I have is if a user uploades a huge movie file, say 8GB in size, then I don't want to store the file on the server as it will soon reach full capacity of space.

  


  I thought a way to tackle this was to stream the output from ffmpeg straight to cloud storage like AWS S3. The only way to do this (I believe) is using a PassThrough() stream :

  


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

  


  let PassThroughStream = new PassThrough() ;

  


           FFMpeg('/testvideo.mp4')
                .videoCodec('libx264')
                .audioCodec('libmp3lame')
                .size(`640x480`)
                // Stream input requires manually specifying input format
                .inputFormat('mp4')
                // Stream output requires manually specifying output formats
                .format('mp4')
                // Must be fragmented for stream to work. This causes duration problem.
                .outputOptions('-movflags dash')
                .pipe(PassThroughStream, {end: true})


  


  When the video is created using fragmented MP4, there is no duration associated with the file which means it has no length metadata. That makes playback difficult in a browser and is unacceptable :

  


  

  


  The only way I have been able to get a proper length property set in the file's metadata is by not using fragmented MP4 (that is the -movflags dash part in the code above). By not using this, I cannot stream the output directly to cloud storage - I have to save the file somewhere locally first.

  


  I think I am missing something but don't know what. How could this be solved ? I want to process and write the output to AWS S3 without storing the file locally without creating a fragmented MP4.

  


• fate : split off Microsoft codec FATE tests into their own file

  14 décembre 2011, par Diego Biurrun

  fate : split off Microsoft codec FATE tests into their own file