CHIRP

What you're seeing is what Yaesu calls "masking". On a yaesu (or at least, most of them), when you delete a memory the radio just marks it as deleted but does not actually erase what was there. In chirp legacy, it supported showing these as greyed out (or "ghosted" as you say). Old chirp also had some ability to do full deletes (which isn't what the radio does) but it was very yaesu-specific and not technically kosher. New chirp doesn't support that, and just shows those memories as deleted like the radio does and that's why you see the difference.

So with that explanation, I think we can close this as not a bug?

Thanks Dan. Is there a way in CHIRP-next to make sure those masked memories don't show up in memory banks? That was how I noticed the issue in the first place.

But at least for the moment, it sounds like the best solution for VX-6R owners is, use CHIRP-legacy.

Oh I missed that part. You're saying that the deleted channels still show up in bank view on the radio, even though they're gone from the regular memory view?

If so, that was also a bug in chirp-legacy, just unintentional and maybe work-around-able by doing the full delete-after-mask... maybe? If you confirm, I'll try to look at that, but I have neither of those radios so I'll definitely need you to test a solution.

Hi Dan: That's correct. On the VX-6R, using an image generated with CHIPR-next, deleted/masked channels still show up in bank view on the radio. (Don't worry about the FT-60R; user error on my part, CHIRP-next is working fine with that radio.)

I'd be happy to test a solution if you can come up with one.