Hey all, I just released a Chrome extension to open Jitsi Meet videos in pop-out windows. Useful if you want to arrange your video conference across multiple monitors, or if you want to grab individual streams with e.g. OBS Studio.
Yesterday I played around with the individual video feeds in our Jitsi conference and streamed from OBS for the first time, to put the extension to the test.
I’m already quite happy with the what Jitsi enables us to do and looking forward to enhancing the extension further. I must admit the approach I’ve taken with the extension feels like it may brake in the future, because I rely primarily on the external API, but also directly call functions from lib-jitsi-meet. So I’d have to keep my extension code in sync with changes made to those APIs, when they’re deployed to meet.jit.si.
Looking forward to receive some feedback!
Also I have a question. Is it possible, in my scenario, to make the logging of Jitsi Meet (and its dependencies) less verbose, to only log errors? I’ve tried pasting JitsiMeetJS.setLogLevel(JitsiMeetJS.logLevels.ERROR);
in the console on meet.jit.si
. It reduces logging but I still see more than just errors. Could logging perhaps be reduced using the external api?
Is there a way to override the default logging config?
// Logging configuration
var loggingConfig = {
// default log level for the app and lib-jitsi-meet
defaultLogLevel: 'trace',
// Option to disable LogCollector (which stores the logs on CallStats)
// disableLogCollector: true,
// The following are too verbose in their logging with the
// {@link #defaultLogLevel}:
'modules/RTC/TraceablePeerConnection.js': 'info',
'modules/statistics/CallStats.js': 'info',
'modules/xmpp/strophe.util.js': 'log'
};