CHIRP

After loading random images from many different radios into today's CHIRP-next build (20230619), common images with 256 memories or less appear to load virtually instantly. Even an image with 2 banks of 500 channels (BTECH_UV-50X3) loads all 1000 memories in under 3 seconds. All seems normal to me.

If all you are doing is asking a question, it would have been more appropriate and seen by more eyes is asked in one of the CHIRP mailing lists. If you is to reporting a bug, then you should provide details that show/explain why you think loading times are slow. For example, load up a CHIRP build from a week ago to measure and compare the load times between last weeks build and the current one.

Jim KC9HI

It used to be almost instant last week. Now, it takes 7-8 seconds to load. Not horrible, but not the same. It feels like longer.
I suppose I could uninstall, then check, and then go install the latest. By the way, today's build did not seem any faster than yesterday's.
:-/

Instantaneous for me as well on all three platforms, using a radio with >1000 memories. Nothing has changed in the last couple weeks that could account for a change, that I can think of.

As Jim noted, just saying "feels slow" doesn't give us much to go on. You say "all models affected" but I'm sure you haven't tested all of them. Please attach an image that loads slowly for you so someone else can verify with the same image, same driver, same version.

Doug Nelson wrote in #note-2:

It used to be almost instant last week. Now, it takes 7-8 seconds to load. Not horrible, but not the same. It feels like longer.
I suppose I could uninstall, then check, and then go install the latest. By the way, today's build did not seem any faster than yesterday's.
:-/

I'll bet that after you install a build from last week, or even last month, they are also slow (which would indicate this is something to do with your computer and has nothing to do with CHIRP).

Jim KC9HI

This issue seems to have cleared up. Not sure if it is a newer version of Chirp, or an unrelated issue. Reboot OS might have helped also. Anyways, this bug can be closed. Thank you.

I don't know how to close a bug, but this one works for me now. I have some other open bugs which might also need attention.
Thank you.