Recherche avancée

Médias (0)

Mot : - Tags -/xml-rpc

Aucun média correspondant à vos critères n’est disponible sur le site.

Autres articles (102)

  • Publier sur MédiaSpip

    13 juin 2013

    Puis-je poster des contenus à partir d’une tablette Ipad ?
    Oui, si votre Médiaspip installé est à la version 0.2 ou supérieure. Contacter au besoin l’administrateur de votre MédiaSpip pour le savoir

  • Use, discuss, criticize

    13 avril 2011, par

    Talk 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.

  • 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 (11471)

  • How can I make windows "like" the mp4 files I create in Linux and sync with Rsync

    17 juillet 2019, par Geoff Fox

    I am a meteorologist on TV remotely from a studio I built. My control room uses a TriCaster, an amazing studio-in-a-box which runs on a Windows 7 variant. I make my weather maps myself on a Centos 7 machine — around 40,000/day.

    I don’t entirely understand the problem, but here’s a quote from someone helping me at NewTek (the TriCaster company)

    Rsync is built on a *nix based environment where all the file permissions and attributes are based on the Linux environment. There is no meaning for this in NTFS and Windows. The result is you get files that will most likely have the read-only flag set or no flag at all. Other attributes will be delivered as null. I’m sure from your own programming experience, programs don’t like null values and they generally have to be accounted for very specifically.

    And so the finely tuned TriCaster stumbles, meaning lost frames or other problems caused by my short weather animations.

    Here are some samples of the Rsync code I use

    rsync -r -t -s -v --no-p --chmod=ugo=rwX /var/www/html/output/loops/mp4/conus*.mp4 /mnt/tricaster/Clips/Import
    rsync -r -t -s -v --no-p --chmod=ugo=rwX /var/www/html/output/loops/mp4/nebraska*.mp4 /mnt/tricaster/Clips/Import
    rsync -r -t -s -v --no-p --chmod=ugo=rwX /var/www/html/output/loops/mp4/northernplains*.mp4 /mnt/tricaster/Clips/Import

    These are mp4 files. They are only used locally. I really don’t care what flags are checked and permissions filled as long as Windows 7 doesn’t care.

    At this point I always like to tell folks, though I do write some code my last computer class was in high school,’67-68 semester. Thanks in advance for your help.

  • ffmpeg subtitle font size too big

    21 avril 2020, par Harry Vũ

    After making subtitles in Aegisub, I save it as .ass file, with font size set from style manager,
I used this command

    



    ffmpeg -i video.mp4 -b:v 1M -vf subtitles=subtitle.ass out.mp4


    



    but the output file has the font a few sizes too big, larger than the original size I set in Aegisub.
Did I do something wrong ?
This was the intended size :

    



    enter image description here

    



    And this is the output size :

    



    enter image description here

    



    Here's the ass file
ass file

    


  • h264 : don’t sync pic_id between threads.

    3 avril 2017, par Ronald S. Bultje
    h264 : don’t sync pic_id between threads.
    

    This is how the ref list manager links bitstream IDs to H264Picture/Ref
    objects, and is local to the producer thread. There is no need for the
    consumer thread to know the bitstream IDs of its references in their
    respective producer threads.

    In practice, this fixes tsan warnings when running fate-h264 :

    WARNING : ThreadSanitizer : data race (pid=19295)
    Read of size 4 at 0x7dbc0000e614 by main thread (mutexes : write M1914) :
    #0 ff_h264_ref_picture src/libavcodec/h264_picture.c:112 (ffmpeg+0x0000013b3709)
    [..]
    Previous write of size 4 at 0x7dbc0000e614 by thread T2 (mutexes : write M1917) :
    #0 build_def_list src/libavcodec/h264_refs.c:91 (ffmpeg+0x0000013b46cf)

    • [DH] libavcodec/h264_picture.c