Hi Sam, You need to send an email to the "subscribe" email before you can send a link to the regular mailing list.
See: http://openmeetings.apache.org/mail-lists.html Sebastian ---------- Forwarded message ---------- From: < dev-reject-1374551648.99671.nabjfpicninhfbfen...@openmeetings.apache.org> Date: 2013/7/23 Subject: MODERATE for [email protected] To: Cc: dev-allow-tc.1374551648.ogfkbfkimmilajplcecg-srcald34= [email protected] To approve: dev-accept-1374551648.99671.nabjfpicninhfbfen...@openmeetings.apache.org To reject: dev-reject-1374551648.99671.nabjfpicninhfbfen...@openmeetings.apache.org To give a reason to reject: %%% Start comment %%% End comment ---------- Weitergeleitete Nachricht ---------- From: Samuel Caldwell <[email protected]> To: "[email protected]" <[email protected]> Cc: Date: Mon, 22 Jul 2013 20:53:35 -0700 (PDT) Subject: client side audio processing I'm not sure if this message belongs in the dev or user list, starting here. I am attempting to add audio processing functionality to the client of openmeetings. I have modified test-setup.lzx for audio only send/receive and am able to get raw audio data and play it. I need to process this data prior to playing it and am having a difficult time integrating my processing engine with the test file, much less the client binary. The audio processing utilities are written in native code due to the intensive nature of the algorithms. These utilities are complete for windows and android, an iOS version is in progress. Any pointers would be helpful. As is always the case, time is critical and I am willing to enlist and fund experienced help. Success in this step will likely lead to a several month follow on project, adding additional processing features and integrating with video playback which at a glance looks to be a significant challenge. Thanks in advance for any help and your consideration. Best regards, Sam Caldwell +1.813.220.6232 -- Sebastian Wagner https://twitter.com/#!/dead_lock http://www.webbase-design.de http://www.wagner-sebastian.com [email protected]
