culturehub / livelab Goto Github PK

I'm trying to run LiveLab in an educational setting. When I send the room link to students (both in the network and outside the network) they don't see anyone else. Could this be due to a firewall running on the educational network? Can you tell me what ports need to be open to allow LiveLab to make connections with other clients?

Is your feature request related to a problem? Please describe.
It seems possible to get more accurate information about camera resolution and capabilities by calling track.getCapabilities() on an already active user media track. https://developer.mozilla.org/en-US/docs/Web/API/MediaStreamTrack/getCapabilities

Still researching this and will document more information here.

In Current version of chrome and Mac OS Monterey, LiveLab is not allowing me to share my entire screen and my window. It is allowing me to share another chrome browser.

Describe the bug
When internet goes in and out, loses connection between some members of call. It seems that when a user's socket connection is interrupted, the user is removed from the server list of connected users. When the socket connection reactivates, the user reconnects to other participants in the room via WebRTC, but does not return to the server list of users.

What is the expected behavior?
A clear and concise description of what you expected to happen.
User should reconnect to all users in room, and name should be added to server.

**What version of the LiveLab are you using? What room of LiveLab are you in? **
1.4.0

Describe the bug
*Issue running LiveLab in Safari browser. Homepage opens but once I press start I can't see in the room. After being in the room for a couple of minutes I get an error message and get kicked out. Receive this error message below *

Note: Updated for v1.3.9 beta

Starting LiveLab

To use LiveLab, go to https://livelab.app using Chrome environment.
It could also be accessed on Android phones or tablets. (ios devices not supported currently)

Initiation Page

1. Select your initial media devices
At the initiation page, once you grant permission for the website to access your camera and microphone as a first-time user, your media list should be auto-loaded, and the media devices connected to your laptop that are available can be selected from the video and audio drop-down menu.

** if your chrome browser doesn't pop up the media access permission box when first visit, check out our issue #3 for how to reset site permissions.

2. Name
Type in the name you will be using during the session in the "name" column.
Your input will be remembered and automatically filled in next time you use Livelab.

3. Advanced configuration of your media
Click on the "settings" button on the initiation page to open the advanced setting menu, in which you can configure your media input.
Video: Select your input, and use the input columns to adjust the video resolution and framerate.
Audio: Select your audio input, and use the checkbox to turn on/off the audio processing functions.

4. Start a session
Click on the "Start" button. Once you click "start" to start a session, you will join a room with a randomly generated room name, which is shown in the URL. You can now copy and share the URL with other people in order to add them to the session

5. Join a session via a shared URL link
If you join LiveLab via an URL link shared by others, click on "start" button will bring you to the room indicated in that shared URL.

Main Workspace

All the functions are integrated into the menu bar on the right side, which includes (from top-down):

• Turn on/off your camera
  

• Mute/unmute your microphone
  

• Screen Share
  

• Add Media Stream: add additional cameras and audio streams to the same session
  

• End Call: end your session and exit the room
  

• Settings:
  -- select the number of output switchers
  -- select different layout modes
  

• Output Volume Control: use the audio mixer to control the master volume and volumes of individual feeds
  

• Chat:
  

• Show Participant List: show how many people are in the room with their media feed information
  

Describe the bug
npm run dev fails as dotenv not installed

What is the expected behavior?
dotenv in package.json

**What version of the LiveLab are you using? What room of LiveLab are you in? **
1.4.5

Describe the bug
When you change the 'room' parameter of the page without reloading the page, LiveLab will use the previous room, rather than the updated room

To Reproduce
Steps to reproduce the behavior:
When you change the 'room' parameter of the page without reloading the page, LiveLab will use the previous room, rather than the updated room

Expected behavior
Check for user update in the URL when 'join' is pressed

Desktop (please complete the following information):

• OS: Ubuntu 18.04
• Browser Chromium
• Version 86.0.4240

Describe the bug
*What went wrong? Please give a clear and concise description of what the bug is, including the date, room URL, and the context when the issue happened. *
Like the title says, I cannot scroll down in order to have access to the >>START button while on Landscape mode.

What is the expected behavior?
A clear and concise description of what you expected to happen.
Be able to access the >>START button. A better suggestion would be to make it accessible without scrolling at all.

**What version of the LiveLab are you using? What room of LiveLab are you in? **
Running last version v1.4.6 beta
I believe this is happening in all rooms.

Did this bug happen before? How often did it happen?
(E.g. Yes, and this bug happened after I... OR No, it never works for me before...)

User Environment:
(please run the following troubleshooting tests from What is My User Agent? and WebRTC Troubleshooter, and paste the test results in this section to provide more info about the user environment and device configuration where the bug happens)

Steps to reproduce the problem:

Easy to reproduce.
-Just open Chrome on an Android (I am running on Samsung Galaxy S9)
-Put phone in landscape mode and access LiveLab room.

You cannot scroll to access the >>START button. Only if you put it back to portrait mode are you allowed to access it

Additional context
Add any other context or thoughts about the problem here

When you use Livelab, or any of its testing versions, for the first time, the Chrome browser should pop up windows right underneath the address bar on the initiation page to ask for access permission to your devices' camera and mic:

Once you click "Allow" for both, your audio and video feeds should be loaded, and you should see your video feed in the background.

Then you should refresh the whole page to activate the function to read all of your input devices (default webcam, external webcam, camTwist, etc.)

Common Issues:
There are cases when the browser doesn't pop up options to allow mic&camera, and in the console you could find errors as following:

You then will need to reset your browser permissions.

Steps to reset Chrome permissions for LiveLab

1. Click the lock icon next to address bar
2. Open Site Settings

3. Under Permissions, set "Camera" and "Microphone" to "Allow"

4. Come back to the Livelab initation page, and reload the page. You should see both your audio and video feeds are loaded now.

Describe the bug
What went wrong? Please give a clear and concise description of what the bug is.
when I log in and uncheck the audio function (Eco cancellations, auto-gains, noise) from the Advance setting I think Auto gain keep enable.

What is the expected behavior?
A clear and concise description of what you expected to happen.
I think all audio options should be turned off.

What version of the LiveLab are you using?
Please provide the version number, or the URL with the port number, to help us identify which version of LiveLab are you in
Livelab.app:8000

Did the function work before?
(E.g. Yes, and this bug happened after I... OR No, it never works for me before...)
I think yes.

Did this bug happened before? How often did it happen?
I think All time for this version

User Environment:
(please copy the info from here What is My User Agent? to provide more info about the user environment where the bug happens)
Chrome/83.0.4103.61

Steps to reproduce the problem:

Check on your Console:

1. Right-click on the webpage, and select 'Inspect '
2. Click on the 'Console' option on the top
3. Check to see any console log addressing the error
4. Screenshots: If applicable, add screenshots to help explain your problem.

Additional context
Log says all funtion is false but in real sound has feels like keep auto gain.

In an earlier version of LiveLab that uses the web audio API with media streams, echo cancellation wasn't applied properly, which causes audio of each stream to be rendered twice and created annoying echo.

This seems to be a bug with WebRTC handling audio processing functions. There's a reported issue addressing the not functioning of AEC when using web audio API:
Issue 687574: AEC when using Web Audio API

Additional context
https://developer.mozilla.org/en-US/docs/Web/API/MediaTrackConstraints/facingMode

Describe the bug
When I share on twitter, the preview image does not load. https://cards-dev.twitter.com/validator

Describe the bug
*What went wrong? Please give a clear and concise description of what the bug is, including the date, room URL, and the context when the issue happened. *
On Chrome in Android, the function Open video into its own window crashes Chrome. I also tested this in Brave browser

What is the expected behavior?
A clear and concise description of what you expected to happen.
Not to crash :)

**What version of the LiveLab are you using? What room of LiveLab are you in? **
Please provide the version number of Livelab, which could be found at the initiation page right underneath the title "LiveLab", and the room URL, and paste the info in this section
Version: v1.4.6 beta
Room URL: every room

Did this bug happen before? How often did it happen?
(E.g. Yes, and this bug happened after I... OR No, it never works for me before...)
It always happens!

User Environment:
(please run the following troubleshooting tests from What is My User Agent? and WebRTC Troubleshooter, and paste the test results in this section to provide more info about the user environment and device configuration where the bug happens)

I believe this is a bug that affects all devices. If this is not true, I will provide the necessary data asap.

Steps to reproduce the problem:
-Open Chrome and type room address.
-Select camera and mic and press >>START
-Once inside and communicating with other device, press the icon for Open video into its own window

This crashes Chrome instantly.

Additional context
Add any other context or thoughts about the problem here

BTW, is there a possibility to make the video fullscreen on Android as well as on Windows 10?
Thank you!

PS: Open video into its own window has a typo and is actually written incorrectly like this: Open video into it's own window

Describe the solution you'd like
When clicking 'add screen', an option is included to share the audio from a given browser tab. This seems to only work in Chrome.

Additional context
Add any other context or screenshots about the feature request here.