James Tauber's Blog 2008/11/06
Song Project: RH Piano Riff
Most of my pop song ideas begin with either a chord progression voiced a particular way on piano or some bass line. The song we'll be talking about here falls in to the first category.
I remember when I first started composing in high school, I did a lot of songs that were just permutations of I, IV, V and vi chords (so in C, that would be C, F, G and Am).
I remember one instrumental I wrote in Year 10 (called "Mystical Movements in Green")—that my drama class choreographed a dance to—used the chord progression vi IV I V and in particular was voiced with the vi and I in the second inversion. I always liked the way it sounded.
A couple of weeks ago, I was improvising on my digital piano and took a liking to the following variation:
III . vi . IV . I V
with the vi and I again in the second inversion. I was playing in F at the time with a driving 3+3+2 rhythm in the right hand, so the resultant riff was:
which sounds something like this:
download if embed doesn't work
This will form the basis for the song.
All material for this project is made available under a Creative Commons BY-NC-SA license so you are free to redistribute and remix with attribution but under the same license and not commercially.
by : Created on Nov. 6, 2008 : Last modified Nov. 6, 2008 : (permalink)
Song Project
One series I thought would be fun to kick off this month is to talk about music composition and record producing and engineering by working through a song. I've chosen a song I just started working on last month and the idea is I'll go through the process from initial idea to final produced song over a series of blog entries.
All material for this project is made available under a Creative Commons BY-NC-SA license so you are free to redistribute and remix with attribution but under the same license and not commercially.
I'll get started with the music in a separate post right away.
by : Created on Nov. 6, 2008 : Last modified Nov. 6, 2008 : (permalink)
Atom, Google Reader and Duplicates on Planets
For a while I've wondered why posts syndicated across multiple planets don't get picked up by Google Reader as duplicates (and automatically marked read when I've read it the first time around).
I wasn't sure whether the problem was:
- the source feeds
- the planet feeds
- Google Reader itself
so I decided to investigate further with my own feed as the source and the three planets my site is syndicated to (that I know of).
Let's take my post Cleese and Disk Images.
My feed gives both an id and a link for both the feed itself and each individual entry. That makes it possible, at least, for planets and readers to do the Right Thing. So I don't think the problem is my feed.
On the Official Planet Python:
- there is an RSS 1.0 feed
- the rdf:about is not the same as the id in my feed but is the link URL (subtlety different but the planet is doing the wrong thing, IMHO)
- there is no authorship or source information
On both the Unofficial Planet Python and on Sam Ruby's Planet Intertwingly:
- there is an Atom feed
- the entry Cleese and Disk Images has the same id as in my feed and a distinct link.
- the source element gives appropriate information about my blog and the original feed
- the author (which I only give on the source feed not each entry) is not inherited on to the entry in the planet feed, only included in the source
Note that the handling of the author by the latter two feeds is correct per the Atom RFC, although I have noticed that Safari's feed reader gets this wrong and, despite the author in the source element, uses the inherited author from the planet feed itself.
But, in short, the Atom-feed-based Planets do the Right Thing, although IMHO the RSS-1.0-based Official Planet Python does not. That may not be the Planet's fault. The RSS 1.0 Spec (or any RSS for that matter) may not make the distinction between id and link.
So given that my feed and two of the planet feeds do the right thing, I guess that places the blame with Google Reader.
Why does Google Reader not honour the entry id and automatically mark duplicates as already read when you've read it the first time. That's my pony request for Google Reader.
And by the way, the same thing applies to feeds themselves, not just entries. Feedburner, for example, does the right thing and passes through the id of a source Atom feed into its own Atom feed version. However, if you subscribe to both the source and Feedburner version of of a feed, Google Reader doesn't not identify them as the same feed. Of course, if either are RSS, I'd assume all bets are off.
So, in summary, Atom supports doing the Right Thing. The Atom-based Planets do the Right Thing. Google Reader doesn't take advantage of this.
by : Created on Nov. 6, 2008 : Last modified Nov. 6, 2008 : (permalink)