Recherche avancée

Médias (3)

Mot : - Tags -/spip

Autres articles (43)

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

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

  • Contribute to translation

    13 avril 2011

    You can help us to improve the language used in the software interface to make MediaSPIP more accessible and user-friendly. You can also translate the interface into any language that allows it to spread to new linguistic communities.
    To do this, we use the translation interface of SPIP where the all the language modules of MediaSPIP are available. Just subscribe to the mailing list and request further informantion on translation.
    MediaSPIP is currently available in French and English (...)

Sur d’autres sites (5698)

  • Revision 0e1e16db90 : Enable mmx loop filter routines The mmx routines work as expected for the loop

    12 juin 2013, par John Koleszar

    Changed Paths :
     Modify /vp9/common/vp9_rtcd_defs.sh



    Enable mmx loop filter routines

    The mmx routines work as expected for the loop filter, so enable them.

    Change-Id : I2bbd9b99a4445fcba17bb95002f1fb6e01fe8f85

  • Concatenated Video created with FFMPEG is longer than expected [closed]

    11 février 2024, par Snickbrack

    I am using this Video-List :

    


    file 'C:\Users\X\Documents\test\input.mp4'
inpoint 00:00:02.7650000
outpoint 00:00:04.7650000


    


    and the following Command :

    


    ffmpeg -y -safe 0 -f concat -i output.txt -map 0:v -map 0:a -c:a copy -c:v copy output.mp4


    


    which should result in a Video with 2 Seconds in Length. But if I do a check with ffprobe I get this :

    


    Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'output.mp4':
  Metadata:
    major_brand     : isom
    minor_version   : 512
    compatible_brands: isomiso2avc1mp41
    encoder         : Lavf60.16.100
  Duration: 00:00:04.85, start: 0.000000, bitrate: 394 kb/s
  Stream #0:0[0x1](und): Video: h264 (High) (avc1 / 0x31637661), yuv420p(tv, bt709, progressive), 1920x1080 [SAR 1:1 DAR 16:9], 382 kb/s, 30 fps, 30 tbr, 15360 tbn (default)
    Metadata:
      handler_name    : VideoHandler
      vendor_id       : [0][0][0][0]
  Stream #0:1[0x2](und): Audio: aac (LC) (mp4a / 0x6134706D), 48000 Hz, stereo, fltp, 2 kb/s (default)
    Metadata:
      handler_name    : SoundHandler
      vendor_id       : [0][0][0][0]


    


    Whats the cause of this ?

    


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

Navigation