
Recherche avancée
Médias (1)
-
Bug de détection d’ogg
22 mars 2013, par
Mis à jour : Avril 2013
Langue : français
Type : Video
Autres articles (49)
-
MediaSPIP v0.2
21 juin 2013, parMediaSPIP 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, parPar 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, parMediaSPIP 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 (7346)
-
Trying to stream a video loop using FFMPEG. However, I keep getting the error "Cannot Write the Headers Server returned 400 Bad Request" [closed]
8 mai 2023, par lokit khemkaI am using
mediamtx
for starting RTSP server. The command that I am using for ffmpeg is as follows :

ffmpeg -re -stream_loop -1 -i ./clouds.mp4 -f rtsp -rtsp_transport tcp rtsp://localhost:8554


The tried various different options but not luck. I am not getting the ffmpeg to stream the video.


The file details are as follows :


Input #0, mov,mp4,m4a,3gp,3g2,mj2, from './clouds.mp4':
 Metadata:
 major_brand : mp42
 minor_version : 0
 compatible_brands: mp42isomavc1
 creation_time : 2023-01-12T20:44:34.000000Z
 Duration: 00:00:56.34, start: 0.000000, bitrate: 2952 kb/s
 Stream #0:0[0x1](und): Video: h264 (High) (avc1 / 0x31637661), yuv420p(tv, bt709, progressive), 1920x1080, 2758 kb/s, 29.97 fps, 29.97 tbr, 30k tbn (default)
 Metadata:
 creation_time : 2023-01-12T20:44:34.000000Z
 handler_name : Vimeo Artax Video Handler
 vendor_id : [0][0][0][0]
 encoder : AVC Coding
 Stream #0:1[0x2](und): Audio: aac (LC) (mp4a / 0x6134706D), 48000 Hz, stereo, fltp, 189 kb/s (default)
 Metadata:
 creation_time : 2023-01-12T20:44:34.000000Z
 handler_name : Vimeo Artax Audio Handler
 vendor_id : [0][0][0][0]
Stream mapping:
 Stream #0:0 -> #0:0 (h264 (native) -> mpeg4 (native))
 Stream #0:1 -> #0:1 (aac (native) -> aac (native))



The error on
mediamtx
terminal window is :

2023/05/08 17:30:43 INF [RTSP] [session 298895e1] created by 127.0.0.1:38024
2023/05/08 17:30:43 INF [RTSP] [conn 127.0.0.1:38024] closed (invalid path)



-
FFMPEG to command not working as i intend [closed]
11 mai 2023, par KillerHaseTVI want to cut my video by using timestamps. I have a txt file with my timestamps and I put them in the correct variables. For example, $startzeit = 00:00:01 and $endzeit = 00:00:10. So, I want :01 -> :10 and not :01 and run for 10 seconds until :11.


The problem has something to do with "-to" because the timestamps are correct.


Here is my code


$segment = 0
$pathtxt = "D:\Streamshit\Stream\Videos schneiden\timestamps.txt"
$pathvideo = "D:\Streamshit\Stream\Videos schneiden\2023-05-04_18-59-45.mkv"
$zeile = (Get-Content -LiteralPath $pathtxt).Length
$segment_list = @(Get-Content -LiteralPath $Pathtxt)

while($segment -lt $zeile){

 $timestamp = $segment_list[$segment].split(",")
 $startzeit = $timestamp[0]
 $endzeit = $timestamp[1]
 $TEST = "D:\Streamshit\Stream\Videos schneiden\Clips\video$segment.mp4"
 $segment++ 
 ffmpeg -ss $startzeit -i $pathvideo -to $endzeit -c copy $TEST 
}



and here are my timestamps :


00:00:01,00:00:10
00:00:24,00:00:41
00:01:29,00:01:42
00:02:19,00:02:46
00:04:11,00:04:58
00:08:38,00:08:42
00:10:05,00:10:14
00:12:07,00:14:47
00:16:59,00:17:20
00:26:31,00:27:00
00:34:36,00:36:56
00:39:01,00:39:21
00:46:32,00:46:53
00:48:00,00:48:58
00:51:11,00:52:01
00:56:15,00:57:52
00:59:20,01:01:20
01:03:21,01:03:40
01:12:02,01:12:17
01:14:48,01:14:59
01:15:13,01:19:03
01:19:14,01:19:23
01:23:49,01:24:06
01:24:23,01:24:50
01:25:13,01:26:10
01:26:45,01:26:56
01:29:08,01:29:29
01:31:54,01:32:10
01:36:32,01:37:41
01:39:37,01:39:53
01:55:30,01:56:02
02:13:07,02:13:44
03:12:19,03:12:50



I already tried it with just -t which is normally doing what my code is doing and -to should do what I want, but it doesn't.


-
how can I assign unique AVFoundation camera device names ?
28 avril 2023, par mcgregor94086Short summary :
I have a USB multi-camera array device. According to system_profiler, each of these webcams share the same name : "USB Camera". I have no unique name I can use with FFMPEG AVFoundation and get images from that specific camera. How can I tell FFMPEG the specific camera that I want (each has a unique USB path that I normally use to identify a specific camera.


I can solve this problem on Linux, but I can't figure out how to do it on macOS.


How I might do this on Linux
I know the unique USB Path to each camera, and I would like to use this to assign a unique Name that I can address using FFMPEG when taking images. On Linux I can use the udev system to make those assignments,


In Linux, I can reassign a new unique camera name using /etc/udev/rules.d/60-v4l.rules. with something like this :


SUBSYSTEMS=="usb", ENVID_VENDOR_ID=="0bda", ENVID_MODEL_ID=="5829", ENVID_PATH_TAG==platform-fd500000_pcie-0000_01_00_0-usb_1_4_5_1_3_1_1, ENVID_V4L_PRODUCT="Cam_00"
SUBSYSTEMS=="usb", ENVID_VENDOR_ID=="0bda", ENVID_MODEL_ID=="5829", ENVID_PATH_TAG==platform-fd500000_pcie-0000_01_00_0-usb_1_4_5_1_3_1_3, ENVID_V4L_PRODUCT="Cam_01"
...


More details :
Of course macOS doesn't work this way, as it uses AVFoundation to address video devices.


When I attach the device I see that 16 new cameras now appear when I type query system_profiler SPCameraDataType, it prints the output shown further below


You may notice that there are 16 cameras all named "USB Camera :" but system_profiler is reporting that each has a "Unique ID :" that is different for each camera. This Unique ID is composed of a unique USB Path (e.g. '0x1441311') concatenated with the "Vendor ID" ('00bda') and product ID ('5829') all expressed in hexadecimal.


Unfortunately, this means every camera has the same generic name in iPhoto, and when specifying the input camera in FFMPEG with AVFoundation syntax, I can't seem to indicate which specific camera I want.


I want to take 1 photo from each camera in a specific order. I have a table that maps each camera's USB Path to a desired name that would make it easy for me to trigger the camera captures in the sequence I desire.


In Linux, I can reassign a new unique camera name using /etc/udev/rules.d/60-v4l.rules.


SUBSYSTEMS=="usb", ENVID_VENDOR_ID=="0bda", ENVID_MODEL_ID=="5829", ENVID_PATH_TAG==platform-fd500000_pcie-0000_01_00_0-usb_1_4_5_1_3_1_1, ENVID_V4L_PRODUCT="Cam_00"
SUBSYSTEMS=="usb", ENVID_VENDOR_ID=="0bda", ENVID_MODEL_ID=="5829", ENVID_PATH_TAG==platform-fd500000_pcie-0000_01_00_0-usb_1_4_5_1_3_1_3, ENVID_V4L_PRODUCT="Cam_01"
...


% system_profiler SPCameraDataType


Camera :


USB Camera:

 Model ID: UVC Camera VendorID_3034 ProductID_22569
 Unique ID: 0x144131100bda5829

USB Camera:

 Model ID: UVC Camera VendorID_3034 ProductID_22569
 Unique ID: 0x144200000bda5829

USB Camera:

 Model ID: UVC Camera VendorID_3034 ProductID_22569
 Unique ID: 0x144141400bda5829

USB Camera:

 Model ID: UVC Camera VendorID_3034 ProductID_22569
 Unique ID: 0x144131300bda5829

USB Camera:

 Model ID: UVC Camera VendorID_3034 ProductID_22569
 Unique ID: 0x144141300bda5829

USB Camera:

 Model ID: UVC Camera VendorID_3034 ProductID_22569
 Unique ID: 0x144121200bda5829

USB Camera:

 Model ID: UVC Camera VendorID_3034 ProductID_22569
 Unique ID: 0x144121400bda5829

USB Camera:

 Model ID: UVC Camera VendorID_3034 ProductID_22569
 Unique ID: 0x144133000bda5829

USB Camera:

 Model ID: UVC Camera VendorID_3034 ProductID_22569
 Unique ID: 0x144131200bda5829

USB Camera:

 Model ID: UVC Camera VendorID_3034 ProductID_22569
 Unique ID: 0x144141100bda5829

USB Camera:

 Model ID: UVC Camera VendorID_3034 ProductID_22569
 Unique ID: 0x144143000bda5829

USB Camera:

 Model ID: UVC Camera VendorID_3034 ProductID_22569
 Unique ID: 0x144121300bda5829

USB Camera:

 Model ID: UVC Camera VendorID_3034 ProductID_22569
 Unique ID: 0x144110000bda5829

USB Camera:

 Model ID: UVC Camera VendorID_3034 ProductID_22569
 Unique ID: 0x144141200bda5829

FaceTime HD Camera (Built-in):

 Model ID: UVC Camera VendorID_1452 ProductID_34068
 Unique ID: 0x8020000005ac8514

USB Camera:

 Model ID: UVC Camera VendorID_3034 ProductID_22569
 Unique ID: 0x144300000bda5829



MacBook Pro, OS X 10.11
Posted on Apr 27, 2023 10:49 PM
Reply


Page content loaded
There are no replies.
how can I assign unique AVFoundation camera device names ?
Reply