Show HN: Songftware – Music Written Like Software
songftware.com
songftware.com
The author is pushing the same ideas in other places (sorry for the signup-walled Quora link):
http://jeffmeyerson.quora.com/Musicians-and-Engineers?srid=p...
As the OP appears to be the original author, I will ask the following: Do you really believe the "engineer mindset" is the best way of thinking in all situations? If so, why are engineers not the top musicians in the world? Many engineers are/have been in bands. But the majority of successful musicians follow at least some of the "bad traits" you list. Wouldn't the basic laws of consumer choice and capitalism bring "engineer musicians" to the top of the charts every time if those habits were really bad?
It isn't satire. Have you ever tried to write electronic music with a group of people?
You basically argue musicians should act more like you. Do you really want a world of yous? Because I don't, I believe there is room for every mindset. If you really want to improve electronic music production, try starting with the users. Find out what their needs are. I would hesitate to separate you from your users, but you appear to do that yourself in this article.
Yes there are many good engineer+musicians. But I've never seen a group of musicians use a KANBAN board.
It's like a service-oriented architecture. If there is a lot of demand on a service, you spin up another copy of it.
I'm continually proud and disappointed with my own results. I know I could do more if I was working with a team.
The "Why" described is that when the instrument is a single computer running a DAW, it has poor concurrency. You could change the instrument model instead to one that re-enables concurrency. You are doing the inverse presumably because you haven't had a good jam session before and only feel comfortable sitting behind the DAW. To get around this problem, you're rationalizing a process which is actually less efficient than jamming, as it straightjackets the creativity into a "waterfall" process instead of an "agile" one.
The Postal Service used waterfall when making their album.
Sit down at the piano, press record, and make up a piano piece on the spot. This is a fun creative exercise - the results often suck but sometimes something good comes out of it. You can't be super-original harmonically or you'll lose the thread and stop - but it's good for practicing discipline. [1]
Sit down with a couple of people you get along with, press record, and jam. Same thing as above - you can't get too crazy harmonically, but you can definitely mess around with layering and intensity. [2]
Write some lyrics and then try and write some music by yourself to fit around it. I'm not sure, but I think this sort of music leads to simpler song forms. [3]
Write some music to the point that they suggest syllables and vowel sounds, and then pound your head against the wall trying to find words that fit those musical moments you want. This is really, really hard but eventually rewarding. [4]
Sit in a room with your bandmates, jam together to come up with material, and then work/argue together to craft it into a song form. I haven't done this but I think it ends up with stuff that can be cohesive (good) or homogenous (bad). This can be done over a distance through dropbox etc also.
Come up with some electronica beats and then hire someone to come in and yell out phrases she reads from magazine ads, punctuated by dirty talk and sexual grunts. I haven't done this either, but it's responsible for a good percentage of the top 40.
(Links just for examples from my own history, listen or don't - I don't intend this as self-promotion.)
[1] https://soundcloud.com/curtsiffert/slowrain [2] http://thesalvagery.bandcamp.com [3] https://itunes.apple.com/us/album/damn-my-eyes/id899061469?i... [4] https://itunes.apple.com/us/album/she-believes/id899061469?i...
It looks like this is still in the experimental/conception stage. Right now it seems more like a mental model for music than actual tools. I'd be interested in seeing what analogies besides code would be applicable or might have lessons learned. For example, I know that collaboration and sharing of mechanical engineering design software is relatively less useable/mature than sharing a git repository. For artists that collaboratively work on 3D models or images I'd imagine that the workflow is passing around .psds or whatever, rather than final images because everyone is on the same platform.
I'll be paying attention as this develops.
I have heard good things about Splice, which allows git-like collaboration.
What I want to underscore: there are great tools for individual and small-group creativity. I'm interested in processes for a large team that allows asynchronicity and scalable development.
I have worked in all these environments and yes, there are aspects of process ... and principles, techniques, and mindset which can be taken from engineering and applied to creative pursuits. Good point.
I have a strong bias to action and want to experiment with the ideas I laid out.