Because latency always is an issue - especially in live situations - it is important to know how much latency is added by which element.
It would be cool if there was a switch to enable monitoring the accumulated latency per module in the modular view.
So there could be two modes: one shows the full latency at the given module (accumulated, including the latency of all other following modules in the chain). An the second one just tells the latency that each module add on its own. Color coding could help to quicky see the impact of each module. Green = 0ms, yellow = 1..5 ms, orange = 6..20 ms, red = 21..n ms. These ranges should be editable.
The value for latency could be a little text box with the latency value in ms at a corner of the module.
Would be wonderful!
FR: Display accumulated latency in the modular view for every module
-
- KVRAF
- 3154 posts since 28 Mar, 2008 from a Galaxy S7 far far away
-
- KVRAF
- 13862 posts since 24 Jun, 2008 from Europe
Quick tip: Right-click any module -> Info.
This info pane includes the input latency, process latency and output latency for that module.
This info pane includes the input latency, process latency and output latency for that module.
-
- KVRist
- Topic Starter
- 164 posts since 27 Sep, 2004
That's nice 
Eventually you could still allow a direct display of any of these values directly at the module and for all modules at once. With additional color coding this quickly gives an overview where the drivers for the overall latency are. Because you might want to reduce latency and don't know where it comes from. Having a direct visualisation (as a mode that can be enabled and disabled) will help to sort out the culprits.
Eventually you could still allow a direct display of any of these values directly at the module and for all modules at once. With additional color coding this quickly gives an overview where the drivers for the overall latency are. Because you might want to reduce latency and don't know where it comes from. Having a direct visualisation (as a mode that can be enabled and disabled) will help to sort out the culprits.
-
- KVRAF
- 13862 posts since 24 Jun, 2008 from Europe
Surely good ideas.
Pls also read this: viewtopic.php?t=357048
Another quick tip: You can assign a shortcut key to that "Info" function, that way it's much faster to inspect the latencies of a module.
Pls also read this: viewtopic.php?t=357048
Another quick tip: You can assign a shortcut key to that "Info" function, that way it's much faster to inspect the latencies of a module.
-
- KVRAF
- 3154 posts since 28 Mar, 2008 from a Galaxy S7 far far away
Hi Jo, maybe instead of this:
Add this to your signature:Pls also read this: viewtopic.php?t=357048
It may save you repeating this over and over again
-
- KVRAF
- 13862 posts since 24 Jun, 2008 from Europe
-
- KVRAF
- 3154 posts since 28 Mar, 2008 from a Galaxy S7 far far away
