RPi Using Skypekit - Revision history

Prehensile: /* Prerequisites */

2012-07-01T22:12:05Z

‎Prerequisites

Prehensile at 23:14, 30 June 2012

2012-06-30T23:14:55Z

Prehensile at 21:08, 30 June 2012

2012-06-30T21:08:59Z

Prehensile at 20:48, 30 June 2012

2012-06-30T20:48:24Z

Prehensile at 20:47, 30 June 2012

2012-06-30T20:47:11Z

Prehensile: /* Building an Audio Host & running an example app */

2012-06-30T20:45:15Z

‎Building an Audio Host & running an example app

Prehensile: /* About SkypeKit */

2012-06-25T09:18:30Z

‎About SkypeKit

Prehensile at 22:11, 24 June 2012

2012-06-24T22:11:57Z

Prehensile: added Building an Audio Host & running an example app

2012-06-24T22:10:41Z

added Building an Audio Host & running an example app

Prehensile: moved Using Skypekit to RPi Using Skypekit: namespacing

2012-06-22T20:15:13Z

moved Using Skypekit to RPi Using Skypekit: namespacing

@@ Line 53: / Line 53: @@
 * [http://www.music.mcgill.ca/~gary/rtaudio/index.html RtAudio]. At the time of writing, the most current version is 4.0.11 which can be downloaded [http://www.music.mcgill.ca/~gary/rtaudio/release/rtaudio-4.0.11.tar.gz here].
 * '''libasound2-dev''', the ALSA shared library which RtAudio needs to connect to ALSA (if you're wondering, ALSA is the Linux sound system[http://en.wikipedia.org/wiki/Advanced_Linux_Sound_Architecture]). Install this library with <pre>sudo apt-get install libasound2-dev</pre>
-* '''A USB soundcard''' which has an audio-in port. voicepcmhost-rtaudio fails if it can't connect to an audio input, and the Pi's onboard sound only has an audio-out connection. Connect the device before you turn on the Pi; if its chipset is supported, drivers will be loaded at boot.
+* '''A USB soundcard which has an audio-in port.''' voicepcmhost-rtaudio fails if it can't connect to an audio input, and the Pi's onboard sound only has an audio-out connection. Connect the device before you turn on the Pi; if its chipset is supported, drivers will be loaded at boot.
 * '''Premake''', a build utility which generates a correct makefile for voicepcmhost-rtaudio.
 # '''Download the source''' from [http://industriousone.com/premake/download http://industriousone.com/premake/download].

@@ Line 80: / Line 80: @@
 ##For '''voicepcmhost-rtaudio''':<pre>~/dev/skype/skypekit-sdk_sdk-4.2.1.97_1379776/reference/voicepcmhost-rtaudio/build/voicepcmhost-rtaudio &</pre>
 # Move to the folder containing the Python app examples:<pre>cd ~/dev/skype/skypekit-sdk_sdk-4.2.1.97_1379776/examples/python/tutorial/</pre>
-# Run the autoanswer.py example. This is a simple Python app which will automatically answer any incoming Skype call and connect it to the loopback Audio Host.<pre>python autoanswer.py &lt;Skype account #1 login&gt; &lt;Skype account #1 password&gt;</pre>
+# Run the autoanswer.py example. This is a simple Python app which will automatically answer any incoming Skype call and connect it to the running Audio Host.<pre>python autoanswer.py &lt;Skype account #1 login&gt; &lt;Skype account #1 password&gt;</pre>
 # '''On your desktop''', login to Skype with the details for account #2 and place a call to account #1. You should see a whole load of output spill across the Pi's console, including the lines <pre>Incoming call from:  <Skype account #2 name></pre> and <pre><Skype account #2 name> is now live.</pre>

@@ Line 35: / Line 35: @@
 ===About Audio Hosts===
-The Skypekit ARM runtime needs to connect to an Audio Host at the time that it connects to the Skype network, even if we're not actually interested in making calls (say, using the runtime for chat). An Audio Host is a standalone binary which runs alongside the runtime and provides it with access to audio in & out connections. The [http://developer.skype.com/skypekit/development-guide/audio-video-integration/pcm-audio#_pcmQuickStart Audio PCM Quick Start guide] on [http://developer.skype.com] gives more detail about this setup, but the practical upshot is that we'll need to compile an Audio PCM Host before we can use any of the services provided by the runtime.
+The Skypekit ARM runtime needs to connect to an Audio Host at the time that it connects to the Skype network, even if we're not actually interested in making calls (say, using the runtime for chat). An Audio Host is a standalone binary which runs alongside the runtime and provides it with access to audio in & out connections. The [http://developer.skype.com/skypekit/development-guide/audio-video-integration/pcm-audio#_pcmQuickStart Audio PCM Quick Start guide] on [http://developer.skype.com http://developer.skype.com] gives more detail about this setup, but the practical upshot is that we'll need to compile an Audio PCM Host before we can use any of the services provided by the runtime.
 ''Most of this information is extracted from Skype's [http://developer.skype.com/skypekit/development-guide/audio-video-integration/pcm-audio#_pcmQuickStart Audio PCM Quick Start guide], but this doc seems to lag behind regarding the build system used in more recent versions of the SDK (4.2.1 at time of writing). There's some tidbits of information about the new build system in the [http://developer.skype.com/skypekit/development-guide/general/release-notes Release Notes] for 4.2.1, but other stuff I've basically guessed at/worked out through trial & error. YMMV.''
@@ Line 48: / Line 48: @@
 ===Building voicepcmhost-rtaudio===
-If you'd like to try making an actual call using a mic connected to the Pi, you can build '''voicepcmhost-rtaudio''' which uses the [http://www.music.mcgill.ca/~gary/rtaudio/index.html RtAudio] library to connect to an audio device on the Pi.
+If you'd like to try making a call through to actual audio hardware on the Pi, you can build '''voicepcmhost-rtaudio''' which uses the [http://www.music.mcgill.ca/~gary/rtaudio/index.html RtAudio] library to connect to an audio device.
 ====Prerequisites====
 * [http://www.music.mcgill.ca/~gary/rtaudio/index.html RtAudio]. At the time of writing, the most current version is 4.0.11 which can be downloaded [http://www.music.mcgill.ca/~gary/rtaudio/release/rtaudio-4.0.11.tar.gz here].
-* '''libasound2-dev''', the ALSA shared library which RtAudio needs to connect to ALSA. Install this library with <pre>sudo apt-get install libasound2-dev</pre>
+* '''libasound2-dev''', the ALSA shared library which RtAudio needs to connect to ALSA (if you're wondering, ALSA is the Linux sound system[http://en.wikipedia.org/wiki/Advanced_Linux_Sound_Architecture]). Install this library with <pre>sudo apt-get install libasound2-dev</pre>
 * '''A USB soundcard''' which has an audio-in port. voicepcmhost-rtaudio fails if it can't connect to an audio input, and the Pi's onboard sound only has an audio-out connection. Connect the device before you turn on the Pi; if its chipset is supported, drivers will be loaded at boot.
 * '''Premake''', a build utility which generates a correct makefile for voicepcmhost-rtaudio.

@@ Line 67: / Line 67: @@
 # '''Move to the directory''' where the '''voicepcmhost-rtaudio''' source lives:<pre>~/dev/skype/skypekit-sdk_sdk-4.2.1.97_1379776/reference/voicepcmhost-rtaudio</pre>
 # '''Make a link to the RtAudio source'''. The makefile for voicepcmhost-rtaudio expects the source for RtAudio to be present in this folder at compile-time. We'll make a link back to the extracted source to keep things tidy.<pre>ln -s ~/dev/rtaudio-4.0.11 ./rtaudio-4.0.6</pre>'' '''Note''' that the link is named '''rtaudio-4.0.6''': the makefile is expecting an older version of RtAudio, and rather than mucking about with the makefile, it's probably just better to be a little disingenuous with the link name. This strategy works fine at the time of writing with '''rtaudio-4.0.11''' standing in for '''4.0.6'''.''
-# '''Generate the correct makefile for voicepcmhost-rtaudio''', since the default one doesn't work.<pre>make</pre>This will generate a bunch of makefiles and try to build voicepcmhost-rtaudio, which will fail. This is OK though, since we'll build it in the next step.
+# '''Generate the correct makefile for voicepcmhost-rtaudio''', since the default one doesn't work.<pre>make</pre>This will generate a bunch of makefiles and try to build '''voicepcmhost-rtaudio''', which will fail. This is OK though, since we'll build it in the next step.
 # '''Build voicepcmhost-rtaudio''' with the following commands:<pre>cd ~/dev/skype/skypekit-sdk_sdk-4.2.1.97_1379776/reference/voicepcmhost-rtaudio/build/gmake</pre><pre>make</pre>
 If all of this worked, you should be left with a built binary at '''~/dev/skype/skypekit-sdk_sdk-4.2.1.97_1379776/reference/voicepcmhost-rtaudio/build/voicepcmhost-rtaudio'''.

@@ Line 66: / Line 66: @@
 ##<pre>tar xzvf rtaudio-4.0.11.tar.gz</pre>This should leave you with an extracted folder named '''rtaudio-4.0.11''' in '''~/dev'''.
 # '''Move to the directory''' where the '''voicepcmhost-rtaudio''' source lives:<pre>~/dev/skype/skypekit-sdk_sdk-4.2.1.97_1379776/reference/voicepcmhost-rtaudio</pre>
-# '''Make a link to the RtAudio source'''. The makefile for voicepcmhost-rtaudio expects the source for RtAudio to be present in this folder at compile-time. We'll make a link back to the extracted source to keep things tidy.<pre>ln -s ~/dev/rtaudio-4.0.11 ./rtaudio-4.0.6</pre>''''''Note''' that the link is named '''rtaudio-4.0.6''': the makefile is expecting an older version of RtAudio, and rather than mucking about with the makefile, it's probably just better to be a little disingenuous with the link name. This strategy works fine at the time of writing with ''rtaudio-4.0.11'' standing in for ''4.0.6''.'''
+# '''Make a link to the RtAudio source'''. The makefile for voicepcmhost-rtaudio expects the source for RtAudio to be present in this folder at compile-time. We'll make a link back to the extracted source to keep things tidy.<pre>ln -s ~/dev/rtaudio-4.0.11 ./rtaudio-4.0.6</pre>'' '''Note''' that the link is named '''rtaudio-4.0.6''': the makefile is expecting an older version of RtAudio, and rather than mucking about with the makefile, it's probably just better to be a little disingenuous with the link name. This strategy works fine at the time of writing with '''rtaudio-4.0.11''' standing in for '''4.0.6'''.''
 # '''Generate the correct makefile for voicepcmhost-rtaudio''', since the default one doesn't work.<pre>make</pre>This will generate a bunch of makefiles and try to build voicepcmhost-rtaudio, which will fail. This is OK though, since we'll build it in the next step.
-# '''Build voicepcmhost-rtaudio''' with the following commands:<pre>cd ~/dev/skype/skypekit-sdk_sdk-4.2.1.97_1379776/reference/voicepcmhost-rtaudio/build/gmake</pre>
+# '''Build voicepcmhost-rtaudio''' with the following commands:<pre>cd ~/dev/skype/skypekit-sdk_sdk-4.2.1.97_1379776/reference/voicepcmhost-rtaudio/build/gmake</pre><pre>make</pre>
 <pre>make</pre>
 If all of this worked, you should be left with a built binary at '''~/dev/skype/skypekit-sdk_sdk-4.2.1.97_1379776/reference/voicepcmhost-rtaudio/build/voicepcmhost-rtaudio'''.

@@ Line 33: / Line 33: @@
 ''The rest of this guide is all Pi-side, since I'm not quite ready to attempt to get my Mac cross-compiling for the Pi just yet.''
-===Building voicepcmhost-loopback===
+===About Audio Hosts===
-The Skypekit ARM runtime needs to connect to an Audio Host at the time that it connects to the Skype network, even if we're not actually interested in making calls (say, using the runtime for chat). An Audio Host is a standalone binary which runs alongside the runtime and provides it with access to audio in & out connections. The [http://developer.skype.com/skypekit/development-guide/audio-video-integration/pcm-audio#_pcmQuickStart Audio PCM Quick Start guide] on [http://developer.skype.com] gives more detail about this setup, but the practical upshot is that we'll need to compile an Audio PCM Host before we can use any of the services provided by the runtime. To start with, let's build the simplest reference Audio Host provided in the SDK, ''voicepcmhost-loopback'', which as the name suggests, just copies audio data from its input back to its output.
+The Skypekit ARM runtime needs to connect to an Audio Host at the time that it connects to the Skype network, even if we're not actually interested in making calls (say, using the runtime for chat). An Audio Host is a standalone binary which runs alongside the runtime and provides it with access to audio in & out connections. The [http://developer.skype.com/skypekit/development-guide/audio-video-integration/pcm-audio#_pcmQuickStart Audio PCM Quick Start guide] on [http://developer.skype.com] gives more detail about this setup, but the practical upshot is that we'll need to compile an Audio PCM Host before we can use any of the services provided by the runtime.
 ''Most of this information is extracted from Skype's [http://developer.skype.com/skypekit/development-guide/audio-video-integration/pcm-audio#_pcmQuickStart Audio PCM Quick Start guide], but this doc seems to lag behind regarding the build system used in more recent versions of the SDK (4.2.1 at time of writing). There's some tidbits of information about the new build system in the [http://developer.skype.com/skypekit/development-guide/general/release-notes Release Notes] for 4.2.1, but other stuff I've basically guessed at/worked out through trial & error. YMMV.''
 #  '''Build voicepcmhost-loopback'''. Change to the relevant build directory:<pre>cd ~/dev/skype/skypekit-sdk_sdk-4.2.1.97_1379776/reference/voicepcmhost-loopback/build/gmake</pre> and build it:<pre>make</pre>
 Hopefully, we should now have a built binary at '''~/dev/skype/skypekit-sdk_sdk-4.2.1.97_1379776/reference/voicepcmhost-loopback/build/voicepcmhost-loopback'''.
 ===Making a test call to the Pi===
@@ Line 46: / Line 77: @@
 # Copy the '''.pem''' keyfile to '''~/dev/skype/skypekit-sdk_sdk-4.2.1.97_1379776/examples/python/tutorial'''. We'll use it later to run a test app. Edit '''~/dev/skype/skypekit-sdk_sdk-4.2.1.97_1379776/examples/python/keypair.py''' to reflect the filename of the keyfile.
 # Start the ARM runtime in the background:<pre>~/dev/skype/linux-armv6-skypekit-voicepcm-novideo_4.2.1.723_1708442/bin/linux-armv6le-eabi/linux-armv6-skypekit-voicepcm-novideo &</pre>
-# Start the Voice PCM Audio Host in the background:<pre>~/dev/skype/skypekit-sdk_sdk-4.2.1.97_1379776/reference/voicepcmhost-loopback/build/voicepcmhost-loopback &</pre>
+# Start a Voice PCM Audio Host in the background:
 # Move to the folder containing the Python app examples:<pre>cd ~/dev/skype/skypekit-sdk_sdk-4.2.1.97_1379776/examples/python/tutorial/</pre>
 # Run the autoanswer.py example. This is a simple Python app which will automatically answer any incoming Skype call and connect it to the loopback Audio Host.<pre>python autoanswer.py &lt;Skype account #1 login&gt; &lt;Skype account #1 password&gt;</pre>
-# '''On your desktop''', login to Skype with the details for account #2 and place a call to account #1. You should see a whole load of output spill across the Pi's console, including the lines <pre>Incoming call from:  <Skype account #2 name></pre> and <pre><Skype account #2 name> is now live.</pre> Say something! You should hear it echo back to you from the Pi. Congratultions! You just made your first Skype call to an instance of SkypeKit running on your Pi.
+# '''On your desktop''', login to Skype with the details for account #2 and place a call to account #1. You should see a whole load of output spill across the Pi's console, including the lines <pre>Incoming call from:  <Skype account #2 name></pre> and <pre><Skype account #2 name> is now live.</pre>

@@ Line 10: / Line 10: @@
 When you're developing with SkypeKit, presenting an interface to the user is your responsibility. The core Skype functionality is the runtime's responsibility.
-There are a number of runtimes available for various combinations of OS & architecture. Luckily for us, there's a linux-armv7le-eabi runtime which runs on the Pi.
+There are a number of runtimes available for various combinations of OS & architecture. Luckily for us, there's a ''linux-armv7le-eabi'' runtime which runs on the Pi.
 Handily, the SDK also comes with a bunch of example code which lets you do things like chat & make and receive calls on the command-line.
 ==Prerequisites==

@@ Line 24: / Line 24: @@
 ## Finally, we'll request a key pair. Go back to the project that you created and click "Development key pair". Then click "Request a new key pair" and give it a name (I use dates). Click "Request key pair" after proving you're a human, then "Download the key pair"
 # That's it! You now have everything you need to start slapping together a simple Skype-connected app
-===Building the tools===
-TODO
+==Building an Audio Host & running an example app==
-===Using the example apps provided in the SDK===
-TODO
+Now we've got the SDK, runtime & keyfile, we're ready to start putting things togeher on the Pi. Copy over '''linux-armv6-skypekit-xxx.gz''', '''linux-armv6-skypekit-xxx.tar.gz''', '''skypekit-sdk_sdk-xxx.tar.gz''' and the '''.pem''' keyfile to a sensible place on your Pi (I made '''~/dev/skype''' and put them there) and uncompress both archives with:<pre>tar xvzf filename.gz</pre>