ah ok! that certainly explains things. also ty for LD manual link.
the issue im noticing is that the dld isn’t saving very slow ping times in the patch. we need those slow ping times to access up to the 87sec limit. it seems to save up to around 1.75sec ping time (i.e. ping button flashes every 1.75s) which gives only about 56 seconds delay (w time knob at 100%, switch at +16).
so for example: i create a new vcv patch with dld, and manually click the ping button very slowly, i can then access up to that 87sec delay time. but when i save the .yml and load it on the mm, it reverts back to that 1.75sec max ping button time so i lose access to the 87sec delay time. this is also the case if i reload the .vcv file- the ping button no longer flashes slowly but instead flashes around 1.75s. is this correct behavior or perhaps a bug?
or most likely im just not doing something correctly…
sounds good! looking forward to this CPU > 100% feature. i think using the delay heavily in a performance situation, often is useful to kill the delay buffer quickly to start filling it in again to keep things moving sonically. as opposed to pulling the fdbk all the way down and having to potentially wait up to 87sec
that would certainly be useful- for many creative and live situations.
perfect, great idea- thank you for mentioning!