[solved] manual shortcut in app not working (yet)

Yeah, the link points to an empty page for now, we still have to write the bloody thing! :)

Thank you for noticing it though and have fun testing!

Hello,
and what about the manual-folder in the programms directory?

It's empty, too.

Actually there will be only one user manual, and depending on whether you checked the "manual" component in the installer or not, the manual will be copied to the local disk or not. Then the link in the help menu automatically detects if there is a local version of the manual and opens it, otherwise it opens the online one.

So both are empty for now, until we write the damn thing!

when writing the manual please consider to make/show a sample patch or screenshot for each module and how it has to be connected. For now I don't know how to make the latency report and the stress tool work properly.

thanks a lot.

The stress tool is not really useful, it's a very crude system test utility module. You don't have to connect it, once it is inserted in a patch it will be powered and enabled automatically (same for all modules that don't have audio I/O pins in patcher)

Latency report is used in very particular cases in order to manually correct or adjust the patch latency compensation (which by default is fully automatic, so in most cases you don't have to care about it)

The first scenario that comes to mind is: consider the following connection scheme, where audio is generated by RP, it goes to the soundcard output, then to an external multi effect rack unit (or any external gear) then back into RP via the soundcard input. In this case if you want the audio from the patch to be aligned with the audio that did the round-trip, you would have to disable automatic PDC, and insert this module after the master inputs in order to report the effective latency (mostly as a convenience or visual aid). Then the actual alignment would be done with the "Manual Delay-Compensation" module... but this is already a quite complicated scenario!

But basically this module report to the engine that is has a latency but without touching the signal that goes through it. The manual DC reports a latency *and* delays the signal by the same amount, while the 3rd one (Non-Compensated Delay) just delays the signal but without reporting any latency.