Recherche avancée
Autres articles (85)
-
Submit bugs and patches
13 avril 2011Unfortunately a software is never perfect.
If you think you have found a bug, report it using our ticket system. Please to help us to fix it by providing the following information : the browser you are using, including the exact version as precise an explanation as possible of the problem if possible, the steps taken resulting in the problem a link to the site / page in question
If you think you have solved the bug, fill in a ticket and attach to it a corrective patch.
You may also (...) -
Keeping control of your media in your hands
13 avril 2011, parThe vocabulary used on this site and around MediaSPIP in general, aims to avoid reference to Web 2.0 and the companies that profit from media-sharing.
While using MediaSPIP, you are invited to avoid using words like "Brand", "Cloud" and "Market".
MediaSPIP is designed to facilitate the sharing of creative media online, while allowing authors to retain complete control of their work.
MediaSPIP aims to be accessible to as many people as possible and development is based on expanding the (...) -
Personnaliser en ajoutant son logo, sa bannière ou son image de fond
5 septembre 2013, parCertains thèmes prennent en compte trois éléments de personnalisation : l’ajout d’un logo ; l’ajout d’une bannière l’ajout d’une image de fond ;
Sur d’autres sites (14583)
-
Trouble getting HTML5 vidio to play, in Firefox 33
16 janvier 2015, par RandyI’m preparing to update some old pages to HTML5, and was surprised to see that it worked in Chrome, but not the latest Firefox (v.33.1... also tried v.32). What is odd is this... In Firefox it actually WILL play IF you "coax it". If you move the video position slider to someplace beyond the start (about 5 seconds in) and THEN click play, all is well. Further inspection showed that when I click play, the file pointer was jumping to the end of the file leaving my "poster" photo intact, leading the viewer to think there is nothing else they can do. If, however, you manually move the pointer back to anyplace beyond the first couple of seconds of the file (really !), and THEN click the PLAY button, FF will play the rest of the video fine.
Sometimes i think that to the more technically minded among us, the universe doles out the weirder problems, while God laughs.
I’d suspect video file corruption, but all my conversions were made with the very reliable ffmpeg utility, and tested with VLC. Again, it works fine from Chrome, which supposedly uses the same video format. Here’s a link...
FF will play the older type ogv files, so if this is one of those things where FF, now at version 33 is at fault, I’ll have to detect the browser and write the order myself with a document.write(). But it would be nice to know if there is a more straigh forward solution.
Note that I have tried adding the mime types to my HTACESS file. But the fact that the behavior is the same when point my browsers directly the file on my local machine, makles me doubt that is the problem.
http://pixyland.org/peterpan/OurWedding2a.html
And here is the page code
<table align="center" border="1"><tr><td align="center">
<div align="center">
<video width="640" height="480" controls="controls" poster="Imagezz/Wedding/arIMG_2280.JPG">
<source src="../vids/Arrival.mp4" type="video/mp4">
<source src="../vids/Arrival.webm" type="video/webm">
<source src="../vids/Arrival.ogv" type="video/ogg">
<p>If you are unable to view the video, here are some links to download <br />
in a a few well supported video formats. You may be able to just download <br />
and play one of these files without the browser.<br /><br />
<strong>Download Video:</strong>nbsp;
nbsp;<a href="http://stackoverflow.com/feeds/vids/Arrival.mp4">"MP4"</a>
nbsp;<a href="http://stackoverflow.com/feeds/vids/Arrival.webm">"WEBM"</a>
nbsp;<a href="http://stackoverflow.com/feeds/vids/Arrival.ogv">"Ogg"</a>
</p>
</source></source></source></video>
</div>
</td></tr></table> -
Issue #2 when compiling Xuggler for Raspberry pi with libx264
2 août 2014, par Ashish SharmaI am trying to compile Xuggler for Raspberry Pi(Running on Debian OS aka Raspbian),
I followed the ’Basic Build Instructions’ available here for compiling Xuggler.
After I successfully installed all the prerequisites and set the correct paths, I ran the following command :
ant run-testsAfter sometime I am facing the following error and the ant build fails at libx264 :
scroll at the end of log to see the issue
common/arm/mc-c.c: In function âx264_weight_cache_neonâ:
common/arm/mc-c.c:89:25: warning: assignment discards âconstâ qualifier from pointer target type [enabled by default]
common/arm/mc-c.c:94:25: warning: assignment discards âconstâ qualifier from pointer target type [enabled by default]
common/arm/mc-c.c:99:21: warning: assignment discards âconstâ qualifier from pointer target type [enabled by default]
common/arm/mc-c.c:101:21: warning: assignment discards âconstâ qualifier from pointer target type [enabled by default]
common/arm/mc-c.c: In function âx264_mc_init_armâ:
common/arm/mc-c.c:236:19: warning: assignment discards âconstâ qualifier from pointer target type [enabled by default]
common/arm/mc-c.c:237:19: warning: assignment discards âconstâ qualifier from pointer target type [enabled by default]
common/arm/mc-c.c:238:19: warning: assignment discards âconstâ qualifier from pointer target type [enabled by default]
gcc -Wshadow -O3 -fno-fast-math -I/home/pi/Downloads/xuggle-xuggler/build/native/armv6l-unknown-linux-gnueabihf/captive/stage/home/pi/Downloads/xuggler/include -Wall -I. -I. -I'/home/pi/Downloads/xuggle-xuggler/build/native/armv6l-unknown-linux-gnueabihf/captive/stage/home/pi/Downloads/xuggler/include' -std=gnu99 -mcpu=cortex-a8 -mfpu=neon -fPIC -fomit-frame-pointer -fno-tree-vectorize -c -o common/arm/predict-c.o common/arm/predict-c.c
as -I/home/pi/Downloads/xuggle-xuggler/build/native/armv6l-unknown-linux-gnueabihf/captive/stage/home/pi/Downloads/xuggler/include -Wall -I. -I. -I'/home/pi/Downloads/xuggle-xuggler/build/native/armv6l-unknown-linux-gnueabihf/captive/stage/home/pi/Downloads/xuggler/include' -std=gnu99 -mcpu=cortex-a8 -mfpu=neon -c -DPIC -DHIGH_BIT_DEPTH=0 -DBIT_DEPTH=8 -o common/arm/cpu-a.o common/arm/cpu-a.S
as: unrecognized option '-std=gnu99'
make[1]: *** [common/arm/cpu-a.o] Error 1
make[1]: Leaving directory `/home/pi/Downloads/xuggle-xuggler/build/native/armv6l-unknown-linux-gnueabihf/captive/libx264/csrc'
make: *** [all-local] Error 2I am unable to understand the problem statment "unrecognized option ’-std=gnu99’" here, Can someone please tell me how can I resolve this or circumvent it in xuggler ?
-
Issue #2 when compiling Xuggler for Raspberry pi with libx264
2 août 2014, par Ashish SharmaI am trying to compile Xuggler for Raspberry Pi(Running on Debian OS aka Raspbian),
I followed the ’Basic Build Instructions’ available here for compiling Xuggler.
After I successfully installed all the prerequisites and set the correct paths, I ran the following command :
ant run-testsAfter sometime I am facing the following error and the ant build fails at libx264 :
scroll at the end of log to see the issue
common/arm/mc-c.c: In function âx264_weight_cache_neonâ:
common/arm/mc-c.c:89:25: warning: assignment discards âconstâ qualifier from pointer target type [enabled by default]
common/arm/mc-c.c:94:25: warning: assignment discards âconstâ qualifier from pointer target type [enabled by default]
common/arm/mc-c.c:99:21: warning: assignment discards âconstâ qualifier from pointer target type [enabled by default]
common/arm/mc-c.c:101:21: warning: assignment discards âconstâ qualifier from pointer target type [enabled by default]
common/arm/mc-c.c: In function âx264_mc_init_armâ:
common/arm/mc-c.c:236:19: warning: assignment discards âconstâ qualifier from pointer target type [enabled by default]
common/arm/mc-c.c:237:19: warning: assignment discards âconstâ qualifier from pointer target type [enabled by default]
common/arm/mc-c.c:238:19: warning: assignment discards âconstâ qualifier from pointer target type [enabled by default]
gcc -Wshadow -O3 -fno-fast-math -I/home/pi/Downloads/xuggle-xuggler/build/native/armv6l-unknown-linux-gnueabihf/captive/stage/home/pi/Downloads/xuggler/include -Wall -I. -I. -I'/home/pi/Downloads/xuggle-xuggler/build/native/armv6l-unknown-linux-gnueabihf/captive/stage/home/pi/Downloads/xuggler/include' -std=gnu99 -mcpu=cortex-a8 -mfpu=neon -fPIC -fomit-frame-pointer -fno-tree-vectorize -c -o common/arm/predict-c.o common/arm/predict-c.c
as -I/home/pi/Downloads/xuggle-xuggler/build/native/armv6l-unknown-linux-gnueabihf/captive/stage/home/pi/Downloads/xuggler/include -Wall -I. -I. -I'/home/pi/Downloads/xuggle-xuggler/build/native/armv6l-unknown-linux-gnueabihf/captive/stage/home/pi/Downloads/xuggler/include' -std=gnu99 -mcpu=cortex-a8 -mfpu=neon -c -DPIC -DHIGH_BIT_DEPTH=0 -DBIT_DEPTH=8 -o common/arm/cpu-a.o common/arm/cpu-a.S
as: unrecognized option '-std=gnu99'
make[1]: *** [common/arm/cpu-a.o] Error 1
make[1]: Leaving directory `/home/pi/Downloads/xuggle-xuggler/build/native/armv6l-unknown-linux-gnueabihf/captive/libx264/csrc'
make: *** [all-local] Error 2I am unable to understand the problem statment "unrecognized option ’-std=gnu99’" here, Can someone please tell me how can I resolve this or circumvent it in xuggler ?
Syndiquer tout le site
