-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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 by selection does not work #3077
Comments
It seems Chrome's desktop capture API is not available in node-webkit. |
@warrickhunter: node-webkit works for desktop capture API. The problem that i mentioned is about the small popup window in my screenshot (white window) you can see. That is only missing in node-webkit. See the issue #576 where Roger Wang mentioned he is working on it, but there was no status/updates regarding that issue yet. @rogerwang commented on Dec 3, 2014 |
@shamun: yes I agree with you, the popup is missing. Just to clarify, I was referring to Chrome's desktop capture api which, in Chrome, is accessed by calling |
@warrickhunter: Roger wang was working on it i think. have you seen his comment on issue #576 (posted on Dec 3, 2014), maybe he have it solved already but not yet committed for other dependencies issue. |
What is the Status of this issue please? |
This is planned to be fixed in nw13. But I'll try to fix it in nw12. |
@rogerwang: thank you very much. looking forward to it. you are genius. |
@rogerwang I am half way doing it on OSX platform, shall I finish this ? |
@jtg-gg please go ahead. thanks. looking forward to your implementation. |
@rogerwang @jtg-gg @jtg-gg, were you doing an API, or a full picker window? Great project by the way, thanks. |
@to all: Many Thanks for your contribution. I want to suggest you guys one thing to consider regarding this issue. (if its possible and easy for you guys else please ignore it.) 1 - Add the new window picker or running application picker just like Google Chrome/Canary does Scenario Storm (real life): Why keep method 1 (old) and method 2 (new):Method 1 (OLD): As it is now is very handy too in many scenarios. Method 2 (NEW which is upcoming soon): New feature like Google Chrome, Canary has one disadvantage which i faced with some Bank application requirements. In some BANK (Belgium banks) i need to make an application just like Roger Wang made as in Method 1, they want to execute our apps (Python, Java, Go application) and then simply start screen sharing which was impossible with Google Chrome, Canary because you need be human/real user clicking what to share (we need to automate it for there ATM Machines). But Roger Wang made impossible to possible with his excellent Method 1 implementation. So i think it will be wise programming to keep this both feature's let us choose as third party programmers of nodewebkit to choose, which method (1 or 2) we nee to use, maybe for compatibility we can set the method 2 as default then it will be compatible with other Chrome, Canary applications. Summary:Therefore, is it possible we can keep the existing screen share as it is and if we need Window picker like Chrome we add some additional friendly parameters or so? Both way of screen sharing has its own advantages, it will be smart programming if you guys keep as it is now and beside that include the new feature. Again please ignore if its too complicated and time consuming. |
@redgecombe I am porting google chrome screen picker UI, so it should behave exactly like chrome's screen picker |
I've just made a pull request #3163 |
Not working yet.
http://dl.nwjs.io/live-build/03-09-2015/dd7d7ad-80ebf09-be948af-459755a-2bdc251-c114bb7/nwjs-v0.12.0-win-x64.zip
(only from Google chrome i can share screen, but i should be able to do this also from nodewebkit, its not working) |
@shama I believe the API is different in NW therefore that example wouldn't work as it uses a chrome extension to achieve screensharing. |
@tommoor: main goal was to use it with talky. can you please show me an example how to make the talky compatible with nodewebkit. else this feature will be pointless for our case. if not possible we will make our own chrome version. please confirm. |
@shamun the api is different, in chrome extension, the javascript will call chrome.chooseDesktopMedia this is the documentation for nwjs |
Please note it works for me the way i wanted just if i use Google Chrome itself. But i cant do the similar with NodeWebkit. Example with Google Chrome itself: Can you please kindly take care about this, so that we do not have to re-program chrome web store extensions? |
Then only problem is now i need exactly the same features of:
but with nodewebkit features on it such as : EDIT (NodeWebKit Fallback Reference): Using InnoSetup and Google Chrome offline installer for 32/64-bit https://support.google.com/installer/answer/126299?hl=en |
Hi, |
I did some testing with NW 0.12.1 and got it working using these constraints.
|
Ya even i did the same..
I also have another doubt. When I did the above code, it showed me my own screen in the video tag. But its a screenshot. Not a video screen-sharing. Is it not possible to stream it as video and not screen-shots? |
You need to either do a play() on the video after setting the url, or setting autoplay on it.
or in the tag like
|
Thanks a lot @porsager . Tried that. And it worked :) |
Hi , |
This is fixed and released with v0.13.0-alpha0 |
Is this fixed in 12.2? Thanks! |
no. It's will not be in 0.12. The fix benefits from the change we made in 0.13 |
What is the performance characteristics of nw.js screen capture? Is it viable for screen mirroring low latency video games? |
https://github.com/nwjs/nw.js/wiki/Screen works well only if I set audio to false. |
--auto-select-desktop-capture-source='Entire screen' doesn't work on windows if the user don't have english locale installed, any way to solve this? |
I found a way to capture user desktop without prompt on all platforms (tested on 0.12.2): var sourceId = /darwin/.test(process.platform) ? 'screen:' + gui.Screen.screens[0].id : 'screen:0';
navigator.webkitGetUserMedia({
audio: false,
video: {
mandatory: {
chromeMediaSource: 'desktop',
chromeMediaSourceId: sourceId,
maxWidth: 2000,
maxHeight: 1000
},
optional:[]
}
}, function(screenStream) {
},
function(err) {
console.error('getUserMedia failed!' , err, new Date)
}
); |
Is it possible to computre the screen and stream it to and RTMP server for example ? |
@killgt ...Many Thanks. This Works Perfectly!! |
@shamun Did you succeed in making sharing working( https://talky.io) with node-webkit and chrome? |
General screen sharing seems to be working but the screen sharing by selection (see screenshot below) is not working. In Google Chrome Stable or Canary while sharing screen you get a selection dialog window where you can select which screen you want to share or which running application you want to share. That is missing in the current nodewebkit version last tested with 12(alpha).
The text was updated successfully, but these errors were encountered: