
Recherche avancée
Médias (1)
-
Rennes Emotion Map 2010-11
19 octobre 2011, par
Mis à jour : Juillet 2013
Langue : français
Type : Texte
Autres articles (38)
-
Installation en mode ferme
4 février 2011, parLe mode ferme permet d’héberger plusieurs sites de type MediaSPIP en n’installant qu’une seule fois son noyau fonctionnel.
C’est la méthode que nous utilisons sur cette même plateforme.
L’utilisation en mode ferme nécessite de connaïtre un peu le mécanisme de SPIP contrairement à la version standalone qui ne nécessite pas réellement de connaissances spécifique puisque l’espace privé habituel de SPIP n’est plus utilisé.
Dans un premier temps, vous devez avoir installé les mêmes fichiers que l’installation (...) -
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 -
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 (7742)
-
Error when transcode webm to mp4 using ffmpeg.wasm
17 février 2021, par arpoI have this webm file recorded using MediaRecorder in Chrome.
https://cdn.hibervr.com/video/loop3.webm


When I try to transcode it using ffmpeg.wasm, https://github.com/ffmpegwasm/ffmpeg.wasm


Using this codepen, taken from the official site :
https://codepen.io/jeromewu/pen/NWWaMeY


I get this error in the console and the file isn't playable.


net::ERR_REQUEST_RANGE_NOT_SATISFIABLE



Any clues about how to fix it ?


It works using other webm files like this.
https://phoboslab.org/files/ffmpeg-mt-fixed/jumparound.webm


-
Chromium Build Failed on Windows:D3D Compiler DLL (\third_party\angle\src)
31 mars 2016, par VishI have followed same step mentioned in this question. Few extra flag I have set get propriety FFMPEG codec. Its failing every time, with following logs.
[233/19712] ACTION Copying D3D Compiler DLL...
FAILED: F:\Chrome\depot_tools\python276_bin\python.exe gyp-win-tool action-wrapper environment.x86 copy_compiler_dll_target_copy_dll_a30e198148542d4bce19a5c818c6884f..rsp ..\..\third_party\angle\src
[233/19712] CC obj\third_party\icu\source\stubdata\icuuc.stubdata.obj
ninja: build stopped: subcommand failed.For FFMPEG using following set command :
set GYP_DEFINES=branding=Chromium buildtype=Official component=shared_library disable_nacl=1 enable_automation=0 enable_captive_portal_detection=0 enable_google_now=0 enable_hidpi=0 fastbuild=1 ffmpeg_branding=Chrome incremental_chrome_dll=0 proprietary_codecs=1 remoting=0
My System Information Details :
Windows 10 64 Bit 8 GB RAM. Trail Version of Visual Studio 2015
Installed, but now it is expired. Now I have installed Community
Version 2013 update 4.Does it effect both version effect the execution ? Checked in path, its using
Window Kit 8.1
. What other part should I check for successful execution ? -
OpenCV ffmpeg DLL not loaded when running app on Windows 7, works on 8 and 10
2 novembre 2016, par David G.I need to maintain a desktop app written in C++, using Qt and OpenCV for some video processing. As far as I understood, the decoding part of OpenCV is delegated to ffmpeg in a separate DLL for licensing reasons.
The development environment is on Windows 10, using QT Creator and MSVC12 64-bit as compiler. OpenCV version is 3.0, the official distribution. Here, everything runs fine, I am able to decode a video using VideoCapture::open().
Issues arise when I try to run the application in a standalone fashion with all the required DLLs in the same folder as the .exe file. All cases below are 64-bit OSes.
On a Windows 10 computer, not the same as the developement machine and no developer libraries present, the video decoding works fine. I have tested on a Windows 8 machine as well, no issues so far.
On Windows 7, the things get tricky. The same video files that successfully load during the previous tests are not recognized by the app at all i.e. the isOpened call on VideoCapture returns false. For further testing, I stripped the opencv_ffmpeg300_64.dll file to narrow down the issue on Windows 10 and 8 ; as expected, without this DLL the app is no more able to open the same video files.
It seems that the DLL is simply not recognized on Windows 7.
Edit : Further investigation using Process Explorer clearly shows that the aforementioned DLL is not loaded when the app runs on Windows 7.
- Is there something specific about how Windows 7 manages the DLL path resolution and eventual security measures ? Seems normal that the first search location is the same folder as the executable, which is the case here.
I have tried to trace using WinApiOverride32, with no results.