Device Details
Overview
Name | Version: | SubtleSonic UltraComb 1.1 |
Author: | PeterMcCulloch |
Device Type: | Audio Effect |
Description: | This is a robotize / bouncing-ball effect on steroids. Version 1.1 adds interpolation to the delays so that you can adjust the times without zipper noise. (this is set using the HQ button) You can use UltraComb for comb-filtering, but you can also treat it as a bank of up to 32 delays that you can order in accelerating or decelerating fashion. Use the max time knob to set how many of the delays you listen to, and the attack and release knobs to contour the volumes of the taps. Typically, comb-filters use feedback to create resonance. UltraComb, however, just uses lots of taps on a delay line, so you can have very resonant delays that stop immediately after the specified max time. Because the taps are discrete, you can create patterns that fade in and out as well. Use: This device really shines on percussive material, but you can use it on anything. It also has in/out and momentary switches with separate ramps for on and off, so it's great for adding color / delays to a track temporarily. Documentation (!) available on the website. Check out my other devices here: http://www.maxforlive.com/library/index.php?by=author&q=PeterMcCulloch&submit=Search Follow me on Facebook: http://www.facebook.com/subtlesonic |
Details
Live Version Used: | 8.2.2 |
Max Version Used: | 5.1.8 |
Date Added: | Nov 14 2011 19:25:52 |
Date Last Updated: | May 02 2012 12:56:08 |
Downloads: | 3854 |
ⓘ License: | AttributionNonCommercialShareAlike |
Average Rating
Log in to rate this device |
-n/a- |
Files
Device File: | UltraComb.amxd |
Comments
This has been one of my favorite devices for so long, there's none quite like it.
Note to the author:
I discovered that when the "Time" parameter(s) are automated to change in a sloping fashion (as opposed to instantly), it causes massive CPU spikes / buffer overload. At first, I assumed that it might be from the time-calc readout under "Max Time", but when I removed that process in the Max-patch, the same problem remained.
Could you pin-point the cause in your device? If you're not able to create an update, I'd like to see if I can't fix this myself, as this is a device I literally can't live without, including automating the pitch :)
- Max
Note to the author:
I discovered that when the "Time" parameter(s) are automated to change in a sloping fashion (as opposed to instantly), it causes massive CPU spikes / buffer overload. At first, I assumed that it might be from the time-calc readout under "Max Time", but when I removed that process in the Max-patch, the same problem remained.
Could you pin-point the cause in your device? If you're not able to create an update, I'd like to see if I can't fix this myself, as this is a device I literally can't live without, including automating the pitch :)
- Max
Posted on December 14 2021 by drumbliss |
Report Issue
Login to comment on this device.
Browse the full library
That really does sound great on percussion!
Thanks for sharing!!!!