
Recherche avancée
Autres articles (111)
-
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 (...) -
ANNEXE : Les plugins utilisés spécifiquement pour la ferme
5 mars 2010, parLe site central/maître de la ferme a besoin d’utiliser plusieurs plugins supplémentaires vis à vis des canaux pour son bon fonctionnement. le plugin Gestion de la mutualisation ; le plugin inscription3 pour gérer les inscriptions et les demandes de création d’instance de mutualisation dès l’inscription des utilisateurs ; le plugin verifier qui fournit une API de vérification des champs (utilisé par inscription3) ; le plugin champs extras v2 nécessité par inscription3 (...)
-
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 (14967)
-
Cannot get MediaStream from Electron app to browser via Openvidu media server
11 juin 2021, par foxy.bunnyI'm currently having an issue with openvidu-browser-2.17.0.js


I'm trying to transfer a camera stream from RTSP to an Openvidu media server deployed on cloud and get the stream back on the browser.


The RTSP stream was converted into an HLS stream using FFmpeg and played using hls.js. It was captured in an video tag in HTML and I used the HTMLMediaElement.captureStream().getVideoTrack() to generate MediaStreamTrack and passed it into the videoSource property in initPublisher. This publisher part was wrapped in electron. Then, the stream was connected to our cloud Openvidu server deployed on-premises exactly like in the Docs (https://docs.openvidu.io/en/2.18.0/deployment/deploying-on-premises/). The subscriber part is a simple HTML page displayed on the browser to get the stream from the cloud server. The subscriber is responsible for creating session and generating stream from the media server when streamCreated event occurs.


The whole workflow worked nicely when we tested it with our webcam, however, when we use MediaStreamTrack of our stream video instead of webcam, the subscriber part only showed the blank video.


My question is :


1 : Is it possible to stream an MediaStream to Openvidu media server like that ?


2 : If yes, then what am I doing wrong here ?


Describe the bug


Cannot get MediaStream from Electron app to browser via Openvidu media server.


Expected behavior


Receive the stream from the Electron app to browser via Openvidu media server.


Wrong current behavior


Only get blank video


Client device info


- 

- Chrome Version 91.0.4472.77 (Official Build) (64-bit) on Windows 10 Version 10.0.19042 Build 19042




-
Getting Error with node-media-serve and ffmpeg in heroku
1er juillet 2021, par Anurag GautamI have created a MERN app with video streaming by using
node-media-serve
module, with following configuration

trans: {
 ffmpeg: '/vendor/ffmpeg',
 tasks: [] ,
 .....
}



In local I have installed
ffmpeg
intrans.ffmpeg
. and its working fine, But how we need to install ffmpeg in heroku .

I have tried by adding heroku buildpacks

heroku buildpacks:add https://github.com/jonathanong/heroku-buildpack-ffmpeg-latest.git
but its showing me error. May be some issue with config only.

Heroku error :

2020-09-16T11:23:54.292896+00:00 app[web.1]: 9/16/2020 11:23:54 23 [ERROR] Node Media Trans Server startup failed. ffmpeg:/vendor/ffmpeg cannot be executed.


Guys can you please help me reslove this issue


-
avformat/HLS : modified EXT-X-MEDIA-SEQUENCE header in order to follow the HLS standard
5 février 2014, par Willy Aubryavformat/HLS : modified EXT-X-MEDIA-SEQUENCE header in order to follow the HLS standard
When using the wrap option the EXT-X-MEDIA-SEQUENCE header of the playlist file was reset instead of being incremented.
It is now incremented by one for every media URI removed from the playlist file as the standard states.Signed-off-by : Willy Aubry <waubry@viotech.net>
Signed-off-by : Michael Niedermayer <michaelni@gmx.at>