Erase trackpoints from historical Track in BaseCamp 4.3.4 too slow

Erase trackpoints from historical Track using BaseCamp 4.3.4 (remove glitches, gps drift when not moving, user driving in the wrong direction, stops etc.): to remove each single trackpoint takes 1-2 seconds!
In previous BaseCamp version 4.2.5 I was able to erase multiple trackpoints within one split second.
(Is BaseCamp recalculating track length after each single erase? Not very effective and very irritating).

Update:

Last night I had to clean-up 8 tracks (bicycle and walking). It took me one hour (normally 15-30 minutes), and after half an hour I decided to use MapSource as a work-around.

I tried to reproduce the issue, but I failed to do so. Trackpoints were erased in the same split second as before.

Why? How?

If the GPS (Etrex 30) is not connected to PC/BaseCamp in Mass Storage mode there is no problem.

If the GPS (Etrex 30) is connected to PC/BaseCamp in Mass Storage mode than the performance issue is reproduced.

To resolve: Eject device, restart BaseCamp and performance in erasing trackpoints is ok!

I was not editing a track on Device. The track was being sent from GPS to BaseCamp List and edited in BaseCamp List. There is no real need for GPS to be connected, but I prefer having GPS available.
Number of Archived Tracks on GPS: 10 tracks.
Looking back I think accessing GPS slowed down performance even more (up to 3 seconds per trackpoint). But that's not a fact, just an impression.
  • Former Member
    0 Former Member
    Would you be willing to send us your data by posting it here so I can recreate your performance issue? We have made a number of performance enhancements to this but I am not sure why a device being connected matters.
  • I didn't sent you my database (10.000 waypoints and 1300 tracks). Also: database is not relevant, I have tested today using an empty database.
    I did sent you 9 tracks (used during my testing). But these are also not relevant, any track will do.
    Attached:

    I can imagine why you have doubts whether "device being connected matters".
    And my new conclusion is: No, device being connected doesn't matter. Restarting BaseCamp will do.

    Steps to reproduce (tested again today):
    - Select several Archived Tracks on Device and "Send To..." BaseCamp List.
    - More tracks being selected has more impact on performance than one track being selected.
    - Erase trackpoints in tracks. Which trackpoints are selected is not relevant.
    - Editing more different tracks will have more effect on performance.
    - Editing over a longer period of time will have more effect on performance (that's why I was irritated two days ago after half an hour of rather stupid work).
    - Performance degradation during Erase TrackPoints can be seen by Hourglass being visible. When performance is ok, there is no time available for showing an Hourglass.

    To resolve:
    - Close BaseCamp and Restart BaseCamp.
    So whether or not the Device is still connected is not relevant.
    Now performance in erasing trackpoints is ok!

    My hypothesis:
    - Closing and restarting BaseCamp releases some kind of Reference/Connection to the Tracks being stored on the Device (Source);
    - Closing BaseCamp will store recently imported tracks in a more efficient way.

    I have also tested the effect of importing (File, Import into…) a large number of gpx files (tracks) into a BaseCamp List.
    Now I don't see any performance degradation during Erase TrackPoints.
    So, IMO, tracks being send over from Device is relevant.
  • Former Member
    0 Former Member
    Thanks for the feedback. I will attempt to recreate your problem and open a case if I can. Thanks for sharing your data. I'll keep you posted if I find anything.
  • Former Member
    0 Former Member
    Grrrrr, I am not able to recreate your issue. I imported all of these tracks, edited them all, in some cases in bulk and in others one point at a time following the steps above. It is snappy. You do indeed have 4.3.4 installed? I believe you see this, I am just unable to recreate. Can you possibly share with me the specs of your PC?
  • Also Grrrrrr; :rolleyes:

    PC is Windows 7, 64-bit, i5-2310 CPU @ 2.90Ghz, 6,00 GB.
    USB port might also be relevant: USB 1.1 ports.

    And yes, BaseCamp 4.3.4 installed, in BaseCamp 4.2.5 I have no issues.

    Bulk erase of trackpoints was never an issue, only the single ones: click, click, click, click, click, click, click, click, click, click, click...

    What I would advise you to do: if you can't reproduce then don't make a case out of it and don't get "Grrrrr" about it; :)
    Some users; :confused:
    I was hoping someone else would confirm... and to be honest: two days ago I have seen up to 3 seconds delay, today I had to look carefully for the Hourglass... 1 second was max.
  • Former Member
    0 Former Member
    It may be services running on your computer in the background. I know that in this version (4.3 in general) we took great pains to improve the performance of this. And I'm grrr because, well because :)

    Thanks for the feedback. I will continue trying off and on and if I am able to recreate this I will open a case at that time. Thanks again for the feedback.
  • Former Member
    0 Former Member
    I'm having the same problem. Driving me crazy.
  • I'm seeing almost instantaneous deletion of either single or multi track points, running Win 7 and BC 4.3.4

    I suspect (as posted above) you must have something running in the background.
  • Former Member
    0 Former Member
    Anti virus software or something? Certainly nothing different from before the upgrade.
  • Former Member
    0 Former Member
    I'm sorry but basecamp is virtually unuseable now since the upgrade. Deleting, moving or inserting trackpoints.......easily 2, more like 3 seconds EACH! Creating a track is a nightmare. A 45 minute task is today running 2 hrs. And it happened with the upgrade. Throw in the fake roads that show up with Global Map that can't be turned off and this upgrade is a disaster. Seriously!