Jeff-
I've found Audio Architect to be a fine design tool. As a tool for relatively simple system configuration it's like using a cannon to kill a fly.
Go to hiqnet.harmanpro.com and click on 'software' and then find the link to 'legacy versions' after the jump. You want System Architect 3.2 or 3.3. V3.4 began the transition to the Audio Architect workflow. The firmware updates and JBL v4.x presets are the same as in A.A.
The workflow difference: when you fire up S.A., it will auto-populate the venue with discovered devices but A.A. will not. In A.A. you will find discovered devices in the left-hand column; if you don't see them, look at the bottom of the column and click on "System Explorer". In A.A. you MUST define a room within the venue (in S.A. the venue *was* automatically a room unless you defined multiple rooms) and then drag discovered devices from the Explorer pane into the room.
IOW, they are probably there, you just aren't seeing them. This is why for configuring amps I prefer to use S.A. 3.3 if the hardware is supported.
There are tutorials available for the software platforms but they are targeted at guys who are designing sophisticated systems, and the key word is "design." The software workflow presumes you are starting with a blank page, not with a existing batch of equipment you're simply configuring. Probably a good use of an hour, regardless.
Have fun, good luck.
Tim Mc
ps. I've had the same experience with A.A., re taking a lot of time to discover devices, especially after readdressing them with NetSetter.
