hnewman wrote on Sun, 02 January 2011 22:51 |
Finally demoing this now. Like the sound, but it takes forever to render. Anyone else encounter this? Suggestions? I have not spent much time optimizing Sequoia's CPU handling, but I'm guessing that would not effect the plugin engine anyhow...? |
Macc wrote on Thu, 06 January 2011 14:47 | ||
It certainly takes a lot longer to render with 4x oversampling on. With oversampling off it is much faster, but with the obvious drawbacks. I seem to be preferring either no oversampling or 4x... I don't like the 2x so much. It could be placebo but I hear something different about it... Anyway, like the limiter a lot, though Elephant is still getting used on certain stuff that doesn't get on with Pro-L. |
SafeandSound wrote on Sun, 09 January 2011 12:08 |
...when my primary limiter is not quite working out. |
Andy Krehm wrote on Sat, 01 January 2011 11:20 |
I'm still liking this limiter as much as when I first posted but have discovered a glitch, at least with my processing setup (Mac G5 Dual/PTs 8/RTAS). When I recall a setting, the volume doesn't always go to where it was saved. A mouse click on or near the volume display restores it to where it was saved. This doesn't happen with any of the other saved settings. Anyone else notice this? |
lowland wrote on Thu, 06 January 2011 17:32 |
I notice that on my system when you alt-drag the threshold slider (so the output is correspondingly reduced and you can hear the effect of limiting without a change in loudness) the linkage only seems to work in an upward direction: when you pull the slider down with alt still held the output doesn't go up but stays at the lowest point. I think the two should be linked in both directions, I don't imagine it would be hard to program. |