Recherche avancée

Médias (91)

Autres articles (80)

  • MediaSPIP Player : problèmes potentiels

    22 février 2011, par

    Le lecteur ne fonctionne pas sur Internet Explorer
    Sur Internet Explorer (8 et 7 au moins), le plugin utilise le lecteur Flash flowplayer pour lire vidéos et son. Si le lecteur ne semble pas fonctionner, cela peut venir de la configuration du mod_deflate d’Apache.
    Si dans la configuration de ce module Apache vous avez une ligne qui ressemble à la suivante, essayez de la supprimer ou de la commenter pour voir si le lecteur fonctionne correctement : /** * GeSHi (C) 2004 - 2007 Nigel McNie, (...)

  • L’agrémenter visuellement

    10 avril 2011

    MediaSPIP est basé sur un système de thèmes et de squelettes. Les squelettes définissent le placement des informations dans la page, définissant un usage spécifique de la plateforme, et les thèmes l’habillage graphique général.
    Chacun peut proposer un nouveau thème graphique ou un squelette et le mettre à disposition de la communauté.

  • Taille des images et des logos définissables

    9 février 2011, par

    Dans beaucoup d’endroits du site, logos et images sont redimensionnées pour correspondre aux emplacements définis par les thèmes. L’ensemble des ces tailles pouvant changer d’un thème à un autre peuvent être définies directement dans le thème et éviter ainsi à l’utilisateur de devoir les configurer manuellement après avoir changé l’apparence de son site.
    Ces tailles d’images sont également disponibles dans la configuration spécifique de MediaSPIP Core. La taille maximale du logo du site en pixels, on permet (...)

Sur d’autres sites (4465)

  • Is it still possible to compile modern x264 with the nal long start code used prior to release r1510 ?

    25 avril 2024, par Bryan Knowles

    I'm currently nerding out on old technology with HD-DVDs. The only freely available muxer is hddvdmux, I'm using MultiAVCHD for this.
Beginning with r1510, x264 switched to short start packets for NAL HRD (from what I understand). This makes the stream incompatible with hddvdmux.
deank on doom9 patched hddvdmux to accept short start codes, but in doing so, the video file plays too quickly and the audio goes out of sync.
The results I'm getting from the 2009 release of x264 leave much to be desired in comparison to modern releases, and I'd like to get those benefits while still maintaining compatibility with the original hddvdmux.
Is it possible ? If so... Any chance someone could compile a Windows binary for me with that change ? (I think it needs to be 32 bit, but not sure)

    


    I've tried multiple options with MultiAVCHD 4.1, fell back to 4.0 but am seeing weird rainbowing effects in the color from the extremely old version if x264. I admit I haven't dived in to programming, but seemed like a single change might be a reasonable request from someone already knowledgeable.

    


  • ffmpeg drawtext Arabic fonts doesn't render correctly [closed]

    11 février 2024, par Mahmoud Abdellatief

    what i'm trying to achieve :
loop an image into a video and overlay Arabic Text from the Qur'an on it including the text diacritical mark, using a custom font.

    


    example of the text to be rendered :

    


    بِسْمِ ٱللَّهِ ٱلرَّحْمَـٰنِ ٱلرَّحِيمِ


    


    the font used :
https://fonts.qurancomplex.gov.sa/wp02/wp-content/uploads/2024/01/UthmanicHafs_v22.zip

    


    font's unicode module :

    


    Unicode Module 
 
The Research and Development Unit in the Computer Department at King Fahd Glorious Qur’an Printing Complex relied on the unicode system unicode to create (Hafs) font in the Uthmanic Script, because this system is followed globally among computer and systems manufacturing companies in the world.

Unicode organization is a global code group that is used to define all codes and letters used in most of the world's languages and gathered in one code to facilitate the presentation and delivery on information despite of the language used. This global coding uses 1 to 4 bytes (byte = 8 bits) to encode letters, and so far only a third of the number available in Unicode organization to encode the letters of these languages.

Taking into account Hafs font with the Uthmanic Script, which was built entirely on the unicode system. We can explore the basic letters that were formed according to the following figure:

Whereas the font was developed starting from code (0600 ) to code (066FF ) Taking into account there are several encoded letters that haven't been used at all so it was replaces with the code []. The displayed copy above is the one that is been developed from the basic Arabic coding (0600-06FF) which was updated by Unicode organization in 2009.


    


    expected result :
exported video with correctly rendered text using the given font.

    


    actual result :
the text rendered contains only the diacritical marks ( which are the accents on top of the letters ) without the actual letters.
actual result

    


    what i tried :
this is my test command which exports just an image for faster results :

    


    Ffmpeg -loop 1  -i "image-2.jpg" -vf "drawtext=text='بِسْمِ ٱللَّهِ ٱلرَّحْمَـٰنِ ٱلرَّحِيمِ':fontsize=124:fontcolor=white:fontfile='UthmanicHafsV22.ttf':x=(w-text_w)/2:y=(h-text_h)/2" -frames:v 1  "output.png"


    


      

    • tried adding ft_load_flags , almost tried all of them
    • 


    • tried text_shaping=1 , with no success
    • 


    • tried textfile instead of text
    • 


    • tried changing the font, any font i try with it always have different problems, either some squares instead of the diacritical mark
    • 


    


    p.s im having same results on both latest ffmpeg compiled by myself on macos terminal with all required libraries enabled , and also on flutter ffmpeg kit full gpl

    


  • libavformat/hlsenc.c : Populate OTI using AAC profile in write_codec_attr.

    1er janvier 2024, par Romain Beauxis
    libavformat/hlsenc.c : Populate OTI using AAC profile in write_codec_attr.
    

    This patch populates the third entry for HLS codec attribute using the
    AAC profile.

    The HLS specifications[1] require this value to be the Object Type ID as
    referred to in table 1.3 of ISO/IEC 14496-3:2009[2].

    The numerical constants in the code refer to these OTIs minus one, as
    documented in commit 372597e[3], confirmed by comparing the values in the
    code with the values in the table mentioned above.

    Links :
    1 : https://datatracker.ietf.org/doc/html/rfc6381#section-3.3
    2 : https://csclub.uwaterloo.ca/~ehashman/ISO14496-3-2009.pdf
    3 : https://github.com/FFmpeg/FFmpeg/commit/372597e5381c097455a7b73849254d56083eb056

    Changes in this version :
    - Default value set to "mp4a.40.2" when profile is unknown for backward
    compatibility.

    Signed-off-by : Steven Liu <liuqi05@kuaishou.com>

    • [DH] libavformat/hlsenc.c