0002517: Huge time difference (45024 days, from 1899) when syncing images to gpx - GeoSetter

ID	Project	Category	View Status	Date Submitted	Last Update

0002517	GeoSetter	Image Data	public	2023-04-10 00:09	2023-04-10 20:03

Reporter	zava	Assigned To
Priority	normal	Severity	major	Reproducibility	always
Status	new	Resolution	open
Product Version	4.0.49 beta
Target Version		Fixed in Version

Summary	0002517: Huge time difference (45024 days, from 1899) when syncing images to gpx
Description	GS has never had particular problems syncing images with gpx files, and even now it does it with all my previous gpx files. Yet, with one particular gpx file, which does contain a track suitable to properly sync images (with an appopriate, small time adjustment), it fails syncing and finds a huge time difference (45024 days!) As far ai I could see, the gpx files contains regular items and also the images have a taken date very close with recorded point in the gpx (I inspected image data with GS's edit data and another viewer, I inspected the recorder track points in GS's track point list and also by carefully inspecting the gpx file in a plain text editor; everything looks fine, yet GS provides this very strange failure. To make things easier to reproduce, I am attaching ONE single image and the gpx file. If I try to sync, the image is NOT synced, and the report displays that huge time difference. It is noticeable that the track point date appears as recorded in the year 1899 (!!!), although the actual gpx file seems to contain only appropriate data stamps). Also noticeable, is tha that the report is not related to any of the contained active logs (as is usually the case) but references the overall gpx file. This seems to only happen with this particular gpx file. Close inspection of the gpx code doesn't seem to show any strange timestamps I have repeated all the process generating the gpx file from the GPS unit, with unchanged results. All previous files generated by the same process/GPS unit work flawlessly. Attached, a sample image and the gpx file, in case anybody is willing to look into it or at least try to reproduce the problem. Thank anybody for trying!
Tags	No tags attached.

zava 2023-04-10 00:09 reporter	Sync settings.jpg (117,493 bytes) Sync settings.jpg (117,493 bytes) Sync report.jpg (42,492 bytes) Sync report.jpg (42,492 bytes) 2023 04 08 Nodic.gpx (168,373 bytes) Z4085376_lr.JPG (1,613,512 bytes)

WilfriedB 2023-04-10 08:59 reporter ~0004727	@zava I downloaded you examples and believe the cause of the problem is the GPX file. How did you create it? I opened it with RouteConverter and see the date and time inside the description field, but the Date and Time fields are empty: grafik.png (31,232 bytes) grafik.png (31,232 bytes)

WilfriedB 2023-04-10 09:22 reporter ~0004728	@zava please ignore my previous comment. Only a litte later, I noticed the GPX contains some way points and multiple tracks. However according to RouteConverter, the time stamp of the first track starts later than the time of you jpg. Looking the same track in GeoSetter seems, it doessn't account to the time zone. grafik-2.png (20,915 bytes) grafik-2.png (20,915 bytes) grafik-3.png (120,696 bytes) grafik-3.png (120,696 bytes)

zava 2023-04-10 11:16 reporter ~0004729	Hello WilfriedB, thank you for your concern! I assume you were able to reproduce the problem, right? I agree the problem is probably with the gpx file. The procedure to produce the gpx file (unchanged since 10+ years) is as follows: - receive active logs from Garmin USB unit into Mapsource (old and buggy program, but always worked fine to this purpose) - delete some non relevant tracks (logs from previous days, which were previously recorded in gpx files displaying no problem) - "saving as" gpx file (the one I attached As I said this procedure has been my standard with hundreds of gpx files across the past 10+ years. Both the Garmin GPS unit and Mapsource do have several quirks (such as recording waypoints with no time stamp, while the waypoint date is recorded in the "comment", as you noticed using Routeconverter), but up to this time the resulting gpx file had always been good for GS syincing. Indeed, it does display with no apparent problem and no prehistoric dates in GS and in CompeGps... I may now try to prune the gpx files to the barely minimum content displaying the problem... Concerning your remark "according to RouteConverter, the time stamp of the first track starts later than the time of you jpg. Looking the same track in GeoSetter seems, it doessn't account to the time zone." (if I understood it correctly) In my experience, it is rather normal that jpg dates may be slightly eralier or later than track points. This is due to several factor, and partly compensated by GS's time addiction. But even when no perfect match is achieved, this is usually a "normal" situation, often not preventing synchronization, or at worst leaving an unsynced image but with a "reasonable" time difference (some minutes or hours... But here a track point timestamp appears dated 1899! I guess THIS is somehow the cause of all problems but I have no idea where this date is emerging from! (no such date is reported anywhere in the gpx file, all dates are apparently correct...) Thank you!

zava 2023-04-10 12:03 reporter ~0004730	Hello, I produced a stripped down version of the gpx file: I removed waypoints and all tracks, leaving only one active log (which was taken at the same time as the sample image I originally attached). This gpx file appears correct, it is displayed correctly by GS and by Routeconverter and looks fine in a plain text editor. Both programs correctly show two track points with proper time stamps. Yet, when syincing, GS reports that "no track file was selected or track file contains no coordinates including date time information" (see attach) But, the file DOES contain two apparently valid points, and EVEN GS does display their date time information! (also visible in attached screenshot) WHAT is wrong with this tiny file?! Thank anybody watching! 2023 04 08 Nodic_mod.gpx (1,226 bytes) No time date.jpg (285,728 bytes)

WilfriedB 2023-04-10 12:54 reporter ~0004731	@zava I forgot to mention that I was able to reproduce in the sense that synchronizing was not possible, but did not see the difference of 45024 days. However, using the short version of the GPX, I did get a bug report, I saved and attached here. bugreport.txt (28,231 bytes) date/time : 2023-04-10, 12:46:36, 582ms operating system : Windows 10 x64 build 19045 system language : German system up time : 3 days 2 hours program up time : 22 seconds processors : 4x Intel(R) Core(TM) i5-5200U CPU @ 2.20GHz physical memory : 7002/16258 MB (free/total) free disk space : (C:) 51,11 GB display mode : 1920x1080, 32 bit process id : $3aa8 allocated memory : 417,91 MB largest free block : 701,81 MB executable : GeoSetter.exe exec. date/time : 2023-02-25 19:50 version : 4.0.49.2233 settings folder : C:\Users\User\AppData\Roaming\GeoSetter_beta\ ExifTool folder : C:\Users\User\AppData\Roaming\GeoSetter_beta\tools\exiftool.exe map file : C:\Program Files (x86)\GeoSetter beta\map\map.html map file HTML version : 4.0.39 map file JS version : 4.0.40 contact name : Wilfried Blankertz contact email : W.Blankertz@t-online.de callstack crc : $768221ac, $1c6cc957, $d43154cc exception number : 1 exception class : EAccessViolation exception message : Zugriffsverletzung bei Adresse 00484DF2 in Modul 'GeoSetter.exe'. Lesen von Adresse 00000008. thread $6328 (TExifToolInitThread): 00484df2 +062 GeoSetter.exe Classes 3179 +7 TInterfaceList.Clear 00484d60 +014 GeoSetter.exe Classes 3164 +1 TInterfaceList.Destroy 0040765d +01d GeoSetter.exe System 17188 +3 TInterfacedObject._Release 00407568 +010 GeoSetter.exe System 17033 +7 @IntfClear 004062ff +0bf GeoSetter.exe System 14469 +99 @FinalizeArray 00406214 +020 GeoSetter.exe System 14284 +19 @FinalizeRecord 00404476 +012 GeoSetter.exe System 8497 +10 TObject.CleanupInstance 004043b9 +005 GeoSetter.exe System 8373 +1 TObject.FreeInstance 00462761 +019 GeoSetter.exe madExcept InterceptClassDestroy 00921008 +028 GeoSetter.exe XMLDoc 921 +1 TXMLNodeList.Destroy 0040765d +01d GeoSetter.exe System 17188 +3 TInterfacedObject._Release 00407568 +010 GeoSetter.exe System 17033 +7 @IntfClear 004062ff +0bf GeoSetter.exe System 14469 +99 @FinalizeArray 00406214 +020 GeoSetter.exe System 14284 +19 @FinalizeRecord 00404476 +012 GeoSetter.exe System 8497 +10 TObject.CleanupInstance 004043b9 +005 GeoSetter.exe System 8373 +1 TObject.FreeInstance 00462761 +019 GeoSetter.exe madExcept InterceptClassDestroy 00921e9d +08d GeoSetter.exe XMLDoc 1189 +9 TXMLNode.Destroy 0040765d +01d GeoSetter.exe System 17188 +3 TInterfacedObject._Release 00921eec +008 GeoSetter.exe XMLDoc 1205 +1 TXMLNode._Release 00407568 +010 GeoSetter.exe System 17033 +7 @IntfClear 00484de0 +050 GeoSetter.exe Classes 3178 +6 TInterfaceList.Clear 00484d60 +014 GeoSetter.exe Classes 3164 +1 TInterfaceList.Destroy 0040765d +01d GeoSetter.exe System 17188 +3 TInterfacedObject._Release 00407568 +010 GeoSetter.exe System 17033 +7 @IntfClear 004062ff +0bf GeoSetter.exe System 14469 +99 @FinalizeArray 00406214 +020 GeoSetter.exe System 14284 +19 @FinalizeRecord 00404476 +012 GeoSetter.exe System 8497 +10 TObject.CleanupInstance 004043b9 +005 GeoSetter.exe System 8373 +1 TObject.FreeInstance 00462761 +019 GeoSetter.exe madExcept InterceptClassDestroy 00921008 +028 GeoSetter.exe XMLDoc 921 +1 TXMLNodeList.Destroy 0040765d +01d GeoSetter.exe System 17188 +3 TInterfacedObject._Release 00407568 +010 GeoSetter.exe System 17033 +7 @IntfClear 00ac5544 +14c GeoSetter.exe ExifTool 1121 +19 TExifToolLanguageItems.Create 00ac3112 +062 GeoSetter.exe ExifTool 349 +1 InitExifTool 00ac8659 +021 GeoSetter.exe ExifTool 1762 +0 TExifToolInitThread.Execute 0048f3f6 +036 GeoSetter.exe Classes 9372 +7 ThreadProc 004052b8 +028 GeoSetter.exe System 11562 +33 ThreadWrapper 00462985 +00d GeoSetter.exe madExcept CallThreadProcSafe 004629ef +037 GeoSetter.exe madExcept ThreadExceptFrame 74e30097 +017 KERNEL32.DLL BaseThreadInitThunk >> created by main thread ($4464) at: 00ac85dd +09d GeoSetter.exe ExifTool 1756 +8 TExifToolInitThread.Create main thread ($4464): 00528f82 +1e GeoSetter.exe Forms 6891 +1 TApplication.HandleMessage 0052920e +a6 GeoSetter.exe Forms 6975 +16 TApplication.Run 00ecd054 +4c GeoSetter.exe GeoSetter 179 +4 initialization 74e30097 +17 KERNEL32.DLL BaseThreadInitThunk thread $3dd8: 74e30097 +17 KERNEL32.DLL BaseThreadInitThunk thread $41dc: 74e30097 +17 KERNEL32.DLL BaseThreadInitThunk thread $5910: 74e30097 +17 KERNEL32.DLL BaseThreadInitThunk thread $4aa0: 74e30097 +17 KERNEL32.DLL BaseThreadInitThunk thread $582c: 74e30097 +17 KERNEL32.DLL BaseThreadInitThunk thread $5a5c: 74e30097 +17 KERNEL32.DLL BaseThreadInitThunk thread $9b0: 7594c297 +47 user32.dll MsgWaitForMultipleObjectsEx 7594c23a +1a user32.dll MsgWaitForMultipleObjects 00462985 +0d GeoSetter.exe madExcept CallThreadProcSafe 004629ef +37 GeoSetter.exe madExcept ThreadExceptFrame 74e30097 +17 KERNEL32.DLL BaseThreadInitThunk >> created by main thread ($4464) at: 741f67ca +00 gdiplus.dll thread $9a8 (TWorkerThread): 76874593 +93 KERNELBASE.dll WaitForSingleObjectEx 768744ed +0d KERNELBASE.dll WaitForSingleObject 0053acb3 +17 GeoSetter.exe VirtualTrees 6079 +3 TWorkerThread.Execute 00462aa3 +2b GeoSetter.exe madExcept HookedTThreadExecute 0048f3f6 +36 GeoSetter.exe Classes 9372 +7 ThreadProc 004052b8 +28 GeoSetter.exe System 11562 +33 ThreadWrapper 00462985 +0d GeoSetter.exe madExcept CallThreadProcSafe 004629ef +37 GeoSetter.exe madExcept ThreadExceptFrame 74e30097 +17 KERNEL32.DLL BaseThreadInitThunk >> created by main thread ($4464) at: 0053abaa +16 GeoSetter.exe VirtualTrees 6022 +1 TWorkerThread.Create thread $ae4: 7687e6dd +fd KERNELBASE.dll WaitForMultipleObjectsEx 00462985 +0d GeoSetter.exe madExcept CallThreadProcSafe 004629ef +37 GeoSetter.exe madExcept ThreadExceptFrame 74e30097 +17 KERNEL32.DLL BaseThreadInitThunk >> created by main thread ($4464) at: 754b0ef1 +00 combase.dll thread $14bc: 74e30097 +17 KERNEL32.DLL BaseThreadInitThunk thread $6750: 74e30097 +17 KERNEL32.DLL BaseThreadInitThunk thread $5d78 (TacAddThread): <priority:-1> 76874593 +93 KERNELBASE.dll WaitForSingleObjectEx 768744ed +0d KERNELBASE.dll WaitForSingleObject 004a3713 +17 GeoSetter.exe SyncObjs 132 +2 TEvent.WaitFor 00c0139c +0c GeoSetter.exe sSkinManager 7982 +2 TacAddThread.Execute 0048f3f6 +36 GeoSetter.exe Classes 9372 +7 ThreadProc 004052b8 +28 GeoSetter.exe System 11562 +33 ThreadWrapper 00462985 +0d GeoSetter.exe madExcept CallThreadProcSafe 004629ef +37 GeoSetter.exe madExcept ThreadExceptFrame 74e30097 +17 KERNEL32.DLL BaseThreadInitThunk >> created by main thread ($4464) at: 00bfae96 +22 GeoSetter.exe sSkinManager 6248 +4 TacSkinListController.StartDelayedLoading thread $4670 (TImageDataRefreshThread): 768926c5 +45 KERNELBASE.dll SleepEx 7689266a +0a KERNELBASE.dll Sleep 00a53230 +e4 GeoSetter.exe ImageDataRefreshThread 127 +31 TImageDataRefreshThread.Execute 00462aa3 +2b GeoSetter.exe madExcept HookedTThreadExecute 0048f3f6 +36 GeoSetter.exe Classes 9372 +7 ThreadProc 004052b8 +28 GeoSetter.exe System 11562 +33 ThreadWrapper 00462985 +0d GeoSetter.exe madExcept CallThreadProcSafe 004629ef +37 GeoSetter.exe madExcept ThreadExceptFrame 74e30097 +17 KERNEL32.DLL BaseThreadInitThunk >> created by main thread ($4464) at: 00a530ef +27 GeoSetter.exe ImageDataRefreshThread 80 +2 TImageDataRefreshThread.Create thread $64c8 (TacShellChangeThread): 7687e6dd +fd KERNELBASE.dll WaitForMultipleObjectsEx 7687e5c3 +13 KERNELBASE.dll WaitForMultipleObjects 00b4b96c +5c GeoSetter.exe acShellCtrls 1835 +9 TacShellChangeThread.Execute 0048f3f6 +36 GeoSetter.exe Classes 9372 +7 ThreadProc 004052b8 +28 GeoSetter.exe System 11562 +33 ThreadWrapper 00462985 +0d GeoSetter.exe madExcept CallThreadProcSafe 004629ef +37 GeoSetter.exe madExcept ThreadExceptFrame 74e30097 +17 KERNEL32.DLL BaseThreadInitThunk >> created by main thread ($4464) at: 00b4b86c +44 GeoSetter.exe acShellCtrls 1796 +7 TacShellChangeThread.Create thread $6060 (TImageDataQueueSaveThread): 768926c5 +045 KERNELBASE.dll SleepEx 7689266a +00a KERNELBASE.dll Sleep 00ce9ece +15e GeoSetter.exe ImageDataQueueSaveThread 166 +36 TImageDataQueueSaveThread.Execute 00462aa3 +02b GeoSetter.exe madExcept HookedTThreadExecute 0048f3f6 +036 GeoSetter.exe Classes 9372 +7 ThreadProc 004052b8 +028 GeoSetter.exe System 11562 +33 ThreadWrapper 00462985 +00d GeoSetter.exe madExcept CallThreadProcSafe 004629ef +037 GeoSetter.exe madExcept ThreadExceptFrame 74e30097 +017 KERNEL32.DLL BaseThreadInitThunk >> created by main thread ($4464) at: 00ce9cc7 +033 GeoSetter.exe ImageDataQueueSaveThread 104 +5 TImageDataQueueSaveThread.Create thread $61bc (TImageDataQueueSaveThread): 768926c5 +045 KERNELBASE.dll SleepEx 7689266a +00a KERNELBASE.dll Sleep 00ce9ece +15e GeoSetter.exe ImageDataQueueSaveThread 166 +36 TImageDataQueueSaveThread.Execute 00462aa3 +02b GeoSetter.exe madExcept HookedTThreadExecute 0048f3f6 +036 GeoSetter.exe Classes 9372 +7 ThreadProc 004052b8 +028 GeoSetter.exe System 11562 +33 ThreadWrapper 00462985 +00d GeoSetter.exe madExcept CallThreadProcSafe 004629ef +037 GeoSetter.exe madExcept ThreadExceptFrame 74e30097 +017 KERNEL32.DLL BaseThreadInitThunk >> created by main thread ($4464) at: 00ce9cc7 +033 GeoSetter.exe ImageDataQueueSaveThread 104 +5 TImageDataQueueSaveThread.Create thread $cec (TImageDataQueueSaveThread): 768926c5 +045 KERNELBASE.dll SleepEx 7689266a +00a KERNELBASE.dll Sleep 00ce9ece +15e GeoSetter.exe ImageDataQueueSaveThread 166 +36 TImageDataQueueSaveThread.Execute 00462aa3 +02b GeoSetter.exe madExcept HookedTThreadExecute 0048f3f6 +036 GeoSetter.exe Classes 9372 +7 ThreadProc 004052b8 +028 GeoSetter.exe System 11562 +33 ThreadWrapper 00462985 +00d GeoSetter.exe madExcept CallThreadProcSafe 004629ef +037 GeoSetter.exe madExcept ThreadExceptFrame 74e30097 +017 KERNEL32.DLL BaseThreadInitThunk >> created by main thread ($4464) at: 00ce9cc7 +033 GeoSetter.exe ImageDataQueueSaveThread 104 +5 TImageDataQueueSaveThread.Create thread $53a4 (TImageDataQueueSaveThread): 768926c5 +045 KERNELBASE.dll SleepEx 7689266a +00a KERNELBASE.dll Sleep 00ce9ece +15e GeoSetter.exe ImageDataQueueSaveThread 166 +36 TImageDataQueueSaveThread.Execute 00462aa3 +02b GeoSetter.exe madExcept HookedTThreadExecute 0048f3f6 +036 GeoSetter.exe Classes 9372 +7 ThreadProc 004052b8 +028 GeoSetter.exe System 11562 +33 ThreadWrapper 00462985 +00d GeoSetter.exe madExcept CallThreadProcSafe 004629ef +037 GeoSetter.exe madExcept ThreadExceptFrame 74e30097 +017 KERNEL32.DLL BaseThreadInitThunk >> created by main thread ($4464) at: 00ce9cc7 +033 GeoSetter.exe ImageDataQueueSaveThread 104 +5 TImageDataQueueSaveThread.Create thread $1bc8: 76874593 +93 KERNELBASE.dll WaitForSingleObjectEx 768744ed +0d KERNELBASE.dll WaitForSingleObject 005a7499 +4d GeoSetter.exe VirtualShellNotifier 2260 +9 TVirtualChangeDispatchThread.Execute 00596922 +36 GeoSetter.exe MPThreadManager 676 +22 TCommonThread.ExecuteStub 00462985 +0d GeoSetter.exe madExcept CallThreadProcSafe 004629ef +37 GeoSetter.exe madExcept ThreadExceptFrame 74e30097 +17 KERNEL32.DLL BaseThreadInitThunk >> created by main thread ($4464) at: 005966e1 +6d GeoSetter.exe MPThreadManager 615 +12 TCommonThread.Create thread $5630: 75933a0f +4f user32.dll GetMessageA 005a686b +bb GeoSetter.exe VirtualShellNotifier 1918 +15 TVirtualShellChangeThread.Execute 00596922 +36 GeoSetter.exe MPThreadManager 676 +22 TCommonThread.ExecuteStub 00462985 +0d GeoSetter.exe madExcept CallThreadProcSafe 004629ef +37 GeoSetter.exe madExcept ThreadExceptFrame 74e30097 +17 KERNEL32.DLL BaseThreadInitThunk >> created by main thread ($4464) at: 005966e1 +6d GeoSetter.exe MPThreadManager 615 +12 TCommonThread.Create thread $308c: <priority:-1> 7687e6dd +fd KERNELBASE.dll WaitForMultipleObjectsEx 76706dbc +8c msvcrt.dll _endthreadex 00462985 +0d GeoSetter.exe madExcept CallThreadProcSafe 004629ef +37 GeoSetter.exe madExcept ThreadExceptFrame 74e30097 +17 KERNEL32.DLL BaseThreadInitThunk >> created by main thread ($4464) at: 76706caf +7f msvcrt.dll _beginthreadex thread $66bc: 7594c297 +47 user32.dll MsgWaitForMultipleObjectsEx 75496c82 +72 combase.dll CoWaitForMultipleHandles 00462985 +0d GeoSetter.exe madExcept CallThreadProcSafe 004629ef +37 GeoSetter.exe madExcept ThreadExceptFrame 74e30097 +17 KERNEL32.DLL BaseThreadInitThunk >> created by main thread ($4464) at: 54d32b8a +00 mshtml.dll thread $590c: <priority:-1> 7687e6dd +fd KERNELBASE.dll WaitForMultipleObjectsEx 76706dbc +8c msvcrt.dll _endthreadex 00462985 +0d GeoSetter.exe madExcept CallThreadProcSafe 004629ef +37 GeoSetter.exe madExcept ThreadExceptFrame 74e30097 +17 KERNEL32.DLL BaseThreadInitThunk >> created by main thread ($4464) at: 76706caf +7f msvcrt.dll _beginthreadex thread $3c84: 76874593 +93 KERNELBASE.dll WaitForSingleObjectEx 768744ed +0d KERNELBASE.dll WaitForSingleObject 76706dbc +8c msvcrt.dll _endthreadex 00462985 +0d GeoSetter.exe madExcept CallThreadProcSafe 004629ef +37 GeoSetter.exe madExcept ThreadExceptFrame 74e30097 +17 KERNEL32.DLL BaseThreadInitThunk >> created by main thread ($4464) at: 76706caf +7f msvcrt.dll _beginthreadex thread $3ddc: 76874593 +93 KERNELBASE.dll WaitForSingleObjectEx 768744ed +0d KERNELBASE.dll WaitForSingleObject 00462985 +0d GeoSetter.exe madExcept CallThreadProcSafe 004629ef +37 GeoSetter.exe madExcept ThreadExceptFrame 74e30097 +17 KERNEL32.DLL BaseThreadInitThunk >> created by main thread ($4464) at: 54d32b8a +00 mshtml.dll thread $62d8: <priority:15> 7687e6dd +fd KERNELBASE.dll WaitForMultipleObjectsEx 7687e5c3 +13 KERNELBASE.dll WaitForMultipleObjects 00462985 +0d GeoSetter.exe madExcept CallThreadProcSafe 004629ef +37 GeoSetter.exe madExcept ThreadExceptFrame 74e30097 +17 KERNEL32.DLL BaseThreadInitThunk >> created by main thread ($4464) at: 54d90250 +00 mshtml.dll thread $ce8: 76874593 +93 KERNELBASE.dll WaitForSingleObjectEx 768744ed +0d KERNELBASE.dll WaitForSingleObject 00596c77 +2f GeoSetter.exe MPThreadManager 898 +4 TCommonEventThread.Execute 00596922 +36 GeoSetter.exe MPThreadManager 676 +22 TCommonThread.ExecuteStub 00462985 +0d GeoSetter.exe madExcept CallThreadProcSafe 004629ef +37 GeoSetter.exe madExcept ThreadExceptFrame 74e30097 +17 KERNEL32.DLL BaseThreadInitThunk >> created by main thread ($4464) at: 005966e1 +6d GeoSetter.exe MPThreadManager 615 +12 TCommonThread.Create thread $520: 74e30097 +17 KERNEL32.DLL BaseThreadInitThunk thread $5a7c: 74e30097 +17 KERNEL32.DLL BaseThreadInitThunk thread $677c: 7594c297 +47 user32.dll MsgWaitForMultipleObjectsEx 75496c82 +72 combase.dll CoWaitForMultipleHandles 00462985 +0d GeoSetter.exe madExcept CallThreadProcSafe 004629ef +37 GeoSetter.exe madExcept ThreadExceptFrame 74e30097 +17 KERNEL32.DLL BaseThreadInitThunk >> created by main thread ($4464) at: 54d32b8a +00 mshtml.dll thread $3168: 7594c297 +47 user32.dll MsgWaitForMultipleObjectsEx 75496c82 +72 combase.dll CoWaitForMultipleHandles 00462985 +0d GeoSetter.exe madExcept CallThreadProcSafe 004629ef +37 GeoSetter.exe madExcept ThreadExceptFrame 74e30097 +17 KERNEL32.DLL BaseThreadInitThunk >> created by main thread ($4464) at: 54d32b8a +00 mshtml.dll hardware: + {1ed2bbf9-11f0-4084-b21f-ad83a8e6dcdc} - EPSON WF-2750 Series (FAX) - EPSON WF-2750 Series (FAX) (Kopie 1) - EPSON WF-2760 Series (FAX) - EPSON WF-2760 Series (FAX) (Kopie 1) - EPSON WF-2760 Series (FAX) (Kopie 2) - EPSON WF-2810 Series (FAX) - EPSON WF-2830 Series - EPSON39988D (XP-3100 Series) - EPSON794057 (WF-2760 Series) - Fax - HP OfficeJet 3830 series [83A20B] - Microsoft Print to PDF - Microsoft XPS Document Writer - OneNote for Windows 10 - Stammdruckwarteschlange - WF-2750 Series(Netzwerk) - WF-2810 Series(Netzwerk) + {36fc9e60-c465-11cf-8056-444553540000} - Generic USB Hub - Intel(R) USB 3.0 eXtensible-Hostcontroller – 1.0 (Microsoft) - Mobile 5th Generation Intel(R) Core(TM) USB EHCI Controller - 9CA6 (driver 10.1.1.12) - SAMSUNG Mobile USB Composite Device (driver 2.19.1.0) - USB-Root-Hub - USB-Root-Hub (USB 3.0) - USB-Verbundgerät + {3f966bd9-fa04-4ec5-991c-d326973b5128} - SAMSUNG Android ADB Interface (driver 2.19.1.0) + {4d36e966-e325-11ce-bfc1-08002be10318} - ACPI x64-basierter PC + {4d36e967-e325-11ce-bfc1-08002be10318} - TS256GMTS400 - WDC WDS200T2G0A-00JH30 + {4d36e968-e325-11ce-bfc1-08002be10318} - Intel(R) HD Graphics 5500 (driver 20.19.15.5126) + {4d36e96a-e325-11ce-bfc1-08002be10318} - Intel(R) 9 Series Chipset Family SATA AHCI Controller (driver 14.8.10.1055) + {4d36e96b-e325-11ce-bfc1-08002be10318} - PS/2-Standardtastatur + {4d36e96c-e325-11ce-bfc1-08002be10318} - FxSound Audio Enhancer (driver 14.1.0.0) - Logi Z407 Stereo - Realtek High Definition Audio (driver 6.0.8907.1) - RoxaPlus Stereo - WF-1000XM3 Hands-Free AG Audio - WF-1000XM3 Stereo + {4d36e96d-e325-11ce-bfc1-08002be10318} - SAMSUNG Mobile USB Modem #3 (driver 2.19.1.0) + {4d36e96e-e325-11ce-bfc1-08002be10318} - PnP-Monitor (Standard) + {4d36e96f-e325-11ce-bfc1-08002be10318} - Synaptics Pointing Device (driver 19.0.17.142) + {4d36e970-e325-11ce-bfc1-08002be10318} - Realtek PCIE CardReader (driver 10.0.10125.21277) + {4d36e972-e325-11ce-bfc1-08002be10318} - Bluetooth Device (Personal Area Network) #2 - Intel(R) Dual Band Wireless-AC 7265 (driver 19.51.40.1) - Intel(R) Ethernet Connection (3) I218-V (driver 12.18.9.8) - Microsoft Kernel Debug Network Adapter - Microsoft Wi-Fi Direct Virtual Adapter - Microsoft Wi-Fi Direct Virtual Adapter #3 - WAN Miniport (IKEv2) - WAN Miniport (IP) - WAN Miniport (IPv6) - WAN Miniport (L2TP) - WAN Miniport (Network Monitor) - WAN Miniport (PPPOE) - WAN Miniport (PPTP) - WAN Miniport (SSTP) + {4d36e979-e325-11ce-bfc1-08002be10318} - EPSON WF-2760 Series (driver 2.41.1.0) - HP OfficeJet 3830 series (driver 20.79.1.6594) - Microsoft IPP Class Driver + {4d36e97b-e325-11ce-bfc1-08002be10318} - Microsoft-Controller für Speicherplätze + {4d36e97d-e325-11ce-bfc1-08002be10318} - ACPI-Deckel - ACPI-Energiezustandknopf - ACPI-Schalter - ACPI-Thermozone - Busenumerator für Verbundgeräte - CAD (Charging Arbitration Driver) - DMA-Controller - Eingebetteter, Microsoft ACPI-konformer Controller - Enumerator für virtuelle NDIS-Netzwerkadapter - Fn and function keys (driver 9.2.0.5) - Hauptplatine - Hauptplatinenressourcen - Hauptplatinenressourcen - High Definition Audio-Controller - Hochpräzisionsereigniszeitgeber - Intel Collaborative Processor Performance Control (CPPC) Driver (driver 1.0.0.1018) - Intel(R) Management Engine Interface (driver 1914.12.0.1256) - Lenovo PM Device (driver 1.67.16.42) - Lenovo Power and Battery (driver 10.0.154.0) - Microsoft ACPI-konformes System - Microsoft Basic Display Driver - Microsoft Basic Render Driver - Microsoft Hyper-V-Virtualisierungsinfrastrukturtreiber - Microsoft UEFI-konformes System - Microsoft virtueller Datenträgerenumerator - Microsoft Windows-Verwaltungsschnittstelle für ACPI - Microsoft Windows-Verwaltungsschnittstelle für ACPI - Microsoft Windows-Verwaltungsschnittstelle für ACPI - Microsoft-Systemverwaltungs-BIOS-Treiber - Mobile 5th Generation Intel(R) Core(TM) PCI Express Root Port #3 - 9C94 (driver 10.1.1.9) - Mobile 5th Generation Intel(R) Core(TM) PCI Express Root Port #6 - 9C9A (driver 10.1.1.9) - Mobile 5th Generation Intel(R) Core(TM) Premium SKU LPC Controller - 9CC3 (driver 10.1.1.9) - Mobile 5th Generation Intel(R) Core(TM) Thermal Management Controller - 9CA4 (driver 10.1.1.9) - Numerischer Coprozessor - PCI Standard-Host-CPU-Brücke - PnP-Softwaregeräte-Enumerator - Programmierbarer Interruptcontroller - Redirector-Bus für Remotedesktop-Gerät - Remote Desktop USB Hub - Remotedesktop-Kamerabus - Stammkomplex für PCI-Express - Synaptics SMBus Driver (driver 19.0.17.142) - System CMOS/Echtzeituhr - System Interface Foundation V2 Device (driver 1.2.0.11) - Systemlautsprecher - Systemzeitgeber - UMBus-Stamm-Busenumerator - UMBusenumerator - UMBusenumerator - UMBusenumerator - Volume-Manager - WF-1000XM3 Hands-Free AG + {50127dc3-0f36-415e-a6cc-4cb3be910b65} - Intel(R) Core(TM) i5-5200U CPU @ 2.20GHz - Intel(R) Core(TM) i5-5200U CPU @ 2.20GHz - Intel(R) Core(TM) i5-5200U CPU @ 2.20GHz - Intel(R) Core(TM) i5-5200U CPU @ 2.20GHz + {50dd5230-ba8a-11d1-bf5d-0000f805f530} - Alcor Micro USB Smart Card Reader (driver 1.7.37.0) + {533c5b84-ec70-11d2-9505-00c04f79deaf} - Standard-Volumeschattenkopie - Standard-Volumeschattenkopie - Standard-Volumeschattenkopie - Standard-Volumeschattenkopie + {53d29ef7-377c-4d14-864b-eb3a85769359} - Synaptics FP Sensors (WBF) (PID=0017) (driver 4.5.519.0) + {62f9c741-b25a-46ce-b54c-9bccce08b6f2} - Alcor Micro USB Smart Card Reader 0 - AVM FRITZ!Mediaserver - Bluetooth - EPSON WF-2760 Series - EPSON WF-2810 Series - EPSON WF-2830 Series - EPSON XP-3100 Series - EPSON14F28D (WF-2810 Series) - EPSON39988D (XP-3100 Series) - HP OfficeJet 3830 series [83A20B] - Microsoft Device Association Root Enumerator - Microsoft GS Wavetable Synthesizer - Microsoft Passport Container Enumeration Bus - Microsoft Radio Device Enumeration Bus - Microsoft RRAS Root Enumerator - Smart Card Device Enumeration Bus - WLAN + {6bdd1fc6-810f-11d0-bec7-08002be2092f} - EPSON WF-2830 Series - EPSON39988D (XP-3100 Series) - WSD-Scandienst + {72631e54-78a4-11d0-bcf7-00aa00b7b32a} - Microsoft ACPI-Kontrollmethodenkompatibler Akku - Microsoft ACPI-Kontrollmethodenkompatibler Akku - Microsoft-Netzteil + {745a17a0-74d3-11d0-b6fe-00a0c90f57da} - HID-konformes Gerät - USB-Eingabegerät + {c166523c-fe0c-4a94-a586-f1a80cfbbf3e} - FxSound Speakers (FxSound Audio Enhancer) - Kopfhörer (Logi Z407 Stereo) - Lautsprecher/Kopfhörer (Realtek High Definition Audio) - Mikrofon (Realtek High Definition Audio) + {c30ecea0-11ef-4ef9-b02e-6af81e6e65c0} - EPSON39988D (XP-3100 Series) - WSD-Druckgerät + {ca3e7ab9-b4c3-4ae6-8251-579ef933890f} - Integrated Camera (driver 5.0.18.70) + {d94ee5d8-d189-4994-83d2-f68d7d41b0e6} - Trusted Platform Module 1.2 + {db4f6ddd-9c0e-45e4-9597-78dbbad0f412} - Smartcard-Filtertreiber + {e0cbf06c-cd8b-4647-bb8a-263b43f0f974} - Bluetooth Device (RFCOMM Protocol TDI) - Intel(R) Wireless Bluetooth(R) (driver 22.120.0.3) - Logi Z407 - Logi Z407 AVRCP-Transport - Logi Z407 AVRCP-Transport - Microsoft Bluetooth LE-Enumerator - Microsoft Bluetooth-Auflistung - RoxaPlus - RoxaPlus AVRCP-Transport - RoxaPlus AVRCP-Transport - WF-1000XM3 - WF-1000XM3 AVRCP-Transport - WF-1000XM3 AVRCP-Transport + {eec5ad98-8080-425f-922a-dabf3de3f69a} - Wilfried Blankertz (Galaxy A5) + {f2e7dd72-6468-4e36-b6f1-6488f42c1b52} - Gerätefirmware - Gerätefirmware - ThinkPad T550/W550S System Firmware 1.26 (driver 1.0.0.26) cpu registers: eax = 0eb91034 ebx = 0fa32a7c ecx = 00000000 edx = 00000000 esi = 00000000 edi = 00000001 eip = 00484df2 esp = 0c7bf82c ebp = 0c7bf848 stack dump: 0c7bf82c 6c f9 7b 0c c4 4b 40 00 - 48 f8 7b 0c 00 00 00 00 l.{..K@.H.{..... 0c7bf83c 34 10 b9 0e 01 00 00 00 - 7c 2a a3 0f 58 f8 7b 0c 4.......\|..X.{. 0c7bf84c 65 4d 48 00 ac f8 7b 01 - 7c 2a a3 0f 68 f8 7b 0c eMH...{.\|..h.{. 0c7bf85c 60 76 40 00 00 0f 48 00 - 18 10 b9 0e c4 f8 7b 0c `v@...H.......{. 0c7bf86c 6b 75 40 00 7c 2a a3 0f - 14 10 b9 0e 04 63 40 00 ku@.\|*.......c@. 0c7bf87c 02 00 00 00 3a f6 91 00 - 08 10 b9 0e 14 10 b9 0e ....:........... 0c7bf88c 19 62 40 00 01 00 00 00 - 08 13 40 00 08 10 b9 0e .b@.......@..... 0c7bf89c 7b 44 40 00 00 00 00 00 - 08 10 b9 0e be 43 40 00 {D@..........C@. 0c7bf8ac 08 10 b9 0e 64 27 46 00 - 08 10 b9 0e 0d 10 92 00 ....d'F......... 0c7bf8bc 18 00 00 01 08 10 b9 0e - d4 f8 7b 0c 60 76 40 00 ..........{.`v@. 0c7bf8cc a8 e7 91 00 fc 5c a3 0f - 38 f9 7b 0c 6b 75 40 00 .....\..8.{.ku@. 0c7bf8dc 08 10 b9 0e f8 5c a3 0f - 04 63 40 00 04 00 00 00 .....\...c@..... 0c7bf8ec 02 fb 91 00 e8 5c a3 0f - f8 5c a3 0f 19 62 40 00 .....\...\...b@. 0c7bf8fc 01 00 00 00 08 13 40 00 - e8 5c a3 0f 7b 44 40 00 ......@..\..{D@. 0c7bf90c 00 00 00 00 e8 5c a3 0f - be 43 40 00 e8 5c a3 0f .....\...C@..\.. 0c7bf91c 64 27 46 00 e8 5c a3 0f - a2 1e 92 00 60 3c a3 0f d'F..\......`<.. 0c7bf92c 00 00 00 00 3a 2b ad 01 - e8 5c a3 0f 48 f9 7b 0c ....:+...\..H.{. 0c7bf93c 60 76 40 00 00 00 00 00 - 5c 55 a3 0f 58 f9 7b 0c `v@.....\U..X.{. 0c7bf94c f1 1e 92 00 e8 5c a3 0f - 74 55 a3 0f 88 f9 7b 0c .....\..tU....{. 0c7bf95c 6b 75 40 00 e8 5c a3 0f - 38 5d a3 0f e5 4d 48 00 ku@..\..8]...MH. disassembling: [...] 00484de5 inc dword ptr [ebp-8] 00484de8 3177 dec dword ptr [ebp-$10] 00484deb jnz loc_484dd4 00484ded 3179 mov eax, [ebp-$c] 00484df0 mov edx, [eax] 00484df2 > call dword ptr [edx+8] 00484df5 xor eax, eax 00484df7 pop edx 00484df8 pop ecx 00484df9 pop ecx 00484dfa mov fs:[eax], edx [...] error details: Trying to reproduce the issue reported in MantisBT ID 0002517 with reduced GPX file 2023 04 08 Nodic_mod.gpx bugreport.txt (28,231 bytes)

zava 2023-04-10 13:24 reporter ~0004732	Thank you WilfriedB... even stranger... What "non sync" message does GS give when you are unable to sync? I tried all sort of attempts... I "injected" the gpx code of the first active log into a "working" gpx file... As a result, the track and trackpoints ARE displayed corretly by all programs (routeconverter, GS, CompeGPS...) but GS seems to IGNORE this track. It is listed as LAST , although I inserted it sa first), which is correct (assuming they are reordered according to taken date), but it is IGNORED by the sync process (I get a "best sync" with 13 days error (which is correct given all OTHER timestamps in the file), there's no longer mention of 1899 year of taken date, but that particular track segment is ignored (according to it's taken date, it shpuld correctly sync, or just fail of a couple hours, if timezone not correct. Instead, it is IGNORED... Out of ideas...

WilfriedB 2023-04-10 13:40 reporter ~0004733	@zava in both cases, when I use the original GPX file with tracks selected by default, as well as the reduced GPX I get the normal "No GPS dat message ..." I noticed the "report" button for the first time ever (my ignorance), So clicking it, I see a time difference of -1:00:11. Strange enough, this time, I did not get a burg report, though. grafik-4.png (298,918 bytes)

zava 2023-04-10 13:50 reporter ~0004734	Tried some more: downloaded tracks from GPS unit using Garmin Basecamp (newer than MapSource). Saved as (attached) gpx file. Again, the xml code seems fine. But, when loaed in GS, two spurious waypoints ("Noname" and "Active log 397" appear, which are NOT in the gpx code... Upon trying to sync, GS complains that "no coordinates with time information are in the file (while GS and other programs DO list all the correct trackpoints WITH date stamps... Crazy... I am also attaching a "cleaned up" gpx file where the spurious watpoints were deleted (using GS), but with the same result (attached screenshot). No date time information_BASECAMP.jpg (384,297 bytes) 2023 04 08 Nodic_Basecamp.gpx (111,136 bytes) 2023 04 08 Nodic_Basecamp_spurious WPTs.gpx (165,655 bytes)

zava 2023-04-10 16:09 reporter ~0004736	Hello WilfriedB, your result is in fact qualitatively different from mine, in that it is a CORRECT result! In your case, possibly due to an uncompensated time difference or time zone, GS correctly FOUND time stamps in the gpx file and matched them with the image time stamp; sync still failed, but if you introduced the neccessary time correction (1:00:11), the sync would most probably succeed. In my case, and even with the very same file, GS FAILS to find any time information in the file, although it is present and GS correctly lists and displays it! A totally different result! So there is some difference in the gpx file, but also a major difference in GS behaviour in my environment vs. yours... Very informative insight, thank you...

WilfriedB 2023-04-10 16:51 reporter ~0004738	@zava correct, I finally got it to work, after several attempts to correct the time stamp of the jgp. One key point is the fact that the track list shows the UTC time, whereas the thumbnail shows the local time. Pleas see my screen shots. grafik-5.png (12,092 bytes) grafik-5.png (12,092 bytes) grafik-6.png (91,224 bytes) grafik-6.png (91,224 bytes) grafik-7.png (89,418 bytes) grafik-7.png (89,418 bytes)

zava 2023-04-10 20:03 reporter ~0004739	Hello WilfriedB, definitely GS is working fine on this file on your machine. On mine I definitely keep getting the "1899" spurious dates and other erratic behaviours... On the other hand, I tried GPicSync: in case you don't know about it, it's a fairly limited rogram, not too user friendly and not at all comparable to GS, but it does process the SAME gpx to geolocate the images correctly... Same gpx, same images, different (correct) result... Definitely: - something is "strange" with that gpx file (other files don't cause GS to malfunction - something is also strange with GS (in my environment) - whatever it is, it does not seem to affect GPicSync... This said, I have no way to get deeper into WHAT is going wrong. Last test, I may try GS on a different machine... Thank you for your help!

Date Modified	Username	Field
2023-04-10 00:09	zava	New Issue
2023-04-10 00:09	zava	File Added: Sync settings.jpg
2023-04-10 00:09	zava	File Added: Sync report.jpg
2023-04-10 00:09	zava	File Added: 2023 04 08 Nodic.gpx
2023-04-10 00:09	zava	File Added: Z4085376_lr.JPG
2023-04-10 08:59	WilfriedB	File Added: grafik.png
2023-04-10 08:59	WilfriedB	Note Added: 0004727
2023-04-10 09:22	WilfriedB	File Added: grafik-2.png
2023-04-10 09:22	WilfriedB	File Added: grafik-3.png
2023-04-10 09:22	WilfriedB	Note Added: 0004728
2023-04-10 11:16	zava	Note Added: 0004729
2023-04-10 12:03	zava	File Added: 2023 04 08 Nodic_mod.gpx
2023-04-10 12:03	zava	File Added: No time date.jpg
2023-04-10 12:03	zava	Note Added: 0004730
2023-04-10 12:54	WilfriedB	File Added: bugreport.txt
2023-04-10 12:54	WilfriedB	Note Added: 0004731
2023-04-10 13:24	zava	Note Added: 0004732
2023-04-10 13:40	WilfriedB	File Added: grafik-4.png
2023-04-10 13:40	WilfriedB	Note Added: 0004733
2023-04-10 13:50	zava	File Added: No date time information_BASECAMP.jpg
2023-04-10 13:50	zava	File Added: 2023 04 08 Nodic_Basecamp.gpx
2023-04-10 13:50	zava	File Added: 2023 04 08 Nodic_Basecamp_spurious WPTs.gpx
2023-04-10 13:50	zava	Note Added: 0004734
2023-04-10 16:09	zava	Note Added: 0004736
2023-04-10 16:51	WilfriedB	File Added: grafik-5.png
2023-04-10 16:51	WilfriedB	File Added: grafik-6.png
2023-04-10 16:51	WilfriedB	File Added: grafik-7.png
2023-04-10 16:51	WilfriedB	Note Added: 0004738
2023-04-10 20:03	zava	Note Added: 0004739

View Issue Details

Activities

Issue History