
Recherche avancée
Autres articles (37)
-
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 (...) -
De l’upload à la vidéo finale [version standalone]
31 janvier 2010, parLe chemin d’un document audio ou vidéo dans SPIPMotion est divisé en trois étapes distinctes.
Upload et récupération d’informations de la vidéo source
Dans un premier temps, il est nécessaire de créer un article SPIP et de lui joindre le document vidéo "source".
Au moment où ce document est joint à l’article, deux actions supplémentaires au comportement normal sont exécutées : La récupération des informations techniques des flux audio et video du fichier ; La génération d’une vignette : extraction d’une (...) -
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 (3268)
-
how to choose a screen to capture with ffmpeg in qt on windows
13 octobre 2020, par YouCLI am using qt with ffmpeg to record desktop on windows. My question is : if I have multiple screens, how to control the recording target ?


Now I pass
desktop
to paramurl
in functionint avformat_open_input(AVFormatContext **ps, const char *url, AVInputFormat *fmt, AVDictionary **options);
. Is there some other param form forurl
to control which screen to capture ?

For example, if I only want to record the primary screen, what
url
value should I use ?

I know qt can identify primary screen and other screens. Is there a way to pass the screen id to ffmpeg ?


-
Redirect FFMPEG's output to multiple named pipes on Windows
27 août 2024, par tearvisusI am trying to stream video and audio data into two separate named pipes on Windows.



ffmpeg.exe -f dshow -i video="My camera name":audio="My microphone name" -map 0:1 -ac 1 -f f32le \\.\pipe\audioStream -map 0:0 -f mjpeg \\.\pipe\videoStream




The problem is that FFMPEG does not seem to understand that the outputs
\\.\pipe\audioStream
and\\.\pipe\videoStream
are pipes and treats them like files.


- 

- If the pipes are already created when the FFMPEG starts, it wants to overwrite them and fails.
- Otherwise, it complains that the path does not exist and fails.







As far as I understand, specifying the
pipe:
protocol should do the trick, but I can't figure out how to use it properly, even with a single pipe. I have tried :


- 

pipe:pipeName
pipe:pipe\pipeName
pipe:\\.\pipe\pipeName
pipe://pipeName
pipe://pipe\pipeName
pipe://\\.\pipe\pipeName















I always end up with the same result : the output is written to the console and not to the pipe. If the pipe already exists when the FFMPEG starts, nothing connects to the pipe.



Is it possible to use FFMPEG with named pipes on Windows ? If yes, what is the proper way to do this ?


-
Redirect FFMPEG's output to multiple named pipes on Windows
31 mai 2016, par tearvisusI am trying to stream video and audio data into two separate named pipes on Windows.
ffmpeg.exe -f dshow -i video="My camera name":audio="My microphone name" -map 0:1 -ac 1 -f f32le \\.\pipe\audioStream -map 0:0 -f mjpeg \\.\pipe\videoStream
The problem is that FFMPEG does not seem to understand that the outputs
\\.\pipe\audioStream
and\\.\pipe\videoStream
are pipes and treats them like files.- If the pipes are already created when the FFMPEG starts, it wants to overwrite them and fails.
- Otherwise, it complains that the path does not exist and fails.
As far as I understand, specifying the
pipe:
protocol should do the trick, but I can’t figure out how to use it properly, even with a single pipe. I have tried :pipe:pipeName
pipe:pipe\pipeName
pipe:\\.\pipe\pipeName
pipe://pipeName
pipe://pipe\pipeName
pipe://\\.\pipe\pipeName
I always end up with the same result : the output is written to the console and not to the pipe. If the pipe already exists when the FFMPEG starts, nothing connects to the pipe.
Is it possible to use FFMPEG with named pipes on Windows ? If yes, what is the proper way to do this ?