rtlsdrblog / rtl-sdr-blog

Modified Osmocom drivers with enhancements for RTL-SDR Blog V3 and V4 units.
https://www.rtl-sdr.com
GNU General Public License v2.0
291 stars 44 forks source link

RTL-SDR-BLOG Windows Release V1.1 and 1.2 have some small lags issues in SDR# with AMD CPUs #20

Closed MELERIX closed 1 year ago

MELERIX commented 1 year ago

RTL-SDR-BLOG Windows Release V1.1 have some small lags issues in SDR#, for example when you move the Gain RF sometimes the changes are not applied instantly or sometimes when you change frequencies fastly the spectrum does not change instantly.

rtlsdrblog commented 1 year ago

Is this only with the blog driver, or does it happen with the standard osmocom drivers too?

MELERIX commented 1 year ago

yes, the issue happens with both, and only in the Keenerds driver this issues does not occur.

rtlsdrblog commented 1 year ago

What PC, OS and specs do you have? I don't see this issue at all on any PC I have unfortunately.

MELERIX commented 1 year ago

CPU is AMD RYZEN 5700G, and OS is Windows 10 22H2, I'll try to Made a video of the issue later and also I'll try to check in other PC with Intel CPU to check if the issue persist.

MELERIX commented 1 year ago

ok, here is a video of the issue (sorry my english): https://www.youtube.com/watch?v=wdGxMu_dYC0

btw, I've tested in an Intel CPU i5-3230M and the issue does not ocur.

so seems that only happens with AMD CPUs.

rtlsdrblog commented 1 year ago

I wonder if it's something to do with newer versions of libusb and because keenerds code is very old, and built against an ancient version of libusb.

Can you try with this rtlsdr.dll? I compiled this one with v1.0.20 of libusb which should be around the version keenerd was using in 2016.

Release.zip

rtlsdrblog commented 1 year ago

Also if you haven't already, try updating your motherboard bios. This might be related to the AMD Ryzen issues a lot of people were having in the past.

https://www.reddit.com/r/RTLSDR/comments/u17n00/amd_ryzen_usb_problems_still_there/ https://www.reddit.com/r/Amd/comments/m2wqkf/updated_agesa_coming_for_intermittent_usb/

And try other USB ports:

https://www.reddit.com/r/SSBM/comments/hf41fw/solving_dropped_inputschoppy_movement_on_amd/

MELERIX commented 1 year ago

I wonder if it's something to do with newer versions of libusb and because keenerds code is very old, and built against an ancient version of libusb.

Can you try with this rtlsdr.dll? I compiled this one with v1.0.20 of libusb which should be around the version keenerd was using in 2016.

Release.zip

ok, I've tested that version and sadly the issue is still present :(

MELERIX commented 1 year ago

Also if you haven't already, try updating your motherboard bios. This might be related to the AMD Ryzen issues a lot of people were having in the past.

https://www.reddit.com/r/RTLSDR/comments/u17n00/amd_ryzen_usb_problems_still_there/ https://www.reddit.com/r/Amd/comments/m2wqkf/updated_agesa_coming_for_intermittent_usb/

And try other USB ports:

https://www.reddit.com/r/SSBM/comments/hf41fw/solving_dropped_inputschoppy_movement_on_amd/

btw, the BIOS of my mainboard is already updated with the most recent version and also the chipset driver too, I don't have issues with USB ports at all.

also I've tested with different USB ports (even different gens 2.0, 3.1 and 3.2) and nothing changes, the issue persist.

but I'm guessing that maybe the bug is not in the libusb, maybe is related with few changes that are present in Keenerd driver that fix the issue but that are not present in the osmocom/rtl-sdr blog driver.

rtlsdrblog commented 1 year ago

How about this one? This one I copied the way Keenerd doesn't turn off the i2c repeater in set_center_freq and rtlsdr_set_tuner_gain

Release.zip

MELERIX commented 1 year ago

How about this one? This one I copied the way Keenerd doesn't turn off the i2c repeater in set_center_freq and rtlsdr_set_tuner_gain

Release.zip

good news! that one fixes the issue :D

rtlsdrblog commented 1 year ago

Excellent, will put out a new Windows dll release next week with this fix.