Recherche avancée

Médias (1)

Mot : - Tags -/stallman

Autres articles (72)

  • Gestion des droits de création et d’édition des objets

    8 février 2011, par

    Par défaut, beaucoup de fonctionnalités sont limitées aux administrateurs mais restent configurables indépendamment pour modifier leur statut minimal d’utilisation notamment : la rédaction de contenus sur le site modifiables dans la gestion des templates de formulaires ; l’ajout de notes aux articles ; l’ajout de légendes et d’annotations sur les images ;

  • Dépôt de média et thèmes par FTP

    31 mai 2013, par

    L’outil MédiaSPIP traite aussi les média transférés par la voie FTP. Si vous préférez déposer par cette voie, récupérez les identifiants d’accès vers votre site MédiaSPIP et utilisez votre client FTP favori.
    Vous trouverez dès le départ les dossiers suivants dans votre espace FTP : config/ : dossier de configuration du site IMG/ : dossier des média déjà traités et en ligne sur le site local/ : répertoire cache du site web themes/ : les thèmes ou les feuilles de style personnalisées tmp/ : dossier de travail (...)

  • Keeping control of your media in your hands

    13 avril 2011, par

    The vocabulary used on this site and around MediaSPIP in general, aims to avoid reference to Web 2.0 and the companies that profit from media-sharing.
    While using MediaSPIP, you are invited to avoid using words like "Brand", "Cloud" and "Market".
    MediaSPIP is designed to facilitate the sharing of creative media online, while allowing authors to retain complete control of their work.
    MediaSPIP aims to be accessible to as many people as possible and development is based on expanding the (...)

Sur d’autres sites (10116)

  • ffmpeg 4.1.4 wav to mp3 error who can help me

    23 août 2019, par yang jia

    [swscaler @ 0xc946d000] deprecated pixel format used, make sure you did set range correctly

    [mp3 @ 0xc9621600] Frame rate very high for a muxer not efficiently supporting it.

    Please consider specifying a lower framerate, a different muxer or -vsync 2

    [auto_resampler_0 @ 0xd8e73be0] [SWR @ 0xc8058000] Output channel layout ’6 channels (FLC+BC+SL+SR+TC+TFL)’ is not supported

    [auto_resampler_0 @ 0xd8e73be0] Failed to configure output pad on auto_resampler_0

    Error reinitializing filters !

    Failed to inject frame into filter network : Invalid argument
    Error while processing the decoded data for stream #0:0
    --------- beginning of crash
    2019-02-26 16:04:58.368 27737-27737/com.blplayer.jbl.blplayer A/libc : Fatal signal 7 (SIGBUS), code 1, fault addr 0xc5ca in tid 27737 (er.jbl.blplayer)

    cmd

    ffmpeg -i test.wav -acodec libmp3lame -ar 8000 -ac 2 -y wav2mp3.mp3

     ![enter image description here]this is the log(https://i.stack.imgur.com/Kjs1Q.png)

  • syncing a video file with audio using ffmpeg is returning a video without audio

    31 juillet 2019, par abbood

    When I attempt to sync a .mov video with an .m4a audio file using ffmpeg like so

    ffmpeg -ss 00:00:2 -i test.m4a  -i test.mov -c:v copy -c:a aac -strict experimental output.mp4

    it works like a charm. But right now I’ve recorded a usability test video using adobe XD, and it returned an .mp4 (MPEG-4) video and I manually recorded the audio using quicktimre returning a .m4a audio file.

    Trying to merge them using ffmpeg is returning a video without any audio :

    ffmpeg -i video.mp4  -i audio.m4a -c:v copy -c:a aac -strict experimental output.mp4
    
ffmpeg version 4.1 Copyright (c) 2000-2018 the FFmpeg developers
    
  built with Apple LLVM version 10.0.0 (clang-1000.11.45.5)
    
  configuration: --prefix=/usr/local/Cellar/ffmpeg/4.1_1 --enable-shared --enable-pthreads --enable-version3 --enable-hardcoded-tables --enable-avresample --cc=clang --host-cflags= --host-ldflags= --enable-ffplay --enable-gpl --enable-libmp3lame --enable-libopus --enable-libsnappy --enable-libtheora --enable-libvorbis --enable-libvpx --enable-libx264 --enable-libx265 --enable-libxvid --enable-lzma --enable-opencl --enable-videotoolbox
    
  libavutil      56. 22.100 / 56. 22.100
    
  libavcodec     58. 35.100 / 58. 35.100
    
  libavformat    58. 20.100 / 58. 20.100
    
  libavdevice    58.  5.100 / 58.  5.100
    
  libavfilter     7. 40.101 /  7. 40.101
    
  libavresample   4.  0.  0 /  4.  0.  0
    
  libswscale      5.  3.100 /  5.  3.100
    
  libswresample   3.  3.100 /  3.  3.100
    
  libpostproc    55.  3.100 / 55.  3.100
    
Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'video.mp4':
    
  Metadata:
    
    major_brand     : qt
    
    minor_version   : 0
    
    compatible_brands: qt
    
    creation_time   : 2019-07-31T14:43:18.000000Z
    
    com.apple.quicktime.make: Apple
    
    com.apple.quicktime.model: MacBookPro15,1
    
    com.apple.quicktime.software: Mac OS X 10.14.5 (18F203)
    
    com.apple.quicktime.creationdate: 2019-07-31T17:43:17+0300
    
  Duration: 00:03:46.05, start: 0.000000, bitrate: 498 kb/s
    
    Stream #0:0(und): Video: h264 (Main) (avc1 / 0x31637661), yuv420p(tv, bt709), 374x812 [SAR 1:1 DAR 187:406], 390 kb/s, 60 fps, 60 tbr, 6k tbn, 12k tbc (default)
    
    Metadata:
    
      creation_time   : 2019-07-31T14:43:18.000000Z
    
      handler_name    : Core Media Video
    
      encoder         : H.264
    
    Stream #0:1(und): Audio: aac (LC) (mp4a / 0x6134706D), 8000 Hz, stereo, fltp, 0 kb/s (default)
    
    Metadata:
    
      creation_time   : 2019-07-31T14:43:18.000000Z
    
      handler_name    : Core Media Audio
    
Input #1, mov,mp4,m4a,3gp,3g2,mj2, from 'audio.m4a':
    
  Metadata:
    
    major_brand     : M4A
    
    minor_version   : 0
    
    compatible_brands: M4A mp42isom
    
    creation_time   : 2019-07-31T14:47:26.000000Z
    
    iTunSMPB        :  00000000 00000840 00000000 00000000009DFBC0 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
    
  Duration: 00:03:54.78, start: 0.047891, bitrate: 225 kb/s
    
    Stream #1:0(und): Audio: aac (LC) (mp4a / 0x6134706D), 44100 Hz, mono, fltp, 224 kb/s (default)
    
    Metadata:
    
      creation_time   : 2019-07-31T14:47:26.000000Z
    
      handler_name    : Core Media Audio
    
Stream mapping:
    
  Stream #0:0 -> #0:0 (copy)
    
  Stream #0:1 -> #0:1 (aac (native) -> aac (native))
    
Press [q] to stop, [?] for help
    
[aac @ 0x7fb5a4806a00] Too many bits 16384.000000 > 12288 per frame requested, clamping to max
    
Output #0, mp4, to 'output.mp4':
    
  Metadata:
    
    major_brand     : qt
    
    minor_version   : 0
    
    compatible_brands: qt
    
    com.apple.quicktime.creationdate: 2019-07-31T17:43:17+0300
    
    com.apple.quicktime.make: Apple
    
    com.apple.quicktime.model: MacBookPro15,1
    
    com.apple.quicktime.software: Mac OS X 10.14.5 (18F203)
    
    encoder         : Lavf58.20.100
    
    Stream #0:0(und): Video: h264 (Main) (avc1 / 0x31637661), yuv420p(tv, bt709), 374x812 [SAR 1:1 DAR 187:406], q=2-31, 390 kb/s, 60 fps, 60 tbr, 12k tbn, 6k tbc (default)
    
    Metadata:
    
      creation_time   : 2019-07-31T14:43:18.000000Z
    
      handler_name    : Core Media Video
    
      encoder         : H.264
    
    Stream #0:1(und): Audio: aac (LC) (mp4a / 0x6134706D), 8000 Hz, stereo, fltp, 96 kb/s (default)
    
    Metadata:
    
      creation_time   : 2019-07-31T14:43:18.000000Z
    
      handler_name    : Core Media Audio
    
      encoder         : Lavc58.35.100 aac
    
frame=13563 fps=0.0 q=-1.0 Lsize=   10903kB time=00:03:46.08 bitrate= 395.1kbits/s speed= 916x
    
video:10699kB audio:10kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: 1.805767%

    How can I get around this limitation ?

  • Having trouble obtaining the time from RTP Timestamps obtained through OpenCV

    24 août 2019, par Fr0sty

    I am finding it a bit difficult trying to understand whether or not the hack around with FFmpeg and OpenCV really provided a RTP timestamp. My last post helped a little bit but got me stuck in trying to validate the timestamps obtained through this work around by modifying ffmpeg and opencv.

    FFmpeg version : 4.1.0
    OpenCV version : 3.4.1

    import cv2
    
import time
    
from datetime import datetime, date
    

    
uri = 'rtsp://admin:password@192.168.1.66:554/Streaming/Channels/101'
    
cap = cv2.VideoCapture(uri)
    
'''One is the offset between the two epochs. Unix uses an epoch located at 1/1/1970-00:00h (UTC) and NTP uses 1/1/1900-00:00h.
    
This leads to an offset equivalent to 70 years in seconds (there are 17 leap years between the two dates so the offset is'''
    
time_offset = 2208988800 # (70*365 + 17)*86400 = 2208988800 (in seconds)
    
# offset = 3775484294
    
days = 43697
    
pdat = "1900-01-01 00:00:00:00"
    
mdat = "2019-08-23 22:02:44:00" # str(datetime.now()) + str(datetime.now().time())
    
pdate = datetime.strptime(pdat, "%Y-%m-%d %H:%M:%S:%f").date()
    
mdate = datetime.strptime(mdat, "%Y-%m-%d %H:%M:%S:%f").date()
    
delta = (mdate - pdate).days
    
offset = delta * 86400
    
def time_delta(s):
    
    return (s - time_offset)
    

    
while True:
    
    frame_exists, curr_frame = cap.read()
    
    if frame_exists:
    
        seconds = cap.getRTPTimeStampSeconds()
    
        fraction = cap.getRTPTimeStampFraction()
    
        timestamp = cap.getRTPTimeStampTs()
    
        unix_offset = seconds - time_offset
    
        msec = int((int(fraction) / 0xFFFFFFFF) * 1000.0)
    
        ts = float(str(unix_offset) + "." + str(msec))
    
        # print("Timestamp per Frame:%i" % timestamp)
    
        print((datetime.fromtimestamp(float(ts) + offset)))
    
cap.release()

    My Output :

    On August 23, 2019 at 22:02

    ...
    
2019-08-23 13:59:52.781000
    
2019-08-23 13:59:52.726000
    
2019-08-23 13:59:52.671000
    
2019-08-23 13:59:52.616000
    
2019-08-23 13:59:52.561000
    
2019-08-23 13:59:52.506000
    
2019-08-23 13:59:52.451000
    
2019-08-23 13:59:52.396000
    
2019-08-23 13:59:52.342000
    
2019-08-23 13:59:52.287000
    
2019-08-23 13:59:52.232000
    
2019-08-23 13:59:52.177000
    
2019-08-23 13:59:52.122000
    
2019-08-23 13:59:52.067000
    
2019-08-23 13:59:52.012000
    
2019-08-23 13:59:53.570000
    
2019-08-23 13:59:53.020000
    
2019-08-23 13:59:53.847000
    
2019-08-23 13:59:53.792000

    I’ve noticed how the time increments weirdly (that’s not suppose to happen in the real, current time), such as the last two lines and a few others in between in the output. A bit flabbergasted as to what went wrong. Also trying this out on multiple IP cameras, with each showing a different timestamp probably related to when they were turned on.

Navigation