When I was in Minneapolis (at IPR) doing a bit of Max/MSP teaching, I had a long conversation with a talented and insightful LA-based film/TV composer. We were talking about how we got into Max, and I mentioned that I bought it in 1995 (or so) with the plan of making the ultimate step sequencer. I was obsessed with step sequencers at the time, and couldn't find any software option that could help me.
I'm sure you are wondering why I didn't get me some hardware. Well, nothing new had come out in a while, and while I had a bunch of analog sequencers, they were expensive and not necessarily very flexible.
I bought the Max (and later MSP and Jitter) software, and slowly started working away. Over the years, I had probably have built 100 different step sequencer, and used them for creating a mass of music. It turned out to be a step that informed my whole career.
So, this composer asks me: "Did you find the perfect step sequencer?"
My response was not what he expected. The answer was: "Yes, it is a new sequencer for every use." Frankly, I never found a sequencer that was perfect for every use. But I did find that, by building a lot of reusable pieces that could be easily bolted together, I created a "sequencer toolbox" that could be used to create a custom device for each performance or recording situation that I faced. In doing this, I developed the perfect sequencer for me. I've used it under Wii control, under Manta control, for quickly creating creepy haunted house music and creating jumping dance tracks. This modular approach to step sequencing has also helped me understand the subtle nature of performance interface, and has helped me be a lot more thoughtful about software that I purchase for my own use.
YMMV, but this journey has contained some very valuable rewards.
[ddg]
Saturday, May 16, 2009
Thursday, May 14, 2009
Overthinking (not Overthinking)
After ignoring the OpenGL parts of Jitter (an extension to Max/MSP) for far too long, I've been putting in some considerable time into it. I'm also doing a lot of reading about critical theory (I'm going to be going to graduate school this fall, and want to bone up), with the result that I'm starting to think about my work from the psychological, Marxist, femininist or whatever critical angle.
So I've done a dozen or so OpenGL patches, and I found that my favorite of the bunch doesn't really have a Marxist viewpoint. Or a femininist, or even postmodernist viewpoint (as far as I can tell). See, I wanted to move stuff around a 3-D grid, and I remembered the crazy looking chess game that Spock was always playing in the original TV show. My end result doesn't look anything like that game - it is really more of a Teutonic structure with marching balls. But I recognize it as stemming from the purest Vulcanic school, beamed to me from the deep recesses of my inner Trekkie.
In otherwords, it seemed most interesting because the only real inner meaning it has is a little joke to myself. Maybe that lack of deep thought is what helped something interesting really come outta me.
And maybe someone's gonna come along and kick my tailfin for being such ignorant peasant.
[ddg]
Darwin Grosse
So I've done a dozen or so OpenGL patches, and I found that my favorite of the bunch doesn't really have a Marxist viewpoint. Or a femininist, or even postmodernist viewpoint (as far as I can tell). See, I wanted to move stuff around a 3-D grid, and I remembered the crazy looking chess game that Spock was always playing in the original TV show. My end result doesn't look anything like that game - it is really more of a Teutonic structure with marching balls. But I recognize it as stemming from the purest Vulcanic school, beamed to me from the deep recesses of my inner Trekkie.
In otherwords, it seemed most interesting because the only real inner meaning it has is a little joke to myself. Maybe that lack of deep thought is what helped something interesting really come outta me.
And maybe someone's gonna come along and kick my tailfin for being such ignorant peasant.
[ddg]
Darwin Grosse
Saturday, May 2, 2009
An HP Computer + Vista x64 Grrr-ola
Oh My God.
I recently bought a mini-laptop for live music and audio software testing purposes. Normally I'm pretty Mac focused, but a small Windows laptop for on-the-road Acid, Maschine and FL Studio use seemed to be in order. Since most online reviews of laptops tend toward "How Well This Thing Runs Photoshop And Microsoft Word", there was little help for me in finding a good machine at a cheap price.
So, I went trolling the retail outlets. A lot of inexpensive machines either had too-small hard drives, too-ugly screens or too-heavy bodies. Also, most of them felt like crap in my hands. If the machine isn't going to inspire me in any way, why would I bother.
Also, since everything at retail runs Vista, I didn't think I had much to say about the subject. This is where I was wrong. The machine I ended up selecting was an HP Pavilion DV3-1075us: a nifty little machine with tasty looking graphics, a sizeable drive and an OK chipset. The thing I didn't notice at purchase time was the real killer: Microsoft Vista 64-bit Version.
When I got it home, I found the graphics compelling, but the speed rather, um, crappy. A quick peak at the Task Manager told me why: with no applications running, I was using about 40% of the CPU power. Opening any app would immediately spike the CPU usage, and you could literally hear the machine whimper when I put NI's Maschine on it. Two drums sounding (with no effects) was about the limit of its capability. Unacceptable.
So, using the myriad of posts about the subject, I started peeling stuff off the machine. First, it was the zillions of bloatware pieces HP put on it. I realize that this keeps the price low(-ish), but what a pain in the neck. Doing this work made me feel like buying that old Geek Squad shirt I saw at the Goodwill store.
That got me back a little CPU and a lot of disk space, and much more CPU was returned by getting rid of the 30-day Norton Hellhole. I know that viruses are scary and all, but this wasn't going to be a net-machine, so I didn't want to give up a quarter of the functionality to that pigpen. Dumping a lot of HP-specific services (like the one that says "I'm going to eat a whole bunch of CPU - and generate a whole bunch of heat - waiting breathlessly for you to put a DVD in the drive so I can give you a 13" version of a cinema screen") gave me a bunch back as well. I tried dumping the Aero graphics, but geez that looked ugly in comparison.
I got to the point where Maschine, Acid, Sound Forge and other goodies was running reliably. However, this machine has some pretty crap audio stuff going on (again with the "focused on DVD playing" approach), and I wanted to use a higher-quality audio interface. Not a single interface I have - and I've got ten or twelve - would work on this machine. No matter what I did, there either crackling or freezing (or sometimes both), and I was steaming. Add to this being under deadline for reviews on Acid and the Waldorf Blofeld, and you can imagine that I was ready to return the machine (even though the return window was already gone, I suspected I could threaten to throw it through the front window and get at least half my money back).
Then I got to thinking: this seemed like a rather puny machine to be running Vista x64, but there was really no option to run XP (something that HP and everyone else warns about due to unavailable drivers). But could dropping to Vista x86 (32-bit) work out? I spent some time with my friend and coworker Andrew Pask, and we decided that it was worth the effort. I could either download it from MSDN, order an x86 set of disks from Microsoft or buy a retail package. I chose the latter, since "time = money" right now, and set about upgrading at 10pm last night. At 5am this morning, it was done (along with app installs). All of my software works beautifully. Hardware seems to be fine. NI's Service Center doesn't even blow up on me (a remarkable thing)!
In reviewing the evening with my wife, she remarked on how every new version of Microsoft OS inevitably leads to some number of all-nighters. Whether it was the boned-up Windows 3.0, my initial Win95 debacle, helping my dad with WinME or my sister with WinXP, it all added up to one or more sleepless nights. Now this - what crap.
Alas, I can't blame this on Microsoft (much). HP made a plethora of bad decisions with this machine. 64-bit Vista was a big mistake. Ditto for the 80 lbs. of bloatware included with the machine. I've had good luck with HP machines in the past, and I hope to buy from them in the future. But here is my strong recommendation to HP for future computer systems:
1. Find someone that knows something about OS performance and have them choose the version you will use. Microsoft won't help, nor will whatever salesman buckethead that put x64 on the DV3-1075. This is a technical choice - get a good technical person to do it right.
2. Stop with the crapware already. I'm sure the HP Experience is important to you, but having fifty applications fight for control of the optical drive and the audio card isn't helping. I just wonder what people like my parents (60+ years in age) do when they get a box like this. Well, apparently they call someone like me, or the Geek Squad.
3. Norton is no longer a choice. Not that McAfee and friends are doing that much better, but Norton is neither good for the user nor good for your user experience. Most Norton installs represent a full onslaught of dialog boxes, downloads, flashing dock items and blitzed DSL communications. Is this the experience you want?
I'm sure that I represent a negligible portion of HP's business model, and Accountants Worldwide really wants all of this crap on the computers they buy for their droids. But for me (and the 20-or-so people that ask me about what machine to buy), HP is no longer worth considering. Do I like the 1075? Oh sure I do, but at this point, I've probably done more work on it than HP ever did, so I consider it a "DDG DV3-1075us" rather than anything I bought off the shelf.
And that's a pity.
[ddg]
I recently bought a mini-laptop for live music and audio software testing purposes. Normally I'm pretty Mac focused, but a small Windows laptop for on-the-road Acid, Maschine and FL Studio use seemed to be in order. Since most online reviews of laptops tend toward "How Well This Thing Runs Photoshop And Microsoft Word", there was little help for me in finding a good machine at a cheap price.
So, I went trolling the retail outlets. A lot of inexpensive machines either had too-small hard drives, too-ugly screens or too-heavy bodies. Also, most of them felt like crap in my hands. If the machine isn't going to inspire me in any way, why would I bother.
Also, since everything at retail runs Vista, I didn't think I had much to say about the subject. This is where I was wrong. The machine I ended up selecting was an HP Pavilion DV3-1075us: a nifty little machine with tasty looking graphics, a sizeable drive and an OK chipset. The thing I didn't notice at purchase time was the real killer: Microsoft Vista 64-bit Version.
When I got it home, I found the graphics compelling, but the speed rather, um, crappy. A quick peak at the Task Manager told me why: with no applications running, I was using about 40% of the CPU power. Opening any app would immediately spike the CPU usage, and you could literally hear the machine whimper when I put NI's Maschine on it. Two drums sounding (with no effects) was about the limit of its capability. Unacceptable.
So, using the myriad of posts about the subject, I started peeling stuff off the machine. First, it was the zillions of bloatware pieces HP put on it. I realize that this keeps the price low(-ish), but what a pain in the neck. Doing this work made me feel like buying that old Geek Squad shirt I saw at the Goodwill store.
That got me back a little CPU and a lot of disk space, and much more CPU was returned by getting rid of the 30-day Norton Hellhole. I know that viruses are scary and all, but this wasn't going to be a net-machine, so I didn't want to give up a quarter of the functionality to that pigpen. Dumping a lot of HP-specific services (like the one that says "I'm going to eat a whole bunch of CPU - and generate a whole bunch of heat - waiting breathlessly for you to put a DVD in the drive so I can give you a 13" version of a cinema screen") gave me a bunch back as well. I tried dumping the Aero graphics, but geez that looked ugly in comparison.
I got to the point where Maschine, Acid, Sound Forge and other goodies was running reliably. However, this machine has some pretty crap audio stuff going on (again with the "focused on DVD playing" approach), and I wanted to use a higher-quality audio interface. Not a single interface I have - and I've got ten or twelve - would work on this machine. No matter what I did, there either crackling or freezing (or sometimes both), and I was steaming. Add to this being under deadline for reviews on Acid and the Waldorf Blofeld, and you can imagine that I was ready to return the machine (even though the return window was already gone, I suspected I could threaten to throw it through the front window and get at least half my money back).
Then I got to thinking: this seemed like a rather puny machine to be running Vista x64, but there was really no option to run XP (something that HP and everyone else warns about due to unavailable drivers). But could dropping to Vista x86 (32-bit) work out? I spent some time with my friend and coworker Andrew Pask, and we decided that it was worth the effort. I could either download it from MSDN, order an x86 set of disks from Microsoft or buy a retail package. I chose the latter, since "time = money" right now, and set about upgrading at 10pm last night. At 5am this morning, it was done (along with app installs). All of my software works beautifully. Hardware seems to be fine. NI's Service Center doesn't even blow up on me (a remarkable thing)!
In reviewing the evening with my wife, she remarked on how every new version of Microsoft OS inevitably leads to some number of all-nighters. Whether it was the boned-up Windows 3.0, my initial Win95 debacle, helping my dad with WinME or my sister with WinXP, it all added up to one or more sleepless nights. Now this - what crap.
Alas, I can't blame this on Microsoft (much). HP made a plethora of bad decisions with this machine. 64-bit Vista was a big mistake. Ditto for the 80 lbs. of bloatware included with the machine. I've had good luck with HP machines in the past, and I hope to buy from them in the future. But here is my strong recommendation to HP for future computer systems:
1. Find someone that knows something about OS performance and have them choose the version you will use. Microsoft won't help, nor will whatever salesman buckethead that put x64 on the DV3-1075. This is a technical choice - get a good technical person to do it right.
2. Stop with the crapware already. I'm sure the HP Experience is important to you, but having fifty applications fight for control of the optical drive and the audio card isn't helping. I just wonder what people like my parents (60+ years in age) do when they get a box like this. Well, apparently they call someone like me, or the Geek Squad.
3. Norton is no longer a choice. Not that McAfee and friends are doing that much better, but Norton is neither good for the user nor good for your user experience. Most Norton installs represent a full onslaught of dialog boxes, downloads, flashing dock items and blitzed DSL communications. Is this the experience you want?
I'm sure that I represent a negligible portion of HP's business model, and Accountants Worldwide really wants all of this crap on the computers they buy for their droids. But for me (and the 20-or-so people that ask me about what machine to buy), HP is no longer worth considering. Do I like the 1075? Oh sure I do, but at this point, I've probably done more work on it than HP ever did, so I consider it a "DDG DV3-1075us" rather than anything I bought off the shelf.
And that's a pity.
[ddg]
Subscribe to:
Posts (Atom)
