Wellington Wallace
Wellington Wallace
>If the activity timeout should shut down activity after e.g. 10s, I guess deep noise remove got an issue here... More likely PipeWire. We do not control the link state....
>Would help to be able to force spectrogram/meters to be in sync with what's physically being played at the end of the pipeline The spectrum is at the end of...
> Thanks for analysis, understandable. Still a fully manual knob might possibly make sense? something like passing the snapshots of (spectrum fft info) through a queue of N items, and...
>It seems to me that a simple "delay line" type of knob would be sufficient. I think it is not so simple. But if it is this can be tested...
>obviously, this is kind of niche and only important for users doing live sound monitoring, but of course it's nice to have Not necessarily niche. But it is hard to...
> I didn't think easyeffects supported automatic latency compensation. PipeWire does it for us. Imagine the video playback compensation you explained above. Until a few months ago having EasyEffects in...
>Unless the plugins are somehow able to do this transparently from within the wrapper, Each plugin port receives that latency offset PipeWire uses for compensation. We just have to add...
>The problem is that the output audio is inherently delayed, at a hardware level: pipewire would have to be able to time-travel and apply a negative delay in order for...
>I think another way to explain it is to think of the spectrum as another video player, that needs to be synced with the source video player and the audio...
The question now is the best way to add this delay. The current implementation relies on https://github.com/wwmm/easyeffects/blob/620fa1436a0c7eeda346e16236a2c8a60da5bcb0/src/effects_box.cpp#L450C3-L450C31 for the drawing scheduling. It does not seem `gtk_widget_add_tick_callback` is going to play...