
Recherche avancée
Médias (1)
-
Revolution of Open-source and film making towards open film making
6 octobre 2011, par
Mis à jour : Juillet 2013
Langue : English
Type : Texte
Autres articles (71)
-
Amélioration de la version de base
13 septembre 2013Jolie sélection multiple
Le plugin Chosen permet d’améliorer l’ergonomie des champs de sélection multiple. Voir les deux images suivantes pour comparer.
Il suffit pour cela d’activer le plugin Chosen (Configuration générale du site > Gestion des plugins), puis de configurer le plugin (Les squelettes > Chosen) en activant l’utilisation de Chosen dans le site public et en spécifiant les éléments de formulaires à améliorer, par exemple select[multiple] pour les listes à sélection multiple (...) -
Mise à jour de la version 0.1 vers 0.2
24 juin 2013, parExplications des différents changements notables lors du passage de la version 0.1 de MediaSPIP à la version 0.3. Quelles sont les nouveautés
Au niveau des dépendances logicielles Utilisation des dernières versions de FFMpeg (>= v1.2.1) ; Installation des dépendances pour Smush ; Installation de MediaInfo et FFprobe pour la récupération des métadonnées ; On n’utilise plus ffmpeg2theora ; On n’installe plus flvtool2 au profit de flvtool++ ; On n’installe plus ffmpeg-php qui n’est plus maintenu au (...) -
De l’upload à la vidéo finale [version standalone]
31 janvier 2010, parLe chemin d’un document audio ou vidéo dans SPIPMotion est divisé en trois étapes distinctes.
Upload et récupération d’informations de la vidéo source
Dans un premier temps, il est nécessaire de créer un article SPIP et de lui joindre le document vidéo "source".
Au moment où ce document est joint à l’article, deux actions supplémentaires au comportement normal sont exécutées : La récupération des informations techniques des flux audio et video du fichier ; La génération d’une vignette : extraction d’une (...)
Sur d’autres sites (8900)
-
How to fix the error "duplicate symbol _LOG_BUFFER_LENGTH"
25 mai 2019, par Florentin LupascuI have a Unity project embedded into Swift 4 and when I build the project I get an error from a plugin named FFmpeg (used to record the screen) and the error is next :
duplicate symbol _LOG_BUFFER_LENGTH in:
/Users/developers/Library/Developer/Xcode/DerivedData/DemoApp-bszfgmzljpyourbdjoxkdabtilki/Build/Intermediates.noindex/DemoApp.build/Debug-iphoneos/DemoApp.build/Objects-normal/arm64/cmdutils.o
/Users/developers/Library/Developer/Xcode/DerivedData/DemoApp-bszfgmzljpyourbdjoxkdabtilki/Build/Intermediates.noindex/DemoApp.build/Debug-iphoneos/DemoApp.build/Objects-normal/arm64/ffmpeg.o
duplicate symbol _LOG_BUFFER_LENGTH in:
/Users/developers/Library/Developer/Xcode/DerivedData/DemoApp-bszfgmzljpyourbdjoxkdabtilki/Build/Intermediates.noindex/DemoApp.build/Debug-iphoneos/DemoApp.build/Objects-normal/arm64/cmdutils.o
/Users/developers/Library/Developer/Xcode/DerivedData/DemoApp-bszfgmzljpyourbdjoxkdabtilki/Build/Intermediates.noindex/DemoApp.build/Debug-iphoneos/DemoApp.build/Objects-normal/arm64/ffmpeg_wrapper.o
duplicate symbol _LOG_BUFFER_LENGTH in:
/Users/developers/Library/Developer/Xcode/DerivedData/DemoApp-bszfgmzljpyourbdjoxkdabtilki/Build/Intermediates.noindex/DemoApp.build/Debug-iphoneos/DemoApp.build/Objects-normal/arm64/cmdutils.o
/Users/developers/Library/Developer/Xcode/DerivedData/DemoApp-bszfgmzljpyourbdjoxkdabtilki/Build/Intermediates.noindex/DemoApp.build/Debug-iphoneos/DemoApp.build/Objects-normal/arm64/intercept.o
ld: 3 duplicate symbols for architecture arm64
clang: error: linker command failed with exit code 1 (use -v to see invocation)I want to specify that if I export the project from Unity to Xcode without to embed it is working perfectly with this Plugin.
What can be the problem with this error ?Until now I tried next thing to remove the error but none helped me :
- I checked if I have "-ObjC" in Xcode in "Other Linker Flags" and I don’t have.
- I removed a duplicate library (“libil2cpp.a”) from "Link Binary With Libraries" (XCODE)
- I changed ’No Common Blocks’ from Yes to No (under Targets->Build Settings->Apple LLVM - Code Generation )
At the end I have the same error.
Here is a print screen :Thank you so much if you spend your time to read this and any idea will be helpful.
-
How to setup a virtual mic and pipe audio to it from node.js
28 octobre 2018, par NielllesSummary of what I am trying to achieve :
I’m currently doing some work on a Discord bot. I’m trying to join a voice channel, which is the easy part, and then use the combined audio of the speakers in that voice channel as input for a webpage in a web browser. It doesn’t really matter which browser it is as long as it can be controlled with Selenium.
What I’ve tried/looked into so far
My bot so far is written up in Python using the discord.py API wrapper. Unfortunately listening to, as opposed to putting in, audio hasn’t been exactly implemented great − let alone documented − with discord.py. This made me decide to switch to node.js (i.e. discord.js) for the voice channel stuff of my bot.
After switching to discord.js it was pretty easy to determine who’s talking and create an audio stream (PCM stream) for that user. For the next part I though I’d just pipe the audio stream to a virtual microphone and select that as the audio input on the browser. You can even use FFMPEG from within node.js 1, to get something that looks like this :
const Discord = require("discord.js");
const client = new Discord.Client();
client.on('ready', () => {
voiceChannel = client.channels.get('SOME_CHANNEL_ID');
voiceChannel.join()
.then(conn => {
console.log('Connected')
const receiver = conn.createReceiver();
conn.on('speaking', (user, speaking) => {
if (speaking) {
const audioStream = receiver.createPCMStream(user);
ffmpeg(stream)
.inputFormat('s32le')
.audioFrequency(16000)
.audioChannels(1)
.audioCodec('pcm_s16le')
.format('s16le')
.pipe(someVirtualMic);
}
});
})
.catch(console.log);
});
client.login('SOME_TOKEN');This last part, creating and streaming to a virtual microphone, has proven to be rather complicated. I’ve read a ton of SO posts and documentation on both The Advanced Linux Sound Architecture (ALSA) and the JACK Audio Connection Kit, but I simply can’t figure out how to setup a virtual microphone that will show up as a mic in my browser, or how to pipe audio to it.
Any help or pointers to a solution would be greatly appreciated !
Addendum
For the past couple of days I’ve kept on looking into to this issue. I’ve now learned about ALSA loopback devices and feel that the solution must be there.
I’ve pretty much followed a post that talks about loopback devices and aims to achieve the following :
Simply imagine that you have a physical link between one OUT and one
IN of the same device.I’ve set up the devices as described in the post and now two new audio devices show up when selecting a microphone in Firefox. I’d expect one, but I that may be because I don’t entirely understand the loopback devices (yet).
The loop back devices are created and I think that they’re linked (if I understood the aforementioned article correctly). Assuming that’s the case the only problem I have to tackle is streaming the audio via FFMPEG from within node.js.
-
trying to use fluent-ffpmeg on raspberry pi
3 septembre 2018, par cdoernI am trying to use fluent ffmpeg to make a h264 file into an mp4 file. However, installing regular ffmpeg did not work since ti downloaded a very old version onto my pi. through some research i stumbled upon an ffmpeg installer on npm that installers a newer version and allows you to use it : https://www.npmjs.com/package/@ffmpeg-installer/ffmpeg however, when incorporating this into my project, PM2, the process manager I am using to run my files, throws a very stranger error :
err._length = err.length;
TypeError: Cannot create property '_length' on string 'Unsupported platform/architecture: linux-armbelow is my code for converting the file
const ffmpegPath = require('@ffmpeg-installer/ffmpeg').path;
var ffmpeg = require('fluent-ffmpeg');
ffmpeg.setFfmpegPath(ffmpegPath);
ffmpeg('/home/pi/Videos/video.h264').format('mp4');
ffmpeg.on('error', function(err) {
console.log('an error happened: ' + err.message);
})
// save to file
ffmpeg.save('/home/pi/Videos/testmovie.mp4');