
Recherche avancée
Autres articles (72)
-
Ecrire une actualité
21 juin 2013, parPrésentez les changements dans votre MédiaSPIP ou les actualités de vos projets sur votre MédiaSPIP grâce à la rubrique actualités.
Dans le thème par défaut spipeo de MédiaSPIP, les actualités sont affichées en bas de la page principale sous les éditoriaux.
Vous pouvez personnaliser le formulaire de création d’une actualité.
Formulaire de création d’une actualité Dans le cas d’un document de type actualité, les champs proposés par défaut sont : Date de publication ( personnaliser la date de publication ) (...) -
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 (...) -
Support audio et vidéo HTML5
10 avril 2011MediaSPIP utilise les balises HTML5 video et audio pour la lecture de documents multimedia en profitant des dernières innovations du W3C supportées par les navigateurs modernes.
Pour les navigateurs plus anciens, le lecteur flash Flowplayer est utilisé.
Le lecteur HTML5 utilisé a été spécifiquement créé pour MediaSPIP : il est complètement modifiable graphiquement pour correspondre à un thème choisi.
Ces technologies permettent de distribuer vidéo et son à la fois sur des ordinateurs conventionnels (...)
Sur d’autres sites (10163)
-
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 ? -
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


-
Header missing in mpg, in spite of using avformat_write_header
23 novembre 2012, par TheSHEEEPI am encoding a live rendered video to mpg and/or mp4 (depends on the later usage of the video) using the ffmpeg C API. When encoding to mp4, everything is well. But when encoding to mpg, the resulting video cannot be played by any player. A quick call to ffprobe on it reveals that the header is missing. But this seems pretty much impossible, as I am explicitly writing it.
This is how I write the header, before any frame is encoded :
// ptr->oc is the AVFormatContext
int error = avformat_write_header(ptr->oc, NULL);
if (error < 0)
{
s_logFile << "Could not write header. Error: " << error << endl;
fprintf(stderr, "Could not write header. Error: '%i'\n", error);
return 1;
}There never is any error when writing the header.
For encoding, I am following the official muxing.c example, so I do set the CODEC_FLAG_GLOBAL_HEADER flag. I use CODEC_ID_MPEG2VIDEO (for video) and CODEC_ID_MP2 (for audio).
The result mpg does work when I "encode" it in an additional step with an external ffmpeg executable like this : "ffmpeg -i ownEncoded.mpg -sameq -y working.mpg".
So it seems all the data is there, only the header is missing for some reason...Here is the only thing ffmpeg is reporting before/when writing the header :
mpeg -------------------
lvl: 24
msg: VBV buffer size not set, muxing may failCould that be the problem ?
I wonder what could be wrong here as I encode mp4 with the exact same function, except setting some special values like qmin, qmax, me_method, etc. when encoding to mp4. Do I probably have to set any special values so that ffmpeg really does write the header correctly ?