Some days I wished I had chosen the career of a carpenter. You still have problems to deal with, but at least as a carpenter you can beat the problem with a hammer. You may not be able to solve the problem that way, but it sure would help work out some of the frustrations.
Airports and Telephone Auto Attendants
I am traveling out of the country and needed to call my credit card company to make sure my card did not get frozen while traveling. I called the 800 number on the back of the card and intentionally did not want to speak any of my responses if not necessary. People are sitting around me. Unlike the man who planned a surprise retirement party while yelling into his phone, I didn’t want other people to hear my conversation. It is amazing how much private information people shout into their phones when they are in public.
Anyway.
When I sat down at this end of the airport an hour ago, no one was around and no planes were boarding near me. Therefore, there really weren’t any announcements that would interfere with my phone call.
I got through the initial parts of the call to the bank just fine. But when the auto attendant was asking me specifically what I was calling for and was about to wait for my response an announcement came over the speakers. The auto attendant waited patiently for me to stop talking.
The announcement finished and Mrs. Auto Attendant began speaking. She wasn’t but a couple of words into her apology for not understanding my request when another announcement started. She patiently waited again and when the announcement paused Mrs. Attendant said that she would transfer me to a real person who could better help me with my request.
Other than having to wait through the announcements, that was probably the fastest I have ever gotten a real person when calling a bank since the scourge of the auto attendant began.
ScratchGPIO Sound Problem
I am working on a project to demonstrate some of the things you can do with a Raspberry Pi. I am doing this for our local library. One of the things I thought about building is a drum machine or a piano. The premise is when you touch a switch it causes the Raspberry Pi to play a sound. Very easily done in Python (the language I know best).
However, since this project is to target new users of the Raspberry Pi, I thought it would be nice to use the Scratch programming language. This is a visual programming language that is very powerful and really kid friendly.
The problem with using Scratch though is that it doesn’t natively handle the GPIO interface (General Purpose Input Output). These are 40 pins (or 26 on the older models) coming out of the Raspberry Pi that you can use to control hardware such as robots.
ScratchGPIO
There is a project called ScratchGPIO that gives me the control I need. However, I had a problem with playing sound out of the computer when using the GPIO pins. Each time I would make the program play a sound, Scratch would exit (force quit). Looking through several forum threads did not turn up a solution quickly.
Finally, I found a forum post that gave an answer that solved the problem for me. I wanted to include it here in case it may be a help to others (and because I will probably forget the answer the next time I need it). Hopefully no one will have to dig as long as I did to find a solution.
The steps below assume that you have already read the instructions for getting the program installed. It is also probably a good idea to run the basic first program. Having said that, you probably wouldn’t have come here unless you already had the program up and running and fell into the same problem I had with sound.
Steps
- Start the ScratchGPIO program. When you install it, it will place an icon right on your desktop. Just double click the icon.
- After it is loaded, simply close it.
- Open a terminal window. I do this by typing “alt+F2” that will open a start program box. Inside that box type “lxterminal” and hit enter. Don’t actually type any of the quotation marks in this step.
- Inside the terminal window type “/usr/bin/scratch.old &” then hit enter. Again, no quotes.
- Scratch will re-open. Go to File | Open and select the “rsc” program (which is installed when you install ScratchGPIO).
That should make it so you can now use sound in your programs when using the GPIO interface.
I really don’t know if all those steps are necessary. I know I have opened a program I was working on in step 5 without opening the rsc program. It worked fine without doing that final step.
I would think that some of this can be automated with a script if someone wants to try and think that through. For me, the steps aren’t too cumbersome.
This is another one of the many things I have written up so that I can find the answer for myself when I need it in the future. I hope it is a help to others.
Buy a Raspberry Pi
If you don’t have a Raspberry Pi, head on over to MCM Electronics and buy one from the official US distributor.
Podcasters Who Didn’t Deliver the Norm
Normally I tend to harp on the negative aspects of what podcasters do, but this time I want to applaud two podcasts for doing something different. They each broke out of their normal mode to share content that was appropriate for their audience even though it didn’t fit their expected format. One is a case where a podcast went much longer than normal and the other is a case where they delivered a shorter than normal episode.
Long, But Just Right
I don’t mind long shows as long as they are packed with content and aren’t long for the sake of being long. Stever Robbins at the Get-It-Done Guy podcast released an episode this week that was 20 minutes in length. His shows are normally between 5 and 7 minutes. Though the show was longer and an interview format (he normally does well-scripted monologues) it was appropriate and bursting with great information.
Short, But Appropriate
The other show is the IPM Partnership Podcast with Matt Barfield. Bro. Matt’s shows are usually 15 to 20 mintutes in length with him conducting an interview. In the episode I heard the other day he had someone else conduct the interview and the show was less than 8 minutes long. I applaud him for letting someone else take the mic and for not feeling like he had to fill 20 minutes of time when he only had 8 minutes of content.
Bravo to these two podcasts! And thank you both for being good examples of when it is appropriate to make a show longer and when to make one shorter.
Digital Calendar to the Rescue
Yesterday afternoon I was sitting in my office actually getting work done. (That is quite an amazing accomplishment most days.) Suddenly I got a notification on my phone that said I had an appointment in 1 hour.
The last time I thought about that particular appointment was 3 or 4 days prior to the event. However, because my calendar sends me these types of notifications I was able to prepare for my monthly time at the assisted living home where I am reading a book to the group. We are reading a book about Eric Liddell the Olympic gold medalist and missionary to China.![]()
![]()
While I enjoy the convenience of a paper calendar, and th
e ability to see large blocks of time easily, this is one time where the digital calendar saved me.
Each time I enter an event in my calendar I try to remember to set a notification early enough that if I totally forget about the event, the calendar will remind me in enough time to make it there. In one case I had completely forgotten about scheduling a meeting in a church on a Sunday night in Maryland. My calendar notification went off Friday night to remind me of the speaking engagement. That gave me plenty of time to be ready for the event and no one at the church had to know that I forgot about being there. I think that is the only time I have spaced out on a meeting like that. At least, if I’ve missed others no one called me and told me about it.
