Advanced search

Medias (1)

Tag: - Tags -/publicité

Other articles (76)

  • Les tâches Cron régulières de la ferme

    1 December 2010, by

    La gestion de la ferme passe par l’exécution à intervalle régulier de plusieurs tâches répétitives dites Cron.
    Le super Cron (gestion_mutu_super_cron)
    Cette tâche, planifiée chaque minute, a pour simple effet d’appeler le Cron de l’ensemble des instances de la mutualisation régulièrement. Couplée avec un Cron système sur le site central de la mutualisation, cela permet de simplement générer des visites régulières sur les différents sites et éviter que les tâches des sites peu visités soient trop (...)

  • Contribute to translation

    13 April 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 (...)

  • MediaSPIP 0.1 Beta version

    25 April 2011, by

    MediaSPIP 0.1 beta is the first version of MediaSPIP proclaimed as "usable".
    The zip file provided here only contains the sources of MediaSPIP in its standalone version.
    To get a working installation, you must manually install all-software dependencies on the server.
    If you want to use this archive for an installation in "farm mode", you will also need to proceed to other manual (...)

On other websites (10462)

  • FFMpeg high CPU Utilization

    19 November 2017, by David Ko

    I am trying a trancoding system based on ffmpeg and Quadro P4000 gpu using h264_nvenc. Bud I have also a very high cpu usage while I start a transcoding. on 4 sd streams I have 80+ % cpu usage on 4core I5 with 3,5 GHz. GPU usage based on nvidia-smi is around 3%. What is wrong?
    The system is running on Ubuntu 16.0.3.

    I tried upgrade to newest video driver, also tried use other ffmpeg based solutions with the same result.

    Any idea?
    Thank you
    Dave

  • Appium screen recording doesn't work on simulator

    31 August 2022, by Oks

    I'm running automation tests on simulator and trying to record screen but it crashes on line driver.start_recording_screen()
I'm using Python for testing and Flutter for client side.

    


    self.utils.driver.switch_to_native_context()
driver.start_recording_screen()


    


    Appium logs:

    


    [ffmpeg] ffmpeg version 5.1 Copyright (c) 2000-2022 the FFmpeg developers
[ffmpeg]   built with Apple clang version 13.1.6 (clang-1316.0.21.2.5)
[ffmpeg]   configuration: --prefix=/opt/homebrew/Cellar/ffmpeg/5.1 --enable-shared --enable-pthreads --enable-version3 --cc=clang --host-cflags= --host-ldflags= --enable-ffplay --enable-gnutls --enable-gpl --enable-libaom --enable-libbluray --enable-libdav1d --enable-libmp3lame --enable-libopus --enable-librav1e --enable-librist --enable-librubberband --enable-libsnappy --enable-libsrt --enable-libtesseract --enable-libtheora --enable-libvidstab --enable-libvmaf --enable-libvorbis --enable-libvpx --enable-libwebp --enable-libx264 --enable-libx265 --enable-libxml2 --enable-libxvid --enable-lzma --enable-libfontconfig --enable-libfreetype --enable-frei0r --enable-libass --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg --enable-libspeex --enable-libsoxr --enable-libzmq --enable-libzimg --disable-libjack --disable-indev=jack --enable-videotoolbox --enable-neon
[ffmpeg] 
[ffmpeg]   libavutil      57. 28.100 / 57. 28.100
[ffmpeg]   libavcodec     59. 37.100 / 59. 37.100
[ffmpeg]   libavformat    59. 27.100 / 59. 27.100
[ffmpeg]   libavdevice    59.  7.100 / 59.  7.100
[ffmpeg]   libavfilter     8. 44.100 /  8. 44.100
[ffmpeg]   libswscale      6.  7.100 /  6.  7.100
[ffmpeg]   libswresample   4.  7.100 /  4.  7.100
[ffmpeg] 
[ffmpeg]   libpostproc    56.  6.100 / 56.  6.100
[ffmpeg] 
[ffmpeg] [mjpeg @ 0x148605ab0] No JPEG data found in image
[ffmpeg] 
[ffmpeg] [mjpeg @ 0x14b104080] Could not find codec parameters for stream 0 (Video: mjpeg, none(bt470bg/unknown/unknown)): unspecified size
[ffmpeg] Consider increasing the value for the 'analyzeduration' (0) and 'probesize' (5000000) options
[ffmpeg] Input #0, mjpeg, from '********':
[ffmpeg]   Duration: N/A, bitrate: N/A
[ffmpeg]   Stream #0:0: Video: mjpeg, none(bt470bg/unknown/unknown), 25 tbr, 1200k tbn
[ffmpeg] 
[ffmpeg] Stream mapping:
[ffmpeg]   Stream #0:0 -> #0:0 (mjpeg (native) -> mjpeg (native))
[ffmpeg] Press [q] to stop, [?] for help
[ffmpeg] [mjpeg @ 0x14b004620] No JPEG data found in image
[ffmpeg] Error while decoding stream #0:0: Invalid data found when processing input
[ffmpeg] Cannot determine format of input stream 0:0 after EOF
[ffmpeg] Error marking filters as finished
[ffmpeg] Conversion failed!
[ffmpeg] 
[XCUITest] Screen capture process did not start within 5000ms. Continuing anyway



    


    Anyone knows how to fix it ?
Thanks!

    


  • Manually feeding x264 with my own motion data?

    6 September 2011, by ldoogy

    I am trying to encode a stream using x264 (by feeding individual images), but what's unusual is that I already have some motion information for my frames. I know exactly which areas have been modified in each frame, and I know where motion has occurred in the frame.

    Is there a way to feed x264 my own motion information? I'd like to give it motion vectors for given areas in the frame, and somehow tell it that certain areas in the frame are guaranteed to not have had any motion in them.

    I think this might significantly improve the performance of the encoding (because I'm allowing the codec to completely skip the motion estimation phase), and should also somewhat increase quality in cases where the encoder's motion estimation algos might have missed the motion that actually occurred.

    Do I need to modify the encoder in order to do this, or is this supported in the existing API?