Recherche avancée

Médias (91)

Autres articles (19)

  • Encoding and processing into web-friendly formats

    13 avril 2011, par

    MediaSPIP automatically converts uploaded files to internet-compatible formats.
    Video files are encoded in MP4, Ogv and WebM (supported by HTML5) and MP4 (supported by Flash).
    Audio files are encoded in MP3 and Ogg (supported by HTML5) and MP3 (supported by Flash).
    Where possible, text is analyzed in order to retrieve the data needed for search engine detection, and then exported as a series of image files.
    All uploaded files are stored online in their original format, so you can (...)

  • Contribute to documentation

    13 avril 2011

    Documentation is vital to the development of improved technical capabilities.
    MediaSPIP welcomes documentation by users as well as developers - including : critique of existing features and functions articles contributed by developers, administrators, content producers and editors screenshots to illustrate the above translations of existing documentation into other languages
    To contribute, register to the project users’ mailing (...)

  • Participer à sa traduction

    10 avril 2011

    Vous pouvez nous aider à améliorer les locutions utilisées dans le logiciel ou à traduire celui-ci dans n’importe qu’elle nouvelle langue permettant sa diffusion à de nouvelles communautés linguistiques.
    Pour ce faire, on utilise l’interface de traduction de SPIP où l’ensemble des modules de langue de MediaSPIP sont à disposition. ll vous suffit de vous inscrire sur la liste de discussion des traducteurs pour demander plus d’informations.
    Actuellement MediaSPIP n’est disponible qu’en français et (...)

Sur d’autres sites (4340)

  • Revision b6c75c5a8d : Improve motion detection for low complexity regions. Where there is very subtle

    11 décembre 2014, par Paul Wilkins

    Changed Paths :
     Modify /vp9/encoder/vp9_rdopt.c



    Improve motion detection for low complexity regions.

    Where there is very subtle motion, especially when combined
    with low spatial complexity, the codec sometimes fails to quickly
    pick up the ambient motion field.

    Once it has been established though the field propagates well using
    Nearest and Near MV.

    This patch looks specifically at the case where the Nearest and Near
    have not been established as non zero vectors and in this case
    discounts the cost of searching for a new vector in the rd code.

    This will almost certainly have some implications in terms of encode
    speed but it should be possible to mitigate the impact in a subsequent
    using first pass stats and the local spatial complexity.

    Average results for test sets approximately neutral.

    Change-Id : I44a29e20f11f7ab10f8c93ffbdc50183d9801524

  • lavfi/vsrc_testsrc : switch to activate.

    25 juin 2020, par Nicolas George
    lavfi/vsrc_testsrc : switch to activate.
    

    Allow to set the EOF timestamp.

    Also : doc/filters/testsrc* : specify the rounding of the duration option.

    The changes in the ref files are right.

    For filter-fps-down, the graph is testsrc2=r=7:d=3.5,fps=3.
    3.5=24.5/7, so the EOF of testsrc2 will have PTS 25/7.
    25/7=(10+5/7)/3, so the EOF PTS for fps should be 11/7,
    and the output should contain a frame at PTS 10.

    For filter-fps-up, the graph is testsrc2=r=3:d=2,fps=7,
    for filter-fps-up-round-down and filter-fps-up-round-up
    it is the same with explicit rounding options.
    But there is no rounding : testsrc2 produces exactly 6 frames
    and 2 seconds, fps converts it into exactly 14 frames.

    The tests should probably be adjusted to restore them to
    a useful coverage.

    • [DH] doc/filters.texi
    • [DH] libavfilter/vsrc_testsrc.c
    • [DH] tests/ref/fate/filter-fps-down
    • [DH] tests/ref/fate/filter-fps-up
    • [DH] tests/ref/fate/filter-fps-up-round-down
    • [DH] tests/ref/fate/filter-fps-up-round-up
    • [DH] tests/ref/fate/filter-mpdecimate
  • Prevent "guessing mono" when using FFMPEG ?

    25 juillet 2020, par Daemitrous

    This extention works perfectly fine, I'm just concerned about the message it prints everytime it's called.

    


    The Message when the script is called:

    


    Guessed Channel Layout for Input Stream #0.0 : mono


    


    This is an extention to the discord bot I'm working on using discord.py.

    


    Script

    


    from discord.ext import commands&#xA;from pyttsx3 import init  # TTS Audio converter&#xA;&#xA;import discord&#xA;&#xA;&#xA;ffmpeg_path = r"C:\Users\evand\Documents\Misc\ffmpeg\bin\ffmpeg.exe"&#xA;&#xA;audio_path = r"C:\Users\evand\Documents\Misc\Discord\suhj_bot\Test_mp3\AudioFileForDiscord.mp3"&#xA;&#xA;&#xA;engine = init() # Initializes speach TTS engine with "sapi5" configuration&#xA;&#xA;&#xA;def TTS_save(text, audio=engine): # converts and saves the user&#x27;s text into a TTS audio file ".mp3"&#xA;&#xA;    audio.save_to_file(text, audio_path)&#xA;&#xA;    audio.runAndWait()&#xA;&#xA;&#xA;class Voice(commands.Cog):&#xA;&#xA;    def __init__(self, bot):&#xA;&#xA;        self.bot = bot&#xA;&#xA;    @commands.command(&#xA;&#xA;        name="v",&#xA;        description="The voice command:\n\ng.v <content>"&#xA;&#xA;    )&#xA;&#xA;    async def voice_command(self, ctx, *, args):&#xA;&#xA;        VoiceClient = ctx.voice_client&#xA;&#xA;&#xA;        if VoiceClient is None:&#xA;&#xA;            VoiceClient = await ctx.author.voice.channel.connect() # bot joins voice-channel of user&#xA;&#xA;&#xA;        TTS_save(args) # creates TTS audio file&#xA;&#xA;        VoiceClient.play(discord.FFmpegOpusAudio(audio_path, executable=ffmpeg_path)) # plays audio file through discord bot (.mp3, ffmpeg.exe)&#xA;&#xA;        return&#xA;&#xA;&#xA;def setup(bot):&#xA;&#xA;    bot.add_cog(Voice(bot))&#xA;</content>

    &#xA;

    Is there any way to prevent the program from guessing mono ? I like to keep my code clean and close to errorness.

    &#xA;