Open Jean-Baptiste-Lasselle opened 1 year ago
this one will be useful after adding one new overlay for each join live from a new person : when a given person speaks, the wave reacts only for the overlay of the speaking user.
popopo pour avoir un powerpoint et à chaque slide, le background peut changer https://obsproject.com/forum/resources/transparent-google-slides-player.1788/
mixing multiple audio sources : https://obsproject.com/forum/resources/audio-monitor.1186/
oh excellent if i can apply that one for people who have already joined in the live https://obsproject.com/forum/resources/muted-notification.1706/
this one is even better : https://obsproject.com/forum/resources/scale-to-sound.1336/
if that one helps creating shorts : https://obsproject.com/forum/resources/aitum-vertical.1715/
@BorisTherin celui-là il est pour toi: https://obsproject.com/forum/resources/obs-lottie.1573/
this one maybe for join live feature https://obsproject.com/forum/resources/teleport.1445/
ok alors là voilà clairement un plugin qui permet de faire du join live, en collaboration avec un serveur annexe, qui lui permet de chatter en vidéo audio : https://obsproject.com/forum/resources/camerapro-io-add-remote-video-feeds-into-obs.1578/
voilà un autre candidat encore plus sérieux :
très intéressant celui là aussi pour lancer un compte-à-rebours: https://obsproject.com/forum/resources/boxing-rounds-browser-source-timer.1699/
celui là à la place de StreamFX : https://obsproject.com/forum/resources/3d-effect.1692/
pour que quelqu'un de la régie ait le contrôle uniquement sur une seule overlay, afin d'apporter des éléments à l'antenne, comme d'afficher un numéor , une adresse email, ou encore des données statistiques, ou aller sur google pour faire une recherche ?
séparer l'audio de la vidéo: https://obsproject.com/forum/resources/obs-recording-demuxer.1524/
j'ai fouiller la doc de https://github.com/datarhei/restreamer ils utilsent ce player qui semble tres complet: https://github.com/clappr/clappr demo
concernant un pitch-meter: (detection de l'activité vocale pour le rendu cote overlay intervenants) https://makitweb.com/demos/pitch-volume-detection-in-speech-recognition-javascript
la page traite aussi de reconnaissance voicetotext (en anglais) mais on s'en fout.
leurs volume-meter.js script recupere un context audio (voir video pour nos besoin) & de là on pourra equiper notre overlay intervenants pour render qui s'exprime.
/*
The MIT License (MIT)
Copyright (c) 2014 Chris Wilson
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. */
/*
Usage: audioNode = createAudioMeter(audioContext,clipLevel,averaging,clipLag);
audioContext: the AudioContext you're using. clipLevel: the level (0 to 1) that you would consider "clipping". Defaults to 0.98. averaging: how "smoothed" you would like the meter to be over time. Should be between 0 and less than 1. Defaults to 0.95. clipLag: how long you would like the "clipping" indicator to show after clipping has occured, in milliseconds. Defaults to 750ms.
Access the clipping through node.checkClipping(); use node.shutdown to get rid of it. */
function createAudioMeter(audioContext,clipLevel,averaging,clipLag) { var processor = audioContext.createScriptProcessor(512); processor.onaudioprocess = volumeAudioProcess; processor.clipping = false; processor.lastClip = 0; processor.volume = 0; processor.clipLevel = clipLevel || 0.98; processor.averaging = averaging || 0.95; processor.clipLag = clipLag || 750;
// this will have no effect, since we don't copy the input to the output,
// but works around a current Chrome bug.
processor.connect(audioContext.destination);
processor.checkClipping =
function(){
if (!this.clipping)
return false;
if ((this.lastClip + this.clipLag) < window.performance.now())
this.clipping = false;
return this.clipping;
};
processor.shutdown =
function(){
this.disconnect();
this.onaudioprocess = null;
};
return processor;
}
function volumeAudioProcess( event ) { var buf = event.inputBuffer.getChannelData(0); var bufLength = buf.length; var sum = 0; var x;
// Do a root-mean-square on the samples: sum up the squares...
for (var i=0; i<bufLength; i++) {
x = buf[i];
if (Math.abs(x)>=this.clipLevel) {
this.clipping = true;
this.lastClip = window.performance.now();
}
sum += x * x;
}
// ... then take the square root of the sum.
var rms = Math.sqrt(sum / bufLength);
// Now smooth this out with the averaging factor applied
// to the previous sample - take the max here because we
// want "fast attack, slow release."
this.volume = Math.max(rms, this.volume*this.averaging);
}