On a given project workspace, I import 1300 tracks as assets. Then I copy all tracks from the asset list to add to the new project. When added to project, the properties say I only have 1262 tracks. What happened to the other 38, and why are they not added to the project? I can find a few gaps in my Raster maps once finished where I know I have the data because it shows up on the Dr. Depth maps. Why the discrepancy between the tracks on the asset list and the tracks on the project? They are all copied/highlighted when I add them to the project. It happens this way on every project using the same data. All tracks are converted DRD's to CSV.

With so many tracks, I can't determine an efficient way to determine which tracks are being omitted. No way to print the list of tracks in the project, or even view them all together.

How are you adding the tracks to the project? Select and right-click menu in the asset list? You could try opening the tracks list in the project edit window to see if there are any overlapping tracks (Green background) left that have not been added, and then add them again (add overlapping button). I don't know why they wouldn't have been added in the first place though - could there be duplicates?

I am simply highlighting all the tracks in the asset list, then right clicking, and clicking "add to project" and selecting the project. The asset list has no duplicates, those were discovered and eliminated in the AT5 map create process earlier on, and there were only 7. Each track is a separate CSV with no dupes. I can open the tracks in the project edit window, but that's where the missing 38 tracks do not show up. Its hard to view them when there's 1,300, but a slow scroll through the list didn't reveal any "green" color or highlight. For some reason, there are 38 tracks in the asset list that do not show up in the edit window or on the project. All tracks in the asset list are highlighted prior to being added to project.

Have these "missing" tracks definitely been imported successfully? It sounds like they might not have been - perhaps the depths were all zero, or there was some other issue in the file format? I don't know how you would check - perhaps if the names of the tracks are all different you can sort them by name in the asset list and try to see if any are missing?

It'll have to be something labor-intensive like that. One by one, 1,300 of em. When I first import the tracks to the asset list, it gives the number of tracks being imported, and that matches exactly the number there really is in my track file. It's just from there to the project where some are being left behind, hidden, or something. I'll do some detective work some day with a pen and paper. I see no way to copy or print the list in the track edit window, but I can maybe print my own csv list and have something to use as a check list.

If you want to share your workspace (.rmdb) file I can take a look in the DB and see if I can find out what is going on.

OK, I have started checking off "the list" of each csv file in both locations, and I found a few of them about 150 files into it that were not on either the asset list or the track project list. So, although during the first import of the assets the green indicator bar said "processing 1300 files", it in fact only brought in fewer, 38 fewer.

Why? Well, upon opening a few of the csv's in question, they did in fact have all zeros for depth values. Why is still a mystery, but they were converted from Dr. Depth. They were also not originally recorded by me, but by someone I share data with, but nevertheless, that's why they are not ending up in the project list. Mystery solved, at least concerning why they're not showing up in the project list. I won't worry about finding the other 25 or so, and assume they too have zero values.

So, bad CSV's to start. Garbage in, garbage out, or something like that! I will clean up the garbage, or fix it, and get on to the next task.

I'm glad there is an answer. Perhaps we should look at adding a "X files successfully imported" type message to avoid this confusion in the future.