4 ms·

Cool idea if you are a composer who likes to use version control! I just recently started putting my GarageBand projects in GitHub =)

by 0x5a177 16y ago

AndyKelley 16y ago
That can work but there are some problems: * you don't have a "git log" with an audio preview in each version * what about all the samples that your project depends on? Do you add them to the repository? What about when you have two projects that use the same samples? What happens when your hard drive gets wiped and you lose the samples you didn't commit to the repository? * what about the plugins you use? github can't keep track of the dependencies of the project. * what if you want to collaborate on a project? if two people edit and try to push, you'll have a conflict which is impossible to merge SolidComposer solves all of these problems.
- 0x5a177 16y ago
  Yes, I agree...GitHub or any text-centric SCM is a very simplistic solution that really only works (and not very well) for metadata in audio projects. These points are good answers to the question, "How is SolidComposer better than using another version control system for my compositions?" But I guess my gut reaction — which you can take with many grains of salt because I don't do any work in a collaborative music composition situation — is that of "Geez...it's hard enough to get technical people to jump into my version control workflow, how could I get musicians in on this?" (Which I think you already addressed in another comment that your target audience is maybe the overlap of developers/composers.) I'm reading through your Introducing SolidComposer page and I think it would be helpful if you could condense that down and put it somewhere more accessible (maybe on the front page). I find myself not really wanting to spend time figuring out how the app will help me. Also, the How Does It Work? section actually does not seem appealing. The first situation seems simple and straightforward, whereas when you talk about SolidComposer complaining about missing dependencies, that starts makes me feel uncomfortable. Anyways, I hope this is helpful and good luck with the project. Side note: I recently started playing in a band and one thing I notice is that whenever we get together to practice a particular song, we are always reinventing the song and it never really seems to gel. It's always "How does that part go again? How many measures were we supposed to play that riff?" Could SolidComposer help in that situation?

Cool idea if you are a composer who likes to use version control! I just recently started putting my GarageBand projects in GitHub =)

by 0x5a177 16y ago

Cool idea if you are a composer who likes to use version control! I just recently started putting my GarageBand projects in GitHub =)

AndyKelley 16y ago

That can work but there are some problems: * you don't have a "git log" with an audio preview in each version * what about all the samples that your project depends on? Do you add them to the repository? What about when you have two projects that use the same samples? What happens when your hard drive gets wiped and you lose the samples you didn't commit to the repository? * what about the plugins you use? github can't keep track of the dependencies of the project. * what if you want to collaborate on a project? if two people edit and try to push, you'll have a conflict which is impossible to merge SolidComposer solves all of these problems.

0x5a177 16y ago
Yes, I agree...GitHub or any text-centric SCM is a very simplistic solution that really only works (and not very well) for metadata in audio projects. These points are good answers to the question, "How is SolidComposer better than using another version control system for my compositions?" But I guess my gut reaction — which you can take with many grains of salt because I don't do any work in a collaborative music composition situation — is that of "Geez...it's hard enough to get technical people to jump into my version control workflow, how could I get musicians in on this?" (Which I think you already addressed in another comment that your target audience is maybe the overlap of developers/composers.) I'm reading through your Introducing SolidComposer page and I think it would be helpful if you could condense that down and put it somewhere more accessible (maybe on the front page). I find myself not really wanting to spend time figuring out how the app will help me. Also, the How Does It Work? section actually does not seem appealing. The first situation seems simple and straightforward, whereas when you talk about SolidComposer complaining about missing dependencies, that starts makes me feel uncomfortable. Anyways, I hope this is helpful and good luck with the project. Side note: I recently started playing in a band and one thing I notice is that whenever we get together to practice a particular song, we are always reinventing the song and it never really seems to gel. It's always "How does that part go again? How many measures were we supposed to play that riff?" Could SolidComposer help in that situation?