Mimi wrote:A question, the hardware , the atack goes from 400ms until 1 second, in Program nebula, the atack is 0 until 8.00 , is the same sampling with only a change of number? Exemple: 0 = 400ms and 8.00 = 1 second It is this thought or am I wrong?
Like the release the hardware doesn't deal in time as we are used to. The hardware attack goes from 400 dB per ms to 1 dB per ms So that translated into duration = Attack time 600µs - 12ms Release = 2ms - 800ms
The sampled programs cover the entire range. Atk 0=600us 8=12ms Rel 0=2ms 8=800ms
The true times have been sampled but with most setups nebula wont create anything faster then 2-5ms. Lucky the times faster then that are rarely used musically. But as nebula grows who knows what will be available.
If your bored here is a great review going over the technical aspects. 3rd link deals with durations.
this is great, you got to sample the signs of attack, and was very good, compared to hardware, I would like to know your opinion, not only from your library, more of nebula, and their current control of the atack, I liked very good, but would like your opinion, and learn more about future projects for their compressors, which incidentally, you did wonderfully. nebula in the attack is already trusted? Many people think that attack is fixed and that this dynamic would not be very good, and you with their work showed opposite... The atack in your compressor works well.
just downloaded the 4:1 program. sounds very good BUT there are small clicks/ticks happening normally at the same places (not always with the same level of loudness) BUT if you play-stop-play a short passage about 5 times one of the trials is totally free of these clicks. huh!?
edit: what i've done exactly is inserting the preset into a vocal track, lowering the attack and the threshold a bit. click tick voilà... only lowering the attack also makes it click but not so often, more like 1 out of 2
There is a really There is a click, small, like vinyl slightly lower, even though my machine is fast, modified the Frenqd time, for 25ms, and not worked it seems that is the behavior of attack, I have the previous library and I made the comparison, the clicks not there, I think it changes very fast attack, nebula leads to not understanding, maybe if instead of sampling of all degrees of attack, if could be sampled again attack, with the 5 points of atack, instead of the whole arc of atack, or redo the whole arch with all variants in nat3. Exemple : value: 1 / 5 / 10 /15 /20 /25 /30 /35 /40 /45 Or the five fundamental, 1/ 5 / 10 / 15 / 20 may be possible to do this, is only an idea.
This is when it gets difficult. Tuning Nebula for a need/setup seems to be system dependent. My 3 daws hosts all perform differently with Nebula. Increase your GLOB/Rate. It's a balance between the fastest refresh time a system can handle & smooth playback. This is the appeal with creating fixed rate presets. You can dumb them down for the worst cases scenario. FYI - Please email me directly for support. Do to time I can't always be monitoring forums so activity.
eric is there a global fix for the clicks coming or do we all need to tune it ourselves? i'd prefer the first variant because i'm sure i'm not the only one and as you can see it's not on some antique system either.