Recherche avancée

Médias (0)

Mot : - Tags -/xmlrpc

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

Autres articles (68)

  • Websites made ​​with MediaSPIP

    2 mai 2011, par

    This page lists some websites based on MediaSPIP.

  • Personnaliser en ajoutant son logo, sa bannière ou son image de fond

    5 septembre 2013, par

    Certains thèmes prennent en compte trois éléments de personnalisation : l’ajout d’un logo ; l’ajout d’une bannière l’ajout d’une image de fond ;

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

Sur d’autres sites (6884)

  • Merging .flv chunks from stream site

    4 décembre 2016, par Iztooi

    I’m trying to download a video from an alternative version of the Ustream site. This site is apparently used for a DRM protection, in fact you can’t watch this video without having access to it through a login from this site.
    The video system should be the same used by ustream (same links), that is calling different flv chunks every x seconds and merging them into the stream (similar to an rtmp service, but it doesn’t use this protocol).

    I managed to download every .flv chunks composing this video, but i had issues on merging them into a single file. First of all these flvs files have some audio/video lags/problems, but since there is no other way to download this video i’m not complaining about lags.

    The real issue is that every flv file has an additive increase on the duration, despite having a normal size. Video duration is about 6 seconds, so the first chunk is 6 seconds long, the second chunk is 12 seconds long, although only the first 6 are visible (the remaining 6 are "corrupted"). If i try to merge (with ffmpeg or any video-joining software) all these files (about 600-700, for a total duration of 1 hour and 15 minutes) only the first two sections are visible, then I cannot see anything. (Being more clear, if i try to merge the first 2 chunks, file is 18 seconds long and i can see the first 12 ; if i try to merge the first 3 chunks, file is 36 seconds long and i can still only see the first 12 seconds.)

    Anyone has any idea ?

  • two data streams into one ffmpeg stream

    1er juin 2022, par user5285766

    I have two data streams, each representing a rabbitmq subscriber. Inside audio and video streams, data is in the form of bytes. Something like :

    


    vp = VideoProcess()
ap = AudioProcess()


async def receive_video_data(message: IncomingMessage):
    async with message.process():
        await vp.process(frame=message.body)


async def receive_audio_data(message: IncomingMessage):
    async with message.process():
        await ap.process(packet=message.body)




    


    I wanted to take this data from each stream and put it in the ffmpeg stream, which would open the port on the service. So that I can broadcast this data to other subsystems in the form of an ffmpeg stream (for example, to broadcast audio and video to my html page). Can you tell me what are the options for this task ?

    


    process = sp.Popen(
    shlex.split(
        f"ffmpeg -i ...."
    ))



    


  • Still getting FFMPEG "Segmentation fault" with network stream source with the AmazonLinux 2023 distro [closed]

    28 décembre 2023, par Matthew Drooker

    After referencing https://docs.yucca.app/en/troubleshooting/Segmentation_fault_core_dumped

    


    And using

    


    FFMPEG "Segmentation fault" with network stream source

    


    I thought I had this solved.
But still having the same issue as documented as fixed.

    


    Im using AmazonLinux 2023 distro in a Lambda custom image.

    


    Im trying to use baseImage from FROM --platform=linux/amd64 public.ecr.aws/lambda/nodejs:20

    


    Then doing- RUN dnf install nscd  -y in my Dockerfile allowing the nscd service to be installed per the answer.

    


    But, Im still getting the ffprobe was killed with signal SIGSEGV error with the new AmazonLinux Distro.

    


    Has anyone else faced this with the 2023 Distro ? Or have an answer to this question ?