Recherche avancée

Médias (0)

Mot : - Tags -/optimisation

Aucun média correspondant à vos critères n’est disponible sur le site.

Autres articles (48)

  • Submit bugs and patches

    13 avril 2011

    Unfortunately a software is never perfect.
    If you think you have found a bug, report it using our ticket system. Please to help us to fix it by providing the following information : the browser you are using, including the exact version as precise an explanation as possible of the problem if possible, the steps taken resulting in the problem a link to the site / page in question
    If you think you have solved the bug, fill in a ticket and attach to it a corrective patch.
    You may also (...)

  • Submit enhancements and plugins

    13 avril 2011

    If you have developed a new extension to add one or more useful features to MediaSPIP, let us know and its integration into the core MedisSPIP functionality will be considered.
    You can use the development discussion list to request for help with creating a plugin. As MediaSPIP is based on SPIP - or you can use the SPIP discussion list SPIP-Zone.

  • 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 (6778)

  • FFMPEG command line not using GPU when compressing MP4 file

    13 avril 2022, par StealthRT

    Hey all I have been working on a good command line string to use for my movies that I would like to trim the size down to at least half the current size.

    


    My handbrake information regaurding my GPU and computer system is this :

    


    HandBrake 1.5.1 (2022011000)
OS: Microsoft Windows NT 10.0.19043.0
CPU: Intel(R) Xeon(R) CPU           X5650  @ 2.67GHz (12 Cores, 24 Threads)
Ram: 40940 MB, 
GPU Information:
  Microsoft Remote Display Adapter - 10.0.19041.662
  NVIDIA Tesla K10 - 30.0.14.7141
  NVIDIA Tesla K10 - 30.0.14.7141
  Microsoft Basic Display Adapter - 10.0.19041.868


    


    When I originally made a command line, I was just using it to copy the file over to where it needed to go with the following :

    


    


    ffmpeg -y -hide_banner -threads 8 -hwaccel cuda -hwaccel_device 1
-hwaccel_output_format cuda -v verbose -i "c :\testingvids\AEON FLUX 2005.mp4" -c:v h264_cuvid -gpu:v 1 -preset slow -c copy "c :\testingvids\AEON FLUX 2005 nvidia.mp4"

    


    


    This produced a 828x processing speed :

    


    enter image description here

    


    But for taking that same file and compressing it I seem to only get a 8x speed ?

    


    enter image description here

    


    So that is quite a difference there. Am I using the correct syntax for it to only use my GPU to convert/compress the mp4 with the h264 nvenc ?

    


  • Anomalie #4799 (Nouveau) : Validité du RSS

    26 mai 2021

    Marc, sur https://discuter.spip.net/t/rss-atom-enclosures-et-w3c/152922 signale quelques points de validité à améliorer sur le RSS de la dist

    backend.html

    • balise rss : rajout d’un lien xmlns:atom="http://www.w3.org/2005/Atom"
    • balise channel : rajout de
    • réf : Missing atom:link with rel="self"

    squelette rss-item.html (ou inc-rss.html)

    • enclosures multiples : item contains more than one enclosure
    • suggestion (discutable) rajouter un critère {0,1} dans la boucle document de rss-item.html
    <span class="CodeRay">
    <span class="tag">span><span class="error">(</span><span class="attribute-name">DOCUMENTS</span><span class="error">)</span><span class="error">{</span><span class="attribute-name">id_article</span><span class="error">}</span><span class="error">{</span><span class="attribute-name">mode</span>=<span class="attribute-value">document</span><span class="error">}</span><span class="error">{</span><span class="attribute-name">doublons</span><span class="error">}</span><span class="error">{</span><span class="attribute-name">0</span><span class="error">,</span><span class="attribute-name">1</span><span class="error">}</span><span class="tag">></span>[
    <span class="tag">span> <span class="attribute-name">url</span>=<span class="string"><span class="delimiter">"</span><span class="content">(#URL_DOCUMENT|url_absolue|unique)</span><span class="delimiter">"</span></span><span class="error">[</span> <span class="attribute-name">length</span>=<span class="string"><span class="delimiter">"</span><span class="content">(#TAILLE)</span><span class="delimiter">"</span></span><span class="error">]</span><span class="error">[</span> <span class="attribute-name">type</span>=<span class="string"><span class="delimiter">"</span><span class="content">(#MIME_TYPE)</span><span class="delimiter">"</span></span><span class="error">]</span> <span class="tag">/></span>]
    <span class="tag"></span>
    </span></span></span>
  • How to add "ffmpeg" to the Cloud Run environment or to Dockerfile ?

    16 janvier 2021, par awabs

    I am triying to a logo to video that is uploaded to cloud storage using ffmpeg library, I deployed this code as cloud function is runs only with small size videos, so I decided to move to cloud run, but here I have to build container myself so I used this command instead

    &#xA;

    gcloud builds submit --pack image=europe-west1-docker.pkg.dev/video-sharing-a1mfa/video-sharing-repo/my-image,env=GOOGLE_FUNCTION_TARGET=addLogo&#xA;

    &#xA;

    and it builds the image and I just had to create a service in the Cloud Run and it is running, but unfortunately when I trigger this function I get this error

    &#xA;

    Error: spawn ffmpeg ENOENT&#xA;at Process.ChildProcess._handle.onexit (internal/child_process.js:268:19)&#xA;at onErrorNT (internal/child_process.js:470:16)&#xA;at processTicksAndRejections (internal/process/task_queues.js:84:21)&#xA;

    &#xA;

    Which I am not sure of but I guess is that ffmpeg in not installed in contanier (where it comes preinstalled in the gcloud functions env). Any idea how to install it or what the docker file configuration might be ?

    &#xA;

    here is my code :

    &#xA;

    const { Storage } = require(&#x27;@google-cloud/storage&#x27;);&#xA;const projectId = &#x27;video-sharing-a1mfa&#x27;;&#xA;let gcs = new Storage({&#xA;    projectId&#xA;});&#xA;&#xA;const os = require(&#x27;os&#x27;);&#xA;const path = require(&#x27;path&#x27;);&#xA;const spawn = require(&#x27;child-process-promise&#x27;).spawn;&#xA;&#xA;&#xA;exports.addLogo = async (req, res) => {&#xA;&#xA;const event = JSON.parse(req.body);&#xA;const bucket = event.bucket;&#xA;const contentType = event.contentType;&#xA;const filePath = event.name;&#xA;&#xA;console.log(&#x27;File change detected, function execution started&#x27;);&#xA;if (path.basename(filePath).startsWith(&#x27;resized-&#x27;)) {&#xA;    console.log(&#x27;We already renamed that file!&#x27;);&#xA;    return;&#xA;}&#xA;const destBucket = gcs.bucket(bucket);&#xA;const tmpFilePath = path.join(os.tmpdir(), path.basename(filePath));&#xA;const metadata = { contentType: contentType };&#xA;const tmpLogoPath = path.join(os.tmpdir(), &#x27;watermark.png&#x27;);&#xA;await destBucket.file(&#x27;watermark.png&#x27;).download({&#xA;    destination: tmpLogoPath&#xA;})&#xA;&#xA;const newPath = path.join(os.tmpdir(), &#x27;output.mp4&#x27;)&#xA;&#xA;await destBucket.file(filePath).download({&#xA;    destination: tmpFilePath&#xA;});&#xA;console.log(&#x27;file downloaded to temp&#x27;);&#xA;&#xA;console.log(&#x27;adding watermark&#x27;);&#xA;&#xA;var str = "overlay=10:10"&#xA;&#xA;await spawn(&#x27;ffmpeg&#x27;, [&#x27;-i&#x27;, tmpFilePath, &#x27;-i&#x27;, tmpLogoPath, &#x27;-filter_complex&#x27;, str, newPath]);&#xA;&#xA;&#xA;console.log(&#x27;watermark added&#x27;);&#xA;&#xA;return destBucket.upload(newPath, {&#xA;    destination: path.dirname(filePath) &#x2B; &#x27;/resized-&#x27; &#x2B; path.basename(filePath),&#xA;    metadata: metadata&#xA;});;&#xA;};&#xA;

    &#xA;