
Recherche avancée
Autres articles (41)
-
Les autorisations surchargées par les plugins
27 avril 2010, parMediaspip core
autoriser_auteur_modifier() afin que les visiteurs soient capables de modifier leurs informations sur la page d’auteurs -
HTML5 audio and video support
13 avril 2011, parMediaSPIP uses HTML5 video and audio tags to play multimedia files, taking advantage of the latest W3C innovations supported by modern browsers.
The MediaSPIP player used has been created specifically for MediaSPIP and can be easily adapted to fit in with a specific theme.
For older browsers the Flowplayer flash fallback is used.
MediaSPIP allows for media playback on major mobile platforms with the above (...) -
Support audio et vidéo HTML5
10 avril 2011MediaSPIP utilise les balises HTML5 video et audio pour la lecture de documents multimedia en profitant des dernières innovations du W3C supportées par les navigateurs modernes.
Pour les navigateurs plus anciens, le lecteur flash Flowplayer est utilisé.
Le lecteur HTML5 utilisé a été spécifiquement créé pour MediaSPIP : il est complètement modifiable graphiquement pour correspondre à un thème choisi.
Ces technologies permettent de distribuer vidéo et son à la fois sur des ordinateurs conventionnels (...)
Sur d’autres sites (9912)
-
closing goroutine spawned by fiber endpoint
30 mai 2023, par NitinI have a program that is rtsp cameras to hls format using ffmpeg for streaming.
creating goroutines for each rtsp link as ffmpeg runs in background


Streams are added by following code.


func StreamProcess(data <-chan StreamData, ctx context.Context) {
for v := range data {
 ctx, _ := context.WithCancel(ctx)
 go func() {
 if !getStreams(v.camera_id) {
 var stream StreamState
 stream.camera_id = v.camera_id
 stream.state = true
 go Stream(v, ctx)
 wg.Wait()
 } else {
 return
 }
 }()
} 



}


Streaming function which runs ffmpeg command.


func Stream(meta StreamData, ctx context.Context) error {
 log.Println("Started Streaming")
 ffmpegCmd := exec.Command("ffmpeg", "-i", meta.rtsp, "-pix_fmt", "yuv420p", "-c:v", "libx264", "-preset", "ultrafast", "-b:v", "600k", "-c:a", "aac", "-b:a", "160k", "-f", "rtsp", fmt.Sprintf("rtsp://localhost:8554/%s", meta.camera_id))
 output, _ := ffmpegCmd.CombinedOutput()

 log.Println(string(output))

 for {
 select {
 case <-ctx.Done():
 log.Println("killing process")
 ffmpegCmd.Process.Kill()
 return nil
 }
 }}



my Goal is to stop each os.exec process (ffmpeg command) or at least close all goroutines that are under ffmpeg commands without closing fiber server.


** help required new to golang **


-
which port ffmpeg is using for streaming to a rtmp(or rtmps) server running in a cloud location
12 janvier 2023, par elsaI am working with ffmpeg and rtmp camera streaming in a constrained environment.
I have rtmp server running on a cloud (say eg. 11.23.123.13 in port 1935 for rtmp & 4936 for rtmps).
However is there any port on sending end , i should request team to open to avoid blocking the stream sending from device end to rtmp server end(camera streaming end). Only port 443 is open in device where camera connected and ffmpeg commands are running.


It would be helpful if somebody give insights on how network is connecting from ffmpeg encoder to rtmp server


- 

- Getting the details how network is connecting from ffmpeg encoder to rtmp server ?
- Which ports to be open in device end(where camera connecting) to start ffmpeg streaming to rtmp server running on cloud ?






-
avcodec/mediacodecdec : don't break out if both input and output port return try again
19 octobre 2022, par Zhao Zhiliavcodec/mediacodecdec : don't break out if both input and output port return try again
At the beginning of decoding, if we feed mediacodec too fast, the
input port will return try again. It takes some time for mediacodec
to consume bitstream and output frame. So the output port also return
try again. It possible that mediacodec_receive_frame doesn't consume
any AVPacket and no AVFrame is output. Then both avcodec_send_packet()
and avcodec_receive_frame() return EAGAIN, which shouldn't happen.This bug can be produced with decoding benchmark on Pixel 3.
Signed-off-by : Zhao Zhili <zhilizhao@tencent.com>