
Recherche avancée
Médias (1)
-
Bug de détection d’ogg
22 mars 2013, par
Mis à jour : Avril 2013
Langue : français
Type : Video
Autres articles (53)
-
Amélioration de la version de base
13 septembre 2013Jolie sélection multiple
Le plugin Chosen permet d’améliorer l’ergonomie des champs de sélection multiple. Voir les deux images suivantes pour comparer.
Il suffit pour cela d’activer le plugin Chosen (Configuration générale du site > Gestion des plugins), puis de configurer le plugin (Les squelettes > Chosen) en activant l’utilisation de Chosen dans le site public et en spécifiant les éléments de formulaires à améliorer, par exemple select[multiple] pour les listes à sélection multiple (...) -
Le plugin : Podcasts.
14 juillet 2010, parLe problème du podcasting est à nouveau un problème révélateur de la normalisation des transports de données sur Internet.
Deux formats intéressants existent : Celui développé par Apple, très axé sur l’utilisation d’iTunes dont la SPEC est ici ; Le format "Media RSS Module" qui est plus "libre" notamment soutenu par Yahoo et le logiciel Miro ;
Types de fichiers supportés dans les flux
Le format d’Apple n’autorise que les formats suivants dans ses flux : .mp3 audio/mpeg .m4a audio/x-m4a .mp4 (...) -
Organiser par catégorie
17 mai 2013, parDans MédiaSPIP, une rubrique a 2 noms : catégorie et rubrique.
Les différents documents stockés dans MédiaSPIP peuvent être rangés dans différentes catégories. On peut créer une catégorie en cliquant sur "publier une catégorie" dans le menu publier en haut à droite ( après authentification ). Une catégorie peut être rangée dans une autre catégorie aussi ce qui fait qu’on peut construire une arborescence de catégories.
Lors de la publication prochaine d’un document, la nouvelle catégorie créée sera proposée (...)
Sur d’autres sites (5395)
-
License or not ? As website owner do i have to pay license for using ffmpeg (x264) -> mp4 decoding in my webiste ?
28 août 2014, par lindermanI am very confused about my legal or illegal rights to use H.264 mp4 file.
I had long time reading various websites about should i pay license or not ... still cant understand ..
So here is the exact situation :
I have website , where users can upload their videos. Videos are taken with their smart-phones or home cameras , or webcam etc.
After they upload their videos , i am using FFMPEG (x264) to convert the video from 3gp, mov, or even "mp4 to mp4".
Then other users can watch these decoded videos on my website.
I am not charging the end users anything. My website is free for uploaders and viewers.
You will be right if you say that my website have the same purpose as youtube - and you will be right.. video sharing !
So ME - as website owner , hosting buyer and ffmpeg user ... should i have to pay license ? OR ABANDON THE MP4 decoding in my website ?
Thank you
-
I can't seem to install opencv2.4.13 for Python3.4 on Mac El Capitan
11 décembre 2020, par user4351838I have already tried : https://www.youtube.com/watch?v=U49CVY8yOxw.


So I download opencv2.4.13, create the build folder, open cmake, configure, generate and then go to terminal and type in make.


I get this :


Richie's Macbook Air:build Richie$ make
[ 2%] Built target zlib
[ 6%] Built target libtiff
[ 10%] Built target libjpeg
[ 14%] Built target libjasper
[ 16%] Built target libpng
[ 23%] Built target IlmImf
[ 26%] Built target opencv_core
[ 31%] Built target opencv_imgproc
[ 32%] Built target opencv_video
[ 32%] Built target opencv_flann
[ 32%] Building CXX object modules/highgui/CMakeFiles/opencv_highgui.dir/src/cap_ffmpeg.cpp.o
In file included from /Users/Richie/Downloads/opencv-2.4.13/modules/highgui/src/cap_ffmpeg.cpp:45:
/Users/Richie/Downloads/opencv-2.4.13/modules/highgui/src/cap_ffmpeg_impl.hpp:71:6: error: 
 "libswscale is necessary to build the newer OpenCV ffmpeg wrapper"
 #error "libswscale is necessary to build the newer OpenCV ffmpeg wrapper"
 ^
/Users/Richie/Downloads/opencv-2.4.13/modules/highgui/src/cap_ffmpeg_impl.hpp:481:9: error: 
 use of undeclared identifier 'sws_freeContext'
 sws_freeContext(img_convert_ctx);
 ^
/Users/Richie/Downloads/opencv-2.4.13/modules/highgui/src/cap_ffmpeg_impl.hpp:965:17: error: 
 use of undeclared identifier 'SWS_BICUBIC'
 SWS_BICUBIC,
 ^
/Users/Richie/Downloads/opencv-2.4.13/modules/highgui/src/cap_ffmpeg_impl.hpp:998:5: error: 
 use of undeclared identifier 'sws_scale'
 sws_scale(
 ^
/Users/Richie/Downloads/opencv-2.4.13/modules/highgui/src/cap_ffmpeg_impl.hpp:1639:46: error: 
 use of undeclared identifier 'SWS_BICUBIC'
 SWS_BICUBIC,
 ^
/Users/Richie/Downloads/opencv-2.4.13/modules/highgui/src/cap_ffmpeg_impl.hpp:1645:14: error: 
 use of undeclared identifier 'sws_scale'
 if ( sws_scale(img_convert_ctx, input_picture->data,
 ^
/Users/Richie/Downloads/opencv-2.4.13/modules/highgui/src/cap_ffmpeg_impl.hpp:1693:9: error: 
 use of undeclared identifier 'sws_freeContext'
 sws_freeContext(img_convert_ctx);
 ^
/Users/Richie/Downloads/opencv-2.4.13/modules/highgui/src/cap_ffmpeg_impl.hpp:2290:9: warning: 
 ignoring return value of function declared with warn_unused_result
 attribute [-Wunused-result]
 avformat_write_header(oc_, NULL);
 ^~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~
1 warning and 7 errors generated.
make[2]: *** [modules/highgui/CMakeFiles/opencv_highgui.dir/src/cap_ffmpeg.cpp.o] Error 1
make[1]: *** [modules/highgui/CMakeFiles/opencv_highgui.dir/all] Error 2
make: *** [all] Error 2
Richie's Macbook Air:build Richie$ 



From what I can see, it says


"libswscale is necessary to build the newer OpenCV ffmpeg wrapper"



I do have ffmpeg installed (using brew). Does anyone know ?


-
Recapping WebM’s First Week
The WebM project launched last Wednesday with broad industry backing (watch video of the announcement). The list of supporters keeps growing with new additions such as the popular VLC media player, Miro Video Converter, HeyWatch cloud encoding platform, and videantis programmable processor platform. We’re also happy to see that future versions of IE will support playback of VP8 when the user has installed the codec.
Our announcement sparked discussions in the community around the design and quality of our developer release. We’ve done extensive testing of VP8 and know that the codec can match or exceed the quality of other leading codecs. Starting this week, the engineers behind WebM will post frequently to this blog with details on how to make optimal use of its VP8 video codec and Vorbis audio codec. We are confident that the open development model will bring additional improvements that will further optimize WebM. In fact, the power of open development is already visible, with developers submitting patches and the folks at Flumotion enabling live streaming support in their product just three days after the project was launched.
Keep an eye on this blog for regular updates on the adoption and development of WebM. To participate in the conversation or to ask questions of the WebM team, please join our discussion group.
John Luther
Product Manager, Google