
Recherche avancée
Autres articles (59)
-
Les formats acceptés
28 janvier 2010, parLes commandes suivantes permettent d’avoir des informations sur les formats et codecs gérés par l’installation local de ffmpeg :
ffmpeg -codecs ffmpeg -formats
Les format videos acceptés en entrée
Cette liste est non exhaustive, elle met en exergue les principaux formats utilisés : h264 : H.264 / AVC / MPEG-4 AVC / MPEG-4 part 10 m4v : raw MPEG-4 video format flv : Flash Video (FLV) / Sorenson Spark / Sorenson H.263 Theora wmv :
Les formats vidéos de sortie possibles
Dans un premier temps on (...) -
Publier sur MédiaSpip
13 juin 2013Puis-je poster des contenus à partir d’une tablette Ipad ?
Oui, si votre Médiaspip installé est à la version 0.2 ou supérieure. Contacter au besoin l’administrateur de votre MédiaSpip pour le savoir -
Automated installation script of MediaSPIP
25 avril 2011, parTo 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 (9727)
-
Révision 18140 : r18139 etait tout aussi incorrect que r18120 car, par le jeu des inclusions, la ...
27 juin 2011, par cedric -on teste donc count/strlen selon le type
-
Further SMC Encoding Work
25 août 2011, par Multimedia Mike — GeneralSometimes, when I don’t feel like doing anything else, I look at that Apple SMC video encoder again.
8-bit Encoding
When I last worked on the encoder, I couldn’t get the 8-color mode working correctly, even though the similar 2- and 4-color modes were working fine. I chalked the problem up to the extreme weirdness in the packing method unique to the 8-color mode. Remarkably, I had that logic correct the first time around. The real problem turned out to be with the 8-color cache and it was due to the vagaries of 64-bit math in C. Bit shifting an unsigned 8-bit quantity implicitly results in a signed 32-bit quantity, or so I discovered.Anyway, the 8-color encoding works correctly, thus shaving a few more bytes off the encoding size.
Encoding Scheme Oddities
The next step is to encode runs of data. This is where I noticed some algorithmic oddities in the scheme that I never really noticed before. There are 1-, 2-, 4-, 8-, and 16-color modes. Each mode allows encoding from 1-256 blocks of that same encoding. For example, the byte sequence :0x62 0x45
Specifies that the next 3 4×4 blocks are encoded with single-color mode (of byte 0×62, high nibble is encoding mode and low nibble is count-1 blocks) and the palette color to be used is 0×45. Further, opcode 0×70 is the same except the following byte allows for specifying more than 16 (i.e., up to 256) blocks shall be encoded in the same matter. In light of this repeat functionality being built into the rendering opcodes, I’m puzzled by the existence of the repeat block opcodes. There are opcodes to repeat the prior block up to 256 times, and there are opcodes to repeat the prior pair of blocks up to 256 times.
So my quandary is : What would the repeat opcodes be used for ? I hacked the FFmpeg / Libav SMC decoder to output a histogram of which opcodes are used. The repeat pair opcodes are never seen. However, the single-repeat opcodes are used a few times.
Puzzle Solved ?
I’m glad I wrote this post. Just as I was about to hit “Publish”, I think I figured it out. I haven’t mentioned the skip opcodes yet– there are opcodes that specify that 1-256 4×4 blocks are unchanged from the previous frame. Conceivably, a block could be unchanged from the previous frame and then repeated 1-256 times from there.That’s something I hadn’t thought of up to this point for my proposed algorithm and will require a little more work.
Further reading
-
Revision 5563874783 : Backports from the trunk : flvmeta.c (inject_metadata) : Output file is only opene
11 octobre 2007, par Marc NoirotChanged Paths :
Modify /ChangeLog
Modify /amf.c
Modify /flvmeta.c
Modify /types.c
Modify /types.h
Backports from the trunk :
flvmeta.c (inject_metadata) : Output file is only opened after input file reading
succeeded.
types.h, types.c : Transformed most conversion functions into macros, to improve
execution speed.
amf.c (amf_data_decode, amf_data_encode) : Fixed missing break statements.
amf.c (amf_string_encode) : Forgot to count the string length prefix size.