The New Profiler - Further Feedback and Issues
-
Could the profiler be adapted to measure latency?
-
That seems like a natural and good feature.
-
nope, that's completely out of the scope of the profiler - it doesn't know anything about audio signals.
But I've added a small tool that will send an impulse through the signal chain and measure the delay. It's located at Tools -> Check latency. Just turn down your speakers and click on it, then it will measure the latency with the current sample rate and show a message with the value.
I tested it with a few test-patches (a simple delay or oversampling chains) and for me it works quite OK, but let me know if it chokes on "real-world" projects.
Open to suggestions what to do with the value (like including the samplerate / copy to clipboard or generate the code that sets the latency of the plugin).
-
@Christoph-Hart Cool looking forward to trying this. Some preliminary tests were showing the correct results (48 sample delay with the stock Limiter).
Also I am pretty sure I was using the most up-to-date version of HISE for my original post, but I just updated HISE again and it seems the profiler is compiling now so thanks!
-
@Christoph-Hart said in The New Profiler - Further Feedback and Issues:
Just turn down your speakers and click on it,
This should not be a thing; the tool should absolutely mute HISE's audio output while it's open and doings its thing.
-
@Christoph-Hart That was fast.
I'm confused how is that different from what I asked about? -
@aaronventure it does but I can‘t guarantee that you have a delay somewhere or store the output in a custom buffer so that‘s an additional safety measure. It also says this before it actually puts the impulse in the buffer so you can‘t accidentally zap your ears out.
-
@Christoph-Hart Nice. All of these are good points that I hope no one has to learn by personal experience from.
-
@clevername27 said in The New Profiler - Further Feedback and Issues:
I'm confused how is that different from what I asked about?
It doesn't have anything to do with the profiler, it's just a simple function that inserts a impulse into the buffer and measures the delay to the first non-silent sample.
The profiler measures the time stuff takes on different threads with event dependencies so it's a different beast than that.
-
@Christoph-Hart Thank you.
