
Recherche avancée
Autres articles (70)
-
Des sites réalisés avec MediaSPIP
2 mai 2011, parCette page présente quelques-uns des sites fonctionnant sous MediaSPIP.
Vous pouvez bien entendu ajouter le votre grâce au formulaire en bas de page. -
Publier sur MédiaSpip
13 juin 2013Puis-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 -
Changer son thème graphique
22 février 2011, parLe thème graphique ne touche pas à la disposition à proprement dite des éléments dans la page. Il ne fait que modifier l’apparence des éléments.
Le placement peut être modifié effectivement, mais cette modification n’est que visuelle et non pas au niveau de la représentation sémantique de la page.
Modifier le thème graphique utilisé
Pour modifier le thème graphique utilisé, il est nécessaire que le plugin zen-garden soit activé sur le site.
Il suffit ensuite de se rendre dans l’espace de configuration du (...)
Sur d’autres sites (12562)
-
when use idb and ffmepg to record video, Appium Session lose
6 septembre 2023, par azhiWhen use Appium to start the session and open app in iOS, connection will lost after using idb and ffmepg command to record video in java process. At the same time, Xcode will occur connection lost issue. If i open WDA again by manual in iPhone, tests again and connection will be normal. I tied switching port for WDA, unluckily it's the same result. Have any ideas for this, graceful for advice.


test normal when use this way to record video.


Appium log :

[Xcode] xcodebuild exited with code '65' and signal 'null' [HTTP] —> GET /session/f70eef73-ef99-4341-822f-d285d74a8614/timeouts [HTTP] {} [debug] [AppiumDriver@8f28] Encountered internal error running command : NoSuchDriverError : A session is either terminated or not started [debug] [AppiumDriver@8f28] at asyncHandler (/opt/homebrew/lib/node_modules/appium/node_modules/@appium/base-driver/lib/protocol/protocol.js:315:15) [debug] [AppiumDriver@8f28] at /opt/homebrew/lib/node_modules/appium/node_modules/@appium/base-driver/lib/protocol/protocol.js:518:15 [debug] [AppiumDriver@8f28] at Layer.handle [as handle_request] (/opt/homebrew/lib/node_modules/appium/node_modules/express/lib/router/layer.js:95:5) [debug] [AppiumDriver@8f28] at next (/opt/homebrew/lib/node_modules/appium/node_modules/express/lib/router/route.js:144:13) [debug] [AppiumDriver@8f28] at Route.dispatch (/opt/homebrew/lib/node_modules/appium/node_modules/express/lib/router/route.js:114:3) [debug] [AppiumDriver@8f28] at Layer.handle [as handle_request] (/opt/homebrew/lib/node_modules/appium/node_modules/express/lib/router/layer.js:95:5) [debug] [AppiumDriver@8f28] at /opt/homebrew/lib/node_modules/appium/node_modules/express/lib/router/index.js:284:15 [debug] [AppiumDriver@8f28] at param (/opt/homebrew/lib/node_modules/appium/node_modules/express/lib/router/index.js:365:14) [debug] [AppiumDriver@8f28] at param (/opt/homebrew/lib/node_modules/appium/node_modules/express/lib/router/index.js:376:14) [debug] [AppiumDriver@8f28] at Function.process_params (/opt/homebrew/lib/node_modules/appium/node_modules/express/lib/router/index.js:421:3) [debug] [AppiumDriver@8f28] at next (/opt/homebrew/lib/node_modules/appium/node_modules/express/lib/router/index.js:280:10) [debug] [AppiumDriver@8f28] at logger (/opt/homebrew/lib/node_modules/appium/node_modules/morgan/index.js:144:5) [debug] [AppiumDriver@8f28] at Layer.handle [as handle_request] (/opt/homebrew/lib/node_modules/appium/node_modules/express/lib/router/layer.js:95:5) [debug] [AppiumDriver@8f28] at trim_prefix (/opt/homebrew/lib/node_modules/appium/node_modules/express/lib/router/index.js:328:13) [debug] [AppiumDriver@8f28] at /opt/homebrew/lib/node_modules/appium/node_modules/express/lib/router/index.js:286:9 [debug] [AppiumDriver@8f28] at Function.process_params (/opt/homebrew/lib/node_modules/appium/node_modules/express/lib/router/index.js:346:12) [debug] [AppiumDriver@8f28] at next (/opt/homebrew/lib/node_modules/appium/node_modules/express/lib/router/index.js:280:10) [debug] [AppiumDriver@8f28] at jsonParser (/opt/homebrew/lib/node_modules/appium/node_modules/body-parser/lib/types/json.js:113:7) [debug] [AppiumDriver@8f28] at Layer.handle [as handle_request] (/opt/homebrew/lib/node_modules/appium/node_modules/express/lib/router/layer.js:95:5) [debug] [AppiumDriver@8f28] at trim_prefix (/opt/homebrew/lib/node_modules/appium/node_modules/express/lib/router/index.js:328:13) [debug] [AppiumDriver@8f28] at /opt/homebrew/lib/node_modules/appium/node_modules/express/lib/router/index.js:286:9 [debug] [AppiumDriver@8f28] at Function.process_params (/opt/homebrew/lib/node_modules/appium/node_modules/express/lib/router/index.js:346:12) [HTTP] GET /session/66e1fdca-4e8c-418e-a0d1-6d98779b874c/screenshot

-
avcodec/h264_mp4toannexb_bsf : fix missing PS before IDR frames
19 mai 2023, par Zhao Zhiliavcodec/h264_mp4toannexb_bsf : fix missing PS before IDR frames
If there is a single group of SPS/PPS before an IDR frame, but no
SPS/PPS after that, we will miss the chance to reset
idr_sps_seen/idr_pps_seen. No SPS/PPS are inserted afterwards.This patch saves in-band SPS/PPS and insert them before IDR frames
when necessary.Signed-off-by : Zhao Zhili <zhilizhao@tencent.com>
-
How can I get the location of my screenshot made from video with ffmpeg in Node.js ?
17 juin 2023, par Terry WindwalkerThis is how I did it.


const ffmpegPath = require('@ffmpeg-installer/ffmpeg');
import ffmpeg from 'fluent-ffmpeg';
import path from 'path';
const os = require('os');
ffmpeg.setFfmpegPath(ffmpegPath.path);


export const generateThumbnailFromVideo = async (mp4Buffer) => {
 console.log('generateThumbnailFromVideo is triggered');
 const timePosition = '00:00:00.500';
 const filename = `temp/temp-${new Date().getTime()}.png`;
 return new Promise((resolve, reject) => {
 ffmpeg({
 source: bufferToStream(mp4Buffer)
 })
 .on('error', (err) => {
 console.error('An error occurred: ' + err.message);
 reject(err);
 })
 .on('end', () => {
 console.log('Thumbnail generated successfully');
 fs.readFile(filename, (err, data) => {
 if (err) {
 console.error('An error occurred while reading the thumbnail file:', err);
 reject(err);
 return;
 }
 fs.unlink(filename);
 uploadBuffer(data, filename, data.length)
 })
 resolve(filename);
 })
 .screenshots({
 timestamps: [timePosition],
 filename: filename,
 folder: 'temp/',
 size: '320x240',
 });
 });
}



And this is the log came up.


generateThumbnailFromVideo is triggered
Thumbnail generated successfully
createProjectMedia is triggered
userId: 1
projectId: 25
mediaArray: [
 {
 mediaUrl: 'medias/1/1686843801535/medias_1_1684753043519_1_(1)_(4)_(1).mp4',
 thumbnailUrl: 'medias/1/1686843801535/medias_1_1684753043519_1_(1)_(4)_(1)_thumbnail.jpg',
 mediaType: 2
 }
]
An error occurred while reading the thumbnail file: [Error: ENOENT: no such file or directory, open 'temp/temp-1686843802255.png'] {
 errno: -2,
 code: 'ENOENT',
 syscall: 'open',
 path: 'temp/temp-1686843802255.png'
}



It claims the screenshot has been created but I cannot find it anywhere. Tried absolute route with
__dirname
andos.tmpdir()
with no luck. The screenshot it claimed has been created are not there.

Can somebody help me out ? I have been stuck here for 5 hours with no progress so far.


Also, I have checked the file
temp
in the root directory of the repo. It is empty.

UPDATE : Checked and can confirm that the router used in the key "folder" (
temp/
) is correct, since deleting that folder will trigger an error saying that the folder is not found. Creating the folder again will remove this error. But even though the "generated successfully" log is printed, the image is not saved in that folder, and the folder is still empty after that log is printed.

That
fs.unlink
is also unrelated. Removing it won't cause any change.