It seems I wasn't clear enough. I'll try to explain everything one more time.
Since screen-sharing is now WebRTC based we (OM devs) can only call browser API to control it Different browsers, different controls, different UI FF (all OSes) allows to choose what to share, this is why there is screen-share dialog with sharing type as a drop-down Chrome version < 72 (all OSes) requires browser plugin to perform screen-sharing Chrome version > 72 (all OSes) do native screen-sharing without plugin, and you can select the area in browser only, this is why sharing-type is disabled All browsers don't allow to get current screen-sharing width/height, this is why we have width/height input on screen-sharing dialog Screen-sharing video is being displayed using above width/height, this is why you have unnecessary borders On Sun, 14 Apr 2019 at 03:19, Aaron Hepp <aaron.h...@gmail.com> wrote: > See attached on the application running on a bare metal Windows 7 > install. > > Firefox: > Application and Window: both exhibited what you see in the video > Screen: displayed without any issues > > Chrome: > Application: black screen no flashing (but you can see the cursor moving > on the remote screen) > Screen: displayed without any issues > > One question on the screen sharing. Is there a way for it to actually > fill the window? As you by the video there is a white boarder on the top > and bottom. If you try to resize the windows, it resizes the content but > also increases the white boarder all around the screen. Didn't know if > there was a way for it to fill the "pop-up" instead of being bordered. > even when setting the height and width different you just get the screen > larger but the boarder is still just as big > > On 4/13/19 2:40 PM, R. Scholz wrote: > > Hello, > > in the evening I spent some time to ttry out the dekstop-sharing under > different circumstances. > > OS: Windows 10 1809 > > Browser: Firefox 66.0.3 > When I choose the "sharing-icon" I can slect between 3 possibilites. > No matter what I choose: A Software written in Delphi make at the viewer > only a black window. > > Chrome: 73.0.3683.103 > When I choose the "sharing-icon" I can not select between Screen, Window > ... > This box is disabled, I can ony choose "Screen". The FPS is disabled too. > Here the Delphi-Software runs perfectly. No black screen. > > Result: > Firefox: Black window > Chrome: Works perfect > > Have anybody an idea why in Chrome it works, in Firefox not? > (I tested Edge too, but there I get certificate-errors when I start the > Sharing. But it's OK, it's a virtual machine > and I have there no https-certificate.) > > Best regards, > > René > > > > Am 13.04.2019 um 14:13 schrieb Maxim Solodovnik: > > Is this behavior Browser/OS dependent? > > On Sat, 13 Apr 2019 at 17:23, Aaron Hepp <aaron.h...@gmail.com> wrote: > >> Looks like there is some "program types" that it has trouble capturing. >> Would say a flaw of WebRTC. I have the same problems with certain java >> based programs. When doing the screen sharing, you will get a black screen >> but if you look every now and then is will show for a brief instance then >> back to black "Flickers" more so. This was when capturing (window or >> Application). If you capture the screen then it can display it without >> issues. >> >> On 4/13/19 3:34 AM, R. Scholz wrote: >> >> Hello, >> >> when I share a program in OM5 some programs only show at the viewer a >> black window. >> (I told it in an email a few days ago and Maxim made some ideas to >> identify the problem.) >> >> I tried out a lot of programs and, beneath our own programmed software I >> saw that the >> product "SoftPerfect Network Scanner" make this black screen too. >> In my own "system-tools-libary" I use the (old) free-version "4.4.5". >> (Its totally enough, this free version >> do exactly what I want.) >> >> A look into the binary-code shows that it is a delphi-program. >> >> Has anyone an idea I can try? >> >> Best regards, >> >> René >> >> >> >> >> Am 13.04.2019 um 09:19 schrieb R. Scholz: >> >> Hello Aaron, >> >> I think it is the same problem I had a few weeks ago. (And I hope I >> solved it.) >> >> To your questions with the log: You find relevant logs at "/opt/logs" >> e.g. "/opt/%OMDIR%/logs". The actual log is named "catalina.out". >> >> When it is the error I think you have to edit the "mysql-persistence.xml" >> You find it in the openmeeting-Directory -> >> webapps/openmeetings/WEB-INF/classes/META-INF. >> >> Here the part of my email. >> >> My Solution: >> >> The Parameter "serverTimezone" must in the first line of the >> Driver-command (where is separated by "&"). >> It doesn't matter where you put it. >> When I put it into the comma-separated-part it's not functionally. >> >> >> Here's my line in the mysql-persistence.xml: >> >> value="DriverClassName=com.mysql.cj.jdbc.Driver >> , >> Url=jdbc:mysql://localhost:3306/openmeetings?autoReconnect=true&useUnicode=true& >> *serverTimezone=Europe/Berlin&*createDatabaseIfNotExist=true&characterEncoding=utf-8 >> &connectionCollation=utf8_general_ci&cachePrepStmts=true&cacheCallableStatements=true&cacheServerConfiguration=true&useLocalSessionState=true&elideSetAutoCommits=true&alwaysSendSetIsolation=false&enableQueryTimeouts=false&prepStmtCacheSize=3000&prepStmtCacheSqlLimit=1000&useSSL=false&nullNamePatternMatchesAll=true >> , maxTotal=100 >> , maxIdle=100 >> , minIdle=0 >> , maxWaitMillis=10000 >> , TestOnBorrow=true >> , poolPreparedStatements=true >> , Username= >> , Password=" /> >> >> >> I hope it helps. >> >> >> Best regards, >> >> >> René >> >> >> >> >> >> >> Am 13.04.2019 um 01:58 schrieb Aaron Hepp: >> >> Where are the connection logs to the database located at? Just stood up >> a new OM5 instance on a Ubuntu 16.04 install. went through all the steps, >> but does not look like it is making a connection to the MySQL database. >> >> Could not create connection to database server. Attempted reconnect 3 >> times. Giving up. >> >> Database is up and listening on port 3306, made sure database name, user >> and password were correct, but keep getting the errors. Was going to look >> at the logs but forgot where they are at to determine what the issue was. >> >> >> >> >> > > -- > WBR > Maxim aka solomax > > > > -- WBR Maxim aka solomax
