Hi George, I have added also one more configuration value in the config.xml to configure AEC. "echoPath" Specifies the echo path length (in milliseconds). A longer echo path means better echo cancellation but also introduces longer delays and requires more processing power. The default value is 128; the only other possible value is 256.
You might play around with that a bit if you like. Sebastian 2013/2/17 George Kirkham <[email protected]> > I would not have expected that any other device could use the microphone > when OM (or another application) was also using the microphone. > > George Kirkham > > Sent from Windows Mail > > *From:* [email protected] > *Sent:* 17 February 2013 11:31 > *To:* Maxim Solodovnik, George Kirkham, Тимур Тлеукенов > *CC:* dev > *Subject:* Re: Proposed changed for the AEC feature and compilation of > SWF11 > > Please keep the following limitations in mind when using the new > "enhanced" mode of the Microphone: > > - You can only use a *single* enhanced audio capture at any given time. > > So it is not possible to open another browser and run OpenMeetings using > the same device. > > It might be also that you cannot use Skype or other applications that try > to access the microphone at the same time while you are using the > Microphone in OpenMeetings > > Sebastian > > > > 2013/2/17 [email protected] <[email protected]> > >> I have enabled the AEC feature in the client in r1446971. >> There might be some new options to check in the enhancedOptions. >> Basic guide is here: >> >> http://www.adobe.com/devnet/flashplayer/articles/acoustic-echo-cancellation.html >> Some of them could be made configurable in the config.xml, but I had no >> time yet to look into it more detailed. >> >> @Maxim If the issue with the file permission and the mxmlc executable is >> fixed, IMHO you can close OPENMEETINGS-529 >> @George You are welcome to test with your users >> @Timur Theoretically we can use SPEEX codec. I think SPEEX is a bit >> better for AEC and bandwidth usage. However my issue was the last time I >> used it our recordings do no more work cause FFMPEG had very poor SPEEX >> support. But I guess for VoIP integration SPEEX would be even more handy. >> Would it help you if there is SPEEX in use? >> >> Sebastian >> >> >> 2013/2/17 [email protected] <[email protected]> >> >> The new debug URL is now: >>> http://localhost:5080/openmeetings/?swf=maindebug.as3.swf11.swf >>> >>> Sebastian >>> >>> >>> 2013/2/17 [email protected] <[email protected]> >>> >>> If I modify the needed audio/video components I do receive this error >>>> during build. >>>> >>>> -compile.flash: >>>> [java] Compiling: main.as3.lzx to maindebug.as3.swf11.swf >>>> [java] Exception in thread "main" >>>> org.openlaszlo.utils.ChainedException: org.openlaszlo.sc.CompilerError: >>>> Error running external compiler: java.io.IOException: Cannot run program >>>> "/Users/swagner/Documents/workspaces/openmeetings_zz/Openmeetings/build/openlaszlo46/WEB-INF/flexsdk/4.6.0/bin/mxmlc": >>>> error=13, Permission denied >>>> [java] at >>>> org.openlaszlo.compiler.SWF9Writer.finish(SWF9Writer.java:561) >>>> [java] at >>>> org.openlaszlo.compiler.ObjectWriter.finish(ObjectWriter.java:536) >>>> [java] at >>>> org.openlaszlo.compiler.Compiler.compile(Compiler.java:485) >>>> [java] at >>>> org.openlaszlo.compiler.Compiler.compile(Compiler.java:210) >>>> [java] at org.openlaszlo.compiler.Main.compile(Main.java:408) >>>> [java] at org.openlaszlo.compiler.Main.lzc(Main.java:348) >>>> [java] at org.openlaszlo.compiler.Main.main(Main.java:109) >>>> [java] Caused by: org.openlaszlo.sc.CompilerError: Error running >>>> external compiler: java.io.IOException: Cannot run program >>>> "/Users/swagner/Documents/workspaces/openmeetings_zz/Openmeetings/build/openlaszlo46/WEB-INF/flexsdk/4.6.0/bin/mxmlc": >>>> error=13, Permission denied >>>> [java] at >>>> org.openlaszlo.sc.SWF9Generator.callFlexCompiler(SWF9Generator.java:1204) >>>> [java] at >>>> org.openlaszlo.sc.SWF10Compiler.finishApp(SWF10Compiler.java:70) >>>> [java] at >>>> org.openlaszlo.compiler.SWF9Writer.finish(SWF9Writer.java:545) >>>> [java] ... 6 more >>>> [java] Caused by: org.openlaszlo.sc.CompilerError: Error running >>>> external compiler: java.io.IOException: Cannot run program >>>> "/Users/swagner/Documents/workspaces/openmeetings_zz/Openmeetings/build/openlaszlo46/WEB-INF/flexsdk/4.6.0/bin/mxmlc": >>>> error=13, Permission denied >>>> [java] at >>>> org.openlaszlo.sc.SWF9Generator.callFlexCompiler(SWF9Generator.java:1204) >>>> [java] at >>>> org.openlaszlo.sc.SWF10Compiler.finishApp(SWF10Compiler.java:70) >>>> [java] at >>>> org.openlaszlo.compiler.SWF9Writer.finish(SWF9Writer.java:545) >>>> [java] at >>>> org.openlaszlo.compiler.ObjectWriter.finish(ObjectWriter.java:536) >>>> [java] at >>>> org.openlaszlo.compiler.Compiler.compile(Compiler.java:485) >>>> [java] at >>>> org.openlaszlo.compiler.Compiler.compile(Compiler.java:210) >>>> [java] at org.openlaszlo.compiler.Main.compile(Main.java:408) >>>> [java] at org.openlaszlo.compiler.Main.lzc(Main.java:348) >>>> [java] at org.openlaszlo.compiler.Main.main(Main.java:109) >>>> >>>> BUILD FAILED >>>> >>>> My modified build.xml looks like this: >>>> <target name="compile.laszlo.main.as3" >>>> depends="compile.laszlo.main.debug.as3"> >>>> >>>> <antcall target="-compile.flash" inheritAll="true" >>>> inheritRefs="true"> >>>> <param name="flash.classpath.ref" value="laszlo46.lib" /> >>>> <param name="flash.src.dir" value="${laszlo.as3.src.dir}" /> >>>> >>>> <param name="flash.lps.home" value="${laszlo46.home}" /> >>>> <param name="flash.runtime" value="swf11" /> >>>> <param name="flash.main.file" value="main.as3.lzx" /> >>>> <param name="flash.out.file" value="main.as3.swf11.swf" /> >>>> <param name="flash.debug" value="" /> >>>> </antcall> >>>> </target> >>>> >>>> <target name="compile.laszlo.main.debug.as3" >>>> depends="-retrieve-openlaszlo46"> >>>> >>>> <antcall target="-compile.flash" inheritAll="true" >>>> inheritRefs="true"> >>>> <param name="flash.classpath.ref" value="laszlo46.lib" /> >>>> <param name="flash.src.dir" value="${laszlo.as3.src.dir}" /> >>>> >>>> <param name="flash.lps.home" value="${laszlo46.home}" /> >>>> <param name="flash.runtime" value="swf11" /> >>>> <param name="flash.main.file" value="main.as3.lzx" /> >>>> <param name="flash.out.file" >>>> value="maindebug.as3.swf11.swf" /> >>>> >>>> <param name="flash.debug" value="--debug" /> >>>> </antcall> >>>> </target> >>>> >>>> >>>> I think the XML is correct, the paths point to valid files but I wonder >>>> why the SWF11 compilation has this issue. I never saw this happen in SWF10 >>>> and the 4.5 SDK. >>>> >>>> After doing a manual: chmod +x >>>> /Users/swagner/Documents/workspaces/openmeetings_zz/Openmeetings/build/openlaszlo46/WEB-INF/flexsdk/4.6.0/bin/mxmlc >>>> >>>> Everything seems to be fine. >>>> >>>> Sebastian >>>> >>>> >>>> 2013/2/16 [email protected] <[email protected]> >>>> >>>> Thanks! I will test later today. >>>>> >>>>> Sebastian >>>>> Am 16.02.2013 00:18 schrieb "Maxim Solodovnik" <[email protected]>: >>>>> >>>>> 1) and 2) are done >>>>>> >>>>>> here is the example of ant target modified to use 4.9.5 compiler and >>>>>> resulting "BUILD SUCCESSFUL" (32-bit JDK only) >>>>>> >>>>>> <target name="compile.laszlo.networktesting.debug" depends="* >>>>>> -retrieve-openlaszlo46*"> >>>>>> <antcall target="-compile.flash" inheritAll="true" inheritRefs="true"> >>>>>> <param name="flash.classpath.ref" value="*laszlo46.lib*" /> >>>>>> <param name="flash.src.dir" >>>>>> value="${laszlo.as3.src.dir}/networkTesting" /> >>>>>> <param name="flash.lps.home" value="${*laszlo46.home*}" /> >>>>>> <param name="flash.runtime" value="*swf11*" /> >>>>>> <param name="flash.main.file" value="networktesting.lzx" /> >>>>>> <param name="flash.out.file" value="*networktestingdebug.swf11.swf*" >>>>>> /> >>>>>> <param name="flash.debug" value="--debug" /> >>>>>> </antcall> >>>>>> </target> >>>>>> >>>>>> highlighted are parts necessary to use Flex 4.6 >>>>>> In effect since rev. 1446514 >>>>>> >>>>>> >>>>>> >>>>>> On Fri, Feb 15, 2013 at 5:56 PM, Maxim Solodovnik < >>>>>> [email protected]> wrote: >>>>>> >>>>>>> According to this: >>>>>>> http://www.openlaszlo.org/pipermail/laszlo-dev/2012-July/024933.html >>>>>>> >>>>>>> we going to be limited on 32bit JDK :( >>>>>>> >>>>>>> >>>>>>> >>>>>>> On Fri, Feb 15, 2013 at 5:41 PM, Maxim Solodovnik < >>>>>>> [email protected]> wrote: >>>>>>> >>>>>>>> Flex 4.6 is not included into openlaszlo 5.0. Will use 4.9.5. >>>>>>>> >>>>>>>> >>>>>>>> On Fri, Feb 15, 2013 at 1:47 PM, Maxim Solodovnik < >>>>>>>> [email protected]> wrote: >>>>>>>> >>>>>>>>> ok >>>>>>>>> I'll check and send you results of this investigation >>>>>>>>> >>>>>>>>> >>>>>>>>> On Fri, Feb 15, 2013 at 1:45 PM, [email protected] < >>>>>>>>> [email protected]> wrote: >>>>>>>>> >>>>>>>>>> I think we need Flex 4.6. >>>>>>>>>> It could be that still this is our branch to use: >>>>>>>>>> http://svn.openlaszlo.org/openlaszlo/branches/flex4.6/ >>>>>>>>>> >>>>>>>>>> And as far as I know this branch is a 1:1 copy of the 4.9.5 >>>>>>>>>> release. >>>>>>>>>> >>>>>>>>>> But lets check OpenLaszlo trunk, maybe somebody has made the >>>>>>>>>> changes needed to have swf11 and flex 4.6 available. >>>>>>>>>> >>>>>>>>>> Sebastian >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> 2013/2/15 [email protected] <[email protected]> >>>>>>>>>> >>>>>>>>>> Plz check what SDK is used internally / what Flex (what version >>>>>>>>>>> of mxmlc.jar) compiler is used? >>>>>>>>>>> It might happen that this does not even compile to SWF11. >>>>>>>>>>> My Internet is currently pretty slow, sorry it would take a >>>>>>>>>>> while to check that here. >>>>>>>>>>> >>>>>>>>>>> Thanks! >>>>>>>>>>> Sebastian >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> 2013/2/15 Maxim Solodovnik <[email protected]> >>>>>>>>>>> >>>>>>>>>>>> http://www.openlaszlo.org/download >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> OpenLaszlo Latest Nightly Builds >>>>>>>>>>>> points to 5.0b2 >>>>>>>>>>>> I'll use it >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> On Fri, Feb 15, 2013 at 1:12 PM, [email protected] < >>>>>>>>>>>> [email protected]> wrote: >>>>>>>>>>>> >>>>>>>>>>>>> ah sure Raju has set up a new repository. >>>>>>>>>>>>> If there is a nightly build from that we should use it. >>>>>>>>>>>>> >>>>>>>>>>>>> Can you please post the link to it? >>>>>>>>>>>>> I guess you need a nightly build, building OpenLaszlo from >>>>>>>>>>>>> source is not so straightforward ... you need a lot of special >>>>>>>>>>>>> tools. >>>>>>>>>>>>> actually without OSX its almost impossible (except you are a >>>>>>>>>>>>> cygwin geek) >>>>>>>>>>>>> >>>>>>>>>>>>> Sebastian >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> 2013/2/15 Maxim Solodovnik <[email protected]> >>>>>>>>>>>>> >>>>>>>>>>>>>> I googled openlaszlo swf 11 and get the post regarding latest >>>>>>>>>>>>>> openlaszlo from git >>>>>>>>>>>>>> it is 5.0 currently >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> On Fri, Feb 15, 2013 at 12:59 PM, [email protected] < >>>>>>>>>>>>>> [email protected]> wrote: >>>>>>>>>>>>>> >>>>>>>>>>>>>>> Good question. >>>>>>>>>>>>>>> Basically we have that 4.9.5 version from Raju which is >>>>>>>>>>>>>>> using the needed flex SDK internally. >>>>>>>>>>>>>>> I don't know if those changes ever made it into the 5.0 >>>>>>>>>>>>>>> Version, espacially which flex SDK 5.0 is using internally. >>>>>>>>>>>>>>> If 5.0 uses a newer SDK and supports swf11 we should use it. >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Seb >>>>>>>>>>>>>>> Am 15.02.2013 18:28 schrieb "Maxim Solodovnik" < >>>>>>>>>>>>>>> [email protected]>: >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Should openlaszlo 4.9.5 or 5.0 should be used? >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> On Fri, Feb 15, 2013 at 10:50 AM, Maxim Solodovnik < >>>>>>>>>>>>>>>> [email protected]> wrote: >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> OK I'll handle 1 and 2 today (or tonight :) ) >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> On Fri, Feb 15, 2013 at 10:48 AM, [email protected] < >>>>>>>>>>>>>>>>> [email protected]> wrote: >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> From my perspective we need to do the following: >>>>>>>>>>>>>>>>>> 1) add openlaszlo 4.9.5 to our ivy list to have both >>>>>>>>>>>>>>>>>> runtime environments: 4.9 and 4.9.5 >>>>>>>>>>>>>>>>>> Question: How will ivy behave when you want / force both >>>>>>>>>>>>>>>>>> versions? Cause I can imagine Ivy will think that 4.9.5 is >>>>>>>>>>>>>>>>>> sufficient to >>>>>>>>>>>>>>>>>> download. >>>>>>>>>>>>>>>>>> But we need also version 4.9 because 4.9.5 does not SWF8 >>>>>>>>>>>>>>>>>> file format anymore. >>>>>>>>>>>>>>>>>> Any ideas on that? >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> My roughest idea would be to rename the entire .tgz file >>>>>>>>>>>>>>>>>> so that it will treat it as if those or completely different >>>>>>>>>>>>>>>>>> packages. >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> 2) And then we need to refactor the build.xml to have two >>>>>>>>>>>>>>>>>> openlaszlo directories (laszlo.home) options. >>>>>>>>>>>>>>>>>> So when compiling the SWF8 stuff it will use >>>>>>>>>>>>>>>>>> openlaszlo4.9 and when it compiles to SWF11 it will use >>>>>>>>>>>>>>>>>> openlaszlo 4.9.5 >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> 3) We need to refactor the Audio/Video components. >>>>>>>>>>>>>>>>>> Basically >>>>>>>>>>>>>>>>>> in editRecordStreamSWF10.lzx line 240 "getMicrophone" has >>>>>>>>>>>>>>>>>> to be replaced with: "getEnhancedMicrophone" >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> http://help.adobe.com/en_US/FlashPlatform/reference/actionscript/3/flash/media/Microphone.html >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> And there has to be checked which of those config values >>>>>>>>>>>>>>>>>> are valid (or which ones are important to be added). Cause >>>>>>>>>>>>>>>>>> enhanced >>>>>>>>>>>>>>>>>> microphones have a different option set. >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> Some of those new variables should be made available >>>>>>>>>>>>>>>>>> through the config.xml (and old ones removed). >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> @Maxim: If you could take care about 1) + 2) I would be >>>>>>>>>>>>>>>>>> really thankful. Issue 3) is basically something I have been >>>>>>>>>>>>>>>>>> testing >>>>>>>>>>>>>>>>>> already. >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> Thanks! >>>>>>>>>>>>>>>>>> Sebastian >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> -- >>>>>>>>>>>>>>>>>> Sebastian Wagner >>>>>>>>>>>>>>>>>> https://twitter.com/#!/dead_lock >>>>>>>>>>>>>>>>>> http://www.webbase-design.de >>>>>>>>>>>>>>>>>> http://www.wagner-sebastian.com >>>>>>>>>>>>>>>>>> [email protected] >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> -- >>>>>>>>>>>>>>>>> WBR >>>>>>>>>>>>>>>>> Maxim aka solomax >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> -- >>>>>>>>>>>>>>>> WBR >>>>>>>>>>>>>>>> Maxim aka solomax >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> -- >>>>>>>>>>>>>> WBR >>>>>>>>>>>>>> Maxim aka solomax >>>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> -- >>>>>>>>>>>>> Sebastian Wagner >>>>>>>>>>>>> https://twitter.com/#!/dead_lock >>>>>>>>>>>>> http://www.webbase-design.de >>>>>>>>>>>>> http://www.wagner-sebastian.com >>>>>>>>>>>>> [email protected] >>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> -- >>>>>>>>>>>> WBR >>>>>>>>>>>> Maxim aka solomax >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> -- >>>>>>>>>>> Sebastian Wagner >>>>>>>>>>> https://twitter.com/#!/dead_lock >>>>>>>>>>> http://www.webbase-design.de >>>>>>>>>>> http://www.wagner-sebastian.com >>>>>>>>>>> [email protected] >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> -- >>>>>>>>>> Sebastian Wagner >>>>>>>>>> https://twitter.com/#!/dead_lock >>>>>>>>>> http://www.webbase-design.de >>>>>>>>>> http://www.wagner-sebastian.com >>>>>>>>>> [email protected] >>>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> -- >>>>>>>>> WBR >>>>>>>>> Maxim aka solomax >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> WBR >>>>>>>> Maxim aka solomax >>>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> WBR >>>>>>> Maxim aka solomax >>>>>>> >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> WBR >>>>>> Maxim aka solomax >>>>>> >>>>> >>>> >>>> >>>> -- >>>> Sebastian Wagner >>>> https://twitter.com/#!/dead_lock >>>> http://www.webbase-design.de >>>> http://www.wagner-sebastian.com >>>> [email protected] >>>> >>> >>> >>> >>> -- >>> Sebastian Wagner >>> https://twitter.com/#!/dead_lock >>> http://www.webbase-design.de >>> http://www.wagner-sebastian.com >>> [email protected] >>> >> >> >> >> -- >> Sebastian Wagner >> https://twitter.com/#!/dead_lock >> http://www.webbase-design.de >> http://www.wagner-sebastian.com >> [email protected] >> > > > > -- > Sebastian Wagner > https://twitter.com/#!/dead_lock > http://www.webbase-design.de > http://www.wagner-sebastian.com > [email protected] > -- Sebastian Wagner https://twitter.com/#!/dead_lock http://www.webbase-design.de http://www.wagner-sebastian.com [email protected]
