
Recherche avancée
Médias (1)
-
The pirate bay depuis la Belgique
1er avril 2013, par
Mis à jour : Avril 2013
Langue : français
Type : Image
Autres articles (31)
-
Submit enhancements and plugins
13 avril 2011If you have developed a new extension to add one or more useful features to MediaSPIP, let us know and its integration into the core MedisSPIP functionality will be considered.
You can use the development discussion list to request for help with creating a plugin. As MediaSPIP is based on SPIP - or you can use the SPIP discussion list SPIP-Zone. -
Que fait exactement ce script ?
18 janvier 2011, parCe script est écrit en bash. Il est donc facilement utilisable sur n’importe quel serveur.
Il n’est compatible qu’avec une liste de distributions précises (voir Liste des distributions compatibles).
Installation de dépendances de MediaSPIP
Son rôle principal est d’installer l’ensemble des dépendances logicielles nécessaires coté serveur à savoir :
Les outils de base pour pouvoir installer le reste des dépendances Les outils de développements : build-essential (via APT depuis les dépôts officiels) ; (...) -
Contribute to documentation
13 avril 2011Documentation is vital to the development of improved technical capabilities.
MediaSPIP welcomes documentation by users as well as developers - including : critique of existing features and functions articles contributed by developers, administrators, content producers and editors screenshots to illustrate the above translations of existing documentation into other languages
To contribute, register to the project users’ mailing (...)
Sur d’autres sites (6756)
-
expecting bitrate : 352 kb/s WAV but getting bitrate 353 kb/s
7 avril 2019, par FindOutIslamNowUsing
ffprobe
to get the converted wav properties, I getInput #0, wav, from '01.wav':
Metadata:
title : 1
album : 1
track : 1
encoder : Lavf58.12.100
Duration: 00:00:02.28, bitrate: 353 kb/s
Stream #0:0: Audio: pcm_s16le ([1][0][0][0] / 0x0001), 22050 Hz, 1 channels, s16, 352 kb/sThe files were converted using the command (windows) :
FOR /R wav_22k_353 %%F in (*.wav) do C:\ffmpeg-4.1-win64-static\bin\ffmpeg -i %%F -acodec pcm_s16le -ar 22050 -ac 1 -b:a 352k wav_22k\%%~nF.wav
Getting 353 instead of 352. Is there any way to solve the issue ?
EDIT
The original files info, for example :
Input #0, wav, from '01.wav':
Metadata:
title : 1
album : 1
track : 1
Duration: 00:00:02.28, bitrate: 354 kb/s
Stream #0:0: Audio: pcm_s16le ([1][0][0][0] / 0x0001), 11025 Hz, 2 channels, s16, 352 kb/s -
avcodec/mpeg12enc : Also inline chroma subsampling
25 décembre 2021, par Andreas Rheinhardtavcodec/mpeg12enc : Also inline chroma subsampling
ff_mpeg1_encode_mb() contains two inlined calls to
mpeg1_encode_mb_internal() ; these calls are supposed
to inline the properties depending upon the color space
used. Yet inlining vertical chroma subsampling (which
allows to remove complete branches and blocks depending
upon them) has been forgotten.Signed-off-by : Andreas Rheinhardt <andreas.rheinhardt@outlook.com>
-
How to distinguish between identical cameras in Libav/ffmpeg ?
6 janvier 2020, par user1810087I have two identical cameras connected and using Libav/FFmpeg. The option settings are :
format = "dshow"
input = "video=Videology USB-C Camera"However, I am not able to distinguish between the two identical cameras. If I try to print out the list of devices, I get the following :
$> FFmpeg -list_devices true -f dshow -i dummy
[dshow @ 02597f60] DirectShow video devices
[dshow @ 02597f60] "Integrated Camera"
[dshow @ 02597f60] "Videology USB-C Camera"
Last message repeated 1 times
[dshow @ 02597f60] DirectShow audio devices
[dshow @ 02597f60] "Microphone (Realtek High Defini"The cameras do appear as the same device, twice. The only thing I see so far, is the USB-port differs in the OS-hardware properties. Is it anyhow possible to distinguish between them ?