Recherche avancée

Médias (2)

Mot : - Tags -/plugins

Autres articles (30)

  • Keeping control of your media in your hands

    13 avril 2011, par

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

  • Submit bugs and patches

    13 avril 2011

    Unfortunately a software is never perfect.
    If you think you have found a bug, report it using our ticket system. Please to help us to fix it by providing the following information : the browser you are using, including the exact version as precise an explanation as possible of the problem if possible, the steps taken resulting in the problem a link to the site / page in question
    If you think you have solved the bug, fill in a ticket and attach to it a corrective patch.
    You may also (...)

  • Creating farms of unique websites

    13 avril 2011, par

    MediaSPIP 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" (...)

Sur d’autres sites (5334)

  • FFMpeg on docker

    31 mai 2022, par user1765862

    I'm trying to run FFMpegCore library in the docker
Here is my 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

#fix for using System.Drawing.Common on docker
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 .


    


    When I try to use any of FFMpegCore commands I'm getting following error in the log

    


    


    System.ComponentModel.Win32Exception (2) : An error occurred trying to
start process 'ffmpeg' with working directory '/var/task'. No such
file or directory

    


    


  • lavu/hwcontext_qsv : make qsv hwdevice works with oneVPL

    4 janvier 2021, par Haihao Xiang
    lavu/hwcontext_qsv : make qsv hwdevice works with oneVPL

    In oneVPL, MFXLoad() and MFXCreateSession() are required to create a
    
workable mfx session[1]
    

    Add config filters for D3D9/D3D11 session (galinart)
    

    The default device is changed to d3d11va for oneVPL when both d3d11va
    
and dxva2 are enabled on Microsoft Windows
    

    This is in preparation for oneVPL support
    

    [1] https://spec.oneapi.io/versions/latest/elements/oneVPL/source/programming_guide/VPL_prg_session.html#onevpl-dispatcher
    

    Co-authored-by : galinart <artem.galin@intel.com>
    
Signed-off-by : galinart <artem.galin@intel.com>
    
Signed-off-by : Haihao Xiang <haihao.xiang@intel.com>
    • [DH] libavutil/hwcontext_qsv.c

  • input : Add a workaround for swscale overread bugs

    22 octobre 2017, par Henrik Gramner
    input : Add a workaround for swscale overread bugs

    swscale can read past the end of the input buffer, which may result in
    
crashes if such a read crosses a page boundary into an invalid page.
    

    Work around this by adding some padding space at the end of the buffer when
    
using memory-mapped input frames. This may sometimes require copying the
    
last frame into a new buffer on Windows since the Microsoft memory-mapping
    
implementation has very limited capabilities compared to POSIX systems.
    • [DH] input/input.c
    • [DH] input/input.h

Navigation