
Recherche avancée
Médias (1)
-
The Great Big Beautiful Tomorrow
28 octobre 2011, par
Mis à jour : Octobre 2011
Langue : English
Type : Texte
Autres articles (43)
-
La file d’attente de SPIPmotion
28 novembre 2010, parUne file d’attente stockée dans la base de donnée
Lors de son installation, SPIPmotion crée une nouvelle table dans la base de donnée intitulée spip_spipmotion_attentes.
Cette nouvelle table est constituée des champs suivants : id_spipmotion_attente, l’identifiant numérique unique de la tâche à traiter ; id_document, l’identifiant numérique du document original à encoder ; id_objet l’identifiant unique de l’objet auquel le document encodé devra être attaché automatiquement ; objet, le type d’objet auquel (...) -
Ajouter des informations spécifiques aux utilisateurs et autres modifications de comportement liées aux auteurs
12 avril 2011, parLa manière la plus simple d’ajouter des informations aux auteurs est d’installer le plugin Inscription3. Il permet également de modifier certains comportements liés aux utilisateurs (référez-vous à sa documentation pour plus d’informations).
Il est également possible d’ajouter des champs aux auteurs en installant les plugins champs extras 2 et Interface pour champs extras. -
Possibilité de déploiement en ferme
12 avril 2011, parMediaSPIP peut être installé comme une ferme, avec un seul "noyau" hébergé sur un serveur dédié et utilisé par une multitude de sites différents.
Cela permet, par exemple : de pouvoir partager les frais de mise en œuvre entre plusieurs projets / individus ; de pouvoir déployer rapidement une multitude de sites uniques ; d’éviter d’avoir à mettre l’ensemble des créations dans un fourre-tout numérique comme c’est le cas pour les grandes plate-formes tout public disséminées sur le (...)
Sur d’autres sites (5345)
-
Conflict between FFmpeg and Vitamio
16 juin 2016, par Âu Mậu DươngI need your help.
When I add vitamio library to my projet. it error out :FATAL EXCEPTION : main Process : inetwork.tictictalk.chat, PID :
24161
java.lang.UnsatisfiedLinkError : org.bytedeco.javacpp.avutil
at java.lang.Class.classForName(Native Method)
at java.lang.Class.forName(Class.java:308)
at org.bytedeco.javacpp.Loader.load(Loader.java:413)
at org.bytedeco.javacpp.Loader.load(Loader.java:381)
at org.bytedeco.javacpp.avcodec$AVPacket.(avcodec.java:1650)
at org.bytedeco.javacv.FFmpegFrameRecorder.(FFmpegFrameRecorder.java:149)
at com.uniprogy.streamini.streamingScreen.activities.StreamingActivityCV.initRecorder(StreamingActivityCV.java:280)
at com.uniprogy.streamini.streamingScreen.activities.StreamingActivityCV.startRecording(StreamingActivityCV.java:305)
at com.uniprogy.streamini.streamingScreen.activities.StreamingActivityCV.startStreaming(StreamingActivityCV.java:380)
at com.uniprogy.streamini.streamingScreen.fragments.StreamingFragment.onActivityCreated(StreamingFragment.java:109)
at android.support.v4.app.Fragment.performActivityCreated(Fragment.java:1983)
at android.support.v4.app.FragmentManagerImpl.moveToState(FragmentManager.java:1092)
at android.support.v4.app.FragmentManagerImpl.moveToState(FragmentManager.java:1252)at android.support.v4.app.BackStackRecord.run(BackStackRecord.java:738)
at android.support.v4.app.FragmentManagerImpl.execPendingActions(FragmentManager.java:1617)
at android.support.v4.app.FragmentManagerImpl$1.run(FragmentManager.java:517)
at android.os.Handler.handleCallback(Handler.java:739)
at android.os.Handler.dispatchMessage(Handler.java:95)
at android.os.Looper.loop(Looper.java:145)
at android.app.ActivityThread.main(ActivityThread.java:5951)
at java.lang.reflect.Method.invoke(Native Method)
at java.lang.reflect.Method.invoke(Method.java:372)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1399)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1194)If I delete vitamio, my project work well.
I use vitamio 4.0 : https://github.com/yixia/VitamioBundle -
v4l2loopback device detected by Chrome, not seen by Zoom or Firefox
14 novembre 2020, par uri sh.I am trying to create a loopback device from my webcam to be accessible from both Zoom and a browser. I created three v4l2loopback devices :


sudo modprobe v4l2loopback devices=3 video_nr=10,11,12 card_label="Loopback_1","Loopback_2","Virtual_cam" exclusive_caps=1,1,0



followed by :


ffmpeg -i /dev/video0 -f v4l2 -vcodec rawvideo -pix_fmt yuv420p /dev/video10 -f v4l2 /dev/video11



Both devices are detected by Chrome, yet not seen by either Zoom nor Firefox.
Following advice on other questions on stackoverflow I tried setting the device properties using v4l2loopback-ctl, using
v4l2loopback-ctl set-caps "video/x-raw,format=UYVY,width=640,height=480" /dev/video10
, and got in response :



Setting pipeline to PAUSED ...
ERROR : Pipeline doesn't want to pause.
ERROR : from element /GstPipeline:pipeline0/GstV4l2Sink:v4l2sink0 : Device '/dev/video10' is not a output device.
Additional debug info :
v4l2_calls.c(636) : gst_v4l2_open () : /GstPipeline:pipeline0/GstV4l2Sink:v4l2sink0 :
Capabilities : 0x85208000
Setting pipeline to NULL ...
Freeing pipeline ...
output to /dev/video10 failed




I also tried using gst-launch-1.0 :


gst-launch-1.0 v4l2src device=/dev/video0 ! v4l2sink device=/dev/video10



which tells me that /dev/video10 is not an output device :




Setting pipeline to PAUSED ...
ERROR : Pipeline doesn't want to pause.
ERROR : from element /GstPipeline:pipeline0/GstV4l2Sink:v4l2sink0 : Device '/dev/video10' is not a output device.
Additional debug info :
v4l2_calls.c(636) : gst_v4l2_open () : /GstPipeline:pipeline0/GstV4l2Sink:v4l2sink0 :
Capabilities : 0x85208000
Setting pipeline to NULL ...
Freeing pipeline ...




I am running Xubuntu 20.04, kernel version 5.4.0-52-generic, with v4l2loopback-dkms v.0.12.3-1ubuntu0.1, and v4l2loopback-utils.


My goal here is to get a device to be consumed by a desktop Node.js server which will open up a web app using
xdg-open
(thus the need for both Chrome AND Firefox), which will output a processed videostream that could be consumed by a video chat app, such as Zoom or Jitsi.

Any help will be greatly appreciated.


-
Why is the ffmpeg process in discordpy terminating without playing anything ?
18 janvier 2024, par Bummbumm6I'm making a discord bot for playing music (ik very unoriginal) and everytime I try to play music, it gives this error :


2023-02-18 12:31:54 INFO discord.player ffmpeg process 4024 has not terminated. Waiting to terminate...
2023-02-18 12:31:54 INFO discord.player ffmpeg process 4024 should have terminated with a return code of -9.



It is in the voice chat and didn't play anything. Here's my code if you need it :


print("defining functions")
import discord, pytube, os, threading
from moviepy import editor
from discord.ext.commands import Bot
intents=discord.Intents.default()
intents.message_content = True
intents.voice_states = True
bot = Bot("b!",intents=intents)
check = False
token = "redacted"
@bot.command()
async def play(ctx, arg):
 await ctx.send("Downloading...")
 try:
 yt = pytube.YouTube(arg)
 print("STREAM: "+str(yt.streams.filter(only_audio=True,mime_type="audio/webm",type="audio",abr="160kbps")))
 def download(yt):
 print("DOWNLOADING STREAM TO AUDIO.WEBM")
 yt.streams.filter(only_audio=True,mime_type="audio/webm",type="audio",abr="160kbps").order_by("abr").first().download(filename="audio.webm")
 print("EXPORTING TO MP3")
 editor.AudioFileClip("audio.webm").write_audiofile("audio.webm"[:-5] + ".mp3")
 os.remove("audio.webm")
 print("DONE")
 thread = threading.Thread(target=download, args=(yt,))
 thread.start()
 thread.join()
 try:
 channel = ctx.author.voice.channel
 try:
 vc = await channel.connect()
 except Exception:
 ctx.send("already in vc, one sec")
 except Exception:
 pass
 vc.play(discord.FFmpegPCMAudio(source="audio.mp3", executable="./ffmpeg"))
 except Exception:
 pass
bot.run(token)




It worked on my computer in VS Code, but I wanted to test it on Replit and only there I got the error. I tried :


- 

- Reinstalling discord, pynacl, even pytube and moviepy.
- Using a local copy of ffmpeg on replit, see line 36.
- Adding the intents that were described in a different thread.








One thing that always happens is the exit code being -9 but the process number changing (ofc). I saw a GitHub Issue about this too which is not showing a fix so how do I fix that ?