Advanced search

Medias (91)

Other articles (105)

  • Encoding and processing into web-friendly formats

    13 April 2011, by

    MediaSPIP automatically converts uploaded files to internet-compatible formats.
    Video files are encoded in MP4, Ogv and WebM (supported by HTML5) and MP4 (supported by Flash).
    Audio files are encoded in MP3 and Ogg (supported by HTML5) and MP3 (supported by Flash).
    Where possible, text is analyzed in order to retrieve the data needed for search engine detection, and then exported as a series of image files.
    All uploaded files are stored online in their original format, so you can (...)

  • Ajouter des informations spécifiques aux utilisateurs et autres modifications de comportement liées aux auteurs

    12 April 2011, by

    La manière la plus simple d’ajouter des informations aux auteurs est d’installer le plugin Inscription3. Il permet également de modifier certains comportements liés aux utilisateurs (référez-vous à sa documentation pour plus d’informations).
    Il est également possible d’ajouter des champs aux auteurs en installant les plugins champs extras 2 et Interface pour champs extras.

  • Gestion de la ferme

    2 March 2010, by

    La ferme est gérée dans son ensemble par des "super admins".
    Certains réglages peuvent être fais afin de réguler les besoins des différents canaux.
    Dans un premier temps il utilise le plugin "Gestion de mutualisation"

On other websites (13127)

  • ffmpeg not available on Oracle Linux 9 update 3 [closed]

    19 January 2024, by Red Cricket

    I cannot figure out how to install ffmpeg on a Oracle Linux 9 update 3 (RHCK).

    


    [root@snc-ol93-rhck ~]# dnf install ffmpeg-free
Last metadata expiration check: 0:14:16 ago on Wed 17 Jan 2024 04:48:34 PM UTC.
Error:
 Problem: package ffmpeg-free-5.1.4-2.el9.x86_64 from ol9_developer_EPEL requires libavfilter.so.8()(64bit), but none of the providers can be installed
  - package ffmpeg-free-5.1.4-2.el9.x86_64 from ol9_developer_EPEL requires libavfilter.so.8(LIBAVFILTER_8)(64bit), but none of the providers can be installed
  - package libavfilter-free-5.1.3-1.el9.x86_64 from ol9_developer_EPEL requires librubberband.so.2()(64bit), but none of the providers can be installed
  - package libavfilter-free-5.1.4-1.el9.x86_64 from ol9_developer_EPEL requires librubberband.so.2()(64bit), but none of the providers can be installed
  - package libavfilter-free-5.1.4-2.el9.x86_64 from ol9_developer_EPEL requires librubberband.so.2()(64bit), but none of the providers can be installed
  - cannot install the best candidate for the job
  - nothing provides ladspa needed by rubberband-2.0.1-1.el9.x86_64 from ol9_developer_EPEL
  - nothing provides ladspa needed by rubberband-3.1.0-2.el9.x86_64 from ol9_developer_EPEL
  - nothing provides ladspa needed by rubberband-3.1.3-1.el9.x86_64 from ol9_developer_EPEL
(try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages)


    


    Turns out I needed to install the repo like so in my ansible playbook

    


    dnf install https://mirrors.rpmfusion.org/free/el/rpmfusion-free-release-9.noarch.rpm


    


  • lavc/vvc: Check slice structure

    10 January, by Frank Plowman
    lavc/vvc: Check slice structure
    

    The criteria for slice structure validity is similar to that of
    subpicture structure validity that we saw not too long ago [1].
    The relationship between tiles and slices must satisfy the following
    properties:

    * Exhaustivity. All tiles in a picture must belong to a slice. The
    tiles cover the picture, so this implies the slices must cover the
    picture.
    * Mutual exclusivity. No tile may belong to more than one slice, i.e.
    slices may not overlap.

    In most cases these properties are guaranteed by the syntax. There is
    one noticable exception however: when pps_tile_idx_delta_present_flag is
    equal to one, each slice is associated with a syntax element
    pps_tile_idx_delta_val[i] which "specifies the difference between the
    tile index of the tile containing the first CTU in the ( i + 1 )-th
    rectangular slice and the tile index of the tile containing the first
    CTU in the i-th rectangular slice" [2]. When these syntax elements are
    present, the i-th slice can begin anywhere and the usual guarantees
    provided by the syntax are lost.

    The patch detects slice structures which violate either of the two
    properties above, and are therefore invalid, while building the
    slice map. Should the slice map be determined to be invalid, an
    AVERROR_INVALIDDATA is returned. This prevents issues including
    segmentation faults when trying to decode, invalid bitstreams.

    [1]: https://ffmpeg.org//pipermail/ffmpeg-devel/2024-October/334470.html
    [2]: H.266 (V3) Section 7.4.3.5, Picture parameter set RBSP semantics

    Signed-off-by: Frank Plowman <post@frankplowman.com>

    • [DH] libavcodec/vvc/ps.c
  • FFMPEG in Node.js: Conversion Failed

    11 July 2024, by cuneyttyler

    I have a small node.js web app. I use like this in a get request:

    &#xA;

    app.get(&#x27;/api/voice/:gender/:voice/:pitch&#x27;, function(req, res){&#xA;        if(req.params.pitch == "1" || req.params.pitch == "1.0") {&#xA;            const file = "./voices/" &#x2B; req.params.gender.toLowerCase() &#x2B; "/" &#x2B; req.params.voice &#x2B; ".mp3"&#xA;            res.download(file);&#xA;            return&#xA;        }&#xA;&#xA;        const inputFile = "./voices/" &#x2B; req.params.gender.toLowerCase() &#x2B; "/" &#x2B; req.params.voice &#x2B; ".mp3"&#xA;        const output_file = "./Audio/Temp/" &#x2B; req.params.voice &#x2B; ".mp3"&#xA;        ffmpeg()&#xA;                .input(inputFile)&#xA;                .audioCodec(&#x27;pcm_s16le&#x27;) // Set the audio codec to PCM with 16-bit depth&#xA;                .audioFrequency(44100) // Set the sample rate&#xA;                .on(&#x27;error&#x27;, function(err) {&#xA;                    console.error(&#x27;Error while converting:&#x27;, err);&#xA;                })&#xA;                .on(&#x27;end&#x27;, function() {&#xA;                    // res.download(output_file)&#xA;                })&#xA;                .save(output_file);&#xA;&#xA;    });&#xA;

    &#xA;

    It gives Conversion Failed error:

    &#xA;

    [2024-07-11T18:11:22.880Z] Error while converting: Error: ffmpeg exited with code 1: Conversion failed!&#xA;&#xA;    at ChildProcess.<anonymous> (d:\Dev\Anima\Client\node_modules\fluent-ffmpeg\lib\processor.js:180:22)&#xA;    at ChildProcess.emit (d:\Dev\Anima\Client\lib\events.js:519:28)&#xA;    at ChildProcess._handle.onexit (d:\Dev\Anima\Client\lib\internal\child_process.js:294:12)&#xA;    at Process.callbackTrampoline (node:internal/async_hooks:130:17) {stack: &#x27;Error: ffmpeg exited with code 1: Conversion …Trampoline (node:internal/async_hooks:130:17)&#x27;, message: &#x27;ffmpeg exited with code 1: Conversion failed!&#xA;&#x27;}&#xA;</anonymous>

    &#xA;

    When I use same code in a node.js desktop(.exe) app, it successfully runs. When I use it in an express.js app, it fails. Error message is not clear. What is the issue?

    &#xA;