Recherche avancée

Médias (1)

Mot : - Tags -/vidéo

Autres articles (80)

  • Websites made ​​with MediaSPIP

    2 mai 2011, par

    This page lists some websites based on MediaSPIP.

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

  • (Dés)Activation de fonctionnalités (plugins)

    18 février 2011, par

    Pour gérer l’ajout et la suppression de fonctionnalités supplémentaires (ou plugins), MediaSPIP utilise à partir de la version 0.2 SVP.
    SVP permet l’activation facile de plugins depuis l’espace de configuration de MediaSPIP.
    Pour y accéder, il suffit de se rendre dans l’espace de configuration puis de se rendre sur la page "Gestion des plugins".
    MediaSPIP est fourni par défaut avec l’ensemble des plugins dits "compatibles", ils ont été testés et intégrés afin de fonctionner parfaitement avec chaque (...)

Sur d’autres sites (8730)

  • HTML 5 currentTime accuracy

    1er septembre 2015, par Daniel

    I’m working on a project where we are using the value from the video element’s currentTime property to perform processing on the server backend using ffmpeg. I’ve come across an issue where the video element seems to report a time code that is slightly different from the time code ffmpeg needs to access the correct point in the video.

    So for instance in Firefox if the currentTime property reports that the current video time is 26.83 I might find that the frame I really want ended at 26.72 and so if I use the time to extract a frame using ffmpeg on the server I get the next frame instead of the current frame.

    The amount of offset seems to be slightly different in different parts of the video and in different videos. But the offset is usually close to one tenth of a second in Firefox. In chrome the currentTime actually seems to be ahead or the correct currentTime by about 5 hundredths of a second. It’s more difficult to figure out the offset in IE because the place where the frame shifts seems to change as I enter different time codes to look for the exact time code where the frame changes.

    I’m pretty sure the time as used by ffmpeg is the correct time. It seems to agree more closely with other video editing software such as adobe premier.

    Any ideas on what could be causing this behavior ?

    JS to get currentTime :

    AVideo.prototype.getCurrentTime = function()
    
{
    
   return this.videoElement[0].currentTime;
    
};

    Resulting ffmpeg command :

    ffmpeg -y -i '/tmp/myVideo.mov' -vframes 1 -ss 2.4871 -f image2   -y '/tmp/myFrame.jpg' 2>&1

  • ffmpeg.a : No such file or directory while running ccViewer iOS Swift [closed]

    22 janvier 2023, par Sarwat

    I am running a build which is available in in GitHub (https://github.com/lithium0003/ccViewer/tree/v1.4.3) to connect direct storages through RCLONE (Google Drive, OneDrive etc.)

    


    I am following steps to compile which provided GitHub ccViewer readme
how to compile :

    


    if you did not set up, run these commands.

    


    sudo xcode-select --switch /Applications/Xcode.app/Contents/Developer/
brew install nasm
brew install yasm
prepare depencency

./chromecast.sh
cd work
./clone.sh
./build.sh
open with Xcode and compile

open workspace "ccViewer.xcworkspace"
select scheme "CryptCloudViewer" and build


    


    but I am getting ffmpeg.a not found. Please check attached images of Xcode and Command prompt.

    


    error: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/libtool: can't open file: lib/*.a (No such file or directory)
error: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/libtool: can't open file: lib/*.a (No such file or directory)
error: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/libtool: can't open file: lib/*.a (No such file or directory)
cp: ../output/ios/include/*: No such file or directory
cp: ../output/ios/ffmpeg.a: No such file or directory
cp: ../output/simulator/include/*: No such file or directory
cp: ../output/simulator/ffmpeg.a: No such file or directory
cp: ../output/macos/include/*: No such file or directory
cp: ../output/macos/ffmpeg.a: No such file or directory


    


    enter image description here

    


  • Merge commit ’8e673efc6f5b7a095557664660305148f2788d30’

    19 mai 2013, par Michael Niedermayer
    Merge commit ’8e673efc6f5b7a095557664660305148f2788d30’

    * commit ’8e673efc6f5b7a095557664660305148f2788d30’ :
    
  prores : update FATE test to account for alpha plane present in the test sample
    
  configure : Add basic valgrind-massif support
    

    Conflicts :
    
	tests/fate/prores.mak
    
	tests/ref/fate/prores-alpha
    

    Merged-by : Michael Niedermayer <michaelni@gmx.at>
    • [DH] configure
    • [DH] doc/developer.texi
    • [DH] tests/fate/prores.mak
    • [DH] tests/ref/fate/prores-alpha

Navigation