-
Notifications
You must be signed in to change notification settings - Fork 7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Screen sharing #2233
Comments
Can you share more details? |
Hi, this is a really weird tool meet.jit.si does not a single time do what is should nor what it is supposed to do. What a chaos. Completely unusable.am on Linux, KDE Neon, with latest stable Firefox , then I go to the address and want to share with someone and when I click screensharing it does this: https://prnt.sc/hi3s2j |
What is the exact problem you are facing with meet.jit.si? Have you tried with chrome/chromium, Firefox is known to use a lot of CPU when doing webrtc calls. This a video conferencing solution which involves several server-side components(jitsi-videobridge, jicofo, web server and prosody a xmpp server) and a webrtc javascript web application(jitsi-meet) which all are needed so it can operate. If you want to install it, the easiest way is to use Debian/Ubuntu machine and read the guide. Other than that, you just open a page, copy the link and send it to another participant to open it in their browser and that's it, for the best experience we recommend using chrome or chromium. |
Thank you for trying to help me. Look, I opened the URL in firefox cause it is my browser now after I left Chromium really disappointed. I used the meet.jit.si and wanted to show ANY window to the other but she, using safari on iMac couldnt see anything. The voice stuff was very bad, the whole fucntionality leaves me really wondering and then that when I want to present screen why should I see it in Big or nearly full view myself? I see my screen already on my real screen. get me? |
No need for a screencast I know what you are talking about, we have discussed this a number of times. But we came to the same conclusion: this is physics, you cannot stop a mirror from displaying the view from the other mirror. And as I said earlier screen sharing is to be used with other tabs/windows/screens there is no point of showing your own conference screen, but if you want to do that, you know what is the result. There is information about the desktop client and about jitsi-meet and the other projects on the website. I already send you a link to jitsi-meet installation guide. If you want to use the desktop client you need a service to use it with, xmpp or sip service you need to find and subscribe to it. But for best video experience we recommend using chrome and jitsi-meet. Browsers like Edge and Safari are in their early stage of using webrtc, and so we are working on adding support for them, but for example safari, for now, we only support audio there. I can continue explaining about browsers and problems they have, but there is no need to go in details, and these are stuff we cannot change, we can only try to adopt with them and give to the user the best possible experience, which is not always the best for them. |
Ok. The other tabs dont work, the only tab that is showing ANY kind of reaction is the one that records itself. I hoped to have a solution to present to foreign clients but maybe this is not the way to go |
What is the browser and its version that you are using? You are trying on meet.jit.si, right? There are numerous ways we can see what is the problem. For example, you can send me the link you were testing with and I can check what can be the cause of the problem. |
I used firefox 57.0.1 on KDE neon |
Can you try with chrome/chromium? |
I can, yes. I also looked for app in chromium they had no effect. Let me see Okay, this looks amazing: https://prnt.sc/hi88j6 And also I was able to share the wahtever window there was open. this was what I should have been warned off when I used Firefox, because there not even 105 of that works. But this looks good. Now taking part, I mean WATCHING, will it work with the other three major browsers? FF, IE and safari? Thanks for your help already so far. |
So for IE there was a support using a third-party plugin, but this soon will be removed and only Edge will be supported. Safari, for now, is audio only. |
If Chrome/Chromium are the only web browsers that work well with the screensharing feature, then why not have a pop-up appear to the user (if they attempt to use screensharing, and are not using Chrome/Chromium), that they would do well to use Chrome/Chromium instead, and then use the screensharing feature. Let the tool be self-documenting! Just be honest about what currently works, and doesn't work, respective of the browser in use, as they try different features out. That would make for much less frustration, I think. |
@esbeeb Firefox browser works well with Screen sharing, Chrome needs to install a separate extension. But in Chrome 70 version there are improvements with native screen sharing api: https://groups.google.com/forum/#!msg/discuss-webrtc/Uf0SrR4uxzk/uO8sLrWuEAAJ |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
I test screen sharing on current https://meet.jit.si/ version in Chrome 71, is still want to install extension and not works without extension. As I understand, via @damencho Maybe you implement |
After upgrading to Chromium 72 it works, seems in 70 & 71 this feature is not enabled by default! |
Monsieur,
Vous êtes convoqué à une seance d'entrevue et de simulation qui se tiendra le jeudi 21 février 2018 au local TSE 713 d’après l’horaire suivant :
· 9h30 à 12h30 :
· 13h30 à 16h30 : CREÉ
Le mercredi 20 février 2019 à 14:07:07 UTC−5, Alexey Murz Korepov <notifications@github.com> a écrit :
After upgrading to Chromium 72 it works, seems in 70 & 71 this feature is not enabled by default!
So, @lweffer - let's close this bug as Fixed?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Everytime I try to share the screen it fails.
The text was updated successfully, but these errors were encountered: