Login
You're viewing the front-end.social public feed.
  • Aug 17, 2026, 8:20 PM

    @jcsteh Hey there, I have a person here who encounters stuttering with App2clap sometimes. Is there a way to add a sample buffer of sorts that obviously increases latency, but makes sure the audio stream is more stable in case users encounter something like this more frequently?

    💬 1🔄 0⭐ 0

Replies

  • Aug 17, 2026, 9:20 PM

    @ToniBarth Hmm, curious. From memory, there's already a fairly large buffer (several seconds). So you might get glitches while it settles, but it should settle afterward. But clearly that's not happening here. First thing I'd suggest is increasing the buffer/block size in the DAW; e.g. REAPER Device preferences.

    💬 1🔄 0⭐ 0
  • Aug 17, 2026, 9:21 PM

    @jcsteh The Stuttering occurs not while playing back, but while recording. Are you sure the REAPER buffer causes this too? I assumed the glitch was happening before it even reaches REAPER, but obviously I can be wrong.

    💬 1🔄 0⭐ 0
  • Aug 17, 2026, 9:25 PM

    @ToniBarth Adjusting the block size increases the amount of audio that REAPER will pull from the plugin in one hit. From memory (but it's been a while so I might be misremembering), you can't actually change how much audio Windows feeds from the app in each block. WASAPI init allows you to specify a buffer size, but Windows just ignores it for app capture. I commented the code pretty heavily, so I can double check later, just not at my desk at the moment.

    💬 1🔄 0⭐ 0
  • Aug 18, 2026, 11:06 AM

    @ToniBarth Yeah, from my code comments:
    "Contrary to the documentation, IAudioClient::Initialize ignores the buffer duration here and can return a smaller buffer. We provide it anyway, but it can't be relied upon."
    Also:
    "Windows will only buffer 3 packets at a time."
    So we're somewhat limited by Windows here. I've tried to compensate for that by using a large internal buffer and using a background thread if the host buffer size is larger than 3 x the Windows audio buffer size.
    So, the short of it is that changing the host buffer size may or may not help. It's definitely worth a shot.
    App2Clap also has a bunch of debug logging that can be written to stdout, but you have to recompile with the proper dbg macro uncommented; see src/common.h. I can provide a build with that enabled, but you'd still need to get the output from stdout.

    💬 0🔄 0⭐ 0
  • Aug 18, 2026, 8:03 AM
    @ToniBarth @jcsteh I have the same issue specially when capturing from browsers. I don't need capture browsers so much so I don't have exact solution for this.
    💬 0🔄 0⭐ 0
  • 💬 0🔄 0⭐ 0