I learned of a little airstrip in a rural section of Big Creek in Idaho called Dewey Moore with about 700 ft of usable runway (45.149770,-115.077320). These are my semi-successful landings in Microsoft Flight Simulator (MSFS) at Dewey Moore in the CubCrafters X Cub. I am NOT a pilot, just a flight simmer (and a novice at that).
Monday, November 14, 2022
Tuesday, July 13, 2021
I've recently been exploring the free version of DaVinci Resolve as an alternative to Premiere Pro for my main video editor on Windows 10. I was trying to edit some footage I shot on my iPhone 12 at 4K (3840 x 2160), 60 fps. However, when I imported the videos into DaVinci Resolve 17, it showed the video clips as "offline," yet the audio would still play back. This is because newer videos shot on iPhone commonly use the HEVC (High Efficiency Video Coding, or H.265) format. While macOS natively supports the HEVC/H.265 codec, it is not natively supported by Windows 10 or DaVinci Resolve out of the box.
I found several suggestions in forums suggesting that in order to get DaVinci Resolve and Windows to properly see videos shot on iPhone, you should re-encode them using another codec (like H.264, DNxHD). There were links to all sorts of shady video conversion tools published by untrusted developers. There were also recommendations to transcode the videos using FFmpeg or Handbrake--both acceptable alternatives. But, there's a simpler way and it only costs $0.99.In the Microsoft Store, there is a utility called HEVC Video Extensions. After installing this utility, Windows 10, and DaVinci Resolve will be able to read and encode HEVC/H.265 videos shot on iPhone without the need to convert to another format. Also, depending on your hardware, the codec may support hardware decoding, which will provide accelerated performance when editing in DaVinci Resolve on Windows 10. Hopefully that helps someone else out there looking for a simple, elegant solution to this issue.
Friday, April 30, 2021
Recently I wanted to configure a simple script to send an email notification any time a particular Windows 10 machine rebooted. After some quick googling, I whipped up a PowerShell script and then set it up to run in Windows Task Scheduler whenever the system starts up.
But, running a PowerShell script as a scheduled task in Windows isn't so simple. First, you need to invoke the simple PowerShell executable (easy to do as powershell.exe is in the Windows path already), and second, you need to specify what PowerShell script to run using the -File argument. After configuring both of these, I still could not figure out why it was throwing the error 0x1 when trying to run the PowerShell script. Apparently, this is due to a PowerShell execution policy that prevents the script from running (for security reasons). Thankfully, Stack Overflow user briantist posted a nice solution to this issue. All you need to do is configure the task with -ExecutionPolicy Bypass in the arguments when setting up the task:
Don't forget to also add -File "C:\Path To Script\MyScript.ps1" to your arguments to reference the actual script when invoking PowerShell in your task.
It took me days to figure out why I couldn't get this task to run, but thankfully, Stack Overflow came through, and I was able to get it to run. I hope this helps someone else out there who may be getting the 0x1 error when trying to run a PowerShell script as a Scheduled Task in Windows.
Sunday, March 07, 2021
Tuesday, December 29, 2020
Tuesday, November 10, 2020
Monday, August 10, 2020
I have spent months troubleshooting an issue that I was having when trying to import videos (MOV/HEVC) from my iPhone to my MacBook. I experienced the issue on three different MacBook Pro machines, and four different iPhone models (from the iPhone XR to the iPhone 11). The issue is that when using the Image Capture app on macOS to import videos directly from your iPhone, it aborts and randomly shows the following error, "The operation couldn't be completed. (com.apple.ImageCaptureCore error -9956.) (-9956). An error occurred while importing. The item [filename] was not imported":
I spent days troubleshooting basic stuff with Apple support, and was escalated a few times to senior specialists, but never could get anywhere. I re-opened the case after still seeing the error with a new MacBook Pro and new iPhone. Here are some settings that an Apple support rep suggested that I try that actually resolved the issue for me for the time being. Here's what you need to do:
- On your iPhone, go to Settings -> Camera -> Formats, and select "Most Compatible"
- Then, on your iPhone, go to Settings -> Photos, and select "Keep Originals" under the section "Transfer to Mac or PC"
After completing the steps above, try again to import the video using Image Capture, and the videos should transfer quickly and without error. Hope that helps someone who may be struggling with the same issue.
Tuesday, November 06, 2018
Monday, October 29, 2018
Monday, March 12, 2018
Friday, January 26, 2018
The following clip is from the YouTube channel Hushin, which features hunting, fishing, and outdoor activities videos. Eric Chesser, part of the HUSH crew, is struggling to find a deer and is feeling pretty low. But, he comes to the realization that even though he's having a difficult and frustrating hunt, there are a lot worse things than having a bad day hunting. His attitude completely shifts. Eric says, "We do all go through hardships...Be kind, be humble...be positive, give back when you can--it will make you feel better than anything ever will." I love this perspective--it made me want to be more grateful and positive when facing difficult challenges.
The best part is from 7:06 to 9:47: