BaseCamp 4.6.2 incorrect track names

I'm also interested in the answer. When i ride a course and save it with a name on my device (in my case the Edge 820) i expect to see it with that name i gave it in basecamp.

Please bear with me while I make another wild guess.

In the beginning there was a Unix Start date of 12/31/69 or 1/1/1970 or thereabouts. The Global Positioning System picked up this feature. Then in the 1990's mapping and routing companies developed hard coded apps that would disallow prior dates in computer files naming. Then along came Microsoft automated updates, as well as the US and other country's legislative branches monkeying with Daylight Savings Time twice a year so that they could pass at least one law almost unanimously. DST spring forward and fall back could cause mapping app crashes on Windows Operating Systems in particular.

Therefore maybe somebody had a bright idea at Garmin to move the default start date to 12/31/1989 for erroneous file default. Maybe, maybe not, the real reason for that 1989 date??? Or did the OP misread the value of 1969? I can't tell from the fuzzy attachment.

The above is probably not too far from the truth, but I don't think Garmin is responsible for the .fit file format. My understanding is that fit timestamps are in seconds from ... you guessed it 12/31/1989. In the gpx file format, file names have nothing to do with object names. Object names are contained within the file and it is this name that BaseCamp uses. My guess would be that a fit file does not contain a "track" name field within the file and BaseCamp defaults to the timestamp it finds, which must be 12/31/1989. So a time stamp in fit might look something like" 12/31/1989, #" where "#" is in seconds (just speculation).