Recherche avancée

Médias (1)

Mot : - Tags -/publishing

Autres articles (90)

  • Mise à jour de la version 0.1 vers 0.2

    24 juin 2013, par

    Explications des différents changements notables lors du passage de la version 0.1 de MediaSPIP à la version 0.3. Quelles sont les nouveautés
    Au niveau des dépendances logicielles Utilisation des dernières versions de FFMpeg (>= v1.2.1) ; Installation des dépendances pour Smush ; Installation de MediaInfo et FFprobe pour la récupération des métadonnées ; On n’utilise plus ffmpeg2theora ; On n’installe plus flvtool2 au profit de flvtool++ ; On n’installe plus ffmpeg-php qui n’est plus maintenu au (...)

  • Personnaliser en ajoutant son logo, sa bannière ou son image de fond

    5 septembre 2013, par

    Certains thèmes prennent en compte trois éléments de personnalisation : l’ajout d’un logo ; l’ajout d’une bannière l’ajout d’une image de fond ;

  • Les autorisations surchargées par les plugins

    27 avril 2010, par

    Mediaspip core
    autoriser_auteur_modifier() afin que les visiteurs soient capables de modifier leurs informations sur la page d’auteurs

Sur d’autres sites (16544)

  • avcodec/dvbsubdec : Fix conditions for fallback to default resolution

    3 décembre 2021, par softworkz
    avcodec/dvbsubdec : Fix conditions for fallback to default resolution
    

    The previous code expected a segment of type CLUT definition to exist
    in order to accept a set of segments to be complete.
    This was an incorrect assumption as the presence of a CLUT segment
    is not mandatory.
    (version 1.6.1 of the spec is probably a bit more clear about this
    than earlier versions : https://www.etsi.org/deliver/etsi_en/
    300700_300799/300743/01.06.01_20/en_300743v010601a.pdf)

    The incorrect condition prevented proper fallback to using the default
    resolution for the decoding context.

    This also adds variables and moves the fallback check to the outside
    for better clarity.

    Signed-off-by : softworkz <softworkz@hotmail.com>

    • [DH] libavcodec/dvbsubdec.c
  • How can I generate a metadata.mov file for higher-resolution Live Photos (e.g. 1440x2560) ?

    30 juillet, par brijesh patel

    I'm generating Live Photos programmatically for use as wallpapers on iOS. I'm using a known metadata.mov file bundled with the app (likely extracted from a working Live Photo with resolution 1080x1920). This setup works fine when I use a video of the same resolution.

    &#xA;

    I'm using this open-source library to handle the video-to-LivePhoto conversion :
    &#xA;https://github.com/TouSC/Video2LivePhoto

    &#xA;

    However, when I try using a higher-resolution video (e.g. 2560x1440) to avoid black bars on high-resolution devices (like iPhone 14 Pro Max), the Photos app shows the Live Photo, but the motion component doesn't work—it just says “Motion Not Available.”

    &#xA;

    I believe the issue is that the static metadata.mov contains resolution-specific metadata, which prevents it from working correctly with other video sizes.

    &#xA;

      &#xA;
    • Tried changing the resolution of the video (e.g. 1440x2560, 1284x2778) – motion breaks.

      &#xA;

    • &#xA;

    • Tried generating a new .mov file using FFmpeg with a silent video track, matching the new resolution – Live Photo not recognized or shows errors.

      &#xA;

    • &#xA;

    • Tried modifying the existing metadata.mov with tools like FFmpeg, AtomicParsley, Bento4, and mp4box – resulting files often break the Live Photo entirely.

      &#xA;

    • &#xA;

    • I expected to generate a valid metadata.mov (or similar track) that would support the custom resolution and restore Live Photo motion support.

      &#xA;

    • &#xA;

    &#xA;

    static func convertVideo(videoURL: URL, complete: @escaping (_ success: Bool, _ errorMessage: String?) -> Void) {&#xA;    print("start converting")&#xA;    &#xA;    guard let metaURL = Bundle.main.url(forResource: "metadata", withExtension: "mov") else {&#xA;        complete(false, "metadata.mov not found")&#xA;        return&#xA;    }&#xA;&#xA;    let livePhotoSize = CGSize(width: 1440, height: 2560) // &lt;-- updated resolution&#xA;    let livePhotoDuration = CMTime(value: 550, timescale: 600)&#xA;    let assetIdentifier = UUID().uuidString&#xA;&#xA;    guard let documentPath = NSSearchPathForDirectoriesInDomains(.documentDirectory, .userDomainMask, true).first else {&#xA;        complete(false, "Document path not found")&#xA;        return&#xA;    }&#xA;&#xA;    let durationPath = documentPath &#x2B; "/duration.mp4"&#xA;    let acceleratePath = documentPath &#x2B; "/accelerate.mp4"&#xA;    let resizePath = documentPath &#x2B; "/resize.mp4"&#xA;    let finalPath = resizePath&#xA;&#xA;    removeFileIfExists(at: durationPath)&#xA;    removeFileIfExists(at: acceleratePath)&#xA;    removeFileIfExists(at: resizePath)&#xA;&#xA;    let converter = Converter4Video(path: finalPath)&#xA;&#xA;    Task {&#xA;        do {&#xA;            try await converter.durationVideo(at: videoURL, outputPath: durationPath, targetDuration: 3)&#xA;            try await converter.accelerateVideo(at: durationPath, to: livePhotoDuration, outputPath: acceleratePath)&#xA;            try await converter.resizeVideo(at: acceleratePath, outputPath: resizePath, outputSize: livePhotoSize)&#xA;&#xA;            print("### resize Success")&#xA;            let image = try await generateCGImage(finalPath: finalPath)&#xA;&#xA;            await generateLivePhoto(&#xA;                image: image,&#xA;                documentPath: documentPath,&#xA;                assetIdentifier: assetIdentifier,&#xA;                metaURL: metaURL,&#xA;                converter: converter,&#xA;                complete: complete&#xA;            )&#xA;        } catch {&#xA;            print("Video conversion error: \(error)")&#xA;            complete(false, error.localizedDescription)&#xA;            return&#xA;        }&#xA;    }&#xA;}&#xA;

    &#xA;

  • Revision 7ab9a9587b : Remove Wextra warnings from vp9_sad.c As a side-effect, the max_sad check is re

    13 mai 2014, par Deb Mukherjee

    Changed Paths :
     Modify /test/sad_test.cc


     Modify /vp8/common/rtcd_defs.pl


     Modify /vp8/common/sad_c.c


     Modify /vp8/common/variance.h


     Modify /vp8/encoder/mcomp.c


     Modify /vp8/encoder/rdopt.c


     Modify /vp9/common/vp9_rtcd_defs.pl


     Modify /vp9/encoder/vp9_encodeframe.c


     Modify /vp9/encoder/vp9_mbgraph.c


     Modify /vp9/encoder/vp9_mcomp.c


     Modify /vp9/encoder/vp9_rdopt.c


     Modify /vp9/encoder/vp9_sad.c


     Modify /vp9/encoder/vp9_variance.h



    Remove Wextra warnings from vp9_sad.c

    As a side-effect, the max_sad check is removed from the
    C-implementation of VP8, for consistency with VP9, and to
    ensure that the SAD tests common to VP8/VP9 pass.
    That will make the VP8 C implementation of sad a little slower
    but given that is rarely used in practice, the impact will be
    minimal.

    Change-Id : I7f43089fdea047fbf1862e40c21e4715c30f07ca