G'day Dan,

What features and behaviors does the chirp editor need to have to make it equally or more useful than taking it out into excel and back?

As I think you know, I currently produce a bunch of configuration files for just about all of the Australian D-STAR 2m and 70cm repeaters. By exporting the memory information from my primary configuration file to csv format I can then perform a block / replace on large chunks of memories in the Freq, Offset, Tstep and RPT1 and RPT2 fields, which can then be imported back into the radio. CHIRP in its current format, using Export / Modify / Import, makes that a relatively simple process compared to editing one line at a time through the GUI.

Excel is pretty complex and powerful, so making chirp able to rival the functionality may not be feasible, but it's a worthwhile discussion, I think.

Agreed. I have no perspective as to whether there are many others trying to do similar things to me, so I wouldn't suggest putting in a whole heap of effort if I'm the only one with this need.

However... If you were to go down this path... One solution might be to be able to "tag" each of the memories to be changed, choose which field to have its data modified and have a field that can then have the new value entered into it. It still might be a bit kludgy if this has to be done each time, so it would be better still if the tagged entries could be remembered to simplify future editing. I think this would be great if not too difficult...

Cheers,

Davidt, VK3UR