
Recherche avancée
Médias (1)
-
Bug de détection d’ogg
22 mars 2013, par
Mis à jour : Avril 2013
Langue : français
Type : Video
Autres articles (108)
-
MediaSPIP 0.1 Beta version
25 avril 2011, parMediaSPIP 0.1 beta is the first version of MediaSPIP proclaimed as "usable".
The zip file provided here only contains the sources of MediaSPIP in its standalone version.
To get a working installation, you must manually install all-software dependencies on the server.
If you want to use this archive for an installation in "farm mode", you will also need to proceed to other manual (...) -
MediaSPIP version 0.1 Beta
16 avril 2011, parMediaSPIP 0.1 beta est la première version de MediaSPIP décrétée comme "utilisable".
Le fichier zip ici présent contient uniquement les sources de MediaSPIP en version standalone.
Pour avoir une installation fonctionnelle, il est nécessaire d’installer manuellement l’ensemble des dépendances logicielles sur le serveur.
Si vous souhaitez utiliser cette archive pour une installation en mode ferme, il vous faudra également procéder à d’autres modifications (...) -
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 (16434)
-
I am calling ffmpeg from Python. Getting thread.error and repeated attempts to connect to audio stream
16 février 2016, par user2192778I have some code which calls ffmpeg at a particular time of the day to record a web stream. First, the function that calls ffmpeg...
def record_stream():
ffmpegEXE = "C:/pathtoffmpeg/ffmpeg.exe"
subprocess.call([ffmpegEXE, '-i', http://streamurl.mp3, output.mp3], shell=True)Then, the function which schedules
record_stream
according to the clock...def sched ():
i = 0
while True:
x = datetime.today()
y=x.replace(day=x.day+1, hour=i, minute= start_minute, second=0, microsecond=0)
delta_t=y-x
secs=delta_t.seconds+1
t = Timer(secs,stream_record)
t.start()
i = (i + 1) % 24When I launch the .py program an error reads :
Traceback <most recent="recent" call="call" last="last">
... line X, in <module>
sched ()
... line Y, in sched ()
t.start()
... line Z, in start
_start_new_thread(self.__bootstrap,())
thread.error: can't start new thread
</module></most>Despite the error, the program runs.
When it runs, however, ffmpeg initializes over and over again. It connects to the stream, then connects to the stream again (this time saying "output.mp3 already exists. Overwrite ? Y/N" It will do this ten or so times until it finally just records the stream in a normal way.
How do I fix these errors ? How do I stop this issue with ffmpeg connecting repeatedly ?
-
ffmpeg returning nonsense [closed]
7 février 2012, par MarioI use this command
ffmpeg -i X.mpg -b 533k –vcodec h263 -ac 1 -ab 48k -acodec aac -strict experimental -s 352x288 X.3gp
from cmd to convert file X from mpg to 3gp. I even used this yesterday and it worked.
Today I decided to improve the command :ffmpeg –i X.mpg -b 1000k –r 25 –vcodec h263 -ac 1 -ab 15750 –ar 8000 -acodec libopencore_amrnb -s 352x288 X.3gp
Now ffmpeg is completely screwed up, it returns garbage like
[NULL @ 02EFF020] Unable to find a suitable output format for 'ÔÇôvcodec'
ÔÇôvcodec: Invalid argumentor
[NULL @ 02CBEA80] Unable to find a suitable output format for 'ÔÇôi'
ÔÇôi: Invalid argumenteven if I use the first command, which it worked and now, on the same file, in the same directory, with a new fresh ffmpeg executable from the same archive I extracted it before, it doesn't convert anymore.
If I type a nonexistent file as input, ffmpeg gives[NULL @ 02CBEA80] Unable to find a suitable output format for 'ÔÇôr'
ÔÇôr: Invalid argumentI really don't know what to do. Looks like something really basic has been changed...
-
avutil/hwcontext_vulkan : disable multiplane when deriving from cuda
2 juin 2023, par Philip Langdaleavutil/hwcontext_vulkan : disable multiplane when deriving from cuda
Today, cuda is not able to import multiplane images, and cuda requires
images to be imported whether you trying to import to cuda or export
from cuda (in the later case, the image is imported and then copied
into on the cuda side). So any interop between cuda and vulkan requires
that multiplane be disabled.The existing option for this is not sufficient, because when deriving
devices it is not possible to specify any options.And, it is necessary to derive the Vulkan device, because any pipeline
that involves uploading from cuda to vulkan and then back to cuda must
use the same cuda context on both sides, and the only way to propagate
the cuda context all the way through is to derive the device at each
stage.ie :
vf hwupload=derive_device=vulkan,<filters>,hwupload=derive_device=cuda