Recherche avancée
Autres articles (101)
-
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 (...) -
Contribute to translation
13 avril 2011You can help us to improve the language used in the software interface to make MediaSPIP more accessible and user-friendly. You can also translate the interface into any language that allows it to spread to new linguistic communities.
To do this, we use the translation interface of SPIP where the all the language modules of MediaSPIP are available. Just subscribe to the mailing list and request further informantion on translation.
MediaSPIP is currently available in French and English (...) -
Prérequis à l’installation
31 janvier 2010, parPréambule
Cet article n’a pas pour but de détailler les installations de ces logiciels mais plutôt de donner des informations sur leur configuration spécifique.
Avant toute chose SPIPMotion tout comme MediaSPIP est fait pour tourner sur des distributions Linux de type Debian ou dérivées (Ubuntu...). Les documentations de ce site se réfèrent donc à ces distributions. Il est également possible de l’utiliser sur d’autres distributions Linux mais aucune garantie de bon fonctionnement n’est possible.
Il (...)
Sur d’autres sites (7248)
-
doc/examples/extract_mvs : add motion information
12 septembre 2022, par Chema Gonzalezdoc/examples/extract_mvs : add motion information
Note that the motion information includes subpel motion information
This was likely forgotten in 56bdf61baa04c4fd8d165f34499115ce0aa97c43.
Tested :
```
$ make examples -j
...
$ doc/examples/extract_mvs in.264 | head -40 | \
csvcut -C framenum,source,flags |csvlookblockw blockh srcx srcy dstx dsty motion_x motion_y motion_scale ------ ------ ----- ---- ----- ---- -------- -------- ------------ 16 16 20 26 8 8 49 72 4 16 16 152 15 136 8 65 28 4 16 8 360 3 360 4 1 -6 4 16 8 360 13 360 12 -1 4 4 16 16 440 10 440 8 3 10 4 8 16 829 7 836 8 -31 -6 4 8 16 844 7 844 8 -1 -4 4 16 16 1,004 14 1,048 8 -177 24 4 16 16 1,096 8 1,096 8 -1 0 4 16 8 1,417 24 1,416 4 7 82 4 16 8 1,416 13 1,416 12 0 6 4 16 8 87 20 88 20 -7 0 4 16 8 99 44 88 28 45 66 4 ...
```Also :
```
$ make fate -j
...
```Signed-off-by : Michael Niedermayer <michael@niedermayer.cc>
-
lavc/vvc : Don't check motion estimation region for IBC
28 novembre 2024, par Frank Plowmanlavc/vvc : Don't check motion estimation region for IBC
The final parameter of check_available determines whether the motion
estimation region constraints imposed in section 8.5.2.3 of H.266 (V3)
on MVP candidates apply to the current candidate or not. In the case of
IBC spatial merge candidates they do not, as their availability is
dependent only on the criteria described in sections 8.6.2.3 and 6.4.4,
which do not include this constraint on the motion estimation region.Signed-off-by : Frank Plowman <post@frankplowman.com>
-
Extract individual macroblock types and their corresponding motion vectors [closed]
14 mai 2023, par Prajit KumarI need to make a pair for each macroblock from a frame of a video containing its type and motion vector.


I extracted motion vectors by using the python module of mv-extractor.


For macroblock type I used ffmpeg command :
ffmpeg -threads 1 -debug 'mb_type' -i file.h264 -f null -

The info received from ffmpeg command doesn't match with the location of motion vectors extracted (Macroblocks which are divided into smaller blocks of size 8X16 or 16X8 do not match with the info of macroblock size received in motion vector info). Also, the ffmpeg command for extracting macroblock type doesn't work properly on some videos.


Can you please tell a more streamlined way of doing this task.


Syndiquer tout le site
