Patrick

Using the latest urjtag compiled from the 2021 tarfile in the repo, I'm trying to connect to the flash on an OMAP-L138 processor board. I have the BSDL file properly loaded, but trying to initialize a prototype bus using the pin names from the BSDL file is failing: jtag> initbus prototype amsb=EMAA23_MMCSD0CLK_GP47 alsb=EMAA0_GP50 dmsb=EMAD15_GP37 dlsb=EMAD0_GP48 ncs=EMACS2n_GP315 nwe=EMAWEn_GP311 noe=EMAOEn_GP310 error: invalid parameter: parameter we=<signal> or nwe=<signal> is not defined I get...

I think I might've figured it out. However I can't verify if this was the root issue or not. I tried installing Viper4Windows just as a test. It also didn't work, as expected. However, when running the program it asked to install a Visual C++ Redistributable which I did. Not sure if that has anything to do with the beloew results though. Read on... I unistalled Viper4Windows and reinstalled Equalizer APO. However, this time instead of opening my previous config file (named room.txt) I tried editing...

I think I might've figured it out. However I can't verify if this was the root issue or not. I tried installing Viper4Windows just as a test. It also didn't work, as expected. I unistalled that and reinstalled Equalizer APO. However, this time instead of opening my previous config file (named room.txt) I tried editing the default config.txt file. And, it actually worked! Things were changing on the output of my UMC202 as expected. So, I copied over all the parametric EQ settings from the room.txt...

This looks normal to me. I don't see any glaring errors. This was from a reboot, after reinstalling the APO on my devices. Still no effect to either of them. 2020-05-05 19:04:10.834 10540 108B5290 (EqualizerAPO.cpp:100): (TRACE) Initialize 2020-05-05 19:04:10.834 10540 108B5290 (EqualizerAPO.cpp:115): (TRACE) APO GUID: {EACD2258-FCAC-4FF4-B36D-419E924A6D79} 2020-05-05 19:04:10.834 10540 108B5290 (EqualizerAPO.cpp:132): (TRACE) Endpoint GUID: {BF33A1F0-9A3B-4A79-84DC-E18F34467C5D} 2020-05-05 19:04:10.837...

No luck. Installed latest windows updates, completely uninstalled EqAPO, reinstalled UMC202 drivers, and still no effect on either device. Is there any type of debugging that can be done to see what's failing? It's obvious something in the Configurator isn't setting up the APO properly as neither device seems to be able to accept it. This would imply to me that Windows has introduced a new change to the way audio devices handle APO, or there's something else obvious that I'm missing.

Hi Peter, thanks for taking the time to help. No, I'm not using an insider build. I do have some pending windows updates however, including some "important" ones, so I suppose that's another thing to try. In the meantime, more about my current APO woes. Equalizer APO does not work on the onboard realtek chipset either. It's currently enabled on both. When installing Equalizer APO, I've tried both the LFX/GFX and SFX/EFX options and neither one worked. I've also triple-checked that "disable enhancements"...

I've been tearing my hair out all evening trying to get APO to work on a brand new, fresh install of Windows 10. Using both the onboard Realtek audio chipset and an external Behringer UMC202HD interface, Equalizer APO has no effect. I've tried every available driver version for both soundcards, reinstalled APO multiple times, and tried the various modes available in the troubleshooting section of the configurator. Rebooted probably 30 or so times by now. And yes, I've even made sure that "disable...