06/28/2012 3:49 PM
post93942
|
Terry,
If you take a look at the wave.c example I linked there is an "#ifdef
__USAGE" section that shows the usage. If you have a preferred playback
device (/dev/snd/pcmPreferredp) then I think you can get away with running
"wave /path/to/file.wav". If you don't have a preferred output device you
can change the device with the "-a" argument. If you "ls /dev/snd/"
you'll hopefully see "pcmC#D#p" devices, where the # characters are
replaced with the card and device numbers respectfully.
I do not think any sample wave files are shipped with Neutrino. You'll
want to create your own custom wave files for your needs but you could
probably find examples online. Note that .wav is strictly a container
format so it is possible that some wave files do not contain raw pcm data
(instead they might contain encoded data that requires software to decode
that data to pcm), though these types of files are not common.
BlackBerry 10 provides a framework on top of Neutrino that makes some
things easier. Developers that are using the native NDK may still do
direct audio control using these low-level APIs.
A look through the QNX Audio Dev Guide may help. Note that this is
different than the audio DDK, which may be what you were looking at
before. The Audio Dev Guide will probably give you more information then
you ever wanted to know about playing audio but understanding it may go a
long way when you are trying to debug problems related to playback in the
future:
<http://www.qnx.com/developers/docs/6.5.0/topic/com.qnx.doc.neutrino_audio/
about.html>
--
Ryan J. Allen
QNX Software Systems
|
|
|
06/28/2012 3:33 PM
post93944
|
|
|
|