Hi Chris,
On 01/17/2019 10:56 AM, Chris Caudle wrote:
On Wed, January 16, 2019 8:23 am, Dave Phillips wrote:
No hour long recording, but here's the final version:
https://youtu.be/7f2RLTbbs9Y
Very nice. Do I understand correctly that this is essentially an
algorithmic style composition, in that once you setup the patching, the
modules are generating the control "voltages" that determine notes and
frequency, so it starts up and just runs without intervention?
Yes, that's pretty much the picture. The challenge is in setting up the
modules, i.e. their programming. While the music itself is the result of
more-or-less random procedures the sounds themselves are typically
closely designed (read: I spend a lot of time tuning the modules to an
expected behavior).
Edited and mixed with Ardour6. :)
Nice to know that Paul hasn't broken basic functions with all his
re-arranging of the guts. :)
To be clear, that's Ardour6 very-beta, built from git sources.
What type of editing do you actually do (assuming my understanding above
is correct)? Do you listen through and pull out interesting segments and
stitch
together? Or is it lighter weight than that?
In 1625 the editing was straightforward, just selecting and merging
sections of two tracks. The synchronization was easy in this case, and
the only other process involved was a normalization pass. Incidentally,
things were done this way because Rack gets cranky when my patches hit a
certain load limit. I designed the patch for a single performance pass,
but it's too big a hit on my CPU (a 3.5 GHz 6-core AMD). Hence the
multiple takes. In sum, for this recording I added a little more than a
minute to the original by interpolating the "bridge" section.
Thanks for listening, Chris, and thank you for your inquiry as to how it
all got made.
Best regards,
dp
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user@xxxxxxxxxxxxxxxxxxxx
https://lists.linuxaudio.org/listinfo/linux-audio-user
