Recherche avancée

Médias (1)

Mot : - Tags -/belgique

Autres articles (74)

  • Keeping control of your media in your hands

    13 avril 2011, par

    The vocabulary used on this site and around MediaSPIP in general, aims to avoid reference to Web 2.0 and the companies that profit from media-sharing.
    While using MediaSPIP, you are invited to avoid using words like "Brand", "Cloud" and "Market".
    MediaSPIP is designed to facilitate the sharing of creative media online, while allowing authors to retain complete control of their work.
    MediaSPIP aims to be accessible to as many people as possible and development is based on expanding the (...)

  • Contribute to documentation

    13 avril 2011

    Documentation is vital to the development of improved technical capabilities.
    MediaSPIP welcomes documentation by users as well as developers - including : critique of existing features and functions articles contributed by developers, administrators, content producers and editors screenshots to illustrate the above translations of existing documentation into other languages
    To contribute, register to the project users’ mailing (...)

  • Supporting all media types

    13 avril 2011, par

    Unlike most software and media-sharing platforms, MediaSPIP aims to manage as many different media types as possible. The following are just a few examples from an ever-expanding list of supported formats : images : png, gif, jpg, bmp and more audio : MP3, Ogg, Wav and more video : AVI, MP4, OGV, mpg, mov, wmv and more text, code and other data : OpenOffice, Microsoft Office (Word, PowerPoint, Excel), web (html, CSS), LaTeX, Google Earth and (...)

Sur d’autres sites (7286)

  • Streaming audio from mac with ffmpeg to nginx and playback with videojs

    15 juillet 2020, par Disco Fever

    I'm playing around trying to get to stream my Mac's sound to a webpage.

    


    Here's what I have so far :

    


    On the mac :

    


    ffmpeg -f avfoundation -i ":2" -acodec libmp3lame -ab32k -ac 1 -f flv rtmp://myserver:8000/hls/live


    


    On the nginx side :

    


    events {
    worker_connections  1024;
}

rtmp {
    server {
        listen 8000;
        chunk_size 4000;
        application hls {
            live on;
            interleave on;
            hls on;
            hls_path /tmp/hls;
        }
    }
}

http {
    default_type  application/octet-stream;
    sendfile off;
    tcp_nopush on;
    server {

        listen      8080;
        location /hls {
            add_header Cache-Control no-cache;
            types {
                application/vnd.apple.mpegurl m3u8;
                video/mp2t ts;
            }
            root /tmp;
        }
    }
}


    


    Web side :

    


    &#xA;&#xA;&#xA;    &#xA;    &#xA;&#xA;<code class="echappe-js">&lt;script src=&quot;//vjs.zencdn.net/7.8.2/video.min.js&quot;&gt;&lt;/script&gt;&#xA;&#xA;&#xA;&#xA;&#xA;&#xA;

    &#xA;

    No matter what i do I can't get any sound (it's playing on the Mac 100% sure) ; i've tried also putting a video tag instead, i see the image but no sound. What's missing here ? Can this even be achieved ?

    &#xA;

    THanks

    &#xA;

  • Restart ffmpeg on loss of stream

    21 octobre 2018, par JoeN

    I record a rtmps stream with ffmpeg, occasionally the stream drops out for various reasons (isp failure, network problems) Ffmpeg stops and I have to manualy restart it.
    Is there a way to monitor for stream loss and restart ffmpeg ?
    Maybe a script ? I use Linux. I have tried timout stimout but they do not work.

    Here is my ffmpeg command that I enter in terminal

    ffmpeg -i rtmps://(url) -r 25 \
    
-vf "drawtext=fontfile=/usr/share/fonts/truetype/dejavu/DejaVuSans.ttf: text='%{localtime}': x=(w-tw)/2: y=h-(2*lh): fontcolor=white: fontsize=24: box=1: boxcolor=0x00000000@1" \
    
-f segment -strftime 1 -segment_time 1800 \
    
-segment_format mkv /media/joe/disk/a/%m_%d_%Y-%H_%M_%S.mkv

  • Pipe a HTTP response

    30 juillet 2014, par viperfx

    How do I pipe an HTTP response like in NodeJS. Here is the snippet I am using in NodeJS :

    request({
    
  url: audio_file_url,
    
}).pipe(ffmpeg_process.stdin);

    How can I achieve the same result in Go ?

    I am trying to pipe a audio stream from HTTP into an FFmpeg process so that it converts it on the fly and returns the converted file back to the client.

    Just so its clear to everyone here is my source code so far :

    func encodeAudio(w http.ResponseWriter, req *http.Request) {
    
    path, err := exec.LookPath("youtube-dl")
    
    if err != nil {
    
        log.Fatal("LookPath: ", err)
    
    }
    
    path_ff, err_ff := exec.LookPath("ffmpeg")
    
    if err != nil {
    
        log.Fatal("LookPath: ", err_ff)
    
    }
    

    
    streamLink := exec.Command(path,"-f", "140", "-g", "https://www.youtube.com/watch?v=VIDEOID")
    

    
    var out bytes.Buffer
    
    streamLink.Stdout = &amp;out
    
    cmdFF := exec.Command(path_ff, "-i", "pipe:0", "-acodec", "libmp3lame", "-f", "mp3", "-")
    
    resp, err := http.Get(out.String())
    
    if err != nil {
    
        log.Fatal(err)
    
    }
    
    // pr, pw := io.Pipe()
    
    defer resp.Body.Close()
    
    cmdFF.Stdin = resp.Body
    
    cmdFF.Stdout = w
    
    streamLink.Run()
    
    //get ffmpeg running in another goroutine to receive data
    
    errCh := make(chan error, 1)
    
    go func() {
    
        errCh &lt;- cmdFF.Run()
    
    }()
    

    
    // close the pipeline to signal the end of the stream
    
    // pw.Close()
    
    // pr.Close()
    

    
    // check for an error from ffmpeg
    
    if err := &lt;-errCh; err != nil {
    
        // ff error
    
    }
    
}

    Error : 2014/07/29 23:04:02 Get : unsupported protocol scheme ""

Navigation