Sur d’autres sites (8566)

• Revision 103307 : - Les plugins-dist de spip 3.2 ne sont pas supposé avoir de support ...

  11 juin 2018, par spip.franck@… — Log

   Les plugins-dist de spip 3.2 ne sont pas supposé avoir de support pour qu’il fonctionne avec spip 3.1, donc, j’ai fait un z+1 quand il y avait déjà un "y" de différence entre spip 3.1 et 3.2 sinon, j’ai fait un y+1, ainsi il sera toujours possible de faire des corrections d’éventuel bugs future qui ne concernerait que les plugs de la version 3.1
   La version de mini de compatibilité est maintenant 3.2.0-dev, comme, ça, quand l’alpha sortira, cela devrait être bon (quand la version 3.2.0 stable sortira, je mettrais 3.2.0 comme version mini)
   Il y avait aussi un ou deux mots avec des accents comme par exemple &amp ;#232 ; j’ai fait le changement pour y mettre à la place è ou autres

• passing additional values to s3 event notification for lambda consumption

  8 septembre 2017, par user1790300

  I have to write code in react-native that allows a user to upload videos to amazon s3 to be transcoded for consumption by various devices. For the processing after the upload occurs ; I am reviewing two approaches :

  1) I can use Lambda with ffmpeg to handle the transcoding immediately after the uploading occurs (my fear here would be the amount of time required to transcode the videos and the effect on pricing if it takes a considerable amount of time).

  2) I can have s3 pass an sns message to a rest api after the created event occurs and the rest api generate a rabbitmq message that will be processed by worker that will perform the transcoding using ffmpeg.

  Option 1) seems to be the preferable option based on a completion time perspective. How concerned should I be with using 1) considering how long video transcoding might take as opposed to option 2) ?

  Also, regardless, I need a way to pass additional parameters to lambda or along the sns messaging that would allow me to somehow associate the user who uploaded the video with their account. Is there a way to pass additional text-based values to s3 to pass along to lambda or along sns when the upload completes, as a caveat I plan to upload the video directly to s3 using the rest layer(found this answer here : http://docs.aws.amazon.com/AmazonS3/latest/API/RESTObjectPUT.html#RESTObjectPUT-responses-examples) ?

• How to play mp4 video file with HTML5 video tag on iOS (iPhone and iPad) ?

  22 avril 2015, par Mokielas

  I want to display HTML5 video to my users using the video tag. For Firefox, Chrome and Opera WEBM works as expected. In Safari on Windows and Mac my MP4 version works, too. The only problem I’m experiencing is, that it won’t play on iPad and iPhone (Safari of course).

  Create video

  The MP4 (h.264 + acc-lc) is converted like this (with profile : baseline and level 3.0 for maximum compatibility with iOS) :

  • Stream #0:0(eng) : Video : h264 (Constrained Baseline) (avc1 / 0x31637661), yuv420p, 640x352, 198 kb/s, 17 fps, 17 tbr, 17408 tbn, 34 tbc (default)
  • Stream #0:1(eng) : Audio : aac (LC) (mp4a / 0x6134706D), 48000 Hz, stereo, fltp, 56 kb/s (default)

  Edit : Whole ffprobe output (slight changes in bitrate etc. to the above mentioned) :

  Metadata:
  
  major_brand     : isom
  
  minor_version   : 512
  
  compatible_brands: isomiso2avc1mp41
  
  encoder         : Lavf56.30.100
  
  Duration: 00:01:00.05, start: 0.046440, bitrate: 289 kb/s
  
  Stream #0:0(eng): Video: h264 (Constrained Baseline) 
  
  (avc1 /0x31637661), yuv420p, 640x352, 198 kb/s, 25 fps, 25 tbr, 
  
  12800 tbn, 50 tbc (default)
  
  Metadata:
  
    handler_name    : VideoHandler
  
  Stream #0:1(eng): Audio: aac (LC) (mp4a / 0x6134706D), 44100 Hz, 
  
  stereo, fltp, 85 kb/s (default)
  
  Metadata:
  
    handler_name    : SoundHandler

  I found various requirements for iOS devices like this and this, also someone mentioned to add the yuv420p pixel format when converting.

  In fact the ffmpeg cmd looks like this :

  ffmpeg -i __inputfile__ -vcodec libx264 -pix_fmt yuv420p -profile:v baseline -level 3.0 -b:v 200K -r 17 -bt 800K -c:a libfdk_aac -b:a 85k -ar 44100 -y __outputfile_lowversion__.mp4

  Display video

  With Modernizr I detect which format is "supported" and add it to the src or the video tag. Last thing is adding the right MIME type. For mp4 I add type="video/mp4". The full code for the video tag is :

  <video class="p-video" preload="auto" autoplay="" type="video/mp4" src="http://full.url/to/video_low.mp4"></video>

  I tried various ways : own implementation with own interface, controls and stuff from browser vendors and video.js just to check whether i’m too studip for this. All work in the environments listed above except for iPhone and iPad.

  I read this article on Video on the web, especially this part and only serve the "right" file with the "right" type without a posterattribute set.

  My Apache has

  AddType video/mp4                      mp4 m4v f4v f4p
  
  AddType video/ogg                      ogv
  
  AddType video/webm                     webm

  And byte-ranges are enabled. This is needed to get partial content from the server.

  Has anyone a clue what’s going on there ? Thanks in advance !

  Edit : Safari and Chrome both throw MEDIA_ERR_SRC_NOT_SUPPORTED Error on iPad. There must be an issue with the encoding.