---------- Forwarded message ---------- From: seba.wag...@gmail.com <seba.wag...@gmail.com> Date: Tue, Mar 12, 2013 at 3:46 PM Subject: Re: SWF11 components performance/stability To: Maxim Solodovnik <solomax...@gmail.com>
We should simply do some tests to measure the actual video with h264 and the default Sorensen Codec. Then we have some numbers. What are the exact reports for "Flash Player crashing" ? Sebastian 2013/3/12 Maxim Solodovnik <solomax...@gmail.com> > I can add switching H264 off, but I'm not sure if this is the problem. > Most claims are related to the crashing flash in browser. > Do you think this would help? > > > On Tue, Mar 12, 2013 at 2:56 PM, seba.wag...@gmail.com < > seba.wag...@gmail.com> wrote: > >> Sorry I did not meant default h323 I meant the default >> Sorenson Spark <http://en.wikipedia.org/wiki/Sorenson_Spark> (Sorenson >> H.263) >> >> Sebastian >> >> >> 2013/3/12 seba.wag...@gmail.com <seba.wag...@gmail.com> >> >> h264 simply needs more computing time. >>> AEC also is enabled (which needs some percentages more CPU power then >>> the previous implementation). >>> >>> Switching to later Flex SDK is surely desirable but basically the >>> performance is a Flash Player/VirtualMachine issue not a Flash Compiler >>> issue. So as long as there is no Flash Player 12 that requires a later Flex >>> SDK it is unlikely that you will gain performance advantages. >>> >>> I think there is a hardware acceleration for playback of h264 video, but >>> I have really no idea about producing h264 in the browser in that context. >>> >>> From my point of view the main reason for using h264 is the SIP >>> integration. For users that don't use SIP integration using h264 will >>> simply just mean an annoying CPU usage. >>> The case is different for AEC from my point of view. AEC brings >>> enhancement for everybody immediately. And the more of CPU that it uses is >>> only 3-4 % from my point of view. >>> >>> So my preference would be to make the video codec use the standard h323. >>> To be honest: Who has ever complained in the last couple of years about >>> video quality? The discussion is almost always about audio delay, audio >>> quality, micro echo, bad microphones et cetera but actually never about >>> video quality. >>> And from what I have seen h264 also brings no improvements in terms of >>> bandwidth usage. >>> h264 could be available via configuration (or to enable SIP >>> integration), but h323 should be used by default. >>> >>> Sebastian >>> >>> >>> 2013/3/12 Maxim Solodovnik <solomax...@gmail.com> >>> >>>> Hello Raju, Sebastian, >>>> >>>> according to https://issues.apache.org/jira/browse/OPENMEETINGS-559and >>>> various user reports (including mail from Sebastian[1]) >>>> >>>> Main code changes were: adding EnchancedMicrophone and switch to h264 >>>> >>>> According to the Google switching to h264 can cause higher CPU usage. >>>> Can this be fixed by changing H264Level? (currently H264Level.LEVEL_1_2 >>>> is used) >>>> >>>> Maybe you can us understand were performance/stability degradation >>>> caused by code changes? Or maybe it is because of Flex4.6.0? >>>> >>>> Can stability be improved by switching to Flex4.9.1? >>>> >>>> Thanks in advance for your help >>>> >>>> >>>> [1] http://markmail.org/message/2el63qarsjmbvfyy >>>> >>>> <http://markmail.org/message/2el63qarsjmbvfyy>-- >>>> WBR >>>> Maxim aka solomax >>>> >>> >>> >>> >>> -- >>> Sebastian Wagner >>> https://twitter.com/#!/dead_lock >>> http://www.webbase-design.de >>> http://www.wagner-sebastian.com >>> seba.wag...@gmail.com >>> >> >> >> >> -- >> Sebastian Wagner >> https://twitter.com/#!/dead_lock >> http://www.webbase-design.de >> http://www.wagner-sebastian.com >> seba.wag...@gmail.com >> > > > > -- > WBR > Maxim aka solomax > -- Sebastian Wagner https://twitter.com/#!/dead_lock http://www.webbase-design.de http://www.wagner-sebastian.com seba.wag...@gmail.com -- WBR Maxim aka solomax
