
Recherche avancée
Autres articles (54)
-
Les autorisations surchargées par les plugins
27 avril 2010, parMediaspip core
autoriser_auteur_modifier() afin que les visiteurs soient capables de modifier leurs informations sur la page d’auteurs -
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 -
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 (11141)
-
Revision 7ab9a9587b : Remove Wextra warnings from vp9_sad.c As a side-effect, the max_sad check is re
13 mai 2014, par Deb MukherjeeChanged Paths :
Modify /test/sad_test.cc
Modify /vp8/common/rtcd_defs.pl
Modify /vp8/common/sad_c.c
Modify /vp8/common/variance.h
Modify /vp8/encoder/mcomp.c
Modify /vp8/encoder/rdopt.c
Modify /vp9/common/vp9_rtcd_defs.pl
Modify /vp9/encoder/vp9_encodeframe.c
Modify /vp9/encoder/vp9_mbgraph.c
Modify /vp9/encoder/vp9_mcomp.c
Modify /vp9/encoder/vp9_rdopt.c
Modify /vp9/encoder/vp9_sad.c
Modify /vp9/encoder/vp9_variance.h
Remove Wextra warnings from vp9_sad.cAs a side-effect, the max_sad check is removed from the
C-implementation of VP8, for consistency with VP9, and to
ensure that the SAD tests common to VP8/VP9 pass.
That will make the VP8 C implementation of sad a little slower
but given that is rarely used in practice, the impact will be
minimal.Change-Id : I7f43089fdea047fbf1862e40c21e4715c30f07ca
-
Revision 56d048c412 : Moving mv entropy encodings calculation to the encoder side. Moved arrays : vp
26 novembre 2013, par Dmitry KovalevChanged Paths :
Modify /vp9/common/vp9_alloccommon.c
Modify /vp9/common/vp9_entropymv.c
Modify /vp9/common/vp9_entropymv.h
Modify /vp9/encoder/vp9_encodemv.c
Modify /vp9/encoder/vp9_encodemv.h
Modify /vp9/encoder/vp9_onyx_if.c
Moving mv entropy encodings calculation to the encoder side.Moved arrays :
vp9_mv_joint_encodings
vp9_mv_class_encodings
vp9_mv_class0_encodings
vp9_mv_fp_encodingsChange-Id : Iaf5008c579fcbd6d77fdd81d1aef8c71b5f308b7
-
Xuggle IMediaWriter error
10 décembre 2013, par prinsenIm testing xuggle and ran into a strange error. I have looked at the example in the documentation, and the xuggle-related code is identical. (http://www.xuggle.com/public/documentation/java/api/com/xuggle/mediatool/IMediaWriter.html)
public class StorageServer {
private final static String storage = "storage.mp4";
private final static IMediaWriter writer = ToolFactory.makeWriter(storage);
private final static Dimension dimension = new Dimension(320, 240);
protected final static Logger logger = LoggerFactory.getLogger(StorageServer.class);
public static void main(String[] args) {
writer.addVideoStream(0, 0, ICodec.ID.CODEC_ID_MPEG4,
320, 240);
//setup the connection
StreamServerAgent serverAgent = new StreamServerAgent(new StreamFrameListenerIMPL(), dimension);
serverAgent.start(new InetSocketAddress("localhost", 1337));
}
protected static class StreamFrameListenerIMPL implements StreamFrameListener {
private volatile long count = 0;
@Override
public void onFrameReceived(IVideoPicture image) {
logger.info("frame received :{}", count++);
if (count < 100) {
logger.info("Writing frame");
writer.encodeVideo(0, image);
} else if (count > 220) {
// writer.flush(); // doesn't matter
writer.close();
}
}
}When writer.close is called I get a runtime exception :
Error: cannot write packet to read only container
Which seems really strange..