Recherche avancée

Médias (1)

Mot : - Tags -/ticket

Autres articles (53)

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

  • MediaSPIP 0.1 Beta version

    25 avril 2011, par

    MediaSPIP 0.1 beta is the first version of MediaSPIP proclaimed as "usable".
    The zip file provided here only contains the sources of MediaSPIP in its standalone version.
    To get a working installation, you must manually install all-software dependencies on the server.
    If you want to use this archive for an installation in "farm mode", you will also need to proceed to other manual (...)

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

Sur d’autres sites (7930)

  • ros streming with encode h264

    18 mars 2024, par slowmonk
     class ROSImageStream:
def __init__(self):
    self.bridge = CvBridge()
    self.websocket_clients = []
    rospy.init_node('image_stream_node', anonymous=True)
    rospy.Subscriber("/vision/image/color", Image, self.callback)

def callback(self, data):
    cv_image = self.bridge.imgmsg_to_cv2(data, "bgr8")
    _, jpeg = cv2.imencode('.jpg', cv_image, [int(cv2.IMWRITE_JPEG_QUALITY), 50])


    


    Currently, I am attempting to send streaming images via WebSocket. At the moment, I am transmitting them in JPEG-to-byte format and also streaming camera data through a ROS topic in JPEG format.

    


    However, I wish to convert the images to the H.264 format for streaming. Is it feasible to directly implement this Python code to encode images into H.264 format and stream them ? Or, is there a better solution to achieve this ?

    


  • Anomalie #2259 : Modification d’un auteur

    28 août 2011, par Johan .

    Désolé ! Ticket en triple avec #2258 (cf. #2257) suite à : Error 503 Service Unavailable Service Unavailable Guru Meditation : XID : 1751692444 Varnish cache server

  • Problems with muxing fmp4 stream with libav

    20 juillet 2020, par Elias Wagnerberger

    currently i have an application that is supposed to send fragmented mp4 data over a websocket to a client for it to be played there.

    


    i have a working implementation that pipes the raw frames to a spawned ffmpeg process and then reads fragmented mp4 segments from the output pipe before it sends those on to the client where the client then displays the video correctly.

    


    my problem is that when i try to make an implementation using libav it doesnt seem to work. my libav config uses libx264rgb to encode the frames before muxing them to a mp4, but when i try to play the provided segments in a browser using MSE it spits out an error. after having checked chrome ://media-internals i have figured out that the problem lies in the moov box that is one of the two initialization boxes of a fmp4 stream.

    


    chrome apparently has a problem with parsing that box when its sent from libav, but not when its sent from ffmpeg.

    


    my question is :
What is the correct muxer configuration of libav so that it creates a fragmented mp4 stream where the client can recieve media boxes from the middle, after having been provided the init boxes ?

    


Navigation