Guys, proposals should be published both on the project wiki (or Apache wiki) and at melange, that's important not to miss melange.
-- With best regards / с наилучшими пожеланиями, Alexei Fedotov / Алексей Федотов, http://dataved.ru/ +7 916 562 8095 On Mon, Apr 2, 2012 at 2:35 PM, [email protected] <[email protected]> wrote: > *Have I understood right that upload stream from a user with a wide > > connection is with high quality, but then when it has gone to the > server the quality of the download stream could be changed for a user > with narrow connection? What do you think about the importance of the > task?* > => No, curently we can't deliver different stream based on user > configuration. Basically this task requires to modify Red5. > Importance of that feature ... well sure it would be nice and important to > be able to have the option to watch a stream in different quality modes and > eventually in HTTP streaming instead of flash. At some point it will require > you to think about how to transcode the stream on server side et cetera. So > it is basically a server side project. However it is up to you to decide if > you want to apply for such a project. > > *How do you estimate this task? Is it the task for whole GSoC or just a > part? If it is for the whole GSoC, I could make it.* > => Hm yes sure we could make this task grow, however if you want to just do > this single tool you will have to give much more details about it so that > 3th parties understand what is involved in it so that it takes 4 months to > implement it. > > As far is I do understand you want to work with the UI. So your Proposal > could cover those tasks: > 1) Bandwidth / Network testing tool, > attached is a screenshot from such a tool, so that tool would have 5 > indicators: > Ports, Connection, Repeat time, Download Speed, Upload speed > You would need to create a server side servlet for testing the upload speed. > > 2) Add audio/video settings to user profile > User could adjust those settings in the Testing Application that pops up > before he enters the video conference room, That way he can record 5 seconds > and test on its own and then store the settings to his profile. > => You should add a small mockup what of what it should look like > > 3) Improve the video pods > I did not understand what you want to do here > > > Sebastian > > 2012/4/2 German Grekhov <[email protected]> >> >> Sebastian, >> >> thanks for your fast answer. Ok, I have understood that video stream >> resolution auto-adjusting is unuseful feature. So, about your >> suggestions... >> >> > Adjustment of the stream and measuring bandwidth while conferencing is >> > basically a streaming server feature... >> > So if you are going to work on that, your task will be: >> > - analysing which events are available in Red5 >> > - defining which scenarios we can realise using those events and >> > features >> > in Red5 >> > - implementing such scenarios >> >> Have I understood right that upload stream from a user with a wide >> connection is with high quality, but then when it has gone to the >> server the quality of the download stream could be changed for a user >> with narrow connection? What do you think about the importance of the >> task? >> >> > A completely separated thing would be to implement an initial load >> > Tester: >> > A separated tool (comparable to SpeedTest) that checks if you have >> > sufficient down/upload rate, can connect to needed ports and measures >> > your >> > ping time. Such a "bandwidth detection tool" would be implemented as >> > standalong application as you would do that test even outside of >> > OpenMeetings. >> >> How do you estimate this task? Is it the task for whole GSoC or just a >> part? If it is for the whole GSoC, I could make it. >> >> Unfortunately, we have not much time because the proposal should be >> uploaded until the 6th of April, so I need harry up with this choice. >> >> German. >> >> >> > 2012/4/2 [email protected] <[email protected]> >> > >> >> Hi German, >> >> >> >> thanks for the proposal! >> >> >> >> Could you please explain a bit more detailed what you are going to do >> >> and >> >> what tools and methods you will be exactly using? For example for UI >> >> changes it is common that you might include a small mackup that >> >> describes >> >> the changes. >> >> >> >> About the automatic bandwidth detection / adjustment: >> >> I would like to know what process you imagine to adjust the bandwidth. >> >> To >> >> detect the bandwidth is one thing, however to change somebodys >> >> bandwidth >> >> you would need to re-publish his stream with different video settings. >> >> The >> >> width and height of the video has the biggest impact on bandwidth. >> >> However >> >> changing the video pod width/height "auto-magically" is no option... >> >> the >> >> user chooses that value. >> >> The bandwidth detection also cannot change the download rate of >> >> anybody, >> >> you can only influence the upload bandwidth. If you want to change >> >> somebodys download rate the only option you got is turning on/off video >> >> as >> >> we don't provide different streams available for each participant. >> >> Measuring the bandwidth while you are doing conferencing is also not >> >> that >> >> easy, you can hardly do load test permanently while conferencing as the >> >> bandwidth test will affect the conference (for example audio will >> >> stutter >> >> et cetera). >> >> So I wonder what exactly have you in mind ? What tools and methods are >> >> you >> >> going to use ? >> >> >> >> Thanks! >> >> Sebastian >> >> >> >> >> >> >> >> 2012/4/2 German Grekhov <[email protected]> >> >> >> >>> Hello. >> >>> I'm German Grekhov. I want to take a part in Google Summer of code >> >>> with the OpenMeetings project. >> >>> You could find and read my proposal here: >> >>> >> >>> >> >>> https://docs.google.com/document/d/1k0d70n0i-54pnsUgm7FycnHLI6v9yNSdZ_Md4iPDeFA/edit >> >>> >> >>> Everybody has the right of commenting this document. >> >>> >> >>> Best regards, >> >>> German Grekhov. >> >>> >> >> >> >> >> >> >> >> -- >> >> Sebastian Wagner >> >> https://twitter.com/#!/dead_lock >> >> http://www.openmeetings.de <http://incubator.apache.org/openmeetings/> >> >> http://www.webbase-design.de >> >> http://www.wagner-sebastian.com >> >> [email protected] >> >> >> > >> > >> > >> > -- >> > Sebastian Wagner >> > https://twitter.com/#!/dead_lock >> > http://www.openmeetings.de <http://incubator.apache.org/openmeetings/> >> > http://www.webbase-design.de >> > http://www.wagner-sebastian.com >> > [email protected] > > > > > -- > Sebastian Wagner > https://twitter.com/#!/dead_lock > http://www.openmeetings.de > http://www.webbase-design.de > http://www.wagner-sebastian.com > [email protected]
