
Recherche avancée
Autres articles (91)
-
Les sons
15 mai 2013, par -
Soumettre bugs et patchs
10 avril 2011Un logiciel n’est malheureusement jamais parfait...
Si vous pensez avoir mis la main sur un bug, reportez le dans notre système de tickets en prenant bien soin de nous remonter certaines informations pertinentes : le type de navigateur et sa version exacte avec lequel vous avez l’anomalie ; une explication la plus précise possible du problème rencontré ; si possibles les étapes pour reproduire le problème ; un lien vers le site / la page en question ;
Si vous pensez avoir résolu vous même le bug (...) -
Contribute to a better visual interface
13 avril 2011MediaSPIP is based on a system of themes and templates. Templates define the placement of information on the page, and can be adapted to a wide range of uses. Themes define the overall graphic appearance of the site.
Anyone can submit a new graphic theme or template and make it available to the MediaSPIP community.
Sur d’autres sites (6777)
-
Simple Question About Subprocess popen + screen +ffmpeg + youtube-dl
2 juin 2021, par El_Barto_404ffmpeg -i "$(youtube-dl -x -g "https://youtu.be/xhXq9BNndhw")" -f s16le -ac 2 -ar 48000 -acodec pcm_s16le input.raw



can anyone put this inside a popen process after a screen -S Convert ?


I tried already with ' ', with commas.. but nothing


I built a bot on telegram which if you send :


.mandala youtubelink



it takes the link and converts the video from YouTube into a uncompressed file, I need it for a music bot which streams those uncompressed files.


if I run in console :


ffmpeg -i "$(youtube-dl -x -g "https://youtu.be/xhXq9BNndhw")" -f s16le -ac 2 -ar 48000 -acodec pcm_s16le input.raw 



it works but when I try with screen and popen it doesn't.. why ?


@helper.register(pattern=r'.mandala (.+)')
async def mu2342sicbfffffffot(e):
 cheater = e.pattern_match.group(1)
 cheat = cheater
 myorder2224 = ''' "$(youtube-dl -x -g "{}")" '''
 doit = (myorder2224.format(cheater))

 ### I already try to format the variable 
 ### and put doit after -i and 
 ### everything was in '' and commas 
 ### like 'ffmpeg', 'i*, doit, '-f'...
 ### and so on but nothing.. but nope doesn't work.

 p = subprocess.call(['screen','-S','onveter',' ffmpeg -i "$(youtube-dl -x -g "https://www.youtube.com/watch?v=Sw5HQbYGoCA")" -f s16le -ac 1 -acodec pcm_s16le -ar 96k input.pcm'],shell=True)
 await helper.control_panel.send_message(config.chat, "La sto a manna")
 time.sleep(14)
 



I REPEAT ONE MORE TIME :
HOW CAN I USE THAT FFMPEG COMMAND INSIDE A POPEN SUBPROCESS AFTER A Screen -S Convert ?


IF SOMEONE WANT TO KNOW WHY :
Because I want to convert youTube videos to file .raw / .pcm


-
The proper way to limit framerate when recording screen on macOS
5 juillet 2024, par jsxmacOS 14.5, FFmpeg 7.0.1. To record the screen, if I use the code from Wiki, that is,


ffmpeg -f avfoundation -i 1 output.mp4



the frame rate seems to be so high that when I press
q
to stop recording, the following message persists until my MacBook Pro starts to noise by its cooler : "[q] command received. Exiting."

My current solution is to add
-r
after-i
:

ffmpeg -f avfoundation -i 1 -r 24 output.mp4



But I heard that a more correct solution is to replace
-r
with-framerate
and to put it before instead of after-i
:



ffmpeg -f avfoundation -framerate 24 -i 1 output.mp4



Note that I used
-framerate
as an input option instead of-r 24
as an output option, so I'm telling avfoundation to record at 24fps instead of recording at the default fps and then forcing FFmpeg to drop or duplicate frames to give you the desired 24.



This doesn't work for me currently, and appears to be the same as I don't use
-r
at all.

And so, what is the proper way to fix the "too high framerate" issue when recording the screen on macOS ? Do we need
-r
or instead-framerate
, and where to put it, before or after-i
?

Just in case, here is the log of
ffmpeg -f avfoundation -i 1 output.mp4 -v verbose
:

https://github.com/jsx97/test/blob/main/ffmpeg.log


-
Anomalie #4402 (Fermé) : Liste de notices
12 février 2021, par cedric -je ferme ce ticket, car un ticket qui référence un wiki qui liste des patches, ça commence à ressembler à un jeu de pistes
+ depuis novembre 2019 ces notices ont été corrigée
+ maintenant proposer une PR pour chaque cas quand on tombe dessus ça sera beaucoup plus efficace