
Recherche avancée
Médias (1)
-
The Great Big Beautiful Tomorrow
28 octobre 2011, par
Mis à jour : Octobre 2011
Langue : English
Type : Texte
Autres articles (49)
-
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 (...)
-
Creating farms of unique websites
13 avril 2011, parMediaSPIP platforms can be installed as a farm, with a single "core" hosted on a dedicated server and used by multiple websites.
This allows (among other things) : implementation costs to be shared between several different projects / individuals rapid deployment of multiple unique sites creation of groups of like-minded sites, making it possible to browse media in a more controlled and selective environment than the major "open" (...) -
Keeping control of your media in your hands
13 avril 2011, parThe 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 (7855)
-
Opencv linking to current version of ffmpeg only, Updating ffmpeg version breaks opencv library
5 octobre 2019, par AmitI had manually compiled opencv ver3.2 library on mac system, which had been working fine till now. Recently it seems that i had updated the version for ffmpeg, which is managed by brew package manager, leading to breakage of opencv library looking for libavcodec.57.dylib.
Upon looking into library path, i found that libavcodec.dylib is symlinked to libavcodec.58.dylib, which is the most probable cause to above problem.
Now i have two options,
Recompile opencv to link against the latest version of libavcodec
Revert the version of libavcodec to 57
I am looking for a solution in which opencv works independently of the version of libavcodec and should dynamically link with current installed version of library. I should only be recompiling opencv when it is essentially required, like change in API of libavcodec.
-
Updating ffmpeg breaks opencv library
7 octobre 2019, par AmitI had manually compiled opencv ver3.2 library on mac system, which had been working fine till now. Recently it seems that i had updated the version for ffmpeg, which is managed by brew package manager, leading to breakage of opencv library looking for libavcodec.57.dylib.
Upon looking into library path, i found that libavcodec.dylib is symlinked to libavcodec.58.dylib, which is the most probable cause to above problem.
Now i have two options,
Recompile opencv to link against the latest version of libavcodec
Revert the version of libavcodec to 57
I am looking for a solution in which opencv works independently of the version of libavcodec and should dynamically link with current installed version of library. I should only be recompiling opencv when it is essentially required, like change in API of libavcodec.
-
How to setup FFMPEGInterop to Use DRM playready
1er novembre 2019, par marinamovies32I am using FFMPEGInterop class to play UWP video. I need to play it with playready setup but am running into issues.
I can play playready with just mediaplayerelement and creating the protection manager, but when I create a FFMPEGMSS to stream it, than it fails. Says value is out of range when adding the protection manager to the MediaStreamSource.
var StreamSource = FFmpegMSS.GetMediaStreamSource();
var protectionManager = new Windows.Media.Protection.MediaProtectionManager();
Windows.Foundation.Collections.PropertySet cpSystems = new Windows.Foundation.Collections.PropertySet();
cpSystems.Add("{F4637010-03C3-42CD-B932-B48ADF3A6A54}", "Microsoft.Media.PlayReadyClient.PlayReadyWinRTTrustedInput"); //Playready
protectionManager.Properties.Add("Windows.Media.Protection.MediaProtectionSystemIdMapping", cpSystems);
protectionManager.Properties.Add("Windows.Media.Protection.MediaProtectionSystemId", "{F4637010-03C3-42CD-B932-B48ADF3A6A54}");
protectionManager.ServiceRequested += ProtectionManager_ServiceRequested;
protectionManager.ComponentLoadFailed += ProtectionManager_ComponentLoadFailed;
protectionManager.Properties.Add("Windows.Media.Protection.MediaProtectionContainerGuid", "{9A04F079-9840-4286-AB92-E65BE0885F95}");
var supportsHardwareDrm = PlayReadyStatics.CheckSupportedHardware(PlayReadyHardwareDRMFeatures.HardwareDRM);
if (!supportsHardwareDrm)
{
protectionManager.Properties["Windows.Media.Protection.UseSoftwareProtectionLayer"] = true;
}
Windows.Storage.ApplicationDataContainer localSettings = Windows.Storage.ApplicationData.Current.LocalSettings;
Header.Text = supportsHardwareDrm ? "SUPPORTED" : "NOT SUPPRTED";
StreamSource.MediaProtectionManager = protectionManager;
mediaElement.Source = MediaSource.CreateFromMediaStreamSource(StreamSource);I should be able to play playready DRM with a setup protection manager to start but down get any info on it so confused on the next step for it.