Demo 6 just finnished rendering to an mp3.
It'll be up in a while on the demo page.
Its here:
http://c-l-a-m-p.wikispaces.com/demos
I've decided to hold back on the written evaluations, and finish up my demos. I've used most of the software, and you can see my status with my checklist I made in googledocs.
http://docs.google.com/View?id=dcbdsd28_199gq8jv4d8
Basically, its a list of all the software I plan to use (much different than the rough draft list I put up, with a coded status for each one.
Monday, April 26, 2010
Wednesday, April 21, 2010
Saturday, April 17, 2010
CLAMP: audio interface up and running
Hello all!
Its been a few weeks since my last post, and I apologize for my lag. Fieldwork has left me with not a lot of time for little updates like these. Its been alot of experimenting, outlining, screenshotting, praying, and writing on my part. But its (mostly) been a blast to do!
In under 36 hours I have to finish a rough draft of my research paper, so things can be a little crunched for time. It looks like a majority will be CLAMP condensed into one paper, but we'll see what happens.
I write this post to praise my reader, Mr. Adam Carpenter, who shares my love of making music and seems to genuinely support my efforts for this project. He has lent me his Tascam US-122 firmware audio/midi interface. You may be saying "Paul, you have the US-144 audio interface, why would you want something below?" In a word: compatibility. Linux drivers don't support the US-144 well enough yet, and they support the US-122 beautifully. Today I got it hooked up and running in under half an hour. The US-122 will make it possible for me to hook up things like quality microphones and ukuleles and basses to my computer. This is a very exciting moment for me, and its all possible thanks to my man Mr.Carpenter!
Don't worry Mr.C, I'll be taking good care of it.
-Paul
PS: here is the article I used to get the interface working:
https://help.ubuntu.com/community/TASCAM_US-122
Its been a few weeks since my last post, and I apologize for my lag. Fieldwork has left me with not a lot of time for little updates like these. Its been alot of experimenting, outlining, screenshotting, praying, and writing on my part. But its (mostly) been a blast to do!
In under 36 hours I have to finish a rough draft of my research paper, so things can be a little crunched for time. It looks like a majority will be CLAMP condensed into one paper, but we'll see what happens.
I write this post to praise my reader, Mr. Adam Carpenter, who shares my love of making music and seems to genuinely support my efforts for this project. He has lent me his Tascam US-122 firmware audio/midi interface. You may be saying "Paul, you have the US-144 audio interface, why would you want something below?" In a word: compatibility. Linux drivers don't support the US-144 well enough yet, and they support the US-122 beautifully. Today I got it hooked up and running in under half an hour. The US-122 will make it possible for me to hook up things like quality microphones and ukuleles and basses to my computer. This is a very exciting moment for me, and its all possible thanks to my man Mr.Carpenter!
Don't worry Mr.C, I'll be taking good care of it.
-Paul
PS: here is the article I used to get the interface working:
https://help.ubuntu.com/community/TASCAM_US-122
Sunday, April 4, 2010
CLAMP: working rubric
Tonight I worked on around 7 CASEs, or CLAMP Audio Software Evaluation's. These basically consist of a rubric and a written review of each one.
I posted this for two reasons:
1. To exclaim that my rubric is done! and that the guidelines (WIP) can be viewed here
2. To post a sample, which is here
Reviews definitely will take longer to do, and will give the audience a much better sense of what the software is about. I will work on those in the weeks to come.
peace out!
I posted this for two reasons:
1. To exclaim that my rubric is done! and that the guidelines (WIP) can be viewed here
2. To post a sample, which is here
Reviews definitely will take longer to do, and will give the audience a much better sense of what the software is about. I will work on those in the weeks to come.
peace out!
Monday, March 29, 2010
Should be asleep. But all hail the opensource movement!
I should be asleep but I just thought I'd share two things:
1. This ad promoting the Linux operating system always pumps me up. I remember watching it years ago. I just watched it a few minutes ago, and I could pick up all the connections to the open-source revolution. It was a very satisfying rewatch for me and I hope you enjoy.
2. Project Durian, the opensource movie project is doing its part in being a completely opensource movie. Not only will the project files for the movie be available once it is done, but it is relying on much user support to contribute to the movie. I don't know if they went to this extent in the previous open movies, but it truley makes me excited seeing stuff like this.
Off to bed maybe.
-P
1. This ad promoting the Linux operating system always pumps me up. I remember watching it years ago. I just watched it a few minutes ago, and I could pick up all the connections to the open-source revolution. It was a very satisfying rewatch for me and I hope you enjoy.
2. Project Durian, the opensource movie project is doing its part in being a completely opensource movie. Not only will the project files for the movie be available once it is done, but it is relying on much user support to contribute to the movie. I don't know if they went to this extent in the previous open movies, but it truley makes me excited seeing stuff like this.
Off to bed maybe.
-P
CLAMP rant
Sometimes, ignorance displeases me.
Since no one reads this and I know my teacher likes transparency, I thought I'd go ahead and rant.
I got a concise message about my project page. one of the two lines said this:
"calendar is good, but the weekend only work was curious."
I was called out on it in class, and I thought he was kidding. Apparently he was not.
Ok. Let this be known: just because I begin stuff on weekends doesn't mean they'll end on weekends. I fixed the problem so even morons can understand what I mean when I say "begin demo x" on friday.
I am insulted that anyone would think that I am doing weekend only work. The entire electronic music community should be insulted as well. Any person worth mentioning knows it can take weeks to create a worth while track. And thats using familiar software. I'm using over 20 different kinds of software. Most of these I have to learn how to use in a weeks time. On top of that, I have to make something musical out of it. You tell me again that that is weekend only work. I respect this dude alot, but if this man only went to my page describing what Demos were, I think it would be obvious to see that these take time.
As I said before, I've tailored my calender so that an audience failing to read and interpret my cryptic calenders can instead visually see that it takes time. But world, Id like to let you know that this was for you and not me.
My calenders and action plan can be seen at this address
The good news is that I got another bit of advice:
"also add some more details on interviews and such things"
I'll agree with that one. More details on my interviews will be publicly available as soon as possible.
Since no one reads this and I know my teacher likes transparency, I thought I'd go ahead and rant.
I got a concise message about my project page. one of the two lines said this:
"calendar is good, but the weekend only work was curious."
I was called out on it in class, and I thought he was kidding. Apparently he was not.
Ok. Let this be known: just because I begin stuff on weekends doesn't mean they'll end on weekends. I fixed the problem so even morons can understand what I mean when I say "begin demo x" on friday.
I am insulted that anyone would think that I am doing weekend only work. The entire electronic music community should be insulted as well. Any person worth mentioning knows it can take weeks to create a worth while track. And thats using familiar software. I'm using over 20 different kinds of software. Most of these I have to learn how to use in a weeks time. On top of that, I have to make something musical out of it. You tell me again that that is weekend only work. I respect this dude alot, but if this man only went to my page describing what Demos were, I think it would be obvious to see that these take time.
As I said before, I've tailored my calender so that an audience failing to read and interpret my cryptic calenders can instead visually see that it takes time. But world, Id like to let you know that this was for you and not me.
My calenders and action plan can be seen at this address
The good news is that I got another bit of advice:
"also add some more details on interviews and such things"
I'll agree with that one. More details on my interviews will be publicly available as soon as possible.
Tuesday, March 23, 2010
CLAMP Calender
CLAMP calender available publicly at this link:
http://sites.google.com/site/conciselinuxaudiomusicproject/
http://sites.google.com/site/conciselinuxaudiomusicproject/
Subscribe to:
Posts (Atom)