
Recherche avancée
Médias (1)
-
La conservation du net art au musée. Les stratégies à l’œuvre
26 mai 2011
Mis à jour : Juillet 2013
Langue : français
Type : Texte
Autres articles (61)
-
L’agrémenter visuellement
10 avril 2011MediaSPIP est basé sur un système de thèmes et de squelettes. Les squelettes définissent le placement des informations dans la page, définissant un usage spécifique de la plateforme, et les thèmes l’habillage graphique général.
Chacun peut proposer un nouveau thème graphique ou un squelette et le mettre à disposition de la communauté. -
Personnaliser les catégories
21 juin 2013, parFormulaire de création d’une catégorie
Pour ceux qui connaissent bien SPIP, une catégorie peut être assimilée à une rubrique.
Dans le cas d’un document de type catégorie, les champs proposés par défaut sont : Texte
On peut modifier ce formulaire dans la partie :
Administration > Configuration des masques de formulaire.
Dans le cas d’un document de type média, les champs non affichés par défaut sont : Descriptif rapide
Par ailleurs, c’est dans cette partie configuration qu’on peut indiquer le (...) -
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
Sur d’autres sites (10912)
-
doc/html : fix styling issue with Texinfo 7.0
8 novembre 2023, par Frank Plowmandoc/html : fix styling issue with Texinfo 7.0
Texinfo 7.0 produces quite different HTML to Texinfo 6.8. Without
this change, enumerated option flags (i.e. Possible values of x
are...) render as white text on a white background with Texinfo 7.0
and are unreadable. This change removes a style for the selector
`.table .table` which causes the background to turn white for these
elements. As far as I can tell, it is not actually used anywhere in
files generated by Texinfo 6.8.Signed-off-by : Frank Plowman <post@frankplowman.com>
-
FFMpeg PHP : Unable to load FFProbe
23 septembre 2023, par Artem KonyaevI am using the Lumen PHP framework which is the form of Laravel. On the server side I have Bitnami.


I get the 500 error when the code that uses FFMpeg is being executed. My part of the code which leads to the problem :


$ffmpeg = FFMpeg::create([
 'ffmpeg.binaries' => '/opt/bitnami/apache/htdocs/vendor/php-ffmpeg/php-ffmpeg/src/FFMpeg',
 'ffprobe.binaries' => '/opt/bitnami/apache/htdocs/vendor/php-ffmpeg/php-ffmpeg/src/FFProbe',
 'timeout' => 0
]);



I also tried it without 'timeout'.


Here are the details of the error that I get in the server response :




[ExecutableNotFoundException](#trace-box-2) [ExecutableNotFoundException](#trace-box-1)


HTTP 500 Internal Server Error


Unable to load FFProbe


Exceptions 2


FFMpeg\Exception\ExecutableNotFoundException


in /opt/bitnami/apache/htdocs/vendor/php-ffmpeg/php-ffmpeg/src/FFMpeg/Driver/FFProbeDriver.php (line 50)


- 

-
        $binaries = $configuration->get('ffprobe.binaries', ['avprobe', 'ffprobe']);


-
        


-
        try {


-
            return static::load($binaries, $logger, $configuration);


-
        } catch (BinaryDriverExecutableNotFound $e) {


-
            throw new ExecutableNotFoundException('Unable to load FFProbe', $e->getCode(), $e);


-
        }


-
    }


-
}
























I tried changing the project folder rights by
sudo chmod -R 777 /opt/bitnami/apache/htdocs
. Not sure if it worked. Here is the current state :



$ ls -l /opt/bitnami/apache/htdocs
total 328
drwxrwxrwx 10 bitnami root 4096 Feb 20 16:16 app
-rwxrwxrwx 1 bitnami root 1094 Feb 20 16:16 artisan
drwxrwxrwx 2 bitnami root 4096 Feb 20 16:16 bootstrap
-rwxrwxrwx 1 bitnami root 1076 Jul 2 00:25 composer.json
-rwxrwxrwx 1 bitnami root 274159 Jul 2 00:25 composer.lock
drwxrwxrwx 5 bitnami root 4096 Feb 20 16:16 database
-rwxrwxrwx 1 bitnami root 4871 May 18 15:46 index_default.html
-rwxrwxrwx 1 bitnami root 592 Feb 20 16:16 phpunit.xml
drwxrwxrwx 2 bitnami root 4096 Feb 20 16:16 public
-rwxrwxrwx 1 bitnami root 1920 Feb 20 16:16 README.md
drwxrwxrwx 3 bitnami root 4096 Feb 20 16:16 resources
drwxrwxrwx 2 bitnami root 4096 Feb 20 16:16 routes
drwxrwxrwx 5 bitnami root 4096 Feb 20 16:16 storage
drwxrwxrwx 2 bitnami root 4096 Feb 20 16:16 tests
drwxrwxrwx 36 bitnami root 4096 Jul 2 00:46 vendor





Tried adding this to my .env file in /opt/bitnami/apache/htdocs :




FFMPEG_BINARIES=/opt/bitnami/apache/htdocs/vendor/php-ffmpeg/php-ffmpeg/src/FFMpeg
FFPROBE_BINARIES=/opt/bitnami/apache/htdocs/vendor/php-ffmpeg/php-ffmpeg/src/FFProbe





-
-
How to convert webm blob to mp4 blob in angular 11 ?
16 juin 2023, par shubham patilI Have recorded the video using MediaRecorder after recording its storing that blob in webm format but after downloading the video its not supporting to share as media.


I tried ffmpeg but its not working showing below error


Error: ./node_modules/@ffmpeg/ffmpeg/src/browser/fetchFile.js 29:51
Module parse failed: Unexpected token (29:51)
File was processed with these loaders:
 * ./node_modules/@angular-devkit/build-angular/src/babel/webpack-loader.js
 * ./node_modules/@ngtools/webpack/src/ivy/index.js
You may need an additional loader to handle the result of these loaders.
| /* From remote server/URL */
| } else {
> const res = await fetch(new URL(_data, import.meta.url).href);
| data = await res.arrayBuffer();
| }

Error: ./node_modules/@ffmpeg/ffmpeg/src/browser/getCreateFFmpegCore.js 33:52
Module parse failed: Unexpected token (33:52)
File was processed with these loaders:
 * ./node_modules/@angular-devkit/build-angular/src/babel/webpack-loader.js
 * ./node_modules/@ngtools/webpack/src/ivy/index.js
You may need an additional loader to handle the result of these loaders.
| throw Error('corePath should be a string!');
| }
> const coreRemotePath = new URL(_corePath, import.meta.url).href;
| const corePath = await toBlobURL(
| coreRemotePath,

Error: ./node_modules/@ffmpeg/ffmpeg/src/browser/defaultOptions.js 7:68
Module parse failed: Unexpected token (7:68)
File was processed with these loaders:
 * ./node_modules/@angular-devkit/build-angular/src/babel/webpack-loader.js
 * ./node_modules/@ngtools/webpack/src/ivy/index.js
You may need an additional loader to handle the result of these loaders.
| */
| const corePath = typeof process !== 'undefined' && process.env.NODE_ENV === 'development'
> ? new URL('/node_modules/@ffmpeg/core/dist/ffmpeg-core.js', import.meta.url).href
| : `https://unpkg.com/@ffmpeg/core@${pkg.devDependencies['@ffmpeg/core'].substring(1)}/dist/ffmpeg-core.js`;



Im not able to resolve this error.


here is the package.json


{
 "name": "convert",
 "version": "1.0.0",
 "private": true,
 "description": "Motor",
 "scripts": {
 "ng": "ng",
 "start": "node --max_old_space_size=4096 node_modules/@angular/cli/bin/ng serve --port 4300",
 "test": "ng test",
 "lint": "tslint ./src/**/*.ts -t verbose",
 "e2e": "ng e2e"
 },
 "keywords": [],
 "author": "",
 "dependencies": {
 "@angular/animations": "~11.2.14",
 "@angular/common": "~11.2.14",
 "@angular/compiler": "~11.2.14",
 "@angular/core": "~11.2.14",
 "@angular/forms": "~11.2.14",
 "@angular/localize": "^11.2.14",
 "@angular/platform-browser": "~11.2.14",
 "@angular/platform-browser-dynamic": "~11.2.14",
 "@angular/router": "~11.2.14",
 "@ffmpeg/ffmpeg": "^0.11.6",
 "@ng-bootstrap/ng-bootstrap": "4.2.1",
 "@ngui/auto-complete": "^3.0.0",
 "angular-in-memory-web-api": "~0.8.0",
 "angular2-toaster": "^8.0.0",
 "core-js": "2.6.5",
 "hammerjs": "^2.0.8",
 "jquery": "^3.2.1",
 "moment": "^2.24.0",
 "moment-timezone": "^0.5.17",
 "mux.js": "^6.3.0",
 "ng-circle-progress": "1.6.0",
 "ng2-toastr": "^4.1.2",
 "ngui-angular2-auto-complete": "^0.1.1",
 "ngx-device-detector": "^2.0.10",
 "ngx-spinner": "^7.2.0",
 "rxjs": "6.6.7",
 "rxjs-compat": "^6.0.0-rc.0",
 "systemjs": "3.1.0",
 "tslib": "^2.0.0",
 "video.js": "^8.3.0",
 "zone.js": "~0.10.2"
 },
 "devDependencies": {
 "@angular-devkit/build-angular": "~0.1102.13",
 "@angular/cli": "^11.2.13",
 "@angular/compiler-cli": "^11.2.14",
 "@types/dom-mediacapture-record": "^1.0.16",
 "@types/jasmine": "~3.6.0",
 "@types/node": "^12.11.1",
 "canonical-path": "1.0.0",
 "codelyzer": "^6.0.0",
 "concurrently": "^4.1.0",
 "jasmine-core": "~3.6.0",
 "karma": "~6.3.2",
 "karma-chrome-launcher": "~3.1.0",
 "karma-cli": "^2.0.0",
 "karma-jasmine": "~4.0.0",
 "karma-jasmine-html-reporter": "^1.5.0",
 "lite-server": "^2.4.0",
 "lodash": "^4.16.4",
 "protractor": "~7.0.0",
 "raw-loader": "^4.0.2",
 "rimraf": "^2.6.3",
 "tslint": "~6.1.0",
 "typescript": "4.0.7"
 },
 "repository": {}
}



and here is ffmpeg code


const ffmpeg = createFFmpeg({
 log: true,
 });