
Recherche avancée
Autres articles (31)
-
La file d’attente de SPIPmotion
28 novembre 2010, parUne file d’attente stockée dans la base de donnée
Lors de son installation, SPIPmotion crée une nouvelle table dans la base de donnée intitulée spip_spipmotion_attentes.
Cette nouvelle table est constituée des champs suivants : id_spipmotion_attente, l’identifiant numérique unique de la tâche à traiter ; id_document, l’identifiant numérique du document original à encoder ; id_objet l’identifiant unique de l’objet auquel le document encodé devra être attaché automatiquement ; objet, le type d’objet auquel (...) -
Support de tous types de médias
10 avril 2011Contrairement à 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) (...)
-
HTML5 audio and video support
13 avril 2011, parMediaSPIP uses HTML5 video and audio tags to play multimedia files, taking advantage of the latest W3C innovations supported by modern browsers.
The MediaSPIP player used has been created specifically for MediaSPIP and can be easily adapted to fit in with a specific theme.
For older browsers the Flowplayer flash fallback is used.
MediaSPIP allows for media playback on major mobile platforms with the above (...)
Sur d’autres sites (4074)
-
qsv : Update ffmpeg qsv_errors to recognize GPU hang and other statuses
28 juillet 2022, par Dmitry Rogozhkinqsv : Update ffmpeg qsv_errors to recognize GPU hang and other statuses
GPU hang is one of the most typical errors on Intel GPUs in
case something goes wrong. It's important to recognize it
explicitly for easier bugs triage. Also, this error code
can be used to trigger GPU recovery path in self-written
applications.There were 2 other statuses which MediaSDK can ppotentially return,
MFX_ERR_NONE_PARTIAL_OUTPUT and MFX_ERR_REALLOC_SURFACE. Adding
them as well.v2 : move MFX_ERR_NONE_PARTIAL_OUTPUT next to MFX_WRN_* (Haihao)
Signed-off-by : Hon Wai Chow <hon.wai.chow@intel.com>
Signed-off-by : Dmitry Rogozhkin <dmitry.v.rogozhkin@intel.com>
Signed-off-by : Haihao Xiang <haihao.xiang@intel.com> -
Crashing Adobe Premiere CC Pro when importing H264 MP4 file
30 octobre 2017, par rpoI am screencasting with kazam in Ubuntu which is h264.
To edit the video i tried to use vegas pro latest version. It only play the audio without any video.
Then i tried to edit it with adobe premier 2017. Whenever i import the file(mp4) the premier pro just crash without any useful message.
I installed quicktime for the codecs but no luck. I also converted the media with Format Factory(http://www.pcfreetime.com/) to MOV ... but premier just crash.
How can i solve this ?
here is the MediaInfo :
General
Complete name : C:\Users\user\Desktop\vdo.mp4
Format : MPEG-4
Format profile : Base Media / Version 2
Codec ID : mp42 (mp42/mp41/isom/iso2)
File size : 23.0 MiB
Duration : 9 min 20 s
Overall bit rate : 344 kb/s
Encoded date : UTC 2017-02-11 06:43:57
Tagged date : UTC 2017-02-11 06:43:57
Video
ID : 1
Format : AVC
Format/Info : Advanced Video Codec
Format profile : High 4:4:4 Predictive@L4
Format settings, CABAC : No
Format settings, ReFrames : 1 frame
Codec ID : avc1
Codec ID/Info : Advanced Video Coding
Duration : 9 min 20 s
Bit rate : 343 kb/s
Maximum bit rate : 2 097 kb/s
Width : 1 674 pixels
Height : 858 pixels
Display aspect ratio : 1.951
Frame rate mode : Constant
Frame rate : 15.000 FPS
Color space : YUV
Chroma subsampling : 4:4:4
Bit depth : 8 bits
Scan type : Progressive
Bits/(Pixel*Frame) : 0.016
Stream size : 22.9 MiB (100%)
Writing library : x264 core 148 r2643 5c65704
Encoding settings : cabac=0 / ref=1 / deblock=0:0:0 / analyse=0:0 / me=dia / subme=0 / psy=1 / psy_rd=1.00:0.00 / mixed_ref=0 / me_range=16 / chroma_me=1 / trellis=0 / 8x8dct=0 / cqm=0 / deadzone=21,11 / fast_pskip=1 / chroma_qp_offset=6 / threads=4 / lookahead_threads=1 / sliced_threads=0 / nr=0 / decimate=1 / interlaced=0 / bluray_compat=0 / constrained_intra=0 / bframes=0 / weightp=0 / keyint=150 / keyint_min=15 / scenecut=0 / intra_refresh=0 / rc=cqp / mbtree=0 / qp=15 / ip_ratio=1.40 / aq=0
Language : English
Encoded date : UTC 2017-02-11 06:43:57
Tagged date : UTC 2017-02-11 06:43:57 -
ffmpeg - Buffer the whole output file before writing to OutputStream
21 mai 2020, par daldoyI'm building a transcoder on AWS Lambda. It reads a video file (of any format) from S3 and it outputs an mp4 file to S3.



When using ffmpeg to stream the output file to S3, it is required to use "-movflags frag_keyframe", and the generated file will be a fragmented mp4.



Is there any way I can write to an OutputStream and get a non-fragmented mp4 ? Something like buffering the whole output file before writing it to the OutputStream ?



Discarded solutions :



- 

-
Write the output file on the /tmp storage of the Lambda function and then copy the non-fragmented mp4 to S3. Problem : it has a limited size of 512 MB.
-
Create a RAM Disk (3008 MB) on AWS Lambda and write the output file there before copying to S3. Problem : it's not possible to create a RAM Disk on AWS Lambda.






-