Re: Screen Share, Scaling

very much correct ... On 11/21/20 10:35 AM, Maxim Solodovnik wrote: this new thread should be started some iterations ago :))) and it also illustrates how something can be easily added to open source project, and how hard to remove it :)) On Fri, 20 Nov 2020 at 21:12, kaffeesurrogat

Re: Screen Share, Scaling

this new thread should be started some iterations ago :))) and it also illustrates how something can be easily added to open source project, and how hard to remove it :)) On Fri, 20 Nov 2020 at 21:12, kaffeesurrogat wrote: > Dear all, > > I messed up the thread. Thus a new subject. Sorry for

Re: Users per room client browser scalability

Hello all, I had one other idea on how Zoom is handling this. I watched a Zoom conference where there were up to 37 participants. The participants were spread over 2 internal Zoom pages. The first page was in a 5x5 array (25) and the second was also in a 5x5 array that including the remaining 12

Re: optimize performance

Dear Alex, which one is the port openmeetings is listing on ? Still 5443 ? I've posted a message with the subject "Behind a companies firewall, changing ports and udp packages to tcp ?" changing from 5443 to standard https . Just had a few occasions to test this sitting at my companies

Re: [DISCUSSION] release current 5.1.0 as 5.0.2

this thread is a total mess now ;-( sorry sorry . On 20/11/2020 15:03, Maxim Solodovnik wrote: > NP :) > > Actually what I meant by "were used for display purposes" is > > * userA streams his/her screen at FHD 1920x1080 (but specifies > 300x900 at sharing dialog) > > as a result > > *

Re: [DISCUSSION] release current 5.1.0 as 5.0.2

NP :) Actually what I meant by "were used for display purposes" is - userA streams his/her screen at FHD 1920x1080 (but specifies 300x900 at sharing dialog) as a result - userB receives FHD video 1920x1080, but displays it in a 300x300 window as a bonus 300x300 also being used

Fwd: [DISCUSSION] release current 5.1.0 as 5.0.2

sorry maxim, send this message directly to you not to the list. need to learn how to use thunderbird Forwarded Message Subject:Re: [DISCUSSION] release current 5.1.0 as 5.0.2 Date: Fri, 20 Nov 2020 14:48:39 +0100 From: kaffeesurrogat Reply-To:

Re: Conference room limit 25?

it is recommended limit for version 4 AFAIK right now best report we have for v5: 8 participants in the same room with audio/video On Fri, 20 Nov 2020 at 11:53, Robert Savickas wrote: > Dear Maxim, > > Just a quick question about the intended room structure. > > When creating conference room,

Re: [DISCUSSION] release current 5.1.0 as 5.0.2

On Fri, 20 Nov 2020 at 20:28, kaffeesurrogat wrote: > Dear Maxim, > > > On 20/11/2020 13:09, Maxim Solodovnik wrote: > > > > > > On Fri, 20 Nov 2020 at 18:53, kaffeesurrogat > > wrote: > > > > Hi Everybody, > > > > is it a bug or a feature ? > > > >

Re: [DISCUSSION] release current 5.1.0 as 5.0.2

:-) On 11/20/20 4:05 PM, Maxim Solodovnik wrote: I guess we will made everybody's life easier if we move to the simpler versioning So let it be - 5.1.0 - 6.0.0 Are there any objections? (minors will be for the "super fast" security fixed, like it was with 5.0.1 :))) On Fri, 20 Nov 2020 at

Re: [DISCUSSION] release current 5.1.0 as 5.0.2

I guess we will made everybody's life easier if we move to the simpler versioning So let it be - 5.1.0 - 6.0.0 Are there any objections? (minors will be for the "super fast" security fixed, like it was with 5.0.1 :))) On Fri, 20 Nov 2020 at 19:29, Ali Alhaidary wrote: > True, but that is

Re: Login screen

Done, and I will lose my super power :-( On 11/20/20 3:43 PM, Maxim Solodovnik wrote: Thanks :) found it :)) please create JIRA :) On Fri, 20 Nov 2020 at 19:19, Ali Alhaidary mailto:ali.alhaid...@the5stars.org>> wrote: Good to know that you now know that I know ;-) steps: 1.

Re: Login screen

Thanks :) found it :)) please create JIRA :) On Fri, 20 Nov 2020 at 19:19, Ali Alhaidary wrote: > Good to know that you now know that I know ;-) > > steps: > 1. stop all servers (DB, turn, KMS and OM) > 2. install new snapshot, keeping same data in another folder. > 3. reboot server. > 4. start

Re: [DISCUSSION] release current 5.1.0 as 5.0.2

True, but that is because they have merged x and y together for long period of time, but internally you might find a.b.c.x.y.z ... On 11/20/20 3:12 PM, Maxim Solodovnik wrote: On Fri, 20 Nov 2020 at 18:53, Ali Alhaidary mailto:ali.alhaid...@the5stars.org>> wrote: I assume that x.y.z

Re: Login screen

Good to know that you now know that I know ;-) steps: 1. stop all servers (DB, turn, KMS and OM) 2. install new snapshot, keeping same data in another folder. 3. reboot server. 4. start KMS and OM as turn and DB starts with server boot. 5. first user logs in, this screen shows :-) , and never

Re: [DISCUSSION] release current 5.1.0 as 5.0.2

On Fri, 20 Nov 2020 at 18:53, Ali Alhaidary wrote: > I assume that x.y.z is: > It depends :)) modern software has higher majors than old days :))) you can check for example browser versions :)) > x: major technology change: as 4 to 5 moving from flash to WebRTC, so 5 > stays. > y: introducing

Re: [DISCUSSION] release current 5.1.0 as 5.0.2

On Fri, 20 Nov 2020 at 18:53, kaffeesurrogat wrote: > Hi Everybody, > > is it a bug or a feature ? > > I'm running: > > > Name > OpenMeetings > Version > 5.1.0-SNAPSHOT > Revision > b9b202a > Build date > 2020-11-18T09:35:56Z > > Previous versions offered to set the screen size before starting

Re: [DISCUSSION] release current 5.1.0 as 5.0.2

I assume that x.y.z is: x: major technology change: as 4 to 5 moving from flash to WebRTC, so 5 stays. y: introducing new functionality or big code change, since SIP is not implemented yet, 0 stays, unless considering tables DB change that is not compatible with 0, so it should be 1. z:

Re: [DISCUSSION] release current 5.1.0 as 5.0.2

Hi Everybody, is it a bug or a feature ? I'm running: Name OpenMeetings Version 5.1.0-SNAPSHOT Revision b9b202a Build date 2020-11-18T09:35:56Z Previous versions offered to set the screen size before starting screen shares. This option is gone. I would love have it back ... ;-) Screen share

Re: [DISCUSSION] release current 5.1.0 as 5.0.2

El vie, 20-11-2020 a las 09:51 +0100, Alvaro escribió: > BTW we can update the versioningrelease 5.1.0 "as is"and if/when SIP > will be ready release 6.0.0 : ...this is. .

Re: [DISCUSSION] release current 5.1.0 as 5.0.2

...This is a good idea . El vie, 20-11-2020 a las 14:45 +0700, Maxim Solodovnik escribió: > BTW we can update the versioningrelease 5.1.0 "as is" > and if/when SIP will be ready release 6.0.0 : > > WDYT? > > On Fri, 20 Nov 2020 at 14:44, Maxim Solodovnik > wrote: