05-28-2021, 04:46 AM
(05-27-2021, 09:14 PM)Qiel Wrote:(05-27-2021, 07:46 AM)Shannon Wrote: The initial value I calculate turns out to be the best starting point. For some people, that's all they need, and for others the autoconfig will lead them to more loops, days on, whatever. The way I determine it is to query what produces the best long term happiness balance between myself and my customers. So before things were as complex as they were, it was a fixed value, and over time I realized that a fixed value, no matter how accurate, would always have outliers if the target demographic was big enough. So I created the autoconfig module for those people who need a different value. Over time, I have seen that the models typically introduce the program at a safe usage pattern that may be less than what some need, but it is what will work best for the majority. Between that and autoconfig, everyone gets where they are going with the highest likelihood of success.
Measuring the power level isn't done by usage patterns. There are certain variables in the script and in the Platinum Lake configuration protocol that determine power level. It is by observing those that I can get a good idea of what's happening with power levels.
In other words, did you said that starting 5.75.7G, the ASRB2 are the basic starting point and after some cycle, it's up to the user how to expose themself with the subs. Is that right?
Not quite.
The calculated values will work just fine for most people. But if they don't, after a couple of cycles you'll be able to tell and you'll be able to make adjustments. That doesn't mean everyone should make adjustments. It is the starting point because most people will find that is the best setting. But it's a bell curve, and some will need something else.
If you find that at the end of two cycles you're not getting results, or your results aren't as good as they should be, you need to make adjustments. If that is the case, then feel free to start adjusting ONE variable at a time, ONE notch at a time, ONE per ASRB2 cycle until you find your solution. The autoconfig will usually guide you. But for example, if you decide that the variable you want to adjust is days off, then you might go from 1 loop, 2 days on, 3 days off to start with OFv3 to a setting of 1 loop per day on, 2 days on and 2 days off. 3 days off one notch difference would be 2 or 4, and if you want more impact, you increase exposure, so you would have to increase loops, volume or decrease days off. So in this case, we would decrease days off my one notch to 2.
Generally, days off is going to be the best bet for initial adjustment if you need to make adjustments. The goal is to find the sweet spot where you're getting the right amount of exposure to execute. If the current settings work, then leave them alone.
Subliminal Audio Specialist & Administrator
The scientist has a question to find an answer for. The pseudo-scientist has an answer to find a question for. ~ "Failure is the path of least persistence." - Chinese Fortune Cookie ~ Logic left. Emotion right. But thinking, straight ahead. ~ Sperate supra omnia in valorem. (The value of trust is above all else.) ~ Meowsomeness!
The scientist has a question to find an answer for. The pseudo-scientist has an answer to find a question for. ~ "Failure is the path of least persistence." - Chinese Fortune Cookie ~ Logic left. Emotion right. But thinking, straight ahead. ~ Sperate supra omnia in valorem. (The value of trust is above all else.) ~ Meowsomeness!