Alright! Time for my first off-topic post on here, now I get to be a real blogger. Just last month at NAMM, a music industry trade show, Gibson introduced their new digital guitar. The guitar looks and performs like a typical Les Paul, expect for two main differences. First, there is a hex pickup placed right between the bridge and the rear humbucker. The hex pickup picks up the vibrations for each string seperate from each other. But this string seperation would not matter if there was no way to output the seperate string information. So the Gibson digital guitar has a CAT-5 jack next the usual output jack. The signal from the CAT-5 is sent to a breakout box, which can output that data in one of several ways. It can sum all the data and output it to one amp, it can also send the three bass strings to one amp and the three treble strings to a different amp and finally it can send each string an a serparate output to a seperate amp. By sending the signal digitally to the breakout box, you avoid the usual treble bleed off that a long normal guitar chord causes.
Of course, instead of outputing to an amp you could also send this individual string data to a computer that can record 6+ inputs at once. Then you could use a DAW (audio editor like ProTools), to run individual effect chains on each string, allowing you to create some very original sounds. Tying this all together is Gibsons new Audio/Visual transport protocol called MaGIC. While I'm not very qualified to give a summary of the nuts and bolts of this technology, you can look at Gibson's information to get a grasp of what it will do.
As a guitar player, I would love to see Microsoft working with Gibson for some sort of connection with this technology. Currently music and video are two areas where Microsoft doesn't have as strong a showing as they usually do. The combination of upcoming 64-bit versions of Windows, along with some solid software apps to work together with MaGIC could be a killer combination.
On the profiler side of things, Part 2 of my walkthrough of using the Visual Studio Team System profiler in the IDE with be up by Monday, make sure to check out Part 1 if you missed it.
PingBack from http://woodtvstand.info/story.php?id=14794
PingBack from http://cellulitecreamsite.info/story.php?id=4666