Recherche avancée

Médias (1)

Mot : - Tags -/ipad

Autres articles (52)

  • Mise à jour de la version 0.1 vers 0.2

    24 juin 2013, par

    Explications des différents changements notables lors du passage de la version 0.1 de MediaSPIP à la version 0.3. Quelles sont les nouveautés
    Au niveau des dépendances logicielles Utilisation des dernières versions de FFMpeg (>= v1.2.1) ; Installation des dépendances pour Smush ; Installation de MediaInfo et FFprobe pour la récupération des métadonnées ; On n’utilise plus ffmpeg2theora ; On n’installe plus flvtool2 au profit de flvtool++ ; On n’installe plus ffmpeg-php qui n’est plus maintenu au (...)

  • Personnaliser en ajoutant son logo, sa bannière ou son image de fond

    5 septembre 2013, par

    Certains thèmes prennent en compte trois éléments de personnalisation : l’ajout d’un logo ; l’ajout d’une bannière l’ajout d’une image de fond ;

  • Ecrire une actualité

    21 juin 2013, par

    Présentez les changements dans votre MédiaSPIP ou les actualités de vos projets sur votre MédiaSPIP grâce à la rubrique actualités.
    Dans le thème par défaut spipeo de MédiaSPIP, les actualités sont affichées en bas de la page principale sous les éditoriaux.
    Vous pouvez personnaliser le formulaire de création d’une actualité.
    Formulaire de création d’une actualité Dans le cas d’un document de type actualité, les champs proposés par défaut sont : Date de publication ( personnaliser la date de publication ) (...)

Sur d’autres sites (8824)

  • Working directory in Dockerfile is not what is expected to be

    31 mai 2022, par user1765862

    I have following Dockerfile

    


    FROM public.ecr.aws/lambda/dotnet:6 AS base

FROM mcr.microsoft.com/dotnet/sdk:6.0-bullseye-slim as build
WORKDIR /src
COPY ["AWSServerless.csproj", "AWSServerless/"]
RUN dotnet restore "AWSServerless/AWSServerless.csproj"

WORKDIR "/src/AWSServerless"
COPY . .
RUN dotnet build "AWSServerless.csproj" --configuration Release --output /app/build

FROM build AS publish

RUN apt-get update && apt-get install -y apt-utils libgdiplus libc6-dev

RUN apt-get install -y ffmpeg

RUN dotnet publish "AWSServerless.csproj" \
            --configuration Release \ 
            --runtime linux-x64 \
            --self-contained false \ 
            --output /app/publish \
            -p:PublishReadyToRun=true  

FROM base AS final
WORKDIR /var/task

CMD ["AWSServerless::AWSServerless.LambdaEntryPoint::FunctionHandlerAsync"]
COPY --from=publish /app/publish .


    


    As per ffmpeg docs In order to use ffmpeg I need to set its binary folder
for example with

    


    {
  "BinaryFolder": "/var/task",
  "TemporaryFilesFolder": "/tmp"
}


    


    Error

    


    


    An error occurred trying to start process './ffmpeg' with working
directory '/var/task'. No such file or directory

    


    


    What is the working directory here ?

    


    Update :
Actual error is being thrown when I try to execute following command (FFMpegCore package) from my api controller

    


    public class MyController : ControllerBase&#xA;{&#xA;    public async Task<string> Get()&#xA;    {    &#xA;         await FFMpegArguments&#xA;               .FromPipeInput(new StreamPipeSource(myfile))&#xA;               .OutputToPipe(new StreamPipeSink(outputStream), options => options&#xA;                  .WithVideoCodec("vp9")&#xA;                  .ForceFormat("webm"))&#xA;                  .ProcessAsynchronously();&#xA;         ...&#xA;    }    &#xA;}&#xA;</string>

    &#xA;

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