Recherche avancée
Autres articles (51)
-
Encodage et transformation en formats lisibles sur Internet
10 avril 2011MediaSPIP transforme et ré-encode les documents mis en ligne afin de les rendre lisibles sur Internet et automatiquement utilisables sans intervention du créateur de contenu.
Les vidéos sont automatiquement encodées dans les formats supportés par HTML5 : MP4, Ogv et WebM. La version "MP4" est également utilisée pour le lecteur flash de secours nécessaire aux anciens navigateurs.
Les documents audios sont également ré-encodés dans les deux formats utilisables par HTML5 :MP3 et Ogg. La version "MP3" (...) -
Des sites réalisés avec MediaSPIP
2 mai 2011, parCette page présente quelques-uns des sites fonctionnant sous MediaSPIP.
Vous pouvez bien entendu ajouter le votre grâce au formulaire en bas de page. -
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 (...)
Sur d’autres sites (4577)
-
RTSP streaming on Android client using FFMpeg
10 août 2013, par rurtleI am working on a hobby project the goal for which is to develop an Android application capable of streaming live feeds captured through web cams in a LAN setting using FFMpeg as the underlying engine. So far, I did the following -
A. Compiling and generating FFMpeg related libraries for the following releases -
FFMpeg version : 2.0
NDK version : r8e & r9
Android Platform version : android-16 & android-18thisthisthisthis
Toolchain version : 4.6 & 4.8
Platform built on : Fedora 18 (x86_64)B. Creating the files Android.mk & Application.mk in appropriate path.
However, when it came to writing the native code for accessing appropriate functionality of FFMpeg from the application layer using Java, I'm stuck with following questions -
a) Which all of FFMpeg's features I need to make available from native to app layer for streaming real-time feeds ?
b) In order to compile FFMpeg for Android, I followed this link. Whether the compilation options are sufficient for handling *.sdp streams or do I need to modify it ?
c) Do I need to make use of live555 ?I am totally new to FFMpeg and Android application development and this is going to be my first serious project for Android platform. I have been searching for relevant tutorials dealing with RTSP streaming using FFMpeg for a while now without much success. Moreover, I tried the latest development build of VLC player and found it to be great for streaming real-time feeds. However, it's a complex beast and the goal for my project is of quite limited nature, mostly learning - in a short time span.
Could you suggest some pointers (e.g. links, documents or sample code) on how can I write the native code for utilizing FFMpeg library and subsequently use those functionality from the app layer for streaming real-time feeds ? Moreover, will really appreciate if you could let me know the kind of background knowledge necessary for this project from a functional standpoint (in a language agnostic sense).
-
OpenCV on MacOS : Match Camera Index and Name
15 janvier, par rpi_guruI have a builtin camera and a USB webcam connected to my MacOS.


Here is a result of
system_profiler SPCameraDataType -xmlcommand :

<?xml version="1.0" encoding="UTF-8"?>

<plist version="1.0">
<array>
 <dict>
 <key>_SPCommandLineArguments</key>
 <array>
 <string>/usr/sbin/system_profiler</string>
 <string>-nospawn</string>
 <string>-xml</string>
 <string>SPCameraDataType</string>
 <string>-detailLevel</string>
 <string>full</string>
 </array>
 <key>_SPCompletionInterval</key>
 <real>1.1997909545898438</real>
 <key>_SPResponseTime</key>
 <real>1.2810090780258179</real>
 <key>_dataType</key>
 <string>SPCameraDataType</string>
 <key>_detailLevel</key>
 <integer>-1</integer>
 <key>_items</key>
 <array>
 <dict>
 <key>_name</key>
 <string>USB Camera</string>
 <key>spcamera_model-id</key>
 <string>UVC Camera VendorID_3141 ProductID_25453</string>
 <key>spcamera_unique-id</key>
 <string>0x11000000c45636d</string>
 </dict>
 <dict>
 <key>_name</key>
 <string>FaceTime HD Camera</string>
 <key>spcamera_model-id</key>
 <string>FaceTime HD Camera</string>
 <key>spcamera_unique-id</key>
 <string>EAB7A68F-EC2B-4487-AADF-D8A91C1CB782</string>
 </dict>
 </array>
 <key>_parentDataType</key>
 <string>SPHardwareDataType</string>
 <key>_properties</key>
 <dict>
 <key>_name</key>
 <dict>
 <key>_isColumn</key>
 <string>NO</string>
 <key>_isOutlineColumn</key>
 <string>NO</string>
 <key>_order</key>
 <string>0</string>
 </dict>
 <key>spcamera</key>
 <dict>
 <key>_order</key>
 <string>10</string>
 </dict>
 <key>spcamera_model-id</key>
 <dict>
 <key>_order</key>
 <string>30</string>
 </dict>
 <key>spcamera_unique-id</key>
 <dict>
 <key>_order</key>
 <string>40</string>
 </dict>
 <key>volumes</key>
 <dict>
 <key>_detailLevel</key>
 <string>0</string>
 </dict>
 </dict>
 <key>_timeStamp</key>
 <date>2024-11-29T21:57:28Z</date>
 <key>_versionInfo</key>
 <dict>
 <key>com.apple.SystemProfiler.SPCameraReporter</key>
 <string>1.2.0</string>
 </dict>
 </dict>
</array>
</plist>


As you can see, I have a couple of video input devices :
USB Camera&FaceTime HD Camera

The problem is that when I use
cap = cv2.VideoCapture(0), it uses theFaceTime HD Camera.

Can we match the camera index in OpenCV with the camera names ?


P.S. I tried
ffmpeg, but it returned similar result :



ioreg | grep -i camresult :



-
releases doc formating
13 février 2013, par jonrohanm docs/releases.md
releases doc formating
Syndiquer tout le site
