Recherche avancée

Médias (0)

Mot : - Tags -/optimisation

Aucun média correspondant à vos critères n’est disponible sur le site.

Autres articles (44)

  • Participer à sa traduction

    10 avril 2011

    Vous pouvez nous aider à améliorer les locutions utilisées dans le logiciel ou à traduire celui-ci dans n’importe qu’elle nouvelle langue permettant sa diffusion à de nouvelles communautés linguistiques.
    Pour ce faire, on utilise l’interface de traduction de SPIP où l’ensemble des modules de langue de MediaSPIP sont à disposition. ll vous suffit de vous inscrire sur la liste de discussion des traducteurs pour demander plus d’informations.
    Actuellement MediaSPIP n’est disponible qu’en français et (...)

  • HTML5 audio and video support

    13 avril 2011, par

    MediaSPIP 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, par

    Le 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 (...)

Sur d’autres sites (8621)

  • 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