Recherche avancée

Médias (1)

Mot : - Tags -/berlin

Autres articles (51)

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

  • Mise à disposition des fichiers

    14 avril 2011, par

    Par défaut, lors de son initialisation, MediaSPIP ne permet pas aux visiteurs de télécharger les fichiers qu’ils soient originaux ou le résultat de leur transformation ou encodage. Il permet uniquement de les visualiser.
    Cependant, il est possible et facile d’autoriser les visiteurs à avoir accès à ces documents et ce sous différentes formes.
    Tout cela se passe dans la page de configuration du squelette. Il vous faut aller dans l’espace d’administration du canal, et choisir dans la navigation (...)

  • MediaSPIP version 0.1 Beta

    16 avril 2011, par

    MediaSPIP 0.1 beta est la première version de MediaSPIP décrétée comme "utilisable".
    Le fichier zip ici présent contient uniquement les sources de MediaSPIP en version standalone.
    Pour avoir une installation fonctionnelle, 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 (7182)

  • CCTV DVR recovery

    5 juin 2014, par bitmadmax

    I need to recover footage from one of these unbranded CCTV DVR units. I am unable to gain access to the unit via a password, factory reset or backdoor, which would otherwise have let me "export" the footage.

    So I have pulled the hard disk and made a copy of it. The original unit is Linux-based which ran off a chip, and an EXT filesystem laid down on the hard disk itself. There is one partition which appears to contain the "raw" CCTV footage.

    The hex structure appears as though each frame begins with 00dcH264, 01dcH264, 10dcH264 and so on... I think the 00, 01, 10 etc refers to the channel/camera input number. The hex contents after the H264 portion appears completely random, of variable length and has no signature, and is followed immediately with the next xxdcH264 header.

    When I use ffprobe across the entire raw footage partition, it is only detecting the 1 video stream. I can use ffmpeg to "force" it to read it in as H.264 and dump it out into an MP4 file that I can play. However, this gives me the problem that the footage as an individual file is quite "noisy" and has frames from each channel appearing randomly.

    Is there anyway I could maybe separate out the footage into say a file for each channel ? I am not a great programmer so something as simple as possible would be ideal. I did note that ffprobe determined that some of the frames were of different resolution - it is likely that the different channels recorded their image at different dimensions, I just wondered if another way might be to get ffprobe/ffmpeg to output frames based on their image dimensions perhaps ?

    EDIT : sample hex below :

    Offset      0  1  2  3  4  5  6  7   8  9 10 11 12 13 14 15
    00000000   32 31 64 63 48 32 36 34  76 08 00 00 00 00 00 00   21dcH264v      
    00000016   1E 8B 77 07 6A 00 00 00  00 00 00 01 61 FC 03 51    ‹w j       aü Q
    00000032   42 83 FC C5 C6 BD 50 63  5F 37 68 B6 B5 B8 4F E0   BƒüÅÆ½Pc_7h¶µ¸Oà
    00000048   2E 74 B8 FF BB BD 70 1C  DE 1E 7A 8C 0F            .t¸ÿ»½p Þ zŒ

    (variable length)....

    Offset      0  1  2  3  4  5  6  7   8  9 10 11 12 13 14 15
    00000000   D3 30 59 01 FA 98 08 A0  0A 27 01 49 19 C1 0C 89   Ó0Y ú˜   ' I Á ‰
    00000016   83 AC 6B 28 03 8D 92 29  38 18 BA 95 82 B3 BA C6   ƒ¬k(  ’)8 º•‚³ºÆ
    00000032   33 0A 74 10 1A D5 89 3B  90 A0 19 1F A9 93 00 10   3 t  Õ‰;    ©“  
    00000048   92 AA 70 32 31 64 63 48  32 36 34                  ’ªp21dcH264
  • How to extract good quality frame in pixel format from live mpeg-ts stream ?

    2 février 2024, par Aven

    I use the command below to stream my ts file for my programe :

    


    ffmpeg -re -i independent_frame.ts -f mpegts udp://127.0.0.1:10002


    


    Below is the code of my programe, I'm trying to extract each frame in pixel format from the stream by using FFmpeg, but I found the quality is not good as it should be of the extracted frame ( I know OpenCV can do this, But I have other reason have to use FFmpeg ). I tried to put -qscale:v 2 in FFmpeg command, but it seems change nothing. Does anyone know how to enhance the frame quality in this case ? Thanks !

    


    stream = 'udp://127.0.0.1:10002'
H, W = 720, 1280

command = [ 'ffmpeg',
            '-i', stream ,
            '-pix_fmt', 'bgr24', # brg24 for matching OpenCV
            '-qscale:v', '2', 
            '-f', 'rawvideo',
            'pipe:' ]

# Execute FFmpeg as sub-process with stdout as a pipe
process = subprocess.Popen(command, stdout=subprocess.PIPE, bufsize=10**8)#10**8

# Load individual frames in a loop
nb_img = H*W*3

# Read decoded video frames from the PIPE until no more frames to read
num = 0
while True:
    # Read decoded video frame (in raw video format) from stdout process.
    buffer = process.stdout.read(W*H*3)

    # Break the loop if buffer length is not W*H*3 (when FFmpeg streaming ends).
    if len(buffer) != W*H*3:
        break

    img = np.frombuffer(buffer, np.uint8).reshape(H, W, 3)
    num +=1

    if num == 435:
        cv2.imwrite('435.png', img)
        cv2.imshow('img', img)  # Show the image for testing
        cv2.waitKey(0)
        cv2.destroyAllWindows()
        break

process.stdout.close()
process.wait()
cv2.destroyAllWindows()


    


  • How to parse WMV (ASF) file ? Can't find length of data packets

    9 mars 2018, par bukkojot

    I try to parse WMV (ASF) files without any SDK, just by decoding raw bytes. Now I have problem with ASF_Data_Object, where I can’t find length of data packet. More precise, Single payload data packet.

    See image :
    Sample

    Here I have 9 packets, but unable to find size of individual packet. How I can determine border between packets ?

    I think, my problem at byte 0x411, where field "Length type flags". As you can see, here 0 value, so all flags are zero. Even Packet Length Type.

    enter image description here
    enter image description here

    Yes, 0 value here allowed here. But how to read this type of content ?

    This is now compressed payload, as replication data is 8, not 1. So, this is single payload without additional fields of size.

    Sample of WMV file : https://files.catbox.moe/b51l2j.wmv