![]() This was before I made any changes in Preferences. I loaded up a new SD card with today's dashcam footage and everything was OK, the video showed, speed in the video window, and location on Google Map. I did the above and then installed 3.8.0 (Intel). I was lucky, I found my registration code from December 2016! I will be investigating this further and come to the bottom of it. Although both Intel and M1 versions of 3.8.0 work for me, I suspect one of these differences is the culprit that's causing you grief (probably the last item I mentioned). That is not only a major change in CPU architecture, but also a change in macOS version (Big Sur vs Mojave), a change in Xcode compiler version, a change in build process (Intel+arm64 vs just Intel), a change in auxiliary library builds, and a change in application signing, bundling, and entitlement process. First of all, I moved the entire project from a 2015 MacBook Pro (Intel) to a 2020 MacBook Air (M1). ![]() ![]() But v3.8.0 is different than earlier versions in a few significant ways. The actual source code differences between 3.7.0 and 3.8.0 are very very minor. Not to bore with details but for those that are interested, here's little background info about Mac Dashcam Viewer v3.8.0. Then try loading your videos again and see if everything is back to normal. If you're using a registered version of Dashcam Viewer, yes, you will need to re-enter your registration code again (I can provide this to you if you can't find it). This clears out Dashcam Viewer's settings and resets to defaults.
0 Comments
Leave a Reply. |