Recherche avancée
Autres articles (71)
-
MediaSPIP version 0.1 Beta
16 avril 2011, parMediaSPIP 0.1 beta est la première version de MediaSPIP décrétée comme "utilisable".
Le fichier zip ici présent contient uniquement les sources de MediaSPIP en version standalone.
Pour avoir une installation fonctionnelle, il est nécessaire d’installer manuellement l’ensemble des dépendances logicielles sur le serveur.
Si vous souhaitez utiliser cette archive pour une installation en mode ferme, il vous faudra également procéder à d’autres modifications (...) -
MediaSPIP 0.1 Beta version
25 avril 2011, parMediaSPIP 0.1 beta is the first version of MediaSPIP proclaimed as "usable".
The zip file provided here only contains the sources of MediaSPIP in its standalone version.
To get a working installation, you must manually install all-software dependencies on the server.
If you want to use this archive for an installation in "farm mode", you will also need to proceed to other manual (...) -
Amélioration de la version de base
13 septembre 2013Jolie sélection multiple
Le plugin Chosen permet d’améliorer l’ergonomie des champs de sélection multiple. Voir les deux images suivantes pour comparer.
Il suffit pour cela d’activer le plugin Chosen (Configuration générale du site > Gestion des plugins), puis de configurer le plugin (Les squelettes > Chosen) en activant l’utilisation de Chosen dans le site public et en spécifiant les éléments de formulaires à améliorer, par exemple select[multiple] pour les listes à sélection multiple (...)
Sur d’autres sites (10419)
-
avfilter/vf_vmafmotion : Check dimensions
29 mai 2021, par Michael Niedermayer -
Getting Error with node-media-serve and ffmpeg in heroku
1er juillet 2021, par Anurag GautamI have created a MERN app with video streaming by using
node-media-servemodule, with following configuration

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


In local I have installed
ffmpegintrans.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.gitbut 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


-
FFMPEG doesn't convert with the right Create Date on a MTS to MP4 process
2 novembre 2020, par bob338423I'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 :


- 

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


-
Mediainfo gaves same output as exiftool..








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


Thanks


-
Syndiquer tout le site
