Recherche avancée

Médias (1)

Mot : - Tags -/ogg

Autres articles (65)

  • Mise à jour de la version 0.1 vers 0.2

    24 juin 2013, par

    Explications des différents changements notables lors du passage de la version 0.1 de MediaSPIP à la version 0.3. Quelles sont les nouveautés
    Au niveau des dépendances logicielles Utilisation des dernières versions de FFMpeg (>= v1.2.1) ; Installation des dépendances pour Smush ; Installation de MediaInfo et FFprobe pour la récupération des métadonnées ; On n’utilise plus ffmpeg2theora ; On n’installe plus flvtool2 au profit de flvtool++ ; On n’installe plus ffmpeg-php qui n’est plus maintenu au (...)

  • Personnaliser en ajoutant son logo, sa bannière ou son image de fond

    5 septembre 2013, par

    Certains thèmes prennent en compte trois éléments de personnalisation : l’ajout d’un logo ; l’ajout d’une bannière l’ajout d’une image de fond ;

  • Ecrire une actualité

    21 juin 2013, par

    Présentez les changements dans votre MédiaSPIP ou les actualités de vos projets sur votre MédiaSPIP grâce à la rubrique actualités.
    Dans le thème par défaut spipeo de MédiaSPIP, les actualités sont affichées en bas de la page principale sous les éditoriaux.
    Vous pouvez personnaliser le formulaire de création d’une actualité.
    Formulaire de création d’une actualité Dans le cas d’un document de type actualité, les champs proposés par défaut sont : Date de publication ( personnaliser la date de publication ) (...)

Sur d’autres sites (12652)

  • ffmpeg_kit_flutter_full_gpl,aken down from the official platform,ffmpeg-kit-full-gpl-6.0-ios-xcframework.zip [closed]

    20 avril, par marsdiscovery

    Important plugins for Flutter : ffmpeg_kit_flutter_full_gpl, It has been taken down from the official platform and is no longer under maintenance.
Error message during use :
-> Installing ffmpeg-kit-ios-full-gpl (6.0)

    


    


    Http download
$ /usr/bin/curl -f -L -o /var/folders/b8/thh68v8j4nqfhsjg7x4pv7140000gn/T/d20250420-81226-c8wqz2/file.zip https://github.com/arthenica/ffmpeg-kit/releases/download/v6.0/ffmpeg-kit-full-gpl-6.0-ios-xcframework.zip —create-dirs —netrc-optional —retry 2 -A 'CocoaPods/1.15.2 cocoapods-downloader/2.1'

    


    


    [!] Error installing ffmpeg-kit-ios-full-gpl
[!] /usr/bin/curl -f -L -o /var/folders/b8/thh68v8j4nqfhsjg7x4pv7140000gn/T/d20250420-81226-c8wqz2/file.zip https://github.com/arthenica/ffmpeg-kit/releases/download/v6.0/ffmpeg-kit-full-gpl-6.0-ios-xcframework.zip —create-dirs —netrc-optional —retry 2 -A 'CocoaPods/1.15.2 cocoapods-downloader/2.1'

    


    This file does indeed no longer exist.

    


    Our app heavily relies on ffmpeg_kit_flutter_full_gpl. What should we do now.

    


    Please help me, everyone

    


    I also tried pulling the source code locally, but it still reported the same error

    


  • lavd : deprecate the bktr device

    28 janvier 2024, par Anton Khirnov
    lavd : deprecate the bktr device
    

    It implements BSD-specific support for very old analog capture cards,
    which are highly unlikely to be useful today. After being added in 2005,
    there were never any commits to it beyond compilation fixes and generic
    maintenance. There have also been zero trac tickets for this device, and
    the only related web search result I found concludes that it does not
    work.

    The code also does some unacceptable things, like messing with signal
    handlers and storing its state in global variables.

    • [DH] doc/indevs.texi
    • [DH] libavdevice/bktr.c
    • [DH] libavdevice/version_major.h
  • Long-running AWS Linux process suddenly freezes once in a while

    12 décembre 2022, par Incredi Blame

    I am running a non-stop process on Ubuntu LTS AWS t2.micro instance. Process is ffmpeg downloading network stream from a CCTV. It crashes every 10 min cause of network errors, so I run it in a cycle script like this :

    


    while true
do
    ~command~
done


    


    The cycler-script itself never crashes.

    


    Everything works fine for hours (I check with ssh from time to time). But then sometimes ffmpeg process just freezes. I checked logs, it is writing the stream and it literally freezes mid-way through the stream, no error messages, nothing, as if it is still waiting for the next packet. Just stops working and never wakes up. Usually if the stream goes down ffmpeg complains, spits errors out and crashes. But on this occasion there is nothing and no crash either.

    


    Another mystery is that I run several of such ffmpeg processes and they all freeze at the same time.

    


    The issue with that freezing is the cycler can't restart ffmpegs, as they haven't crashed. When I check frozen processes with ps -aux they are shown as SL, which doesn't tell much, as they are always marked this way. top -i doesn't display them at all as active. When they work as normal it does. If I kill those frozen processes the cycler restarts them and everything works again as it should.

    


    I can always kill those ffmpegs once in a while on some schedule and let cycler restart them. Or check if they froze by timestamps they output and kill them then, so theoretically the problem is solvable. But I just want to know what causes it.

    


    I haven't figured out yet if this freezing happens at the same time of the day, trying to track that now. I don't think it could be related to free space shortage, as I have a cleaner cron job and free space is always available.

    


    So I have the following questions :

    


      

    1. Is there anything on AWS itself which could cause this freezing ? Like some kind of regular maintenance job that messes with running processes ?
    2. 


    3. Could it be caused by Linux freezing long-running processes ? Probably not, as they all freeze at the same time while current running time is different for each.
    4. 


    5. Last one, my cron job that cleans space also cleans out logs that ffmpeg is appending to. The script goes like this :
    6. 


    


    tail "ffmpeg.log" -n 10000 > "tmp.log" && \
    cat "tmp.log" > "ffmpeg.log" && \
    rm "tmp.log"


    


    The logs now are already full and are never fully cleared. Cron job just preserves the last 10000 lines. It runs every 2 min and runs fine for hours. Could it be responsible for this sudden freezing due to some coincidental timing ?

    


    If none of the above is responsible for freezing it must be some streaming issue on the server side, which I have no access to. In that case I would have to rely on detecting freezing and restarting ffmpegs.