A bug cropped up in iOS 7 that appears to affect any AIR app that uses sound.  The bug pops up a dialog box requesting microphone permission the first time your app is run under iOS 7 (even if your app does not use the microphone).  After a user clicks “Don’t Allow” or “OK” it will not re-appear- but this unexpected dialog box can be off-putting to anyone using your app under iOS 7.

I submitted a bug for this and Adobe fixed the issue in SDK 3.9 (beta): https://bugbase.adobe.com/index.cfm?event=bug&id=3609631

Recompiling your app against AIR SDK 3.9 should address this issue.  You can find the latest AIR SDK here:  http://labs.adobe.com/downloads/air.html



As a one-person shop I find myself buzzing around the same digital hub day in & day out- surrounded by nothing but  monitors, deadlines and //TODO lists for whatever project I’m working on.

I often forget how much getting up & sketching out a simple diagram on physical surface can help to clarify stuff.

This post is a reminder to myself and others who don’t work in a space with other people- try a whiteboard- it can help to clear your head!


EDM’s Fault?

22 Aug

Oh no, even the light curtains are blaming EDM!

Maybe the real fault was that someone coined the term ‘EDM’ to start with…

Typing with a controller is not among the most fun things you can do with your OUYA. Here’s how to pair up a Bluetooth keyboard.

Access files from a USB drive on the OUYA.

How else would you work with files? Here we install ES File Manager on the OUYA.

Adobe no longer officially supports the Flash player on Android, but that doesn’t mean you can’t give it a whirl by installing it on the Android 4.1 OUYA build.

As  a $99 Tegra-3 based Android device, the Ouya has a lot of potential for gaming, hacking and generally messing around.  Here’s a brief tutorial on using the web browser.

My mind goes back to when I was living in Chicago, in the fall of 1999.  A somewhat reluctant convert to the Windows platform (from an Amiga 3000- can you blame me?), I was consoled to see a flood of programs appear in what was a very innovative time for computer-based music applications.  There were several multi-track recorders available, and they were all pretty great as far as I was concerned- and allowed the luxury of playing back giant .wav files, when I had been used to stretching tiny samples as far as I could in mod tracking programs.

When it came to recording & playing back several simultaneous tracks, there was a standout application for me- Cool Edit Pro.  Something about it felt familiar, and it was extremely stable on my ‘awesome’ hardware at the time (I think it was a celeron 300a overclocked to 450 MHz).  I remember testing how many takes I could layer on top of one another in Cool Edit Pro and still play back without a hitch.  I got up to over 40 simultaneous before I quit- unable to see anything but flawless playback with nary a pause or click.

Flash forward to 2003- Adobe buys Cool Edit Pro and rebrands it as Adobe Audition, now in it’s third version.  My first inclination was to bounce all of my song parts to .wav files and play them back through Audition.  What could be simpler than a bunch of .wav files, right?

I tend to stay loyal to brands once I know/trust them, but I am sorry to say- Audition in 2010 performs much worse than Cool Edit Pro did in 1999.  This is nearly inconceivable to me, as much as hardware has advanced along with OSes and driver capabilities.  How I can get glitches, pops, and dropouts with a respectable sound card, 4GB or more of ram, and fast CPU’s?

I know better than to make a statement like this based on one hardware configuration.  I have used Audition since it was released in 2003, across no less than five distinct systems with plenty of ram, fast CPU’s and better-than-average sound cards.  Adobe has added several features to the program, but overall it has more glitches- and is just not as stable- as it once was.

For editing tasks, I will still turn to Audition because it is a capable editor.  But for live multi-track sequencing, as much as I wanted it to work- Audition is just not stable enough to use.

The quest for a multi-track sequencer reliable enough for live performances goes on.

The Xybots are dead.  Long live the Xybots!

Upon the successful completion of a mission, the leader of the A-Team often said: “I love it when a plan comes together.”

Well… yeah.  Who likes it when a plan falls apart?

This blog was originally established to chronicle technical hurdles encountered while planning, practicing, and ultimately playing a live show of songs I have written over the years.  It was to be based on the journey towards making such a show happen- but it looks like that journey got a little longer.  Saturday, October 16th 2010 was to be the first Xybots live show.  But it didn’t happen.

The official last straw was a band member’s flu illness a couple of days before the show- the last tidal wave sent forth from a sea of mishaps.  From a lack of pre-show band practices, to some very creative theories on what commitment means (my favorite was someone showing up for practice after a few beers- minus their instrument- on the wrong night)… it became clear that we would not be ready to play in time.

In the beginning, it crossed my mind that having to cancel the show for any reason would be really disappointing.  The day I cancelled it, the strongest sensation I could feel through the fog of recent sleep deprivation was relief.  It was a bummer to have to contact everyone at the last minute to tell them the show was called off (along with the party I planned around it, since we would be playing at my house).  But in the end, that’s what happened.

Where to go from here?  I’m definitely not ready to try and plan another live show.  But I did learn a few things, and picked up a few tricks along the way.  I may take a break from music for awhile, but I’m sure I’ll get back to composing eventually.