alligatorlizard
Active Member
There's obviously no right or wrong answer here, but as it's the first string library I've used that has this option, just curious what other users find works best.
Short version of the question:
Does anyone else also find that Areia works best with the dynamic range knob at 0%, and if so have you run into any problems aligning with other libraries dynamic ranges, or felt this restricts the contrast in dynamics too much throughout a piece?
More details/thoughts, if you're interested:
So far I've always just left the dynamic range knob on default (50%) setting - which works fine, and as all sample libraries have different dynamic ranges anyway, I'm accustomed to automating cubase faders (and/or cc7/11) to keep good relative levels at different dynamics. This can get time consuming though... and while I've given up trying to get a template where everything remains perfectly levelled at all dynamics, I still like to get as close as possible to at least minimise the amount of level-automation I have to do e.g. between an f passage and a p passage.
Playing around with the Dynamic Range knob though, I found Areia actually becomes much more "playable" set at zero (which according to the manual is the original dynamic range it was recorded at) - riding the mod wheel to add expression feels/sounds far more natural, and I'm more likely to use lower dynamics (hence more timbral variation) as the volume doesn't drop so dramatically lower down the mod-wheel range.
However, as stated above, am conscious of how this may not line up with dynamic ranges of other libraries. e.g. HS, which has a fixed dynamic range (other than adjusting the input curve, which isn't really the same thing), gets a lot quieter at low mod wheel values than Areia with dynamic range set at zero. I did experiment with setting Areia's dynamic range knob to match up with HS's dynamic range, but there's no one setting that works across the whole range - and obviously once I start trying to match dynamic ranges with various brass/wind/perc/etc. libraries (some of which also have dynamic range control - e.g. Cinebrass and Berlin WW - but most which don't), variables increase even more... So I've ruled out trying to set it in any sort of "scientific" way - level automation across dynamic ranges with multiple libraries is unavoidable it seems!
I suppose the best approach is probably to decide which is the "dominant" library in a composition then adjust other things around this - e.g. if strings are used throughout, set Areia's dynamic range knob to whatever is preferred, leave it's volume level untouched throughout so it dictates the "base level" at any given dynamic, then adjust other instruments level's as needed throughout the piece. Even set at zero, I feel there's plenty of difference in level between dynamics, so I don't think this would result in too little contrast between loud and soft passages, or detract from e.g. dramatic ppp to fff crescendos. But I'm also wondering if there's a good reason it's set at 50% as default? Will obviously have to experiment, but if anyone's got any tips/pointers here, much appreciated!
Short version of the question:
Does anyone else also find that Areia works best with the dynamic range knob at 0%, and if so have you run into any problems aligning with other libraries dynamic ranges, or felt this restricts the contrast in dynamics too much throughout a piece?
More details/thoughts, if you're interested:
So far I've always just left the dynamic range knob on default (50%) setting - which works fine, and as all sample libraries have different dynamic ranges anyway, I'm accustomed to automating cubase faders (and/or cc7/11) to keep good relative levels at different dynamics. This can get time consuming though... and while I've given up trying to get a template where everything remains perfectly levelled at all dynamics, I still like to get as close as possible to at least minimise the amount of level-automation I have to do e.g. between an f passage and a p passage.
Playing around with the Dynamic Range knob though, I found Areia actually becomes much more "playable" set at zero (which according to the manual is the original dynamic range it was recorded at) - riding the mod wheel to add expression feels/sounds far more natural, and I'm more likely to use lower dynamics (hence more timbral variation) as the volume doesn't drop so dramatically lower down the mod-wheel range.
However, as stated above, am conscious of how this may not line up with dynamic ranges of other libraries. e.g. HS, which has a fixed dynamic range (other than adjusting the input curve, which isn't really the same thing), gets a lot quieter at low mod wheel values than Areia with dynamic range set at zero. I did experiment with setting Areia's dynamic range knob to match up with HS's dynamic range, but there's no one setting that works across the whole range - and obviously once I start trying to match dynamic ranges with various brass/wind/perc/etc. libraries (some of which also have dynamic range control - e.g. Cinebrass and Berlin WW - but most which don't), variables increase even more... So I've ruled out trying to set it in any sort of "scientific" way - level automation across dynamic ranges with multiple libraries is unavoidable it seems!
I suppose the best approach is probably to decide which is the "dominant" library in a composition then adjust other things around this - e.g. if strings are used throughout, set Areia's dynamic range knob to whatever is preferred, leave it's volume level untouched throughout so it dictates the "base level" at any given dynamic, then adjust other instruments level's as needed throughout the piece. Even set at zero, I feel there's plenty of difference in level between dynamics, so I don't think this would result in too little contrast between loud and soft passages, or detract from e.g. dramatic ppp to fff crescendos. But I'm also wondering if there's a good reason it's set at 50% as default? Will obviously have to experiment, but if anyone's got any tips/pointers here, much appreciated!