Recherche avancée

Médias (91)

Autres articles (35)

  • Support de tous types de médias

    10 avril 2011

    Contrairement à beaucoup de logiciels et autres plate-formes modernes de partage de documents, MediaSPIP a l’ambition de gérer un maximum de formats de documents différents qu’ils soient de type : images (png, gif, jpg, bmp et autres...) ; audio (MP3, Ogg, Wav et autres...) ; vidéo (Avi, MP4, Ogv, mpg, mov, wmv et autres...) ; contenu textuel, code ou autres (open office, microsoft office (tableur, présentation), web (html, css), LaTeX, Google Earth) (...)

  • Supporting all media types

    13 avril 2011, par

    Unlike most software and media-sharing platforms, MediaSPIP aims to manage as many different media types as possible. The following are just a few examples from an ever-expanding list of supported formats : images : png, gif, jpg, bmp and more audio : MP3, Ogg, Wav and more video : AVI, MP4, OGV, mpg, mov, wmv and more text, code and other data : OpenOffice, Microsoft Office (Word, PowerPoint, Excel), web (html, CSS), LaTeX, Google Earth and (...)

  • Encoding and processing into web-friendly formats

    13 avril 2011, par

    MediaSPIP automatically converts uploaded files to internet-compatible formats.
    Video files are encoded in MP4, Ogv and WebM (supported by HTML5) and MP4 (supported by Flash).
    Audio files are encoded in MP3 and Ogg (supported by HTML5) and MP3 (supported by Flash).
    Where possible, text is analyzed in order to retrieve the data needed for search engine detection, and then exported as a series of image files.
    All uploaded files are stored online in their original format, so you can (...)

Sur d’autres sites (4553)

  • Package is installed inside docker but actual command provide exception

    1er juin 2022, par user1765862

    I'm trying to use ffmpeg core package inside .net 6 dockerized project. I install ffmpeg core inside Dockerfile, reference actual package FFMpegCore inside solution but when I try to apply any of the commands from the ffmpeg core lib I'm getting error

    


    


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

    


    


    Docker build is done with no error.

    


    Dockerfile

    


    FROM public.ecr.aws/lambda/dotnet:6 AS base
....
RUN apt-get install -y ffmpeg
....
FROM base AS final
WORKDIR /var/task
COPY --from=publish /app/publish .


    


    As per ffmpeg core docs in order to use ffmpeg I need to set its binary folder, so I add ffmpeg.config.json

    


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


    


    Actual error is being thrown when I try to execute following command

    


    


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

    


    


    This is the place where error gets triggered

    


     using FFMpegCore;&#xA; ...&#xA; 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;

    Update :&#xA;After changing BinaryFolder location to /usr/bin I'm getting following error

    &#xA;

    An error occurred trying to start process &#x27;/usr/bin/ffmpeg&#x27; with working directory &#x27;/var/task&#x27;. No such file or directory&#xA;

    &#xA;

    Update #2&#xA;This is my complete Dockerfile

    &#xA;

    FROM public.ecr.aws/lambda/dotnet:6 AS base&#xA;&#xA;FROM mcr.microsoft.com/dotnet/sdk:6.0-bullseye-slim as build&#xA;WORKDIR /src&#xA;COPY ["AWSServerless.csproj", "AWSServerless/"]&#xA;RUN dotnet restore "AWSServerless/AWSServerless.csproj"&#xA;&#xA;WORKDIR "/src/AWSServerless"&#xA;COPY . .&#xA;RUN dotnet build "AWSServerless.csproj" --configuration Release --output /app/build&#xA;&#xA;FROM build AS publish   &#xA;&#xA;RUN apt-get update \&#xA;    &amp;&amp; apt-get install -y apt-utils libgdiplus libc6-dev \&#xA;    &amp;&amp; apt-get install -y ffmpeg&#xA;&#xA;RUN dotnet publish "AWSServerless.csproj" \&#xA;            --configuration Release \ &#xA;            --runtime linux-x64 \&#xA;            --self-contained false \ &#xA;            --output /app/publish \&#xA;            -p:PublishReadyToRun=true  &#xA;&#xA;FROM base AS final&#xA;WORKDIR /var/task&#xA;&#xA;CMD ["AWSServerless::AWSServerless.LambdaEntryPoint::FunctionHandlerAsync"]&#xA;COPY --from=publish /app/publish .&#xA;

    &#xA;

  • avformat/webmdashenc : Don't pass NULL to memcmp

    23 septembre 2019, par Andreas Rheinhardt
    avformat/webmdashenc : Don't pass NULL to memcmp
    

    Affects the FATE-tests webm-dash-manifest-unaligned-video-streams,
    webm-dash-manifest and webm-dash-manifest-representations.

    Signed-off-by : Andreas Rheinhardt <andreas.rheinhardt@gmail.com>

    • [DH] libavformat/webmdashenc.c
  • Nginx VOD Transcoding

    21 décembre 2015, par nicb19

    I’m trying to setup MPEG-DASH video on demand streaming using nginx. I came across the nginx vod module which works great with dash.js but am wondering if anyone has managed to get real-time transcoding working.

    I’ve currently got it setup to play H264 MP4 local files, producing a MPD manifest for a single MP4. I know I can transcode multiple versions of the video and store them on the server, creating a multi URL manifest, but I only have limited space on the server so am not able to do this. Instead, I’m trying to find a way to transcode in real-time to allow more adaptive bitrate streaming like is possible with the nginx rtmp module and ffmpeg (however with MPEG-DASH instead of RTMP since I don’t want to use flash).

    Does anyone know of a way to do this ? Thanks in advanced.