
Recherche avancée
Autres articles (48)
-
Submit bugs and patches
13 avril 2011Unfortunately 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 2011If 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, parMediaspip 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 StealthRTHey 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 :




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




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 2021Marc, 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> - balise rss : rajout d’un lien
-
How to add "ffmpeg" to the Cloud Run environment or to Dockerfile ?
16 janvier 2021, par awabsI 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


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



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


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



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 ?


here is my code :


const { Storage } = require('@google-cloud/storage');
const projectId = 'video-sharing-a1mfa';
let gcs = new Storage({
 projectId
});

const os = require('os');
const path = require('path');
const spawn = require('child-process-promise').spawn;


exports.addLogo = async (req, res) => {

const event = JSON.parse(req.body);
const bucket = event.bucket;
const contentType = event.contentType;
const filePath = event.name;

console.log('File change detected, function execution started');
if (path.basename(filePath).startsWith('resized-')) {
 console.log('We already renamed that file!');
 return;
}
const destBucket = gcs.bucket(bucket);
const tmpFilePath = path.join(os.tmpdir(), path.basename(filePath));
const metadata = { contentType: contentType };
const tmpLogoPath = path.join(os.tmpdir(), 'watermark.png');
await destBucket.file('watermark.png').download({
 destination: tmpLogoPath
})

const newPath = path.join(os.tmpdir(), 'output.mp4')

await destBucket.file(filePath).download({
 destination: tmpFilePath
});
console.log('file downloaded to temp');

console.log('adding watermark');

var str = "overlay=10:10"

await spawn('ffmpeg', ['-i', tmpFilePath, '-i', tmpLogoPath, '-filter_complex', str, newPath]);


console.log('watermark added');

return destBucket.upload(newPath, {
 destination: path.dirname(filePath) + '/resized-' + path.basename(filePath),
 metadata: metadata
});;
};