
Recherche avancée
Autres articles (35)
-
La file d’attente de SPIPmotion
28 novembre 2010, parUne file d’attente stockée dans la base de donnée
Lors de son installation, SPIPmotion crée une nouvelle table dans la base de donnée intitulée spip_spipmotion_attentes.
Cette nouvelle table est constituée des champs suivants : id_spipmotion_attente, l’identifiant numérique unique de la tâche à traiter ; id_document, l’identifiant numérique du document original à encoder ; id_objet l’identifiant unique de l’objet auquel le document encodé devra être attaché automatiquement ; objet, le type d’objet auquel (...) -
Pas question de marché, de cloud etc...
10 avril 2011Le vocabulaire utilisé sur ce site essaie d’éviter toute référence à la mode qui fleurit allègrement
sur le web 2.0 et dans les entreprises qui en vivent.
Vous êtes donc invité à bannir l’utilisation des termes "Brand", "Cloud", "Marché" etc...
Notre motivation est avant tout de créer un outil simple, accessible à pour tout le monde, favorisant
le partage de créations sur Internet et permettant aux auteurs de garder une autonomie optimale.
Aucun "contrat Gold ou Premium" n’est donc prévu, aucun (...) -
MediaSPIP version 0.1 Beta
16 avril 2011, parMediaSPIP 0.1 beta est la première version de MediaSPIP décrétée comme "utilisable".
Le fichier zip ici présent contient uniquement les sources de MediaSPIP en version standalone.
Pour avoir une installation fonctionnelle, 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 (...)
Sur d’autres sites (5569)
-
FFmpeg 16:9 Aspect ratio
29 mai 2020, par Satish KumarFind the Image attachedI have a video of resolution 1920 x 1080, but it is cropped with black in all sides. I found the crop values as 1440:720:240:208.



But when i apply crop with (1440:720:240:208.), the output video loses some portion of videos along the four sides, which is actually present in original input video.



I want to remove only the black border on all sides, but the output video should cover the 16:9 aspect ratio without losing the actual play area as in input (original) video



pl let provide the ffmpeg syntax for the same.


-
Dreamcast Track Sizes
1er mars 2015, par Multimedia Mike — Sega DreamcastI’ve been playing around with Sega Dreamcast discs lately. Not playing the games on the DC discs, of course, just studying their structure. To review, the Sega Dreamcast game console used special optical discs named GD-ROMs, where the GD stands for “gigadisc”. They are capable of holding about 1 gigabyte of data.
You know what’s weird about these discs ? Each one manages to actually store a gigabyte of data. Each disc has a CD portion and a GD portion. The CD portion occupies the first 45000 sectors and can be read in any standard CD drive. This area is divided between a brief data track and a brief (usually) audio track.
The GD region starts at sector 45000. Sometimes, it’s just one humongous data track that consumes the entire GD region. More often, however, the data track is split between the first track and the last track in the region and there are 1 or more audio tracks in between. But the weird thing is, the GD region is always full. I made a study of it (click for a larger, interactive graph) :
Some discs put special data or audio bonuses in the CD region for players to discover. But every disc manages to fill out the GD region. I checked up on a lot of those audio tracks that divide the GD data and they’re legitimate music tracks. So what’s the motivation ? Why would the data track be split in 2 pieces like that ?
I eventually realized that I probably answered this question in this blog post from 4 years ago. The read speed from the outside of an optical disc is higher than the inside of the same disc. When I inspect the outer data tracks of some of these discs, sure enough, there seem to be timing-sensitive multimedia FMV files living on the outer stretches.
One day, I’ll write a utility to take apart the split ISO-9660 filesystem offset from a weird sector.
-
seeking mp4 with audiostream inaccurate in mobile safari
23 février 2015, par dubbeljI have an issue with seeking an MP4 videofile on iOS (ipad). We use currentTime to skip through the video. This is working very well on most browsers, and also for h264 files without an audiostream on iOS. When I add an audiostream to the mp4 file however, the seeking becomes very inaccurate. This leads to all sorts of issues as the application bases a lot around timing.
So we definitely concluded that a file that is encoded (using ffmpeg) with the exact same encoding settings but without audio is working well.
These are the ffmpeg parameters I’m using when encoding with audio (added breaks for readability) :
ffmpeg
-i source.mov
-force_key_frames 00:00:04.840,00:00:04.880,00:00:04.920,00:00:04.960,00:00:05.000,00:00:05.040,00:00:05.080,00:00:14.760,00:00:14.800,00:00:14.840,00:00:14.880,00:00:14.920,00:00:14.960,00:00:15.000,00:00:24.760,00:00:24.800,00:00:24.840,00:00:24.880,00:00:24.920,00:00:24.960,00:00:25.000,00:00:31.720,00:00:31.760,00:00:31.800,00:00:31.840,00:00:31.880,00:00:31.920,00:00:31.960
-c:a libvo_aacenc
-b:a 128k
-ar 44100
-c:v libx264
-preset slow
-crf 21
-g 25
-r 25
-maxrate 2000k
-bufsize 2000k
-pix_fmt yuv420p
-movflags +faststart
-tune zerolatency
-vstats
encoded.mp4Things I’ve tried :
- all available aac and mp3 codecs
- different audio and video bitrates
- different audio frequencies
- with without zerolatency faststart flags
- maximum amount of keyframes in file
- settings keyframes only at (and around) the area where I need to skip to
Any ideas anyone ?