Changes between Version 1 and Version 2 of Testing_Audio_Device_with_pjsystest

Timestamp:

Jul 17, 2009 10:36:09 AM (15 years ago)

Author:

bennylp

Comment:

--

Testing_Audio_Device_with_pjsystest

@@ -21 +21 @@
  - to eliminate audio impairments such as audio stuttering
  - to minimize audio latency
+
+[[BR]]
 
 == Using pjsystest ==
@@ -59 +61 @@
 No need to have pen and paper to note the result, they are recorded to {{{PJSYSTEST_RESULT.TXT}}} file one you exit the program. On Windows Mobile, the file location is in the root device, while on desktop systems is in the directory where the application is run from.
 
+[[BR]]
 
+== Tasks ==
+
+Several things that you could experiment with using pjsystest:
+
+=== Testing different audiodev API backends ===
+
+Some targets such as Windows Mobile as well as desktop platforms offer more than one audiodev API backends (for example on WM there are PA/WMME and native WMME). You don't need to recompile the whole library to experiment with different audiodev API backends, just change REC_DEV_ID and PLAY_DEV_ID in {{{systest.h}}}.
+
+=== Testing different audio buffer size ===
+
+Change OVERRIDE_AUDDEV_REC_LAT and OVERRIDE_AUDDEV_PLAY_LAT in {{{systest.h}}} to experiment with different audio buffer size (values are in milliseconds). The objective is to get the minimum latency without getting audio impairments.
+
+=== Testing different audio device clock rate ===
+
+Choosing higher clock rate in audio device can minimize latency. Change DEV_CLOCK_RATE in {{{systest.h}}} to experiment with different clock rates.
 
 {{{