Recherche avancée

Médias (1)

Mot : - Tags -/MediaSPIP

Autres articles (91)

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

  • Participer à sa traduction

    10 avril 2011

    Vous pouvez nous aider à améliorer les locutions utilisées dans le logiciel ou à traduire celui-ci dans n’importe qu’elle nouvelle langue permettant sa diffusion à de nouvelles communautés linguistiques.
    Pour ce faire, on utilise l’interface de traduction de SPIP où l’ensemble des modules de langue de MediaSPIP sont à disposition. ll vous suffit de vous inscrire sur la liste de discussion des traducteurs pour demander plus d’informations.
    Actuellement MediaSPIP n’est disponible qu’en français et (...)

  • Creating farms of unique websites

    13 avril 2011, par

    MediaSPIP platforms can be installed as a farm, with a single "core" hosted on a dedicated server and used by multiple websites.
    This allows (among other things) : implementation costs to be shared between several different projects / individuals rapid deployment of multiple unique sites creation of groups of like-minded sites, making it possible to browse media in a more controlled and selective environment than the major "open" (...)

Sur d’autres sites (20945)

  • FFmpeg proccess killed while converting .mov file

    10 novembre 2020, par Vala Khosravi

    I'm using FFmpeg to reduce my videos file size when I give a .mov file as an input with this command :

    


    ffmpeg -i in.mov -c:a copy -crf 20 out.mov


    


    program start working and after a while, it gets killed. here are the last lines of the log that I get :

    


    Output #0, mov, to '/home/ubuntu/test.mov':
  Metadata:
    major_brand     : qt
    minor_version   : 0
    compatible_brands: qt
    com.apple.quicktime.creationdate: 2020-08-29T15:03:17+0430
    com.apple.quicktime.make: Apple
    com.apple.quicktime.model: MacBookPro14,1
    com.apple.quicktime.software: Mac OS X 10.15.1 (19B88)
    encoder         : Lavf57.83.100
    Stream #0:0(und): Video: h264 (libx264) (avc1 / 0x31637661), yuv420p, 2866x1716 [SAR 1:1 DAR 1433:858], q=-1--1, 60 fps, 15360 tbn, 60 tbc (default)
    Metadata:
      creation_time   : 2020-11-10T09:04:43.000000Z
      handler_name    : Core Media Data Handler
      encoder         : Lavc57.107.100 libx264
    Side data:
      cpb: bitrate max/min/avg: 0/0/0 buffer size: 0 vbv_delay: -1
    Stream #0:1(und): Audio: aac (LC) (mp4a / 0x6134706D), 44100 Hz, stereo, fltp, 207 kb/s (default)
    Metadata:
      creation_time   : 2020-11-10T09:04:43.000000Z
      handler_name    : Core Media Data Handler
Killed   23 fps=3.6 q=0.0 size=       0kB time=00:00:01.34 bitrate=   0.0kbits/s dup=1 drop=0 speed=0.21x


    


    I tried so many different flags for FFmpeg but still getting the same error.

    


    What's the solution ?
here is my input video file

    


  • ffmpeg options for encoding a video mpeg2video but with .mov extension

    20 septembre 2020, par Selene

    I just finished a project, and need to produce an output in the specific format, should be exactly the same as the format of the video I received.
The best way for me to identify the source format was to use ffprobe. Here was the output of that :

    


    Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'input.mov':
  Metadata:
    creation_time   : 2020-02-27T04:15:23.000000Z
  Duration: 00:00:22.13, start: 0.000000, bitrate: 111320 kb/s
    Stream #0:0(eng): Video: mpeg2video (4:2:2) (xd5c / 0x63356478), yuv422p(tv, bt709, top coded first (swapped)), 1920x1080 [SAR 1:1 DAR 16:9], 109779 kb/s, 54.94 fps, 54.94 tbr, 5494 tbn, 50 tbc (default)
    Metadata:
      creation_time   : 2020-02-27T04:15:23.000000Z
      handler_name    : Gestor de contenido de v?deo Apple
      encoder         : XDCAM HD422 1080i50 (50 Mb/s)
    Stream #0:1(eng): Audio: pcm_s16be (twos / 0x736F7774), 48000 Hz, 2 channels, s16, 1536 kb/s (default)
    Metadata:
      creation_time   : 2020-02-27T04:15:23.000000Z
      handler_name    : Gestor de contenido de sonido Apple


    


    I did a lot of video work on the above file, and as part of my pipeline, I converted the file to ProRes4444. Now I need to get this video into the same format as above.

    


    Couple of questions on the format, if I understand it correctly, mpeg2video is mpeg2, this would not normally appear as .mov file, but the source is as mov container. Why ?

    


    Does the encoder from the input format matter ? specifically the XDCAM ?

    


    Alternative to solving my problem would be to use media encoder, but even that application doesn't seem to give me options at mov + mpeg2, and if it is mov, it almost forces to use Apple ProRes to keep high resolution. Also, none of the options allow me to set fps at the source level, which is 54.94, and the closest option I have is 59.94.

    


    Please help,

    


  • FFMPEG doesn't convert with the right Create Date on a MTS to MP4 process

    2 novembre 2020, par bob338423

    I'm on the progress of convert MTS to MP4, with intact video/audio & Creation date.

    


    This is my process :

    


    I have test.MTS and I'm I'll convert it to test.MP4.

    


    Fist.. my MTS :

    


    OSX:oo bob$ f="test.MTS

OSX:oo bob$     DATE=$(exiftool -d "%Y-%m-%d %H:%M:%S"  "$f" | grep "^Date.*Original" | awk '{print $4, $5;}')

OSX:oo bob$     DATE2=$(exiftool -d "%Y-%m-%d %H:%M:%S%z"  "$f" | grep "^Date.*Original" | awk '{print $4, $5;}')

OSX:oo bob$ echo $DATE

2018-10-26 20:53:27

OSX:oo bob$ echo $DATE2

2018-10-26 20:53:27+0000


    


    I took $DATE and $DATE2 in order to have UTC and try different options.

    


    Now, let's see what Exiftool and mediainfo sees about my MTS :

    


    OSX:oo bob$ exiftool $f | grep "Date/Time"

File Modification Date/Time     : 2018:10:26 21:56:55+02:00

File Access Date/Time           : 2020:11:02 16:12:09+01:00

File Inode Change Date/Time     : 2020:11:01 02:48:49+01:00

Date/Time Original              : 2018:10:26 20:53:27+00:00





OSX:oo bob$ mediainfo $f | grep "date"

Recorded date                            : 2018-10-26 20:53:27+00:00


    


    Up to here.. all good Date is 2018-10-26 20:53:27+00:00 (so UTC or GMT+0).

    


    Now my command to convert :

    


    ffmpeg  -i  "$f" -y -acodec aac -ab 128k  -vcodec copy  -f mp4 -metadata creation_time="$DATE" "./${f%.MTS}.MP4"

ffmpeg  -i  "$f" -y -acodec aac -ab 128k  -vcodec copy  -f mp4 -metadata creation_time="$DATE2" "./${f%.MTS}_2.MP4"


    


    I tried 2 options, $DATE (whithout Timezone) and $DATE2 (With timezone). Conversion is ok, let's see the results :

    


    OSX:oo bob$ exiftool   "./${f%.MTS}.MP4" | grep "Date"

File Modification Date/Time     : 2020:11:02 14:53:24+01:00
File Access Date/Time           : 2020:11:02 16:13:48+01:00
File Inode Change Date/Time     : 2020:11:02 14:53:24+01:00
Create Date                     : 2018:10:26 18:53:27
Modify Date                     : 2018:10:26 18:53:27
Track Create Date               : 2018:10:26 18:53:27
Track Modify Date               : 2018:10:26 18:53:27
Media Create Date               : 2018:10:26 18:53:27
Media Modify Date               : 2018:10:26 18:53:27


OSX:oo bob$ exiftool   "./${f%.MTS}_2.MP4" | grep "Date"

File Modification Date/Time     : 2020:11:02 14:53:13+01:00
File Access Date/Time           : 2020:11:02 16:13:48+01:00
File Inode Change Date/Time     : 2020:11:02 14:53:13+01:00
Create Date                     : 2018:10:26 20:53:27
Modify Date                     : 2018:10:26 20:53:27
Track Create Date               : 2018:10:26 20:53:27
Track Modify Date               : 2018:10:26 20:53:27
Media Create Date               : 2018:10:26 20:53:27
Media Modify Date               : 2018:10:26 20:53:27


OSX:oo bob$ mediainfo  "./${f%.MTS}.MP4" | grep "date"

Recorded date                            : 2018-10-26 20:53:27+00:00
Encoded date                             : UTC 2018-10-26 18:53:27
Tagged date                              : UTC 2018-10-26 18:53:27
Encoded date                             : UTC 2018-10-26 18:53:27
Tagged date                              : UTC 2018-10-26 18:53:27
Encoded date                             : UTC 2018-10-26 18:53:27
Tagged date                              : UTC 2018-10-26 18:53:27



OSX:oo bob$ mediainfo  "./${f%.MTS}_2.MP4" | grep "date"

Recorded date                            : 2018-10-26 20:53:27+00:00
Encoded date                             : UTC 2018-10-26 20:53:27
Tagged date                              : UTC 2018-10-26 20:53:27
Encoded date                             : UTC 2018-10-26 20:53:27
Tagged date                              : UTC 2018-10-26 20:53:27
Encoded date                             : UTC 2018-10-26 20:53:27
Tagged date                              : UTC 2018-10-26 20:53:27


    


    Seems up to here that "./${f%.MTS}_2.MP4" (test_2.MP4) is correct, but, if we check the values in epoch :

    


    OSX:oo bob$ exiftool -d "%s" $f | grep "Date/Time"

File Modification Date/Time     : 1540583815
File Access Date/Time           : 1604329945
File Inode Change Date/Time     : 1604195329
Date/Time Original              : 1540587207

OSX:oo bob$ exiftool -d "%s"  "./${f%.MTS}.MP4" | grep "Date"

File Modification Date/Time     : 1604325204
File Access Date/Time           : 1604330053
File Inode Change Date/Time     : 1604325204
Create Date                     : 1540572807
Modify Date                     : 1540572807
Track Create Date               : 1540572807
Track Modify Date               : 1540572807
Media Create Date               : 1540572807
Media Modify Date               : 1540572807



OSX:oo bob$ exiftool -d "%s"  "./${f%.MTS}_2.MP4" | grep "Date"

File Modification Date/Time     : 1604325193
File Access Date/Time           : 1604330058
File Inode Change Date/Time     : 1604325193
Create Date                     : 1540580007
Modify Date                     : 1540580007
Track Create Date               : 1540580007        
Track Modify Date               : 1540580007
Media Create Date               : 1540580007
Media Modify Date               : 1540580007


    


    BTW, I'm now on GMT+1 (this is my local Timezone)

    


    As you can see :

    


      


    1. Conversion with Timezone (test_2.MP4) seems to be correct, except when I use epoch conversion, shows totally diferent time :

      


      Original MTS > Date/Time Original : 1540587207
MP4 without Timezone > Create Date : 1540572807
MP4 with Timezone > Create Date : 1540580007

      


      MTS >> test.MP4 >> 14400 seg (4h)

      


      MTS >> test_2.MP4 >> 7200 seg (2h)

      


      2. 


    2. Mediainfo gaves same output as exiftool..

      


      3. 


    


    ¿¿ ??? What is happening here ?. Why seems the same date but different with exiftool ?. Why 4h or 2h ?... I'm missing something here.

    


    Thanks

    


Navigation