
Recherche avancée
Autres articles (67)
-
Use, discuss, criticize
13 avril 2011, parTalk to people directly involved in MediaSPIP’s development, or to people around you who could use MediaSPIP to share, enhance or develop their creative projects.
The bigger the community, the more MediaSPIP’s potential will be explored and the faster the software will evolve.
A discussion list is available for all exchanges between users. -
MediaSPIP Player : les contrôles
26 mai 2010, parLes contrôles à la souris du lecteur
En plus des actions au click sur les boutons visibles de l’interface du lecteur, il est également possible d’effectuer d’autres actions grâce à la souris : Click : en cliquant sur la vidéo ou sur le logo du son, celui ci se mettra en lecture ou en pause en fonction de son état actuel ; Molette (roulement) : en plaçant la souris sur l’espace utilisé par le média (hover), la molette de la souris n’exerce plus l’effet habituel de scroll de la page, mais diminue ou (...) -
MediaSPIP version 0.1 Beta
16 avril 2011, parMediaSPIP 0.1 beta est la première version de MediaSPIP décrétée comme "utilisable".
Le fichier zip ici présent contient uniquement les sources de MediaSPIP en version standalone.
Pour avoir une installation fonctionnelle, il est nécessaire d’installer manuellement l’ensemble des dépendances logicielles sur le serveur.
Si vous souhaitez utiliser cette archive pour une installation en mode ferme, il vous faudra également procéder à d’autres modifications (...)
Sur d’autres sites (10117)
-
Problems using Cuda for video transcoding [closed]
19 août 2022, par Jay AdlardI just bought a new pc as my faithful old windows 7 i7 laptop died. Now the laptop had both intel and nvidea gtx660m chips. When I transcoded video with handbrake the intel graphics managed 8fps when I changed over to the nvidia it managed 80fps and the graphics card got nice and hot so was obviously working.


The new machine i bought is a i9 with an nvidea gtx780 running windows 10. When I tried to transcode some video hoping for it to use the cpu and Gpu but no joy,the card stays cool power usage is only a handful of watts higher than it running something simple.I had been using handbrake but I read it doesn’t support Cuda so why the laptop speeded up I don’t know. A friend of mine that is into ffmpeg came round found that ffmpeg reports no Cuda yet the card works fine in every other respect. Unlike the rest of the machine the graphics card wasn’t new but it looked like new…


One thing to note I am not talking about nvenc as the quality is rather poor, no point in capturing uncompressed files cleaning them up and not using an encoder that will do 2 pass and an exhaustive search.
Can anyone recommend a reasonably priced encoder that will use the Cuda cores ?


Has anyone got any idea what the problem is ?


-
Demo of WebM Running on TI OMAP 4 Processor
15 octobre 2010, par noreply@blogger.com (John Luther)Texas Instruments has made a video of HD-resolution (1080p) VP8 (WebM) video playing on their new TI OMAP™ 4 processor, in both Android and Ubuntu.
(If you have a WebM-enabled browser and are enrolled in the YouTube HTML5 beta the video will play in WebM HTML5, otherwise it will play in Flash Player.)
For more info about the OMAP 4 and the IVA 3 video accelerator that enables low-power HD playback of VP8 on the chip, see the TI web site.
-
FFMPEG cropping size is always wrong
19 avril 2020, par SamsyI need a bunch of video to be EXACTLY 1024x512 ( power of 2 video ), not a pixel less, not a pixel more..



I'm scaling them first to 1024 width



Then cropping them to 1024x512



Problem is..



result always ends up with 1 pixel more or 2 less pixels in width etc...



Source dimension : 1624 × 1080
Output dimension : 1022 × 512




Source dimension : 1264 × 720
Output dimension : 1025 × 512




rm -R ./output

mkdir output

cd input

for i in *.mp4;

 do name=`echo "$i" | cut -d'.' -f1`

 FILE="${name}"

 TMP="temp.mp4"

 INPUT="${FILE}.mp4"

 OUT_PUT="../output/${FILE}.mp4"

 JPEG_OUTPUT="../output/${FILE}.jpg"

 echo FILE

 echo INPUT

 ffmpeg -i $INPUT -filter:v scale=1024:-2 -c:a copy ${TMP}

 ffmpeg -i ${TMP} -filter:v "crop=1024:512:exact=1" -c:a copy ${OUT_PUT}

 # ffmpeg -loglevel panic -i $OUT_PUT -vframes 1 -f image2 $JPEG_OUTPUT

 rm ${TMP}

done