Recherche avancée
Autres articles (81)
-
(Dés)Activation de fonctionnalités (plugins)
18 février 2011, parPour gérer l’ajout et la suppression de fonctionnalités supplémentaires (ou plugins), MediaSPIP utilise à partir de la version 0.2 SVP.
SVP permet l’activation facile de plugins depuis l’espace de configuration de MediaSPIP.
Pour y accéder, il suffit de se rendre dans l’espace de configuration puis de se rendre sur la page "Gestion des plugins".
MediaSPIP est fourni par défaut avec l’ensemble des plugins dits "compatibles", ils ont été testés et intégrés afin de fonctionner parfaitement avec chaque (...) -
Activation de l’inscription des visiteurs
12 avril 2011, parIl est également possible d’activer l’inscription des visiteurs ce qui permettra à tout un chacun d’ouvrir soit même un compte sur le canal en question dans le cadre de projets ouverts par exemple.
Pour ce faire, il suffit d’aller dans l’espace de configuration du site en choisissant le sous menus "Gestion des utilisateurs". Le premier formulaire visible correspond à cette fonctionnalité.
Par défaut, MediaSPIP a créé lors de son initialisation un élément de menu dans le menu du haut de la page menant (...) -
Publier sur MédiaSpip
13 juin 2013Puis-je poster des contenus à partir d’une tablette Ipad ?
Oui, si votre Médiaspip installé est à la version 0.2 ou supérieure. Contacter au besoin l’administrateur de votre MédiaSpip pour le savoir
Sur d’autres sites (7768)
-
Zlib vs. XZ on 2SF
I recently released my Game Music Appreciation website. It allows users to play an enormous range of video game music directly in their browsers. To do this, the site has to host the music. And since I’m a compression bore, I have to know how small I can practically make these music files. I already published the results of my effort to see if XZ could beat RAR (RAR won, but only slightly, and I still went with XZ for the project) on the corpus of Super Nintendo chiptune sets. Next is the corpus of Nintendo DS chiptunes.
Repacking Nintendo DS 2SF
The prevailing chiptune format for storing Nintendo DS songs is the .2sf format. This is a subtype of the Portable Sound Format (PSF). The designers had the foresight to build compression directly into the format. Much of payload data in a PSF file is compressed with zlib. Since I already incorporated Embedded XZ into the player project, I decided to try repacking the PSF payload data from zlib -> xz.In an effort to not corrupt standards too much, I changed the ’PSF’ file signature (seen in the first 3 bytes of a file) to ’psf’.
Results
There are about 900 Nintendo DS games currently represented in my website’s archive. Total size of the original PSF archive, payloads packed with zlib : 2.992 GB. Total size of the same archive with payloads packed as xz : 2.059 GB.Using xz vs. zlib saved me nearly a gigabyte of storage. That extra storage doesn’t really impact my hosting plan very much (I have 1/2 TB, which is why I’m so nonchalant about hosting the massive MPlayer Samples Archive). However, smaller individual files translates to a better user experience since the files are faster to download.
Here is a pretty picture to illustrate the space savings :
The blue occasionally appears to dip below the orange but the data indicates that xz is always more efficient than zlib. Here’s the raw data (comes in vanilla CSV flavor too).
Interface Impact
So the good news for the end user is that the songs are faster to load up front. The downside is that there can be a noticeable delay when changing tracks. Even though all songs are packaged into one file for download, and the entire file is downloaded before playback begins, each song is individually compressed. Thus, changing tracks triggers another decompression operation. I’m toying the possibility of some sort of background process that decompresses song (n+1) while playing song (n) in order to help compensate for this.I don’t like the idea of decompressing everything up front because A) it would take even longer to start playing ; and B) it would take a huge amount of memory.
Corner Case
There was at least one case in which I found zlib to be better than xz. It looks like zlib’s minimum block size is smaller than xz’s. I think I discovered xz to be unable to compress a few bytes to a block any smaller than about 60-64 bytes while zlib got it down into the teens. However, in those cases, it was more efficient to just leave the data uncompressed anyway. -
FFMPEG width not divisible by 2 (639x360)
5 octobre 2020, par yasgur99I am using python wrapper command of ffmepeg. I followed the tutorial from here for a "Production ready HLS" : https://docs.peer5.com/guides/production-ready-hls-vod/


This is my code :


subprocess.call(['ffmpeg', '-y', '-i', download_path,
 '-vf', 'scale=w=640:h=360:force_original_aspect_ratio=decrease', \
 '-c:a', 'aac', '-ar', '48000', '-c:v', 'h264', \
 '-profile:v', 'main', '-crf', '20', '-sc_threshold', '0', \
 '-g', '48', '-keyint_min', '48', '-hls_time', '4', \
 '-hls_playlist_type', 'vod', '-b:v', '800k', \
 '-maxrate', '856k', '-bufsize', '1200k', '-b:a', '96k', \
 '-hls_segment_filename', upload_path + \
 '/360p_%03d.ts', upload_path + '/360p.m3u8', \
 '-vf', 'scale=w=842:h=480:force_original_aspect_ratio=decrease', \
 '-c:a', 'aac', '-ar', '48000', '-c:v', 'h264', \
 '-profile:v', 'main', '-crf', '20', '-sc_threshold', '0', \
 '-g', '48', '-keyint_min', '48', '-hls_time', '4', \
 '-hls_playlist_type', 'vod', '-b:v', '1400k', \
 '-maxrate', '1498k', '-bufsize', '2100k', '-b:a', '128k', \
 '-hls_segment_filename', upload_path + \
 '/480p_%03d.ts', upload_path + '/480p.m3u8', \
 '-vf', 'scale=w=1280:h=720:force_original_aspect_ratio=decrease', \
 '-c:a', 'aac', '-ar', '48000', '-c:v', 'h264', \
 '-profile:v', 'main', '-crf', '20', '-sc_threshold', '0', \
 '-g', '48', '-keyint_min', '48', '-hls_time', '4', \
 '-hls_playlist_type', 'vod', '-b:v', '2800k', \
 '-maxrate', '2996k', '-bufsize', '4200k', '-b:a', '128k', \
 '-hls_segment_filename', upload_path + \
 '/720p_%03d.ts', upload_path + '/720p.m3u8', \
 '-vf', 'scale=w=1920:h=1080:force_original_aspect_ratio=decrease', \
 '-c:a', 'aac', '-ar', '48000', '-c:v', 'h264', \
 '-profile:v', 'main', '-crf', '20', '-sc_threshold', '0', \
 '-g', '48', '-keyint_min', '48', '-hls_time', '4', \
 '-hls_playlist_type', 'vod', '-b:v', '5000k', \
 '-maxrate', '5350k', '-bufsize', '7500k', '-b:a', '192k', \
 '-hls_segment_filename', upload_path + '/1080p_%03d.ts', upload_path + '/1080p.m3u8'])


And getting this output


[libx264 @ 0x7fb95500c800] width not divisible by 2 (639x360)
Error initializing output stream 0:0 -- Error while opening encoder for output stream #0:0 - maybe incorrect parameters such as bit_rate, rate, width or height


Any ideas of whats going wrong ?


-
avfilter/vf_vmafmotion : Check dimensions
29 mai 2021, par Michael Niedermayer
Syndiquer tout le site
