
Recherche avancée
Médias (1)
-
Revolution of Open-source and film making towards open film making
6 octobre 2011, par
Mis à jour : Juillet 2013
Langue : English
Type : Texte
Autres articles (83)
-
ANNEXE : Les extensions, plugins SPIP des canaux
11 février 2010, parUn plugin est un ajout fonctionnel au noyau principal de SPIP. MediaSPIP consiste en un choix délibéré de plugins existant ou pas auparavant dans la communauté SPIP, qui ont pour certains nécessité soit leur création de A à Z, soit des ajouts de fonctionnalités.
Les extensions que MediaSPIP nécessite pour fonctionner
Depuis la version 2.1.0, SPIP permet d’ajouter des plugins dans le répertoire extensions/.
Les "extensions" ne sont ni plus ni moins que des plugins dont la particularité est qu’ils se (...) -
Supporting all media types
13 avril 2011, parUnlike 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 (...)
-
Les statuts des instances de mutualisation
13 mars 2010, parPour des raisons de compatibilité générale du plugin de gestion de mutualisations avec les fonctions originales de SPIP, les statuts des instances sont les mêmes que pour tout autre objets (articles...), seuls leurs noms dans l’interface change quelque peu.
Les différents statuts possibles sont : prepa (demandé) qui correspond à une instance demandée par un utilisateur. Si le site a déjà été créé par le passé, il est passé en mode désactivé. publie (validé) qui correspond à une instance validée par un (...)
Sur d’autres sites (7356)
-
NVidia driver libraries in nvidia/cuda image
16 février 2018, par Islam SabyrgaliyevI want to run ffmpeg with cuvid hw-accelerated decoding in the container based on official
nvidia/cuda
image. Ffmpeg is not able to find libnvcuvid.so, although there are all required cuda libs.
The output ofldconfig -p | grep libnv
from the container :libnvrtc.so (libc6,x86-64) => /usr/local/cuda-9.0/targets/x86_64-linux/lib/libnvrtc.so
libnvrtc-builtins.so (libc6,x86-64) => /usr/local/cuda-9.0/targets/x86_64-linux/lib/libnvrtc-builtins.so
libnvidia-ptxjitcompiler.so.1 (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libnvidia-ptxjitcompiler.so.1
libnvidia-opencl.so.1 (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libnvidia-opencl.so.1
libnvidia-ml.so.1 (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libnvidia-ml.so.1
libnvidia-fatbinaryloader.so.390.12 (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libnvidia-fatbinaryloader.so.390.12
libnvidia-compiler.so.390.12 (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libnvidia-compiler.so.390.12
libnvidia-cfg.so.1 (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libnvidia-cfg.so.1
libnvgraph.so (libc6,x86-64) => /usr/local/cuda-9.0/targets/x86_64-linux/lib/libnvgraph.so
libnvblas.so (libc6,x86-64) => /usr/local/cuda-9.0/targets/x86_64-linux/lib/libnvblas.so
libnvToolsExt.so (libc6,x86-64) => /usr/local/cuda-9.0/targets/x86_64-linux/lib/libnvToolsExt.soShould I just copy
libnvcuvid.so
from the host ? Wouldn’t it break if underlying driver version changes ? -
How to set a timeout for FFmpegFrameGrabber grab() method in JavaCV
18 janvier 2019, par Null PointerI’m trying to create a player in Java using JavaCV. But .grab() method takes different amounts of time for each grab. How can I discard a grab() operation when it takes too much time ?
In detail : I’m working on a project to display rtsp streams. To do this, I use JavaCV and its FFmpegFrameGrabber class. Inside a loop I call its .grab() method to grab frames and then I print them on a panel.
(Not knowing the reason) grab() method takes much more time in some calls. For example :- grab : 15ms,
- grab : 13ms,
- grab : 14ms,
- grab : 95ms,
- grab : 12ms, ...
I wish not to wait for a grab, in case it is taking too long like in this fourth call.
(Sorry for not providing a working code, it’s all over different huge classes)
I use the following grabber options (selected by some other colleague) :
grabber.setImageHeight(480);
grabber.setImageWidth(640);
grabber.setOption("reconnect", "1");
grabber.setOption("reconnect_at_eof", "1");
grabber.setOption("reconnect_streamed", "1");
grabber.setOption("reconnect_delay_max", "2");
grabber.setOption("preset", "veryfast");
grabber.setOption("probesize", "192");
grabber.setOption("tune", "zerolatency");
grabber.setFrameRate(30.0);
grabber.setOption("buffer_size", "" + this.bufferSize);
grabber.setOption("max_delay", "500000");
grabber.setOption("stimeout", String.valueOf(6000000));
grabber.setOption("loglevel", "quiet");
grabber.start();Also I tried to do the grab() in another thread and not wait for that to end in case it takes too long. But this time I get an EXCEPTION_ACCESS_VIOLATION when I call .grab() method before the previous one did not end yet. "Calling .release() ; and .restart() ; methods before trying to grab again" also did not solve the access violation.
Is there a setting option to cancel unordinarily long grabs ? (Or wouldn’t it work without these frames (because of a reason that I don’t know))
Thanks
-
Working directory in Dockerfile is not what is expected to be
31 mai 2022, par user1765862I 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
{
 public async Task<string> Get()
 { 
 await FFMpegArguments
 .FromPipeInput(new StreamPipeSource(myfile))
 .OutputToPipe(new StreamPipeSink(outputStream), options => options
 .WithVideoCodec("vp9")
 .ForceFormat("webm"))
 .ProcessAsynchronously();
 ...
 } 
}
</string>