Eponymous

Another Demo Update
Two weeks! Ha! It's been closer to two months.

A few days ago I had some time so I sat down with the ProTools set up again. After considering some advice from jlight, I decided to record a second track of the bass line. I decided to use my Yamaha for the second track, as I had used my Fender for the original recording back in June. The two instruments have different characteristics in their sounds and the two playing together seems to add a "fullness" to the sound.

So all I had to do was record 24 seconds of bass and put together a mix. This should take, what, 15 minutes? It took 45 just to record. Once again ProTools repeatedly crashed. When it wasn't crashing, it would report an error and stop recording. Does anyone know if there are updates for ProTools LE 7.1 that will fix this issue? As it stands now, I can't run ProTools for more than a few seconds without disabling multi-core support on my CPU. I have multiple processors. It is a multi-threaded application. It should run better... But I'll save this for that upcoming ProTools rant I keep promising.

Anyway, after about an hour and fifteen minutes, I got two mixes complete. One of them was accidental and sounds, "interesting." The other is closer to what I had in mind. While I wait for feedback on the actual mix from certain people, everyone is free to enjoy the accidental mix found here.

If anyone actually listens to it, I'd be happy to accept any comments and criticism.

[/album] [permanent link]

Gmail and mutt
I like mutt. Of all the mail clients I've used over the years, it sucks the least. It works well with my mail server.

Despite having my own domain and mail server, I still use gmail for certain things; things I don't mind being retained for 3 years after I delete them, or more specifically, things I want retained for 3 years after I delete them.

I don't like the gmail web interface. I find checking my gmail to be annoying because of this. I remembered gmail offering POP and IMAP. I figured I could use that to get my gmail. Shouldn't be too hard right?

A quick search of Mr. Yahoo and Mr. Google gave me two good starting points: Lifehacker.com and MattCutts.com.

I read the sites and the getmail man page and figured out what I needed to do. First I enabled IMAP for my gmail account. Next, I created the .getmail directory in my home directory then created a getmailrc file there. I want all gmail mail to be delivered to a specific mbox file without going through my normal mail delivery channels. The contents of the getmailrc file are quite simple:

[retriever]
type = SimpleIMAPSSLRetriever
server = imap.gmail.com
username = username@gmail.com
password = usernamespasswordgoeshere
mailboxes = ("inbox",)

[destination]
type = Mboxrd
path = /usr/home/mforde/Mail/GMAIL

The retriever section defines how getmail will retrieve the mail. In this case it uses IMAP over SSL to connect to imap.gmail.com. The mailboxes setting can be used to specify only certain gmail labels to retrieve, but I want anything in the inbox.

The destination section tells getmail what to do with the mail once it has grabbed it from gmail. This configuration dumps it into an mbox file I've named GMAIL.

I chose IMAP over POP because of the slightly-less-than-documented "feature" of gmail only allowing 99 messages at a time over POP.

So to get the initial batch of 7000+ emails, I ran

> getmail -vvv -l

to get verbose output and to leave messages on the gmail server. When that was done I pointed mutt at the GMAIL mbox and like magic, there was my gmail, organized nicely in my terminal.

Now, I want to check to get the latest mail fairly often, and I don't want to download messages already copied over. To accomplish this, I added a crontab to run every 10 minutes and invoke

getmail -l -n -q

This tells getmail to leave copies on the server, only get new messages it hasn't already retrieved, and be quiet about it.

This has worked out well for me. If you're interested in setting up something like this, I highly recommend reading the article at matcutts.com. That article also links to several sample getmailrc files.

[/unix] [permanent link]

Happy Anniversary
The Twilight Zone premiered 50 years ago tonight. Slashdot has a bit about it.

[/musings] [permanent link]

Product Review: ASICS Cumulus-11
This is the third installment of my running product reviews. Last time I said I'd discuss my "current running shoe" but my again I'm a liar. I'm still going to discuss the ASICS Cumulus-11, but it is no longer my current running shoe.

I purchased the Cumulus-11 based on my love of the Cumulus-10, without really trying them. This turned out to be a mistake. The Cumulus-11 is a fine update to the Cumulus-10; however, the changes are better for some runners than others.

The heel of the Cumulus-11 is noticeably firmer than that of the 10. Because of this change, I no longer get adequate compression and cushioning from these shoes. These shoes are not as firm as the Tailwinds previously reviewed either and are closer to the Cumulus-10 than to the Tailwinds. I never had the feeling of running in clogs with the Cumulus-11, but they were firm enough that old injuries were aggravated.

The Cumulus-11 is still on store shelves (at least it was at Fleet Feet this past weekend) and should also be available on-line through retailers such as EastBay. I recommend this shoe to a runner who liked the feel of the Cumulus-10 but had issues with it being too soft.

Next time, we'll discuss my current running shoe, the Nike Vomero+ 4. No really, I have three pairs of these to burn through, I'll be using them for a while.

[/running/reviews] [permanent link]

Eponymous

	About My Infrequently Updated Blog. The web-based journal of M. Forde, computer nerd, endurance athlete, and DeLorean owner contact Subscribe Subscribe to a syndicated feed of my weblog, brought to you by the wonders of RSS. Flavors There's more than one way to view this weblog; try these flavors on for size. index circa 1993 Sections main musings running DeLorean code unix album TBM Archives 2023 2022 2021 2020 2019 2018 2017 2016 2015 2014 2013 2012 2011 2010 2009 2008 2007 Disclaimers, Copyrights, Privacy, Etc. ToS Copyrights Links olix0r.net netmeister.org Giraffes Eat. Run. Sleep.

Eponymous

	About My Infrequently Updated Blog. The web-based journal of M. Forde, computer nerd, endurance athlete, and DeLorean owner contact Subscribe Subscribe to a syndicated feed of my weblog, brought to you by the wonders of RSS. Flavors There's more than one way to view this weblog; try these flavors on for size. index circa 1993 Sections main musings running DeLorean code unix album TBM Archives 2023 2022 2021 2020 2019 2018 2017 2016 2015 2014 2013 2012 2011 2010 2009 2008 2007 Disclaimers, Copyrights, Privacy, Etc. ToS Copyrights Links olix0r.net netmeister.org Giraffes Eat. Run. Sleep.	08 Aug 2008 Another Demo Update Two weeks! Ha! It's been closer to two months. A few days ago I had some time so I sat down with the ProTools set up again. After considering some advice from jlight, I decided to record a second track of the bass line. I decided to use my Yamaha for the second track, as I had used my Fender for the original recording back in June. The two instruments have different characteristics in their sounds and the two playing together seems to add a "fullness" to the sound. So all I had to do was record 24 seconds of bass and put together a mix. This should take, what, 15 minutes? It took 45 just to record. Once again ProTools repeatedly crashed. When it wasn't crashing, it would report an error and stop recording. Does anyone know if there are updates for ProTools LE 7.1 that will fix this issue? As it stands now, I can't run ProTools for more than a few seconds without disabling multi-core support on my CPU. I have multiple processors. It is a multi-threaded application. It should run better... But I'll save this for that upcoming ProTools rant I keep promising. Anyway, after about an hour and fifteen minutes, I got two mixes complete. One of them was accidental and sounds, "interesting." The other is closer to what I had in mind. While I wait for feedback on the actual mix from certain people, everyone is free to enjoy the accidental mix found here. If anyone actually listens to it, I'd be happy to accept any comments and criticism. [/album] [permanent link]

Eponymous

	About My Infrequently Updated Blog. The web-based journal of M. Forde, computer nerd, endurance athlete, and DeLorean owner contact Subscribe Subscribe to a syndicated feed of my weblog, brought to you by the wonders of RSS. Flavors There's more than one way to view this weblog; try these flavors on for size. index circa 1993 Sections main musings running DeLorean code unix album TBM Archives 2023 2022 2021 2020 2019 2018 2017 2016 2015 2014 2013 2012 2011 2010 2009 2008 2007 Disclaimers, Copyrights, Privacy, Etc. ToS Copyrights Links olix0r.net netmeister.org Giraffes Eat. Run. Sleep.	02 Oct 2009 Gmail and mutt I like mutt. Of all the mail clients I've used over the years, it sucks the least. It works well with my mail server. Despite having my own domain and mail server, I still use gmail for certain things; things I don't mind being retained for 3 years after I delete them, or more specifically, things I want retained for 3 years after I delete them. I don't like the gmail web interface. I find checking my gmail to be annoying because of this. I remembered gmail offering POP and IMAP. I figured I could use that to get my gmail. Shouldn't be too hard right? A quick search of Mr. Yahoo and Mr. Google gave me two good starting points: Lifehacker.com and MattCutts.com. I read the sites and the getmail man page and figured out what I needed to do. First I enabled IMAP for my gmail account. Next, I created the .getmail directory in my home directory then created a getmailrc file there. I want all gmail mail to be delivered to a specific mbox file without going through my normal mail delivery channels. The contents of the getmailrc file are quite simple: [retriever] type = SimpleIMAPSSLRetriever server = imap.gmail.com username = username@gmail.com password = usernamespasswordgoeshere mailboxes = ("inbox",) [destination] type = Mboxrd path = /usr/home/mforde/Mail/GMAIL The retriever section defines how getmail will retrieve the mail. In this case it uses IMAP over SSL to connect to imap.gmail.com. The mailboxes setting can be used to specify only certain gmail labels to retrieve, but I want anything in the inbox. The destination section tells getmail what to do with the mail once it has grabbed it from gmail. This configuration dumps it into an mbox file I've named GMAIL. I chose IMAP over POP because of the slightly-less-than-documented "feature" of gmail only allowing 99 messages at a time over POP. So to get the initial batch of 7000+ emails, I ran > getmail -vvv -l to get verbose output and to leave messages on the gmail server. When that was done I pointed mutt at the GMAIL mbox and like magic, there was my gmail, organized nicely in my terminal. Now, I want to check to get the latest mail fairly often, and I don't want to download messages already copied over. To accomplish this, I added a crontab to run every 10 minutes and invoke getmail -l -n -q This tells getmail to leave copies on the server, only get new messages it hasn't already retrieved, and be quiet about it. This has worked out well for me. If you're interested in setting up something like this, I highly recommend reading the article at matcutts.com. That article also links to several sample getmailrc files. [/unix] [permanent link] Happy Anniversary The Twilight Zone premiered 50 years ago tonight. Slashdot has a bit about it. [/musings] [permanent link]

Eponymous

	About My Infrequently Updated Blog. The web-based journal of M. Forde, computer nerd, endurance athlete, and DeLorean owner contact Subscribe Subscribe to a syndicated feed of my weblog, brought to you by the wonders of RSS. Flavors There's more than one way to view this weblog; try these flavors on for size. index circa 1993 Sections main musings running DeLorean code unix album TBM Archives 2023 2022 2021 2020 2019 2018 2017 2016 2015 2014 2013 2012 2011 2010 2009 2008 2007 Disclaimers, Copyrights, Privacy, Etc. ToS Copyrights Links olix0r.net netmeister.org Giraffes Eat. Run. Sleep.	30 Nov 2009 Product Review: ASICS Cumulus-11 This is the third installment of my running product reviews. Last time I said I'd discuss my "current running shoe" but my again I'm a liar. I'm still going to discuss the ASICS Cumulus-11, but it is no longer my current running shoe. I purchased the Cumulus-11 based on my love of the Cumulus-10, without really trying them. This turned out to be a mistake. The Cumulus-11 is a fine update to the Cumulus-10; however, the changes are better for some runners than others. The heel of the Cumulus-11 is noticeably firmer than that of the 10. Because of this change, I no longer get adequate compression and cushioning from these shoes. These shoes are not as firm as the Tailwinds previously reviewed either and are closer to the Cumulus-10 than to the Tailwinds. I never had the feeling of running in clogs with the Cumulus-11, but they were firm enough that old injuries were aggravated. The Cumulus-11 is still on store shelves (at least it was at Fleet Feet this past weekend) and should also be available on-line through retailers such as EastBay. I recommend this shoe to a runner who liked the feel of the Cumulus-10 but had issues with it being too soft. Next time, we'll discuss my current running shoe, the Nike Vomero+ 4. No really, I have three pairs of these to burn through, I'll be using them for a while. [/running/reviews] [permanent link]