Rome wrote:
Hi everyone again.
To answer several posts in one:
1. We'll try to release it before the ARRL DX CW contest? (19 Feb), at least share it with testers.
2. Adapting new firmware for ESDR2 may take a month or even more, at this point it's a waste of time.
3. As far as I know ESDR3 works way faster than ESDR2 and requires fewer CPU resources.
So the issue described by Bob KD8CGH might be in the API used for ESDR3 display or overall CPU load with other third-party software.
It's not normal and should be addressed closer to the release of ESDR3 1.0.
As far as third party and other apps running, I have done several videos of V3 there posted on YouTube and a few within the EESDR site as well
As far as apps and third-party software running when doing most of those videos included SDC, a logger (LogHX 5M contest, Swiss log, Log4OM or AClog) my Outlook email a web browser and at times those alongside a digital mode and more importantly OBS studio have been running on the same PC and with 2 or 3 monitors. Using Vulkan I see a slightly less resource loading and a better overall framerate compared to DX11. DX12 may prove better then DX11 but at this point it hasn't been implemented yet in V3. in any of those videos I never had a lagging experience in V3 when showing adjustments or going over settings and using the rig.
I also have use NVidia Graphics card an older 1050Ti have not experienced that- Curious as to which Graphic card Bob is running? and what driver
One thing I have noticed is the Studio drivers for NVidia are less resource intensive then the gamming driver (Go Figure).
Also performing a CLEAN DRIVER install may fix that issue- NVidia Drivers and updates are horrible!