Recherche avancée

Médias (0)

Mot : - Tags -/presse-papier

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

Autres articles (6)

  • Pas question de marché, de cloud etc...

    10 avril 2011

    Le vocabulaire utilisé sur ce site essaie d’éviter toute référence à la mode qui fleurit allègrement
    sur le web 2.0 et dans les entreprises qui en vivent.
    Vous êtes donc invité à bannir l’utilisation des termes "Brand", "Cloud", "Marché" etc...
    Notre motivation est avant tout de créer un outil simple, accessible à pour tout le monde, favorisant
    le partage de créations sur Internet et permettant aux auteurs de garder une autonomie optimale.
    Aucun "contrat Gold ou Premium" n’est donc prévu, aucun (...)

  • Selection of projects using MediaSPIP

    2 mai 2011, par

    The examples below are representative elements of MediaSPIP specific uses for specific projects.
    MediaSPIP farm @ Infini
    The non profit organizationInfini develops hospitality activities, internet access point, training, realizing innovative projects in the field of information and communication technologies and Communication, and hosting of websites. It plays a unique and prominent role in the Brest (France) area, at the national level, among the half-dozen such association. Its members (...)

  • De l’upload à la vidéo finale [version standalone]

    31 janvier 2010, par

    Le chemin d’un document audio ou vidéo dans SPIPMotion est divisé en trois étapes distinctes.
    Upload et récupération d’informations de la vidéo source
    Dans un premier temps, il est nécessaire de créer un article SPIP et de lui joindre le document vidéo "source".
    Au moment où ce document est joint à l’article, deux actions supplémentaires au comportement normal sont exécutées : La récupération des informations techniques des flux audio et video du fichier ; La génération d’une vignette : extraction d’une (...)

Sur d’autres sites (4136)

  • FFMPEG to command not working as i intend [closed]

    11 mai 2023, par KillerHaseTV

    I 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.

    


  • 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 khemka

    I 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)


    


  • App crashes on Google TV when playing MP4 videos

    14 avril 2023, par fab

    I am having problems with an Android app that was developed for me. The issue occurs when playing MP4 videos ; the app plays them correctly, but at some point, the app crashes and exits. I have been reviewing errors using Android Studio, and the only error that appears is the following :

    


    2023-04-14 00:45:45.846 7221-7650 SurfaceUtils com.app.X D connecting to surface 0xbf0d2808, reason connectToSurface(reconnect) 2023-04-14 00:45:45.848 7221-7654 ACodec com.app.X E [OMX.amlogic.avc.decoder.awesome2] setPortMode on output to DynamicANWBuffer failed w/ err -2147483648 2023-04-14 00:45:45.855 7221-7334 com.app.X com.app.X I get_buffer_dataspace_setting get_metadata return 0 dataspace:268500992 2023-04-14 00:45:45.875 7221-7334 NdkImageReader com.app.X D acquireImageLocked: Overriding buffer format YUV_420_888 to 0x11. 2023-04-14 00:45:45.877 7221-7334 com.app.X com.app.X I get_buffer_dataspace_setting get_metadata return 0 dataspace:268500992 2023-04-14 00:45:45.887 7221-7280 MediaCodec com.app.X D keep callback message for reclaim 2023-04-14 00:45:45.896 7221-7334 com.app.X com.app.X I get_buffer_dataspace_setting get_metadata return 0 dataspace:268500992 2023-04-14 00:45:45.914 7221-7334 com.app.X com.app.X I get_buffer_dataspace_setting get_metadata return 0 dataspace:268500992 2023-04-14 00:45:45.915 7221-7654 SurfaceUtils com.app.X D disconnecting from surface 0xbf0d2808, reason setNativeWindowSizeFormatAndUsage 2023-04-14 00:45:45.915 7221-7654 SurfaceUtils com.app.X D connecting to surface 0xbf0d2808, reason setNativeWindowSizeFormatAndUsage 2023-04-14 00:45:45.915 7221-7654 SurfaceUtils com.app.X D set up nativeWindow 0xbf0d2808 for 1920x1080, color 0x11, rotation 0, usage 0x402b00 2023-04-14 00:45:45.915 7221-7654 ACodec com.app.X W [OMX.amlogic.avc.decoder.awesome2] setting nBufferCountActual to 9 failed: -1010 2023-04-14 00:45:45.922 7221-7654 ion com.app.X E ioctl c0084905 failed with code -1: Invalid argument 2023-04-14 00:45:45.928 7221-7654 ion com.app.X E ioctl c0084905 failed with code -1: Invalid argument 2023-04-14 00:45:45.943 7221-7334 com.app.X com.app.X I get_buffer_dataspace_setting get_metadata return 0 dataspace:268500992 2023-04-14 00:45:45.954 7221-7654 ion com.app.X E ioctl c0084905 failed with code -1: Invalid argument 2023-04-14 00:45:45.960 7221-7654 ion com.app.X E ioctl c0084905 failed with code -1: Invalid argument 2023-04-14 00:45:45.962 7221-7654 ion com.app.X E ioctl c0084905 failed with code -1: Invalid argument 2023-04-14 00:45:45.969 7221-7654 ion com.app.X E ioctl c0084905 failed with code -1: Invalid argument 2023-04-14 00:45:45.979 7221-7654 ion com.app.X E ioctl c0084905 failed with code -1: Invalid argument 2023-04-14 00:45:45.986 7221-7654 ion com.app.X E ioctl c0084905 failed with code -1: Invalid argument

    


    One clarification is that the app is built with IONIC and Angular.

    


    The FFMPEG code that converts the video in golang is as follows :

    


    func ConvertVideoFile(inputFileName, outputFileName string) error { err := ffmpeg_go.Input(inputFileName). Filter("scale", ffmpeg_go.Args{"800:600"}). Output(outputFileName, ffmpeg_go.KwArgs{ "c:v": "libx264", "profile:v": "high", "level": "3.1", "pix_fmt": "yuv420p", "preset": "medium", "crf": "23", "b:v": "782k", "r": "25", "c:a": "aac", "b:a": "2k", "ar": "48000", "movflags": "+faststart", "max_muxing_queue_size": "1024", }, ). OverWriteOutput().ErrorToStdOut().Run() return err }

    


    Remove this error 2023-04-14 00:45:45.848 7221-7654 ACodec com.app.X E [OMX.amlogic.avc.decoder.awesome2

    


Navigation