Recherche avancée

Médias (91)

Autres articles (81)

  • Support de tous types de médias

    10 avril 2011

    Contrairement à beaucoup de logiciels et autres plate-formes modernes de partage de documents, MediaSPIP a l’ambition de gérer un maximum de formats de documents différents qu’ils soient de type : images (png, gif, jpg, bmp et autres...) ; audio (MP3, Ogg, Wav et autres...) ; vidéo (Avi, MP4, Ogv, mpg, mov, wmv et autres...) ; contenu textuel, code ou autres (open office, microsoft office (tableur, présentation), web (html, css), LaTeX, Google Earth) (...)

  • List of compatible distributions

    26 avril 2011, par

    The table below is the list of Linux distributions compatible with the automated installation script of MediaSPIP. Distribution nameVersion nameVersion number Debian Squeeze 6.x.x Debian Weezy 7.x.x Debian Jessie 8.x.x Ubuntu The Precise Pangolin 12.04 LTS Ubuntu The Trusty Tahr 14.04
    If you want to help us improve this list, you can provide us access to a machine whose distribution is not mentioned above or send the necessary fixes to add (...)

  • Automated installation script of MediaSPIP

    25 avril 2011, par

    To overcome the difficulties mainly due to the installation of server side software dependencies, an "all-in-one" installation script written in bash was created to facilitate this step on a server with a compatible Linux distribution.
    You must have access to your server via SSH and a root account to use it, which will install the dependencies. Contact your provider if you do not have that.
    The documentation of the use of this installation script is available here.
    The code of this (...)

Sur d’autres sites (12113)

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


    3. Mediainfo gaves same output as exiftool..

      


    4. 


    


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

    


    Thanks

    


  • Getting Error with node-media-serve and ffmpeg in heroku

    1er juillet 2021, par Anurag Gautam

    I have created a MERN app with video streaming by using node-media-serve module, with following configuration

    


    trans: {
  ffmpeg: '/vendor/ffmpeg',
   tasks: [] ,
   .....
}


    


    In local I have installed ffmpeg in trans.ffmpeg. and its working fine, But how we need to install ffmpeg in heroku .

    


    I have tried by adding heroku buildpacks
heroku buildpacks:add https://github.com/jonathanong/heroku-buildpack-ffmpeg-latest.git but its showing me error. May be some issue with config only.

    


    Heroku error :
2020-09-16T11:23:54.292896+00:00 app[web.1]: 9/16/2020 11:23:54 23 [ERROR] Node Media Trans Server startup failed. ffmpeg:/vendor/ffmpeg cannot be executed.

    


    Guys can you please help me reslove this issue

    


  • Integrate necessary ffmpeg libraries in own project for MCU (microcontrolers) [closed]

    16 septembre 2023, par Borel Kamnang

    I use two ffmpeg commands here :

    


    ffmpeg -i BigBuckBunny_320x180.mp4 -vf scale=192:96,setsar=1:1 outputBBB.mp4
ffmpeg -i outputBBB.mp4 -vf "fps=12,scale=-1:96:flags=lanczos,crop=192:in_h:(in_w-192)/2:0" -c:v rawvideo -pix_fmt rgb565be BigBuckBunny_192x96_12fps.rgb


    


    The first is to downscale an original video and the second is to convert the scaled video to a .rgb format.

    


    As anew user of ffmpeg, I would like to know what are libraries used for that two command to just integrate them in my Arduino IDE C++ project an just call the necessary functions to do the downscale and the conversion.

    


    And another of my concerns is knowing how I can run any ffmpeg in an Raspberry Pi Pico W (RP2040) or ESP32 microcontroller ?

    


    I tried to include the ffmpeg libraries folder in a created Arduino IDE project for Raspberry pico w and the link for files doesn't work. In addition to having the config.h and config components.h files missing in the folder downloaded from the ffmpeg site, there are too many dependencies between .h and .c files.

    


    extern "C" {
  #include "src/ffmpeg/libavcodec/avcodec.h"       
  #include "src/ffmpeg/libavutil/mathematics.h"
}
void setup() {
   Serial.begin(115200);
   delay(10000);
 }
 loop(){
 }


    


    It's been three days today that I've been trying to compile from Arduino IDE, and correct the links in the files.
The problem is also that I don't even have the certainty of what it will work in the Raspberry Pi PicoW or ESP32 afterwards.