Since I've updated Nebula 3 trim mode (OSX), the FRT arrow is blinking, even when I change the dspbuffer value at higher rates.. I changed to 2048, save it, then reload but nothing changed. Put it tho the max, same thing.
I've also made a copy of my previous nebula folder. Tried it, same issue.
Then I've reinstalled the 1.3.475 version, nothing changed with the FRT conversion..Always blinking even tough I've saved it & closed it.
It would be awesome if you could just CMD click/drag the input knob and have it reverse control the output (i.e. trim balance the input/output). This way developers would have to reissue their libraries.
no, this new implementation adds something which was not existing before. You'll find a replacement for DRIVE control named GDRIVE, which behaves like a "real" drive knob. Presets are more accurate, due to a cleaner implementation of the preset inside the vectorial engine. The single developer could choose the amount of GDRIVE, which is far greater than +6dB actually allowed by input/output knob (it could be tuned till -100..+100dB range). So great precision, clean implementation, it doesn't affect other modules because trim is BEFORE the input knob and AFTER the output knob.
why can`t we have both knobs working? drive and trim? most of the programs have still 4 or 5 knobs without any function.. i know it`s different mode and so on.. but it doesn`t seem to be very scientific to make a input/output linked function availible in both modes no?