Recherche avancée

Médias (5)

Mot : - Tags -/open film making

Autres articles (78)

  • Websites made ​​with MediaSPIP

    2 mai 2011, par

    This page lists some websites based on MediaSPIP.

  • MediaSPIP v0.2

    21 juin 2013, par

    MediaSPIP 0.2 est la première version de MediaSPIP stable.
    Sa date de sortie officielle est le 21 juin 2013 et est annoncée ici.
    Le fichier zip ici présent contient uniquement les sources de MediaSPIP en version standalone.
    Comme pour la version précédente, il est nécessaire d’installer manuellement l’ensemble des dépendances logicielles sur le serveur.
    Si vous souhaitez utiliser cette archive pour une installation en mode ferme, il vous faudra également procéder à d’autres modifications (...)

  • Creating farms of unique websites

    13 avril 2011, par

    MediaSPIP platforms can be installed as a farm, with a single "core" hosted on a dedicated server and used by multiple websites.
    This allows (among other things) : implementation costs to be shared between several different projects / individuals rapid deployment of multiple unique sites creation of groups of like-minded sites, making it possible to browse media in a more controlled and selective environment than the major "open" (...)

Sur d’autres sites (13246)

  • dxva2_h264 : add a workaround for old Intel GPUs

    22 avril 2014, par Hendrik Leppkes
    dxva2_h264 : add a workaround for old Intel GPUs
    

    Old Intel GPUs expect the reference frame index to the actual surface,
    instead of the index into RefFrameList as specified by the spec.

    This workaround should be set when using one of the "ClearVideo" decoder
    devices.

    Signed-off-by : Anton Khirnov <anton@khirnov.net>

    • [DH] doc/APIchanges
    • [DH] libavcodec/dxva2.h
    • [DH] libavcodec/dxva2_h264.c
    • [DH] libavcodec/version.h
  • dxva2_h264 : add a workaround for old Intel GPUs

    22 avril 2014, par Hendrik Leppkes
    dxva2_h264 : add a workaround for old Intel GPUs
    

    Old Intel GPUs expect the reference frame index to the actual surface,
    instead of the index into RefFrameList as specified by the spec.

    This workaround should be set when using one of the "ClearVideo" decoder
    devices.

    Signed-off-by : Anton Khirnov <anton@khirnov.net>

    • [DBH] doc/APIchanges
    • [DBH] libavcodec/dxva2.h
    • [DBH] libavcodec/dxva2_h264.c
    • [DBH] libavcodec/version.h
  • Python ThreadedTCPServer : "Name or service not known"

    11 avril 2014, par Hal

    I was developing a ThreadedTCPServer to communicate with a PHP application also residing in this same machine. This is suppose to receive requests from this PHP app and to convert some videos locally using ffmpeg.

    Here's the code :

    # -*- coding: utf-8 -*-
    import os
    import socket
    import threading
    import logging.config
    import SocketServer, time
    from queuev2 import QueueServer

    logging.basicConfig(format=&#39;[%(asctime)s.%(msecs).03d] %(message)s&#39;, datefmt=&#39;%Y-%m-%d %H:%M:%S&#39;, filename=os.path.join(os.path.dirname(os.path.realpath(__file__)), &#39;converter.log&#39;), level=logging.INFO)

    class ThreadedTCPRequestHandler(SocketServer.BaseRequestHandler):

       def handle(self):
           data = self.request.recv(1024)
           cur_thread = threading.current_thread()
           response = "{}: {}".format(cur_thread.name, data)
           videoPool.add(data)
           print "Output! %s" % data
           self.request.sendall(response)

    class ThreadedTCPServer(SocketServer.ThreadingMixIn, SocketServer.TCPServer):
       pass

    if __name__ == "__main__":

       logging.info("Initializing...")
       videoPool = QueueServer()
       HOST, PORT = "localhost", 6666

       server = ThreadedTCPServer((HOST, PORT), ThreadedTCPRequestHandler)
       ip, port = server.server_address

       # Start a thread with the server -- that thread will then start one
       # more thread for each request
       server_thread = threading.Thread(target=server.serve_forever)

       # Exit the server thread when the main thread terminates
       server_thread.daemon = True
       server_thread.start()

       print("Server loop running in thread: %s" % server_thread.name)

       # "Groundhog day" time
       while True:
           time.sleep(999)
           pass

       #server.shutdown()

    This works well in my development laptop, but on the server i'm getting the following error :

    Traceback (most recent call last):
     File "server.py", line 31, in <module>
       server = ThreadedTCPServer((HOST, PORT), ThreadedTCPRequestHandler)
     File "/usr/lib/python2.7/SocketServer.py", line 408, in __init__
       self.server_bind()
     File "/usr/lib/python2.7/SocketServer.py", line 419, in server_bind
       self.socket.bind(self.server_address)
     File "/usr/lib/python2.7/socket.py", line 224, in meth
       return getattr(self._sock,name)(*args)
    socket.gaierror: [Errno -2] Name or service not known
    </module>

    I'm guessing it has to do with the port I'm using (6666), but I've tried others and it hasn't been working. Would Unix Domain Sockets be of use here ? Can you give me an example ?