MSF content & licensing

[jmalge]

But question: cannot be reported in an instrument, or cannot be reported in this instrument (MSF)?

VPS Avenger e.g. reports its latency to the host and it can do this in several ways (none, dynamic, fixed). The problem is specific to MSF.

Okay, well, I'm not sure what Dynamic does, and there's no mention of it in the latest manual, but if it calculates then reports actual latency, then I'm not sure what the point of any of the other modes would be. I've owned VPS Avenger since the day it came out and I've never had to fiddle with the global latency comp mode. I still have it on the default "None" mode.

For the other methods, "None" is what MSF does (right?).

And for the 5,10, and 15ms "fixed" options, seems to me you should be able to do one of at least three things:

1. Put the Utility module in the FX section, go to the Delay section, set the delay as desired, and check "Report as latency".
2. If that doesn't work for some reason, then try putting MXXX or MXXX1 in the FX section, drop the MXXX version of Utility in there, and do the same thing.
3. If none of that works, put MUtility (it's free so you can have it regardless) as an insert after MSF and report your latency there.

Assuming methods 1 or 2 work (I honestly haven't tried, never had a patch show enough latency to need this), then it would presumably be the responsibility of the sound designer to measure the latency and report it from the utility module for each preset that has enough latency to warrant all of this fiddliness.

[XxEDxX]

None is what MSF does, right.

Dynamic mode calculates and reports the latency whenever it changes (e.g. the use of a lookahead compressor in one of the chains). But there may be hosts that have problems with dynamic latency reporting. Though I don't know any of the major ones. Thats were the fixed ones come in handy. It reports a fixed latency to the host but compensates internally depending on what effects you've used. Like your effect have 4ms latency, but your fixed is 5ms, it internally adds 1ms to the signal such that it aligns perfectly.

[Nspace]

XxEDxX
At the other KVR's MFS thread (out of Melda forum, located at Instruments section) called "FYI!! Melda SoundFactory ON SALE NOW",
There are varied ideas an opinions coming from diverse un/interested curious enough posters. jmalge, wrote a very interesting post though shows an apparently complex situation to deal with. Let me paste it here, despite being off topic;

...And the instrument cannot compensate for it...

And :

...Note that the plugin cannot report it to the host, long story...

Interesting, though I wonder why. This is a clear design issue and both are only limitations to MSoundFactory. This has nothing to do with general technical difficulties, as other synths are able to report their latency.

I don't know why either, but I do know it's not hard to set up MSF to produce multiple different latencies in parallel. It's also possible to make those latencies change via modulation (e.g. you can trivially enable/disable a spectral domain effect with a MultiParameter).

So, if I had to guess, I'd say we have an instrument that would have to continuously re-compute and re-report multiple simultaneous latencies to a host that probably can't deal with multiple simultaneous latencies from a single source in the first place.

[XxEDxX]

Thank you. I guess the lanes have to be compensated internally already, else there would be an offset between different oscillators, or am I misunderstanding something? I guess it then would be the best to have a certain fixed latency reported to the host and compensating for it internally. How does that work in MXXX? It's a similar situation there I guess.

[MeldaProduction]

Still the latency? I'll remove all the modules and that's it!

No... Anyways I can actually enable the latency compensation, but that would defeat the purpose. Now you can for example take a pad sound, and on a secondary lane put some spectral delay, which will be delayed, but since it is a delay on a pad, it won't really matter that much... With the compensation enabled if would mean everything will be delayed, period... So not a good idea.

[Gone soft]

Isn't it possible to make latency compensation an option, with a little warning? I know I'd like latency compensation in some situations while it would matter less in others.

[jmg8]

Isn't it possible to make latency compensation an option, with a little warning? I know I'd like latency compensation in some situations while it would matter less in others.

Completely agree with this. Option would be great.

[MeldaProduction]

It's actually rather difficult, but I'll check... Oh well, jmg8, next time you try to persuade me to nonsense like including modules latency, I'll tell you to... you know

[jmg8]

Haha, don't blame me! There were already latency inducing modules before you added the ones I requested

[MeldaProduction]

True, but you made me add more , for instance the Unison FX is yours

[Nspace]

Haha, don't blame me! There were already latency inducing modules before you added the ones I requested

True, but you made me add more , for instance the Unison FX is yours

And because of this influence, and the efforts from developers and device designers commented exchange, together with the community in this Melda forum, include also those opinionated posts at the sometimes dramatic "FYI MFS" thread at KVRaudio's Instruments forum, also including the well behaved Gearslutz MFS thread...

//ALL of us will be at some point to blame/thank for this incredible tool being the flexible, powerful and unique audio tool is actually becoming.
Of course, respect where respect is due.
( for the focused but deep happiness those OPTIONS bring)

[MeldaProduction]

Hehe yeah