Re: Is Session View counterproductive?
Posted: Wed Feb 01, 2012 6:54 am
I've though a lot about this issue, too. To quickly answer the last part -- "what's session view for?" -- I'll just state the obvious cop-out answer that is nonetheless imo accurate: it's for whatever you want it to be for, whatever works for you.
For me, that is absolutely composition of new material. But, I agree with you that it is difficult, daunting and yes, often boring, to have to eventually "re-write" (though really, more accurately, re-arrange) your song in arrangement view, this being usually hours and hours into the songwriting process, when you've already heard your song pieces a zillion times and kinda just want to be DONE with the thing.
But honestly, this is a problem that only exists because of all the positives that session view introduces in the first place. Creating and perfecting the individual chunks of a song has never been faster and more fun than when using session view; the later-on effect of feeling daunted and bored by arrangement is just the inevitable price you pay for having such a cool, efficient tool available to you in the first place. Ultimately, it's not in the least counter-productive because if I try to start writing songs solely in arrangement (or in any other DAW, for that matter) it takes far, far longer (and is less fun) to get the kind of work done that I can get done in session view much more rapidly and in a much more fun manner. So, if you add together session view composition time with the time it takes arranging those session scenes, I think the total time isn't so different than how long it would take to compose a song of the same quality in a traditional arrangement sequencer, because even though that process is one sequencing process versus two, it's a much slower process overall.
At the end of the day, the fault lies not in Ableton for providing 2 methods instead of 1, but on the user, for not being more disciplined in creating a workflow that *knows when to start arranging and stop sequencing new loops in session view*. It's a tricky thing, I know that from experience as well as anyone, but it can be improved upon by the user. You sort of develop this sixth sense that kicks in and says "stop writing new scenes; this shit is ready to be thrown over into arrangement, tweaked, transitions adjusted, and bam, done."
If such a discipline isn't created on the user end, then yeah, loop-itis or whatever that article calls it will totally set in, and nothing gets done. But it's pretty silly to blame this on the sequencer, which is simply providing incredibly efficient and effective tools for getting work done; the user, obviously, has to take on full responsibility for their project and ultimately, their ability to create a finished product out of it.
-M
For me, that is absolutely composition of new material. But, I agree with you that it is difficult, daunting and yes, often boring, to have to eventually "re-write" (though really, more accurately, re-arrange) your song in arrangement view, this being usually hours and hours into the songwriting process, when you've already heard your song pieces a zillion times and kinda just want to be DONE with the thing.
But honestly, this is a problem that only exists because of all the positives that session view introduces in the first place. Creating and perfecting the individual chunks of a song has never been faster and more fun than when using session view; the later-on effect of feeling daunted and bored by arrangement is just the inevitable price you pay for having such a cool, efficient tool available to you in the first place. Ultimately, it's not in the least counter-productive because if I try to start writing songs solely in arrangement (or in any other DAW, for that matter) it takes far, far longer (and is less fun) to get the kind of work done that I can get done in session view much more rapidly and in a much more fun manner. So, if you add together session view composition time with the time it takes arranging those session scenes, I think the total time isn't so different than how long it would take to compose a song of the same quality in a traditional arrangement sequencer, because even though that process is one sequencing process versus two, it's a much slower process overall.
At the end of the day, the fault lies not in Ableton for providing 2 methods instead of 1, but on the user, for not being more disciplined in creating a workflow that *knows when to start arranging and stop sequencing new loops in session view*. It's a tricky thing, I know that from experience as well as anyone, but it can be improved upon by the user. You sort of develop this sixth sense that kicks in and says "stop writing new scenes; this shit is ready to be thrown over into arrangement, tweaked, transitions adjusted, and bam, done."
If such a discipline isn't created on the user end, then yeah, loop-itis or whatever that article calls it will totally set in, and nothing gets done. But it's pretty silly to blame this on the sequencer, which is simply providing incredibly efficient and effective tools for getting work done; the user, obviously, has to take on full responsibility for their project and ultimately, their ability to create a finished product out of it.
-M