Lol- there is no hyperbole(as you put it.) and yes,i may be doing things you never have before... so..yeah w/e.selig wrote:I honestly have no idea what you're talking about here, as I've found the VGM-01 to be incredibly useful - there is literally no other way to accomplish what it can do in Reason! Either you're exaggerating for effect, or you're doing things I've never heard of doing before (wouldn't be the first time for either!).
Maybe you could back off the hyperbole for a bit and explain what it is you're trying to do when you run into this issue?
The VMG is 1 of the most convoluted units i've come across in practice.
It gives inconsistant results even if following developers instructions of use,and them results are only taking a static measurement after insertion.
It by definition will "respond to specific DB values" and them DB values are within a very limited range- -14/-20db is'nt it?
How is your 'average user' going to know what DB a certain unit puts out?
This is REason,not rocket science m8.
Another convoluted response normen..normen wrote:In practice I'd suggest putting the change in latency exactly where you enable that other plugin in the chain you compensate for..
TBTH- that unit will not solve problems that is obviously an issue within the programme itself.If it does not respond in a 'dynamic updated way' what's the point of using it?,if certain parameters change latency values.Eh?
Then your 'knowledge' is also incomplete young man.normen wrote:no plugin I know of has variable processing latency.
I did not come here to argue,just made some observations that others may be overlooking..?
Good day to you.
Rating=0.1