Recherche avancée

Médias (91)

Autres articles (50)

  • List of compatible distributions

    26 avril 2011, par

    The table below is the list of Linux distributions compatible with the automated installation script of MediaSPIP. Distribution nameVersion nameVersion number Debian Squeeze 6.x.x Debian Weezy 7.x.x Debian Jessie 8.x.x Ubuntu The Precise Pangolin 12.04 LTS Ubuntu The Trusty Tahr 14.04
    If you want to help us improve this list, you can provide us access to a machine whose distribution is not mentioned above or send the necessary fixes to add (...)

  • Publier sur MédiaSpip

    13 juin 2013

    Puis-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

  • Ajouter notes et légendes aux images

    7 février 2011, par

    Pour pouvoir ajouter notes et légendes aux images, la première étape est d’installer le plugin "Légendes".
    Une fois le plugin activé, vous pouvez le configurer dans l’espace de configuration afin de modifier les droits de création / modification et de suppression des notes. Par défaut seuls les administrateurs du site peuvent ajouter des notes aux images.
    Modification lors de l’ajout d’un média
    Lors de l’ajout d’un média de type "image" un nouveau bouton apparait au dessus de la prévisualisation (...)

Sur d’autres sites (12989)

  • ffmpeg-kit(macOS swift) - FATAL : Unknown encoder 'libx264'

    21 juillet 2021, par Noob

    I am using FFMPEG-Kit in my macOS app to compress the video file. While executing arguments along with libx264 I am getting FATAL: Unknown encoder 'libx264' I am not sure where to enable libx264. I am using cocoa-pod pod 'ffmpeg-kit-macos-full', '~> 4.4.LTS'. Please help me to resolve this problem. Thank you all.

    


    Below argument perfectly works in my system.

    


    Code :

    


    let arguement = "-i \(sourceURL.path) -c:v libx264 -crf 28 \(destinationURL.path)"

guard let session = FFmpegKit.execute(arguement) else {
    
    print("FFMPEG: Session not created!")
    return
}
guard let returnCode = session.getReturnCode() else {
    
    print("FFMPEG: Error return code!")
    return
}

if ReturnCode.isSuccess(returnCode){
    
    print("FFMPEG: Success")
}else if ReturnCode.isCancel(returnCode){
    
    print("FFMPEG: Cancelled.")
}else{
    
    print("FFMPEG: failed. \(FFmpegKitConfig.sessionState(toString: session.getState()))")

}


    


    Error :

    


    


    Unknown encoder 'libx264'

    


    


  • ffmpeg-kit(macOS swift) - FATAL : Unknown encoder 'libx264'

    21 juillet 2021, par Noob

    I am using FFMPEG-Kit in my macOS app to compress the video file. While executing arguments along with libx264 I am getting FATAL: Unknown encoder 'libx264' I am not sure where to enable libx264. I am using cocoa-pod pod 'ffmpeg-kit-macos-full', '~> 4.4.LTS'. Please help me to resolve this problem. Thank you all.

    


    Below argument perfectly works in my system.

    


    Code :

    


    let arguement = "-i \(sourceURL.path) -c:v libx264 -crf 28 \(destinationURL.path)"

guard let session = FFmpegKit.execute(arguement) else {
    
    print("FFMPEG: Session not created!")
    return
}
guard let returnCode = session.getReturnCode() else {
    
    print("FFMPEG: Error return code!")
    return
}

if ReturnCode.isSuccess(returnCode){
    
    print("FFMPEG: Success")
}else if ReturnCode.isCancel(returnCode){
    
    print("FFMPEG: Cancelled.")
}else{
    
    print("FFMPEG: failed. \(FFmpegKitConfig.sessionState(toString: session.getState()))")

}


    


    Error :

    


    


    Unknown encoder 'libx264'

    


    


  • cafenc : fill in avg. packet size later if unknown

    10 juillet 2021, par Roman Beranek
    cafenc : fill in avg. packet size later if unknown

    Frame size of Opus stream was previously presumed here to be 960 samples
    
(20ms), however sizes of 120, 240, 480, 1920, and 2880 are also allowed.
    
It can also alter on a per-packet basis and even multiple frames may be
    
present in a single packet according to the specification, for the sake
    
of simplicity however, let us assume that this doesn't occur.
    

    Because the mFramesPerPacket field, representing the number of samples
    
per packet in the ffmpeg terminilogy, is the key factor in calculating
    
packet durations and all that follows from that (index, bitrate, ...),
    
it is crucial to get right.
    

    Therefore, if the packet size is not available ahead of time (as it is in
    
the case of Opus), calculate an average from the stream duration once we
    
know how many packets there are and update the filed in the header.
    • [DH] libavformat/cafenc.c

Navigation