Your Computer May Have Errors II
By danlinke on February 2, 2020 10:54 am
a homage to the lost big scary orderlies album "paranoid jumbotron"
Audio works licensed by author under:
CC Attribution Share Alike (BY-SA)
Weeklybeats is a 52 week long music project in which artists compose and publicly release 1 song a week for the entire year.
Starting January 1st 2024 GMT each participant will have one week to upload one finished composition. Any style of music or selection of instruments are welcomed and encouraged.
Sign up or Login to get started or check our FAQ for any help or questions you may have.
WeeklyBeats.com / Music / danlinke's music / Your Computer May Have Errors II
a homage to the lost big scary orderlies album "paranoid jumbotron"
Audio works licensed by author under:
CC Attribution Share Alike (BY-SA)
This is rad. If you don't mind me asking, what equipment did you use for it?
Cool samples and glitching! Are you running parts through a vocoder or ring modulation? Some of the tones and samples have sound like they are being processed. The chaos works well!
Nice, like the breakdown experiment thing in the middle!
thanks! I wasn't really sure where to go after the first part was written so I decided the best way to go was by throwing it against a wall of glitch and seeing what noise came out!
This is rad. If you don't mind me asking, what equipment did you use for it?
Cool samples and glitching! Are you running parts through a vocoder or ring modulation? Some of the tones and samples have sound like they are being processed. The chaos works well!
The entire piece was written in the box! Ableton 9.7.4, Sylenth, Massive and M1 VSTs, while the vocal chops were samples I found on Splice (royalty free, of course).
To answer both of the questions about the processing, the plugin at the core of the chaos and glitching is called livecut. Think of it as a more chaotic cousin of Ableton's beat repeat - a real-time beat slicer but you can also bitcrush and do comb filtering too. I ran the plugin on the two arpeggio parts in the second half, as well as on the main master channel at varying points. I ran a lot of automation to change up stuff like the slicing, pitch range, or the minimum or maximum amount of bars being sliced, among other things.
The processed snare in the first part hasn't had a lot done to it. EQ, flanger and then I automated transposing. The "move it" chop's effect chain was a bit more intense. QuikQuak's Pitchwheel (something of a secret weapon I've used quite a bit this year, it adds a different dimension to repitching samples' key or timbre that Ableton's warp doesn't), auto-tune, a bit of reverb, compression and then finally during the break-down a resonator that has its main note and dry/wet signal automated.
Bit of a long response but I hope there's some good answers in there!
Man the melody and beat that drops back in after the middle section is boss! Nice work! My computer exploded to this!
sinewave wrote:Nice, like the breakdown experiment thing in the middle!
thanks! I wasn't really sure where to go after the first part was written so I decided the best way to go was by throwing it against a wall of glitch and seeing what noise came out!hent03 wrote:This is rad. If you don't mind me asking, what equipment did you use for it?
NWSPR wrote:Cool samples and glitching! Are you running parts through a vocoder or ring modulation? Some of the tones and samples have sound like they are being processed. The chaos works well!
The entire piece was written in the box! Ableton 9.7.4, Sylenth, Massive and M1 VSTs, while the vocal chops were samples I found on Splice (royalty free, of course).
To answer both of the questions about the processing, the plugin at the core of the chaos and glitching is called livecut. Think of it as a more chaotic cousin of Ableton's beat repeat - a real-time beat slicer but you can also bitcrush and do comb filtering too. I ran the plugin on the two arpeggio parts in the second half, as well as on the main master channel at varying points. I ran a lot of automation to change up stuff like the slicing, pitch range, or the minimum or maximum amount of bars being sliced, among other things.The processed snare in the first part hasn't had a lot done to it. EQ, flanger and then I automated transposing. The "move it" chop's effect chain was a bit more intense. QuikQuak's Pitchwheel (something of a secret weapon I've used quite a bit this year, it adds a different dimension to repitching samples' key or timbre that Ableton's warp doesn't), auto-tune, a bit of reverb, compression and then finally during the break-down a resonator that has its main note and dry/wet signal automated.
Bit of a long response but I hope there's some good answers in there!
Thanks! Lots of good info. Always interested in learning how other composers wor, Much appreciated.