Recherche avancée

Médias (1)

Mot : - Tags -/MediaSPIP 0.2

Autres articles (92)

  • Les formats acceptés

    28 janvier 2010, par

    Les commandes suivantes permettent d’avoir des informations sur les formats et codecs gérés par l’installation local de ffmpeg :
    ffmpeg -codecs ffmpeg -formats
    Les format videos acceptés en entrée
    Cette liste est non exhaustive, elle met en exergue les principaux formats utilisés : h264 : H.264 / AVC / MPEG-4 AVC / MPEG-4 part 10 m4v : raw MPEG-4 video format flv : Flash Video (FLV) / Sorenson Spark / Sorenson H.263 Theora wmv :
    Les formats vidéos de sortie possibles
    Dans un premier temps on (...)

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

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

Sur d’autres sites (7059)

  • How to pipe frames in stdout using FFMPEG and Golang

    6 avril 2020, par Sven.DG

    I am fairly new to Golang, my goal is to build a script in Golang that :

    



      

    1. Transcodes the video input .MOV file into frames, using FFMPEG
    2. 


    3. Some downstream process that does something with the emitted frames.
    4. 


    



    Currently I have the following code as a first attempt :

    



    package main

import (
    "fmt"
    "os/exec"
    "strconv"
    "io"
)

const (
    frameX      = 240
    frameY      = 135
    frameSize   = frameX * frameY * 3
)

func main() {
    ffmpeg := exec.Command("ffmpeg", "-i", "project/data/sample.mov", "-vf",  "fps=fps=1/2", "-s", strconv.Itoa(frameX)+"x"+strconv.Itoa(frameY), "-f", "rawvideo", "pipe:1") //nolint
    ffmpegOut, _ := ffmpeg.StdoutPipe()

    if err := ffmpeg.Start(); err != nil {
        panic(err)
    }

    reader(ffmpegOut)
    fmt.Println("Completed. YAY")
}

func reader(ffmpegOut io.Reader) {
    buf := make([]byte, frameSize)
    fmt.Println("Looping..")
    counter := 0
    for {
        if _, err := io.ReadFull(ffmpegOut, buf); err != nil {
            // fmt.Println(err)
        }
        if buf[0] != 0 {
            fmt.Println("Got a frame!!")
            counter++
            fmt.Println(counter)
        }
    }
    fmt.Println("total amount of frames", counter)
}


    



    This is mainly based on this example : https://github.com/pion/example-webrtc-applications/blob/master/gocv-receive/main.go

    



    However, when running this code, it appears that I'm getting an endless amount of data in my downstream reader. I would expect that the counter equals the amount of frames but that is clearly not the case looking at the rate at which the counter increases, so obviously I am doing something wrong. Can anybody point me in the right direction ?

    



    I used the sample .mov file with 1280 x 720 resolution here : https://file-examples.com/index.php/sample-video-files/sample-mov-files-download/.
The video is about 31 seconds so I would expect to see 15 frames downstream in the reader.

    



    Cheers !

    


  • Matomo Further Invests in Security by Doubling Bug Bounty Rewards

    7 janvier 2022, par erin — Community, Press Releases

    Matomo is the leading open-source analytics solution free from data limitations. 

    As our mission states, we aim to create, as a community, the leading open digital analytics platform that gives every user full control of their data. 

    To do this, we operate a Security Bug Bounty Programme. This programme is designed to reward the hard work of skilled security researchers who sacrifice their time and energy to find and report security and vulnerabilities. 

    To continue our investment in security, privacy and transparency, we are increasing the security bug bounty reward to as much as $10,000 USD. This is an increase of 100% from our previous 2020 bug bounty announcement.

    How much can I earn for reporting security bugs ?

    Reward amounts vary depending on the impact :

    • Low issues receive $222
    • Medium issues receive $555
    • High issues receive $1,000
    • Critical issues receive $10,000

    How can I take part ? 

    As of January 2022, global independent security researchers have identified and suggested 138 security related improvements. If you are interested in joining this growing community, head to our Security Bug Bounty Programme to find out how you can take part. 

    We thank you for keeping Matomo safe for our users and theirs.

    About Matomo

    Matomo is the leading open-source analytics solution free from data limitations. Make more informed decisions and enhance your customer experience while ensuring data privacy and ownership. Matomo is the trusted solution for over 1.5 million websites globally. Take back control of your data ownership and challenge the status quo.

  • ffmpeg : check ost->finished in reap_filters()

    14 janvier 2014, par Michael Niedermayer
    ffmpeg : check ost->finished in reap_filters()
    

    This avoids finished output streams continuing to receive frames

    Signed-off-by : Michael Niedermayer <michaelni@gmx.at>

    • [DH] ffmpeg.c