Recherche avancée

Médias (1)

Mot : - Tags -/ogg

Autres articles (111)

  • Submit bugs and patches

    13 avril 2011

    Unfortunately a software is never perfect.
    If you think you have found a bug, report it using our ticket system. Please to help us to fix it by providing the following information : the browser you are using, including the exact version as precise an explanation as possible of the problem if possible, the steps taken resulting in the problem a link to the site / page in question
    If you think you have solved the bug, fill in a ticket and attach to it a corrective patch.
    You may also (...)

  • 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

  • Script d’installation automatique de MediaSPIP

    25 avril 2011, par

    Afin de palier aux difficultés d’installation dues principalement aux dépendances logicielles coté serveur, un script d’installation "tout en un" en bash a été créé afin de faciliter cette étape sur un serveur doté d’une distribution Linux compatible.
    Vous devez bénéficier d’un accès SSH à votre serveur et d’un compte "root" afin de l’utiliser, ce qui permettra d’installer les dépendances. Contactez votre hébergeur si vous ne disposez pas de cela.
    La documentation de l’utilisation du script d’installation (...)

Sur d’autres sites (11982)

  • ffmpeg incorrect border width of ass subtitles

    7 avril 2021, par Tac

    This is what i met when burning the subtitle to the video.

    



    Here is the ass code, I have to use 640x360 in resolution :

    



    [Script Info]
; Script generated by Aegisub 3.2.2
; http://www.aegisub.org/
Title: Default Aegisub file
ScriptType: v4.00+
WrapStyle: 0
YCbCr Matrix: None
PlayResX: 640
PlayResY: 360

[Aegisub Project Garbage]
Last Style Storage: Default
Scroll Position: 154
Active Line: 172
Video Position: 10429

[V4+ Styles]
Format: Name, Fontname, Fontsize, PrimaryColour, SecondaryColour, OutlineColour, BackColour, Bold, Italic, Underline, StrikeOut, ScaleX, ScaleY, Spacing, Angle, BorderStyle, Outline, Shadow, Alignment, MarginL, MarginR, MarginV, Encoding
Style: Default,Arial,45,&H00FFFFFF,&H000000FF,&H00FF0000,&H00000000,0,0,0,0,100,100,0,0,1,5.125,3.125,2,28,28,16,1

[Events]
Format: Layer, Start, End, Style, Name, MarginL, MarginR, MarginV, Effect, Text
Dialogue: 0,0:00:00.94,0:05:12.11,*Default,NTP,0,0,0,,the quick brown dog jumps over the lazy fox.


    



    I usually use MeGUI on Windows (with avs script) to burn. Here is the avs code :

    



    DirectShowSource("C:\Users\xxx\Downloads\test.mp4", fps=25.000, audio=false, convertfps=true).AssumeFPS(25,1)
#deinterlace
#crop
#resize
#denoise

LoadPlugin("C:\Users\xxx\Desktop\megui\tools\avisynth_plugin\VSFilter.dll")
TextSub("C:\Users\xxx\Desktop\ass.ass", 1)

ConvertToYV12()


    



    The subtitle after burning looks like this :

    



    On Windows

    



    



    However, it is unable to use MeGui on Linux. Thus I used ffmpeg. The command I used is like this :

    



    ffmpeg -i test.mp4 -vf ass=ass.ass -crf 25 -an -f mp4 done.mp4
ffmpeg -i test.mp4 -vf ass=ass.ass:original_size=640x360 -crf 25 -an -f mp4 done.mp4
ffmpeg -i test.mp4 -vf ass=ass.ass:original_size=1920x1080 -crf 25 -an -f mp4 done.mp4
ffmpeg -i test.mp4 -vf subtitles=ass.ass -crf 25 -an -f mp4 done.mp4
ffmpeg -i test.mp4 -vf subtitles=ass.ass:original_size=640x360 -crf 25 -an -f mp4 done.mp4
ffmpeg -i test.mp4 -vf subtitles=ass.ass:original_size=1920x1080 -crf 25 -an -f mp4 done.mp4


    



    However, they all looks like this

    



    Subtitle on Linux

    



    



    The effect on windows is what I want. How can i get the effect like that on Linux ? Thanks !

    


  • fate : add more tests for hue video filter

    9 mai 2018, par Tobias Rapp
    fate : add more tests for hue video filter
    

    Adds tests for the hue angle and brightness filter parameters.
    Renames the existing saturation parameter test for consistency.

    Signed-off-by : Tobias Rapp <t.rapp@noa-archive.com>

    • [DH] tests/fate/filter-video.mak
    • [DH] tests/ref/fate/filter-hue
    • [DH] tests/ref/fate/filter-hue1
    • [DH] tests/ref/fate/filter-hue2
    • [DH] tests/ref/fate/filter-hue3
  • How Much H.264 In Each Encoder ?

    8 septembre 2010, par Multimedia Mike — General

    Thanks to my recent experiments with code coverage tools, I have a powerful new — admittedly somewhat specious — method of comparing programs. For example, I am certain that I have read on more than one occasion that Apple’s H.264 encoder sucks compared to x264 due, at least in part, to the Apple encoder’s alleged inability to exercise all of H.264′s features. I wonder how to test that claim ?

    Experiment
    Use code coverage tools to determine which H.264 encoder uses the most features.

    Assumptions

    • Movie trailers hosted by Apple will all be encoded with the same settings using Apple’s encoder.
    • Similarly, Yahoo’s movie trailers will be encoded with consistent settings using an unknown encoder.
    • Encoding a video using FFmpeg’s libx264-slow setting will necessarily throw a bunch of H.264′s features into the mix (I really don’t think this assumption holds much water, but I also don’t know what “standard” x264 settings are).

    Methodology

    • Grab a random Apple-hosted 1080p movie trailer and random Yahoo-hosted 1080p movie trailer from Dave’s Trailer Page.
    • Use libx264/FFmpeg with the ‘slow’ preset to encode Big Buck Bunny 1080p from raw PNG files.
    • Build FFmpeg with code coverage enabled.
    • Decode each file to raw YUV, ignore audio decoding, generate code coverage statistics using gcovr, reset stats after each run by deleting *.gcda files.

    Results

    • x264 1080p video : 9968 / 134203 lines
    • Apple 1080p trailer : 9968 / 134203 lines
    • Yahoo 1080p trailer : 9914 / 134203 lines

    I also ran this old x264-encoded file (ImperishableNightStage6Low.mp4) through the same test. It demonstrated the most code coverage with 10671 / 134203 lines.

    Conclusions
    Conclusions ? Ha ! Go ahead and jump all over this test. I’m already fairly confident that it’s impossible (or maybe just very difficult) to build a single H.264-encoded video that exercises every feature that FFmpeg’s decoder supports. For example, is it possible for a file to use both CABAC and CAVLC entropy methods ? If it’s possible, does any current encoder do that ?