
Recherche avancée
Médias (1)
-
La conservation du net art au musée. Les stratégies à l’œuvre
26 mai 2011
Mis à jour : Juillet 2013
Langue : français
Type : Texte
Autres articles (57)
-
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 -
Des sites réalisés avec MediaSPIP
2 mai 2011, parCette page présente quelques-uns des sites fonctionnant sous MediaSPIP.
Vous pouvez bien entendu ajouter le votre grâce au formulaire en bas de page. -
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 (10782)
-
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"]
 }



-
No module named 'skvideo.io.ffmpeg' in the project
12 juillet 2024, par kyoboEven though I have installed the scikit-video and installed ffmpeg, I still meet this problem :

No module named 'skvideo.io.ffmpeg


Output :


(sd) huishi@huishi:~/workspace/projectsideo_python$ **pip install scikit-video**
Requirement already satisfied: scikit-video in /home/huishi/anaconda3/envs/sdb/python3.8/site-packages (1.1.11)
Requirement already satisfied: scipy in /home/huishi/anaconda3/envs/sdb/python3.8/site-packages (from scikit-video) (1.8.1)
Requirement already satisfied: pillow in /home/huishi/anaconda3/envs/sdb/python3.8/site-packages (from scikit-video) (9.2.0)
Requirement already satisfied: numpy in /home/huishi/anaconda3/envs/sdb/python3.8/site-packages (from scikit-video) (1.23.0)
(sd) huishi@huishi:~/workspace/projectsideo_python$ **sudo apt-get install ffmpeg**
正在读取软件包列表... 完成
正在分析软件包的依赖关系树 
正在读取状态信息... 完成 
ffmpeg 已经是最新版 (7:3.4.11-0ubuntu0.1)。
下列软件包是自动安装的并且现在不需要了:
 docker-scan-plugin gir1.2-goa-1.0 gir1.2-snapd-1
使用'sudo apt autoremove'来卸载它(它们)。
升级了 0 个软件包,新安装了 0 个软件包,要卸载 0 个软件包,有 20 个软件包未被升级。
(sd) huishi@huishi:~/workspace/projectsideo_python$ python RabbitMqUtils.py 
The license has expired.
/home/huishi/workspace/projectsideo_python/train_resource/train_split.py:12: YAMLLoadWarning: calling yaml.load() without Loader=... is deprecated, as the default Loader is unsafe. Please read https://msg.pyyaml.org/load for full details.
 tr_configs = yaml.load(f)
INFO: Created TensorFlow Lite XNNPACK delegate for CPU.
/home/huishi/anaconda3/envs/sdb/python3.8/site-packages/skvideo/__init__.py:306: UserWarning: ffmpeg/ffprobe not found in path: /usr/local/bin
 warnings.warn("ffmpeg/ffprobe not found in path: " + str(path), UserWarning)
Traceback (most recent call last):
 File "RabbitMqUtils.py", line 17, in <module>
 from video_postprocess import post_Process
 File "/home/huishi/workspace/projectsideo_pythonideo_postprocess/post_Process.py", line 12, in <module>
 import skvideo.io
 File "/home/huishi/anaconda3/envs/sdb/python3.8/site-packages/skvideo/io/__init__.py", line 8, in <module>
 from .ffmpeg import *
ModuleNotFoundError: **No module named 'skvideo.io.ffmpeg'**
(sd) huishi@huishi:~/workspace/projectsideo_python$
</module></module></module>


I have tried to upgrade pip and skvideo but it doesn't work.


How can I solve this problem ?


-
nginx rtmp-module can't execute ffmpeg
6 juin 2023, par NasirI am having an issue with nginx-rtmp-module exec ffmpeg command. i have followed the example on 
www.github.com/arut/nginx-rtmp-module



/home/junaid/bin/ffmpeg -f video4linux2 -i /dev/video1 -c:v libx264 -an -f flv rtmp://127.0.0.1:1935/myapp/mystream




the command is working fine in terminal



Config file :



rtmp {
server {
 listen 1935;
 ping 30s;
 notify_method get;

 application myapp {
 live on;
 allow play all;
 exec_static /home/junaid/bin/ffmpeg -f video4linux2 -i /dev/video1 -c:v libx264 -an -f flv rtmp://127.0.0.1:1935/myapp/mystream; 
 }
}




Error log :
http://www.codepad.org/enD4wlZ9



I have tried :



- 

- nginx running as root (have permission to execute ffmpeg)
- using ip instead of localhost
- using complete path to ffmpeg
- executing bash file (having ffmpeg and echo commands : echo commands execute just fine) from nginx











please help me resolve this issue