Recherche avancée

Médias (0)

Mot : - Tags -/signalement

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

Autres articles (49)

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

  • Les autorisations surchargées par les plugins

    27 avril 2010, par

    Mediaspip core
    autoriser_auteur_modifier() afin que les visiteurs soient capables de modifier leurs informations sur la page d’auteurs

  • Supporting all media types

    13 avril 2011, par

    Unlike most software and media-sharing platforms, MediaSPIP aims to manage as many different media types as possible. The following are just a few examples from an ever-expanding list of supported formats : images : png, gif, jpg, bmp and more audio : MP3, Ogg, Wav and more video : AVI, MP4, OGV, mpg, mov, wmv and more text, code and other data : OpenOffice, Microsoft Office (Word, PowerPoint, Excel), web (html, CSS), LaTeX, Google Earth and (...)

Sur d’autres sites (6670)

  • How do I make ffmpeg not open a window when used in Python (Discord Bot Youtube Audio Player Pytube)

    20 juin 2019, par Brandalf

    I am using pytube to create a Discord bot that gets audio from a YouTube video and plays it in the voice channel using the code below. The code works perfectly fine and does what I want which is playing audio from YouTube with a link. The issue is that it uses ffmpeg and when it does, it opens the ffmpeg.exe window. Having a window constantly pop up on my screen is kind of annoying but what’s worse is that if I am playing a game in full screen, when ffmpeg is run, it will tab out of my game. So I’m wondering if there is a way to prevent ffmpeg from opening the window or if there is an alternative to playing youtube audio in Discord with a bot that doesn’t use ffmpeg.

    user=ctx.message.author
    
voice_channel=user.voice.voice_channel
    
vc = await client.join_voice_channel(voice_channel)
    
player = await vc.create_ytdl_player(videoLink)
    
video = pafy.new(videoLink) #runs ffmpeg
    
player.start()

  • To get OpenCV VideoWriter work across platforms consistently for MP4 container with H264 encoding

    28 mars 2019, par Moh

    I am trying to get OpenCV VideoWriter work across platform consistently for MP4 container with H246 encoding.

    Target platforms in order of importance - Ubuntu, Raspbian, OSX

    Basically, my shortcoming at this point is not understanding the relationship of FourCC code (as a parameter to OpenCV VideoWriter) to the FFMPEG backend and its requirements. I am interested to understand the game in play rather than discussing a piece of code.

    What I want to know is when I specify ’X264’ as FourCC code trying to write an x.MP4 file (FFMPEG backend) and the request is marshalled to FFMPEG what requirements/dependencies need to be satisfied by the OS for it to success.

    So far I have got my python stack writing MP4 video files across Raspbian/Ubuntu/OSX, with a hack.

    On my Raspbian stretch installation, I use 0x00000021 as the fourCC code.
    On Ubuntu (VM on OSX) and on OSX, AVC1 works.

    Days of Googling only delivered those hacks, not a good understanding of the problem.

    The x264 as FourCC code leads to one of - failure, non-portable video file + annoying FFMPEG warning.

    I am trying to get to the bottom of it.

    The code,

        #self.__fourCC = cv2.VideoWriter_fourcc('x', '2', '6', '4')
    
    self.__fourCC = cv2.VideoWriter_fourcc('a', 'v', 'c', '1')
    
    if PlatformUtils.isRunningOnRaspberryPi():
    
        self.__fourCC = 0x00000021

    I have control over the version both OpenCV and FFMPEG (if required GStreamer too). I can and have built them for Ubuntu/Raspbian.

  • To get OpenCV VideoWriter work across platforms consistently for MP4 container with H264 encoding

    28 mars 2019, par Moh

    I am trying to get OpenCV VideoWriter work across platform consistently for MP4 container with H246 encoding.

    Target platforms in order of importance - Ubuntu, Raspbian, OSX

    Basically, my shortcoming at this point is not understanding the relationship of FourCC code (as a parameter to OpenCV VideoWriter) to the FFMPEG backend and its requirements. I am interested to understand the game in play rather than discussing a piece of code.

    What I want to know is when I specify ’X264’ as FourCC code trying to write an x.MP4 file (FFMPEG backend) and the request is marshalled to FFMPEG what requirements/dependencies need to be satisfied by the OS for it to success.

    So far I have got my python stack writing MP4 video files across Raspbian/Ubuntu/OSX, with a hack.

    On my Raspbian stretch installation, I use 0x00000021 as the fourCC code.
    On Ubuntu (VM on OSX) and on OSX, AVC1 works.

    Days of Googling only delivered those hacks, not a good understanding of the problem.

    The x264 as FourCC code leads to one of - failure, non-portable video file + annoying FFMPEG warning.

    I am trying to get to the bottom of it.

    The code,

        #self.__fourCC = cv2.VideoWriter_fourcc('x', '2', '6', '4')
    
    self.__fourCC = cv2.VideoWriter_fourcc('a', 'v', 'c', '1')
    
    if PlatformUtils.isRunningOnRaspberryPi():
    
        self.__fourCC = 0x00000021

    I have control over the version both OpenCV and FFMPEG (if required GStreamer too). I can and have built them for Ubuntu/Raspbian.

Navigation