Recherche avancée

Médias (1)

Mot : - Tags -/Rennes

Autres articles (107)

  • Multilang : améliorer l’interface pour les blocs multilingues

    18 février 2011, par

    Multilang est un plugin supplémentaire qui n’est pas activé par défaut lors de l’initialisation de MediaSPIP.
    Après son activation, une préconfiguration est mise en place automatiquement par MediaSPIP init permettant à la nouvelle fonctionnalité d’être automatiquement opérationnelle. Il n’est donc pas obligatoire de passer par une étape de configuration pour cela.

  • MediaSPIP v0.2

    21 juin 2013, par

    MediaSPIP 0.2 est la première version de MediaSPIP stable.
    Sa date de sortie officielle est le 21 juin 2013 et est annoncée ici.
    Le fichier zip ici présent contient uniquement les sources de MediaSPIP en version standalone.
    Comme pour la version précédente, il est nécessaire d’installer manuellement l’ensemble des dépendances logicielles sur le serveur.
    Si vous souhaitez utiliser cette archive pour une installation en mode ferme, il vous faudra également procéder à d’autres modifications (...)

  • Other interesting software

    13 avril 2011, par

    We don’t claim to be the only ones doing what we do ... and especially not to assert claims to be the best either ... What we do, we just try to do it well and getting better ...
    The following list represents softwares that tend to be more or less as MediaSPIP or that MediaSPIP tries more or less to do the same, whatever ...
    We don’t know them, we didn’t try them, but you can take a peek.
    Videopress
    Website : http://videopress.com/
    License : GNU/GPL v2
    Source code : (...)

Sur d’autres sites (18642)

  • Support building C++ files with MSVC

    13 avril 2017, par Aaron Levinson
    Support building C++ files with MSVC

    Made appropriate changes to be able to successfully
    
build C++ files using a Visual C++ build on Windows.
    

    Based on an earlier patch by Kyle Schwarz.
    

    Comments :
    

    — compat/w32pthreads.h : Made appropriate changes to w32pthreads.h to
    
   get it to build when it is being included in a C++ file and built
    
   with Visual C++.  This is mostly a copy of Kyle Schwarz's patch as
    
   described above.
    

    — configure :
    
a) Now calling set_ccvars CXX to cause the various CXX_ variables to
    
   be setup properly.  For example, with MSVC (Microsoft Visual C++),
    
   this causes CXX_O to be set to -Fo$@ instead of using the default
    
   value.  The default value does not work with Visual C++.  This
    
   change will also have the impact of correcting CXX_O (and possibly
    
   CXX_C) for other compilers, although this is really only relevant
    
   for the Intel compiler, in addition to MSVC.
    
b) Now using cl for the C++ compiler for the MSVC toolchain.  This is
    
   currently only relevant for building the
    
   Blackmagic/Decklink-related files under avdevice.
    

    Signed-off-by : Hendrik Leppkes <h.leppkes@gmail.com>
    • [DH] compat/w32pthreads.h
    • [DH] configure

  • How to setup FFMPEGInterop to Use DRM playready

    1er novembre 2019, par marinamovies32

    I 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.

  • arm : Create proper .rdata sections for COFF

    11 janvier 2019, par Martin Storsjö
    arm : Create proper .rdata sections for COFF

    As .rodata isn’t one of the default created sections for COFF, it was
    
created as a read-write data section. By using the default .rdata
    
section name for COFF, it automatically becomes a read-only data section.
    
The existing ".section .rodata" works as intended for ELF though.
    

    This is based on an original patch and diagnose by Tom Tan
    
<Tom.Tan@microsoft.com>.
    

    Signed-off-by : Martin Storsjö <martin@martin.st>
    • [DBH] libavutil/aarch64/asm.S
    • [DBH] libavutil/arm/asm.S

Navigation