Jump to content

bazolo

Members
  • Content Count

    4
  • Joined

  • Last visited

Community Reputation

0 Neutral

About bazolo

  • Rank
    Just Startin'
  1. 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).
  2. 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
  3. Re-released on 6/11/19 fixed version 4.2.7.7 of the driver works ok.
  4. 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).
×