
Recherche avancée
Autres articles (61)
-
Use, discuss, criticize
13 avril 2011, parTalk to people directly involved in MediaSPIP’s development, or to people around you who could use MediaSPIP to share, enhance or develop their creative projects.
The bigger the community, the more MediaSPIP’s potential will be explored and the faster the software will evolve.
A discussion list is available for all exchanges between users. -
MediaSPIP v0.2
21 juin 2013, parMediaSPIP 0.2 est la première version de MediaSPIP stable.
Sa date de sortie officielle est le 21 juin 2013 et est annoncée ici.
Le fichier zip ici présent contient uniquement les sources de MediaSPIP en version standalone.
Comme pour la version précédente, 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 (8384)
-
How to Track Website Visitors : Benefits, Tools and FAQs
31 août 2023, par Erin — Analytics Tips, Marketing -
Deno.run not working with —allow-net flag
29 janvier 2021, par Rishi RajI'm trying to use
Deno.run
to execute anffmpeg
subprocess, followed the deno doc here (https://doc.deno.land/https/github.com/denoland/deno/releases/latest/download/lib.deno.d.ts#Deno.run)


const ffmpeg = Deno.run({ cmd: ['--allow-run', '/usr/local/bin/ffmpeg', '-i','-',

 // video codec config: low latency, adaptive bitrate
 '-c:v', 'libx264', '-preset', 'veryfast', '-tune', 'zerolatency',

 // audio codec config: sampling frequency (11025, 22050, 44100), bitrate 64 kbits
 '-c:a', 'aac', '-ar', '44100', '-b:a', '64k',

 //force to overwrite
 '-y',

 // used for audio sync
 '-use_wallclock_as_timestamps', '1',
 '-async', '1',

 //'-filter_complex', 'aresample=44100', // resample audio to 44100Hz, needed if input is not 44100
 //'-strict', 'experimental',
 '-bufsize', '1000',
 '-f', 'flv', 
 // allow run flag
 rtmpUrl]
 }); 




And I get the following error. I'm passing the
--allow-run
flag as the first argument, is there something that I'm missing here ?


error: Uncaught PermissionDenied: access to run a subprocess, run again with the --allow-run flag



-
avcodec/h2645_sei : loosen up min luminance requirements
25 mai 2024, par Niklas Haasavcodec/h2645_sei : loosen up min luminance requirements
The H.265 specification is quite clear on this case :
> When min_display_mastering_luminance is not in the range of 1 to
> 50000, the nominal maximum display luminance of the mastering display
> is unknown or unspecified or specified by other means not specified in
> this Specification.And so the current code is correct in marking luminance data as invalid
if min luminance is set to 0. However, this breaks playback of at least
several real-world Blu-ray releases, for example La La Land, Planet of
the Apes, and quite possibly a lot more. These come with ostensibly
valid max_luminance tags (1000 nits), but min_luminance set to 0.Loosen up this requirement by guarding it behind FF_COMPLIANCE_STRICT.
We still reject blatantly invalid metadata (wrong value range on
luminance, max set to 0, max below min, min above 50 nits etc.), so this
shouldn't cause any unintended regressions.