
Recherche avancée
Médias (91)
-
Spitfire Parade - Crisis
15 mai 2011, par
Mis à jour : Septembre 2011
Langue : English
Type : Audio
-
Wired NextMusic
14 mai 2011, par
Mis à jour : Février 2012
Langue : English
Type : Video
-
Video d’abeille en portrait
14 mai 2011, par
Mis à jour : Février 2012
Langue : français
Type : Video
-
Sintel MP4 Surround 5.1 Full
13 mai 2011, par
Mis à jour : Février 2012
Langue : English
Type : Video
-
Carte de Schillerkiez
13 mai 2011, par
Mis à jour : Septembre 2011
Langue : English
Type : Texte
-
Publier une image simplement
13 avril 2011, par ,
Mis à jour : Février 2012
Langue : français
Type : Video
Autres articles (41)
-
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 (...) -
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 (...) -
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 (8498)
-
aarch64 : hevc : Specialize put_hevc_\type\()_h*_8_neon for horizontal looping
24 mars 2024, par Martin Storsjöaarch64 : hevc : Specialize put_hevc_\type\()_h*_8_neon for horizontal looping
For widths of 32 pixels and more, loop first horizontally,
then vertically.Previously, this function would process a 16 pixel wide slice
of the block, looping vertically. After processing the whole
height, it would backtrack and process the next 16 pixel wide
slice.When doing 8tap filtering horizontally, the function must load
7 more pixels (in practice, 8) following the actual inputs, and
this was done for each slice.By iterating first horizontally throughout each line, then
vertically, we access data in a more cache friendly order, and
we don't need to reload data unnecessarily.Keep the original order in put_hevc_\type\()_h12_8_neon ; the
only suboptimal case there is for width=24. But specializing
an optimal variant for that would require more code, which
might not be worth it.For the h16 case, this implementation would give a slowdown,
as it now loads the first 8 pixels separately from the rest, but
for larger widths, it is a gain. Therefore, keep the h16 case
as it was (but remove the outer loop), and create a new specialized
version for horizontal looping with 16 pixels at a time.Before : Cortex A53 A72 A73 Graviton 3
put_hevc_qpel_h16_8_neon : 710.5 667.7 692.5 211.0
put_hevc_qpel_h32_8_neon : 2791.5 2643.5 2732.0 883.5
put_hevc_qpel_h64_8_neon : 10954.0 10657.0 10874.2 3241.5
After :
put_hevc_qpel_h16_8_neon : 697.5 663.5 705.7 212.5
put_hevc_qpel_h32_8_neon : 2767.2 2684.5 2791.2 920.5
put_hevc_qpel_h64_8_neon : 10559.2 10471.5 10932.2 3051.7Signed-off-by : Martin Storsjö <martin@martin.st>
-
avcodec/dxvenc, hap(dec|enc) : Move TextureDSPContext to stack
24 janvier 2024, par Andreas Rheinhardt -
Error : Error : Cannot find module '@ffmpeg.wasm/core-mt' Require stack :
30 septembre 2023, par JamesI'm getting this error "Error : Error : Cannot find module '@ffmpeg.wasm/core-mt', When my code is deployed on Vercel (Node.js + TypeScript) Does I get confused because when I try to run the same code on my local machine it works fine


But as I deploy it on Vercel it gives that error. Obviously, i do have "@ffmpeg.wasm/core-mt" installed as said in the package https://github.com/FFmpeg-wasm/FFmpeg.wasm#installation So how do I fix it ?


I'm currently using it like this


import { FFmpeg } from "@ffmpeg.wasm/main";

async function myFunction() {
 const ffmpeg = await FFmpeg.create({
 core: "@ffmpeg.wasm/core-mt",
 log: true,
 });
}



However, in the docs, i see doing like this


import { FFmpeg } from "@ffmpeg.wasm/main";
 
 const ffmpeg = await FFmpeg.create({
 core: "@ffmpeg.wasm/core-mt",
 log: true,
 });

 async function myFunction() {
 // use ffmpeg here
 }



But then i start getting errors like "top-level 'await' expressions are only allowed when the 'module' option is set to 'es2022', 'esnext', 'system', 'node16', or 'nodenext', and the 'target' option is set to 'es2017' or higher."


I tried a couple of StackOverflow solutions but nothing works in my case. So what should I do ?


tsconfig.json :


{
 "compilerOptions": {
 "module": "CommonJS",
 "esModuleInterop": true,
 "allowSyntheticDefaultImports": true,
 "target": "es2017",
 "noImplicitAny": true,
 "moduleResolution": "node",
 "sourceMap": true,
 "outDir": "dist",
 "baseUrl": ".",
 "paths": {
 "*": ["node_modules/*", "src/types/*"]
 }
 },
 "include": ["./src/**/*", "src/firebase/serviceAccountKey.ts"]
 }