
Recherche avancée
Autres articles (100)
-
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 (...) -
Websites made with MediaSPIP
2 mai 2011, parThis page lists some websites based on MediaSPIP.
-
Creating farms of unique websites
13 avril 2011, parMediaSPIP platforms can be installed as a farm, with a single "core" hosted on a dedicated server and used by multiple websites.
This allows (among other things) : implementation costs to be shared between several different projects / individuals rapid deployment of multiple unique sites creation of groups of like-minded sites, making it possible to browse media in a more controlled and selective environment than the major "open" (...)
Sur d’autres sites (14110)
-
Révision 20835 : Chouilla de phpdoc. Il y a une fonction vide dans exec/fond introduite par r1800...
26 septembre 2013, par marcimat - -
Révision 21664 : Report de r21663 : #3309 : mettre un fil d’ariane vide pour la page infos_perso
22 octobre 2014, par marcimat ☺☮☯♫ -
Terminal prompt disappears after asyncio script with ffmpeg writing things is run
8 avril 2022, par David II've followed a simple example https://docs.python.org/3/library/asyncio-task.html#running-tasks-concurrently in trying to learn the basics of asyncio.


It works as expected with most commands however when employed with three ffmpeg commands that take an input and write an output, see the example below, the terminal window prompt becomes invisible after the script has (seemingly successfully run). It responds to typed commands and shows the result but the input isn't shown until I start a new terminal session. It's the same with Code's bash terminal as with Kitty.


It doesn't seem to be a "write to file system concurrantly" problem as the echo lines don't produce the problem. The ffprobe commands don't produce it either but "command1" and 2 and 3 always do. It's the same with other ffmpeg commands that write to the file system via a conversion or a split of an audio input file.


The processes exit with 0 and ffmpeg issues most output to stderr so the output looks like




['ffmpeg -y -i "01 Dia Artio.m4a" "oof1.wav"' exited with 0]
[stderr]
ffmpeg version N-104926-gc8b5f2848d Copyright (c) 2000-2021 the FFmpeg developers
built with gcc 11 (GCC)...




import asyncio

async def run(cmd):
 proc = await asyncio.create_subprocess_shell(
 cmd,
 stdout=asyncio.subprocess.PIPE,
 stderr=asyncio.subprocess.PIPE)

 stdout, stderr = await proc.communicate()
 print(f'[{cmd!r} exited with {proc.returncode}]')
 print(f'[stderr]\n{stderr.decode()}')

async def main():
 # Schedule three calls *concurrently*:
 command1 = "ffmpeg -y -i '01 Dia Artio.m4a' 'oof1.wav'"
 command2 = "ffmpeg -y -i '03 Cleansing.m4a' 'oof3.wav'"
 command3 = "ffmpeg -y -i 'The Cranberries - 10 - Dreaming My Dreams.flac' 'oof2.wav'"

 cat1 = "echo 'cat' > cat.txt"
 cat2 = "echo 'kitteh' > kat.txt"
 cat3 = "echo 'eirlyss' > eirlyss.txt"

 ffprobe1 = "ffprobe oof1.wav"
 ffprobe2 = "ffprobe oof2.wav"
 ffprobe3 = "ffprobe oof1.wav"
 await asyncio.gather(
 run(command1),
 run(command2),
 run(command3)
 )
 
 
asyncio.run(main())



This problem has only happened with this combination of asyncio and ffmpeg and it appears consistent and I would very much like to know what might be the cause of it.


I'm on Fedora 35 with Python 3.10.4 and a self built (via ffmpegs instructs) ffmpeg from a few months back).