
Recherche avancée
Autres articles (98)
-
Activation de l’inscription des visiteurs
12 avril 2011, parIl est également possible d’activer l’inscription des visiteurs ce qui permettra à tout un chacun d’ouvrir soit même un compte sur le canal en question dans le cadre de projets ouverts par exemple.
Pour ce faire, il suffit d’aller dans l’espace de configuration du site en choisissant le sous menus "Gestion des utilisateurs". Le premier formulaire visible correspond à cette fonctionnalité.
Par défaut, MediaSPIP a créé lors de son initialisation un élément de menu dans le menu du haut de la page menant (...) -
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. -
Support audio et vidéo HTML5
10 avril 2011MediaSPIP utilise les balises HTML5 video et audio pour la lecture de documents multimedia en profitant des dernières innovations du W3C supportées par les navigateurs modernes.
Pour les navigateurs plus anciens, le lecteur flash Flowplayer est utilisé.
Le lecteur HTML5 utilisé a été spécifiquement créé pour MediaSPIP : il est complètement modifiable graphiquement pour correspondre à un thème choisi.
Ces technologies permettent de distribuer vidéo et son à la fois sur des ordinateurs conventionnels (...)
Sur d’autres sites (8868)
-
Anomalie #2572 : Erreur à l’activation des plugins : "Erreur... Fichier actionner introuvable"
17 mars 2012, par marcimat -Pendant un temps, on avait une erreur un peu semblable si l’URL du site dans la configuration du SPIP n’était pas correcte (différente de celle utilisée dans le navigateur pour voir le site). Est-ce que c’est le cas chez toi ?
-
google function : TypeError : Cannot read property 'name' of undefined
9 décembre 2019, par JuggernaughtI’m trying to use Google cloud function to transcode videos from a storage bucket and outputs into another bucket using code posted online but with a few adjustments.
but I get the following error :
TypeError : Cannot read property ’name’ of undefined at transcodeVideo
(/srv/index.js:17:56) at /worker/worker.js:825:24 at at
process._tickDomainCallback (internal/process/next_tick.js:229:7)Index.js
const {Storage} = require('@google-cloud/storage');
const projectId = 'cc18-223318';
const storage = new Storage({
projectId: projectId,
});
const ffmpegPath = require('@ffmpeg-installer/ffmpeg').path;
const ffmpeg = require('fluent-ffmpeg');
const transcodedBucket = storage.bucket('2400p');
const uploadBucket = storage.bucket('inpuut');
ffmpeg.setFfmpegPath(ffmpegPath);
exports.transcodeVideo = function transcodeVideo(event, callback) {
const file = event.data;
// Ensure that you only proceed if the file is newly created, and exists.
if (file.metageneration !== '1' || file.resourceState !== 'exists') {
callback();
return;
}
// Open write stream to new bucket, modify the filename as needed.
const remoteWriteStream = transcodedBucket.file(file.name.replace('.webm', '.mp4'))
.createWriteStream({
metadata: {
metadata: file.metadata, // You may not need this, my uploads have associated metadata
contentType: 'video/mp4', // This could be whatever else you are transcoding to
},
});
// Open read stream to our uploaded file
const remoteReadStream = uploadBucket.file(file.name).createReadStream();
// Transcode
ffmpeg()
.input(remoteReadStream)
.outputOptions('-c:v libx264') // Change these options to whatever suits your needs
.outputOptions('-c:a copy')
.outputOptions('-vf "scale=4800:2400"')
.outputOptions('-b:a 160k')
.outputOptions('-b:a 160k')
.outputOptions('-x264-params mvrange=511')
.outputOptions('-f mp4')
.outputOptions('-preset slow')
.outputOptions('-movflags frag_keyframe+empty_moov')
.outputOptions('-crf 18')
// https://github.com/fluent-ffmpeg/node-fluent-ffmpeg/issues/346#issuecomment-67299526
.on('start', (cmdLine) => {
console.log('Started ffmpeg with command:', cmdLine);
})
.on('end', () => {
console.log('Successfully re-encoded video.');
callback();
})
.on('error', (err, stdout, stderr) => {
console.error('An error occured during encoding', err.message);
console.error('stdout:', stdout);
console.error('stderr:', stderr);
callback(err);
})
.pipe(remoteWriteStream, { end: true }); // end: true, emit end event when readable stream ends
}; -
Unable to build solution in Visual Studio 2019 : The BaseOutputPath/OutputPath property is not set for project
23 juillet 2022, par mhadiIn an effort to integrate FFmpeg with Unity, I have been trying to build a solution file in Visual Studio 2019. However, I am currently unable to resolve the following error when I try to build in Visual Studio :




The BaseOutputPath/OutputPath property is not set for project
'FFmpegUnityInterop.vcxproj'. Please check to make sure that you have
specified a valid combination of Configuration and Platform for this
project. Configuration='Release' Platform='x64'. This error may
also appear if some other project is trying to follow a
project-to-project reference to this project, this project has been
unloaded or is not included in the solution, and the referencing
project does not build using the same or an equivalent Configuration
or Platform.




I have tried a number of solutions, including :


- 

- Manually adding the OutputPath in 'FFmpegUnityInterop.vcxproj'

<outputpath>bin/Build/</outputpath>
. - In the FFmpegUnityInterop.vcxproj file, moving the ProjectProperty with my preferred configuration and platform combination to the very top of the list of ProjectProperties (there are 8 of them).
- Building with different configuration and platforms.
- Trying to build from VS Dev Command prompt using the following command :

MSbuild.exe "FFmpegUnityInterop.sln" /p:Configuration=Release /p:Platform="x64"
, as well as from the Visual Studio IDE. - Tried setting the OutputPath in the command line command
(
>MSbuild.exe FFmpegUnityInterop.sln /p:Configuration=Release /p:Platform="AnyCPU" /p:OutputPath = bin\Debug
), only to have
MSbuild throw error MSB1008 (MSBUILD : error MSB1008 : Only one
project can be specified.) - Setting the configuration and platform manually in the Configuration Manager GUI in
Visual Studio.














I may have missed an attempted solution or two above, but I've tried most of the suggestions I found online, only to get the error pasted above. Part of me suspects that my compilation of FFmpeg libraries didn't execute fully, but I unfortunately do not have enough experience to verify that. Any suggestions to resolve this would be much appreciated.


PS. The project was developed privately by a private entity that is currently unreachable


- Manually adding the OutputPath in 'FFmpegUnityInterop.vcxproj'