bazolo

Hi guys. Try to use the LatencyMon app ( https://www.resplendence.com/latencymon ) LatencyMon checks if a system running Windows is suitable for processing real-time audio and other tasks. LatencyMon analyzes the possible causes of buffer underruns by measuring kernel timer latencies and reporting DPC and ISR excecution times as well as hard pagefaults. It will provide a comprehensible report and find the kernel modules and processes responsible for causing audio latencies which result in drop outs. It also provides the functionality of an ISR monitor, DPC monitor and a hard pagefault monitor. LatencyMon will display the highest latencies of a kernel timer and report the highest execution times of ISR and DPC routines as well as hard pagefaults. In most cases it will also find the drivers and processes responsible for executing them. It will create a comprehensible report which also displays all sampled data in a detailed manner allowing you to perform in-depth analysis.

Exactly. That's why I say that this function, acting in this way, is slightly senseless. In my opinion, this function should silence listening monitors ONLY when at least one of the activated input sources is a mic. It would have 2 real advantages: - automatic feedback protection (not only when recording where the user behaves cautiously, but also when the source is switched to a mic accidentally resulting in a loud explosion) - it would eliminate the need for continuous manual adjustment of the speakers volume when switching between the signal sources (mic <-> instrument / line).

I don't know if this is the software bug or intended functionality, but when the "Mute Mains for Mic Record" (POD Farm->Preferences->Hardware) option is activated, listening monitors are muted - not just for the Mics (sensible feedback protection) but for instruments/line inputs also (for what?). I think the instruments/line inputs should not be muted. tested on: OS: Windows 7 SP1 x64 audio: UX2 (driver: 4.2.7.7, USB firmware: 1.02, POD Farm: 2.59) hardware: Xeon W3690, 48GB RAM

Re-released on 6/11/19 fixed version 4.2.7.7 of the driver works ok.

I got the same with UX2 and 4.2.7.7 in Win7x64. (4.2.7.6 I uninstalled first). Additionally, the ASIO Client column in these settings always shows "(none)" and this with the active DAW (in my case Studio One and Reaper).