Recherche avancée

Médias (1)

Mot : - Tags -/MediaSPIP

Autres articles (109)

  • Use, discuss, criticize

    13 avril 2011, par

    Talk to people directly involved in MediaSPIP’s development, or to people around you who could use MediaSPIP to share, enhance or develop their creative projects.
    The bigger the community, the more MediaSPIP’s potential will be explored and the faster the software will evolve.
    A discussion list is available for all exchanges between users.

  • Le profil des utilisateurs

    12 avril 2011, par

    Chaque utilisateur dispose d’une page de profil lui permettant de modifier ses informations personnelle. Dans le menu de haut de page par défaut, un élément de menu est automatiquement créé à l’initialisation de MediaSPIP, visible uniquement si le visiteur est identifié sur le site.
    L’utilisateur a accès à la modification de profil depuis sa page auteur, un lien dans la navigation "Modifier votre profil" est (...)

  • Les sons

    15 mai 2013, par

Sur d’autres sites (11674)

  • OBS and OBS Portable Recording Into Same File Simultaneously

    26 juin 2020, par aerodavo

    Corrupted video file, FFprobe output text file, and FFmpeg output text files are all available to download here :
https://drive.google.com/drive/folders/1R0Y5plgkhTWWFNNKgSNJ5yitpKQbIKgg?usp=sharing

    


    I'm hoping there is a way to extract good video and audio from this video file, this was for a very important job that is impossible to do again. The video linked is a 1 minute recreation of the exact same problem... the actual video file is confidential (for a legal court case) and is much longer/larger. I used the exact same settings, the only difference was the window OBS was capturing (I used a YouTube video as opposed to the videoconference software window used for the deposition).

    


    Here's what happened :

    


    In OBS and OBS Portable, I had the save location set to the same exact folder (this was not how I intended it to be, but I made a last minute change to accommodate what I suspected was a faulty hard drive). I also had a hotkey to start recording on both apps simultaneously. I left the auto-naming scheme in place for both instances of OBS since they were supposed to be saving to two totally different external hard drives. I have since changed the auto-naming so it won't happen again, but this perfect storm resulted in both recordings being written into a single file (see link above), instead of two files as intended. It is unplayabe in VLC.

    


    I ran an FFprobe (available via link above), and found that there are 8 streams in the file. Each file should have had 4 streams (1 video and 3 audio streams per my setup in OBS), so at first glance it looks like all the data is there in some form/arrangement.

    


    I tried to map the 0:0 stream to a new file and tried the same thing with the 0:4 stream (these are the video streams), but did not have any luck extracting good video. Here are the two things I ran (again see link above for text files with full FFmpeg ouput of each) :

    


    ffmpeg -i C :\Users\David\Videos\2020-06-23_17-39-32_corrupted.mkv -map 0:0 -c copy C :\Users\David\Videos\2020-06-23_17-39-32_corrupted_map0-0.mkv

    


    ffmpeg -i C :\Users\David\Videos\2020-06-23_17-39-32_corrupted.mkv -map 0:4 -c copy C :\Users\David\Videos\2020-06-23_17-39-32_corrupted_map0-4.mkv

    


    It seems the audio is intact, as I was able to map one of the audio streams into a wav file... although there seemed to be extra/repeated audio tacked onto where the video/audio should have ended...

    


    It looks to me like both video streams got written into stream 0:0, while stream 0:4 looks empty (because this map results in a very small file). However the thing that's weird (and maybe promising) is that when I play the corrupted file in VLC, it mostly looks like smeared digital colors, but if I click around to different times in the video, it sometimes shows good video, even though it won't show any good video if you just play it from the beginning.

    


    My life would saved if there is a way to extract good video/audio from this corrupted file. Any help would be greatly appreciated, thanks in advance !

    


  • ffmpeg youtube live stream settings screen output [closed]

    25 juin 2020, par brainoverflowse
    

    

    Below works but I do get some warnings:

    ffmpeg -rtsp_transport tcp -i rtsp://admin:password@192.168.0.121:5542/Streaming/Channels/1 -tune zerolatency -vcodec libx264 -pix_fmt + -c:v copy -c:a aac -f flv rtmp://a.rtmp.youtube.com/live2/streamcode
ffmpeg version git-2020-06-20-29ea4e1 Copyright (c) 2000-2020 the FFmpeg developers
  built with gcc 9.3.1 (GCC) 20200523
  configuration: --enable-gpl --enable-version3 --enable-sdl2 --enable-fontconfig --enable-gnutls --enable-iconv --enable-libass --enable-libdav1d --enable-libbluray --enable-libfreetype --enable-libmp3lame --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg --enable-libopus --enable-libshine --enable-libsnappy --enable-libsoxr --enable-libsrt --enable-libtheora --enable-libtwolame --enable-libvpx --enable-libwavpack --enable-libwebp --enable-libx264 --enable-libx265 --enable-libxml2 --enable-libzimg --enable-lzma --enable-zlib --enable-gmp --enable-libvidstab --enable-libvmaf --enable-libvorbis --enable-libvo-amrwbenc --enable-libmysofa --enable-libspeex --enable-libxvid --enable-libaom --enable-libgsm --disable-w32threads --enable-libmfx --enable-ffnvcodec --enable-cuda-llvm --enable-cuvid --enable-d3d11va --enable-nvenc --enable-nvdec --enable-dxva2 --enable-avisynth --enable-libopenmpt --enable-amf
  libavutil      56. 55.100 / 56. 55.100
  libavcodec     58. 93.100 / 58. 93.100
  libavformat    58. 47.100 / 58. 47.100
  libavdevice    58. 11.100 / 58. 11.100
  libavfilter     7. 86.100 /  7. 86.100
  libswscale      5.  8.100 /  5.  8.100
  libswresample   3.  8.100 /  3.  8.100
  libpostproc    55.  8.100 / 55.  8.100
Guessed Channel Layout for Input Stream #0.1 : mono
Input #0, rtsp, from 'rtsp://admin:password@192.168.0.121:5542/Streaming/Channels/1':
  Metadata:
    title           : Media Presentation
  Duration: N/A, start: 0.000000, bitrate: N/A
    Stream #0:0: Video: h264 (Main), yuv420p(progressive), 1920x1080, 20 fps, 30 tbr, 90k tbn, 40 tbc
    Stream #0:1: Audio: pcm_mulaw, 8000 Hz, mono, s16, 64 kb/s
Multiple -c, -codec, -acodec, -vcodec, -scodec or -dcodec options specified for stream 0, only the last option '-c:v copy' will be used.
Stream mapping:
  Stream #0:0 -> #0:0 (copy)
  Stream #0:1 -> #0:1 (pcm_mulaw (native) -> aac (native))
Press [q] to stop, [?] for help
[aac @ 000002a2862cb900] Too many bits 8832.000000 > 6144 per frame requested, clamping to max
Output #0, flv, to 'rtmp://a.rtmp.youtube.com/live2/streamcode':
  Metadata:
    title           : Media Presentation
    encoder         : Lavf58.47.100
    Stream #0:0: Video: h264 (Main) ([7][0][0][0] / 0x0007), yuv420p(progressive), 1920x1080, q=2-31, 20 fps, 30 tbr, 1k tbn, 90k tbc
    Stream #0:1: Audio: aac (LC) ([10][0][0][0] / 0x000A), 8000 Hz, mono, fltp, 48 kb/s
    Metadata:
      encoder         : Lavc58.93.100 aac
[flv @ 000002a285413200] Non-monotonous DTS in output stream 0:0; previous: 283, current: 33; changing to 283. This may result in incorrect timestamps in the output file.
[flv @ 000002a285413200] Non-monotonous DTS in output stream 0:0; previous: 283, current: 100; changing to 283. This may result in incorrect timestamps in the output file.
[flv @ 000002a285413200] Non-monotonous DTS in output stream 0:0; previous: 283, current: 133; changing to 283. This may result in incorrect timestamps in the output file.
[flv @ 000002a285413200] Non-monotonous DTS in output stream 0:0; previous: 283, current: 200; changing to 283. This may result in incorrect timestamps in the output file.
[flv @ 000002a285413200] Non-monotonous DTS in output stream 0:0; previous: 283, current: 233; changing to 283. This may result in incorrect timestamps in the output file.
frame=22107 fps= 20 q=-1.0 size=  713271kB time=00:18:25.30 bitrate=5286.4kbits/s speed=   1x

-----------------

This is what I receive this repeating in yellow when something happens to the stream connection:

    [flv @ 0000026847b60040] Non-monotonous DTS in output stream 0:1; previous: 47046874, current: 7601881; changing to 47046874. This may result in incorrect timestamps in the output file.

    


    


    



    Great site for info and I have learned quite a bit so far in my quest to learn programming. There are a bunch of us who live stream to youtube and use ffmpeg. All we want to do is with the least amount of flags in our command line and make it simple to send a live rtsp connection from our cameras to youtube. I know we have some command line interpretations that we have wrong or need to be taken out or added. Could any of you assist with what we would need to resolve our yellow warnings and when it appears the rtsp stream crashes. I apologize with the learning curve for entering code into the post.

    


  • Why console reports a lot of frame drops on my conversion ?

    24 juin 2020, par Sososlik

    I'm trying to convert a mp4 video file to another H265 mp4 video file. During conversion I'm applying crop, trim and a drawbox.

    
The result file looks good to the eye. But the question is why I see a lot of dropped frames on the console during conversion process ? (last line on the log, parameter "drop=").

    
I searched google, but it says that normal if you do framerate conversion, but I'm not doing that and don't want any framerate change, just apply my filters and convert to H265. What I'm doing wrong ?

    


    D:\folder>ffmpeg -y -i "D:\folder\input.mp4" -c:v libx265 -crf 10 -c:a none -vf "drawbox=x=123:y=123:w=123:h=123:color=black:t=fill, crop=616:1192:52:4" -ss 00:06:53.00 -to 00:12:46.00 "D:\folder\output.mp4"
ffmpeg version N-92683-g32601fb821 Copyright (c) 2000-2018 the FFmpeg developers
  built with gcc 8.2.1 (GCC) 20181201
  configuration: --enable-gpl --enable-version3 --enable-sdl2 --enable-fontconfig --enable-gnutls --enable-iconv --enable-libass --enable-libbluray --enable-libfreetype --enable-libmp3lame --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg --enable-libopus --enable-libshine --enable-libsnappy --enable-libsoxr --enable-libtheora --enable-libtwolame --enable-libvpx --enable-libwavpack --enable-libwebp --enable-libx264 --enable-libx265 --enable-libxml2 --enable-libzimg --enable-lzma --enable-zlib --enable-gmp --enable-libvidstab --enable-libvorbis --enable-libvo-amrwbenc --enable-libmysofa --enable-libspeex --enable-libxvid --enable-libaom --enable-libmfx --enable-amf --enable-ffnvcodec --enable-cuvid --enable-d3d11va --enable-nvenc --enable-nvdec --enable-dxva2 --enable-avisynth --enable-libopenmpt
  libavutil      56. 24.101 / 56. 24.101
  libavcodec     58. 42.100 / 58. 42.100
  libavformat    58. 24.100 / 58. 24.100
  libavdevice    58.  6.101 / 58.  6.101
  libavfilter     7. 46.101 /  7. 46.101
  libswscale      5.  4.100 /  5.  4.100
  libswresample   3.  4.100 /  3.  4.100
  libpostproc    55.  4.100 / 55.  4.100
Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'D:\folder\input.mp4':
  Metadata:
    major_brand     : mp42
    minor_version   : 0
    compatible_brands: isommp42
    creation_time   : 2020-03-03T07:49:33.000000Z
    com.android.version: 9
    com.android.capture.fps: 25.000000
  Duration: 00:26:59.81, start: 0.000000, bitrate: 9590 kb/s
    Stream #0:0(eng): Video: h264 (High) (avc1 / 0x31637661), yuv420p(tv, bt709), 720x1280, 9587 kb/s, SAR 1:1 DAR 9:16, 30.80 fps, 90k tbr, 90k tbn, 180k tbc (default)
    Metadata:
      creation_time   : 2020-03-03T07:49:33.000000Z
      handler_name    : VideoHandle
Stream mapping:
  Stream #0:0 -> #0:0 (h264 (native) -> hevc (libx265))
Press [q] to stop, [?] for help
x265 [info]: HEVC encoder version 2.9+9-f74003e88622
x265 [info]: build info [Windows][GCC 8.2.1][64 bit] 8bit+10bit
x265 [info]: using cpu capabilities: MMX2 SSE2Fast SSSE3 SSE4.2 AVX
x265 [info]: Main profile, Level-3.1 (Main tier)
x265 [info]: Thread pool created using 4 threads
x265 [info]: Slices                              : 1
x265 [info]: frame threads / pool features       : 2 / wpp(19 rows)
x265 [info]: Coding QT: max CU size, min CU size : 64 / 8
x265 [info]: Residual QT: max TU size, max depth : 32 / 1 inter / 1 intra
x265 [info]: ME / range / subpel / merge         : hex / 57 / 2 / 2
x265 [info]: Keyframe min / max / scenecut / bias: 25 / 250 / 40 / 5.00
x265 [info]: Lookahead / bframes / badapt        : 20 / 4 / 2
x265 [info]: b-pyramid / weightp / weightb       : 1 / 1 / 0
x265 [info]: References / ref-limit  cu / depth  : 3 / on / on
x265 [info]: AQ: mode / str / qg-size / cu-tree  : 1 / 1.0 / 32 / 1
x265 [info]: Rate Control / qCompress            : CRF-10.0 / 0.60
x265 [info]: tools: rd=3 psy-rd=2.00 rskip signhide tmvp strong-intra-smoothing
x265 [info]: tools: lslices=7 deblock sao
Output #0, mp4, to 'D:\folder\output.mp4':
  Metadata:
    major_brand     : mp42
    minor_version   : 0
    compatible_brands: isommp42
    com.android.capture.fps: 25.000000
    com.android.version: 9
    encoder         : Lavf58.24.100
    Stream #0:0(eng): Video: hevc (libx265) (hev1 / 0x31766568), yuv420p, 616x1192 [SAR 1:1 DAR 77:149], q=2-31, 30.80 fps, 512845807.00 tbn, 30.80 tbc (default)
    Metadata:
      creation_time   : 2020-03-03T07:49:33.000000Z
      handler_name    : VideoHandle
      encoder         : Lavc58.42.100 libx265
frame= 9053 fps=4.7 q=-0.0 size=  119040kB time=00:04:52.93 bitrate=3329.0kbits/s dup=9 drop=1188 speed=0.151x