In a dream last night, “we”, probably meaning all of surviving humanity, were surrounded by dog like creatures that were immortal, unkillable and unstoppable. And they hated us. There was a suggestion that they could sense our finite lives throughout their infinite ones whatever that means.
Every time they got into a room or a field or any other space, we’d barricade it off and consider it permanently lost, and anybody in that space was lost. There were scenes like in sinking war ships where we could see the people but we didn’t dare open a door to get them in case the dogs got to the door before we could close it again.
There was a very claustrophobic feel of the world shrinking as each space was lost and no chance of ever making gains.
At some point I had volunteers opening a door to make a small enclosed area inside the lost space, kind of like the old video game Qix, but I think I added that note of hope in a semi waking state rather than in the actual dream.
I can’t imagine why I’d dream such a hopeless dream in the middle of a global pandemic and a nation hurtling towards dictatorship.
One of the things I liked about the Garmin VIRB 360 camera is that they actually say “Constantly record for more than 1 hour on 1 charge5 — without overheating” on their product page, which shows a lot more concern for continuous recording than GoPro. They also sell a cradle that gives external power. So I thought I’d be all set for the sort of 2 – 3 hour recordings that have been my holy grail since I got into race videos.
I’ve been running various tests with different combinations of external batteries, and never seemed to get more than 1.5 hours. And today while running a test, I just happened to be looking at my camera when I displayed a “High temperature alert” on the screen just before it shut down. Well, again, I’ve got to give them props in handling high temps better than GoPro – GoPro usually don’t even give you a beep before they shut down for high temps.
But I’m still left with the quandary on how do I keep my cameras from overheating. I’ve thought about covering my camera with tinfoil or attaching a computer CPU heatsink, but a 360 camera doesn’t give you much in the way of non-vital surface to attach things to. Freeze it? My Fenix can act as a remote for it, maybe I could just turn it off in the middle of a race when nothing much is happening?
I decided to make a jump and bought a used Garmin VIRB 360 camera. I was going back and forth about this camera, because it’s several years old and there’s been no hint that Garmin is considering updating it or even improving the support (there are posts in the forums complaining about bugs in Garmin VIRB Edit that have been unfixed since 2016).
But there are two extremely important factors that led me to buying it:
They advertised that it won’t overheat even with an hour’s continuous recording. Considering how many times I’ve lost a GoPro early in a race due to overheating, that’s a good thing to see an action camera care about. GoPro seems to feel that action cameras are meant to record short clips like a downhill ski run or a sky dive, not an hour or more of continuous action.
They make a “powered tripod mount” that allows you to connect your camera to an external USB battery in a water resistant manner.
There’s another cool feature I didn’t know about until I got it home – when it’s paired to my Fenix fitness watch, it will start recording when I hit start on an activity on the Fenix automatically. Also I get a warning on my watch when its battery is getting low. If I get the external battery working, I might prefer not to wait until I hit start to start recording, but it seems like this is a good way to record as much of a race as I can.
I have done a few shoots with it, and so far it seems to give just about exactly an hour of video even with GPS turned on and external sensors and devices paired to it. The video is pretty good quality, and I like the idea of a 360 degree video for seeing all the action in a race.
You should be able to move the viewport around by clicking and dragging or touching and dragging, or even moving your device around if you’re on mobile.
I’m still not sure if I’d rather put up 360 video on YouTube people and hope people see which direction the cool action is happening, or if I’d like to “direct” it.
Here’s a 360 video where I use the “reorient feature” to point the default view where I think the action is, but the viewer can move the viewpoint around manually, and then when I reorient it might get confusing.
Again, you can move the viewpoint around manually, but if you don’t you can see that I’ve tried to move it myself to track things of interest.
And here’s pretty much the same “reoriented” video, but converted to flat so the viewer can’t mess with the viewpoint.
In this one I still track points of interest, but you can’t drag the viewport around to look at things other than what I want you to look at.
The camera records what Garmin calls “G-Metrix” data – i.e. the speed and distance and heart rate and other data that I love to overlay on my videos. By recording it in the camera instead of taking it from my Fenix watch, it simplifies the process of getting the data on the video, but there are a couple of major problems with it
VIRB Edit lets you plonk a gauge on the screen, but it stays in the same place relative to the view, rather than to the viewport – i.e. when you move the viewpoint around, it scrolls off the screen. I’d rather there was an option to keep it static in the viewport as you move the viewpoint around. And this is still true even if you’re using what they call “Hyperframe” to convert the video to flat. You’d think once you made the video flat you could use gauges the way you do on a normal flat video.
There are a different set of gauge templates for 360 videos than for flat videos, and when you use Hyperframe, they still only show you the 360 templates.
VIRB Edit had terrible editing tools. You’d think the difference between doing “trim right” in VIRB Edit and Final Cut Pro X (FCPX) wouldn’t be huge, but Final Cut Pro has keyboard shortcuts as well as “blade” and “blade all” as well a the trims. When it comes to transitions and titles the differences are night and day – there are 156 transitions in my FCPX (some are 3rd party) and 5 transitions in VIRB Edit, and hundreds of titles in FCPX versus 1 in VIRB Edit. Add to that the fact that VIRB crashes with shocking regularity – like 3 times when trying to do that flattened video before I gave up and did it in Final Cut Pro X.
So yes, I can edit the footage in Final Cut Pro – I’m not sure if I can grab it directly off the SD card or if VIRB Edit has to do something first, but I grabbed a video out of the ~/Movies/Garmin directory and dropped it in to FCPX and it recognized it as a 360 video and I was able to point around and do 360 stuff immediately.
So now I’m trying to figure out what my future video workflow will be. If I’m going to always flatten the video, I might keep doing what I have been doing and making a blue screen video with gauges in VIRB Edit and overlaying that on the flat video in FCPX. But if I’m going to output 360 videos, I could stick the gauges down near my boat, and output the full video with the gauges in VIRB Edit then bring it into FCPX for cutting, adding titles and transitions.
Maybe I need to do both for a while and see what people like.
I went out for a paddle today, and had both my Forerunner 920XT and my Fenix 6X on my foot strap, and both set up to “Race an Activity” with the same 10km activity selected. The course I was racing had 57:08.3 as the base time. I had my GoPro so I could grab some shots of both screens. I am doing this because I can’t for the life of me figure out what some of the fields are on the Fenix. I know what fields I need on the 920XT, but the equivalent fields on the Fenix are either in different places, or they show utterly insane values.
This picture is quite early on in the paddle. The 920XT is showing a Estimated Finish Time of 55:21, and Time Ahead of 0:11. So it thinks I’m going 11 seconds faster than the activity I’m racing. Since the difference between the target time of 57:08.3 and the estimated finish time of 55:31 is more than 11 seconds, I assume it means I’m 11 seconds ahead right now, but if I keep it up I’ll finish in 55:21. On the Fenix side, the Estimated Finish Time is 1:01:23. I have no idea why it thinks I’m 6 minutes slower than the 920XT. But here’s the insane part: The Time Behind is showing 42:07:48. WHERE THE FUCK IS THAT 42 HOURS COMING FROM!!! Even if the 42 represents something other than hours, if the time behind is 7:42, I’m trying to figure out what that mathematically relates to, because the estimated finish time is only 4:14 behind the goal time, not 7:42.
Another screen shot around the same time. The top one is labelled “ETE”, I think that’s time remaining. The middle one is distance remaining (9.49 km, so about 500 meters into the “race”). I’m not sure, but I think the bottom one is actually an estimate of the clock time when I’m expected to finish.
This is further along. I assume the prominent number in the middle is the estimated total time? The top one is distance remaining (5.47 km). That syncs up nicely with the 920XT saying I’ve completed 4.53 km.
This is seconds after the previous one. The Fenix is showing an utterly useless map. If there’s a way to zoom this in so it would be more useful, I haven’t discovered it.
And a few seconds later. The Fenix is showing the same distance remaining, although this time in the prominent middle position. The top field is, as I mentioned in the second screen shot, apparently the estimated time to completion. The bottom one is the estimated clock time at completion. No idea why I’d want to know that.
Here’s that baffling “Time Behind” again, still with the strange “42”. The estimated finish time at the bottom of 59:20 lines up OK with the 58:12 earlier in this second set of pictures because I had to stop paddling to take these so I’m getting slower with each shot. But again, even ignoring the “42” in the top field doesn’t make sense, because again, 59:20 is 2:11 slower than the goal time, not 6:39.
I wish there was some documentation on what these fields were, and I wish there was a way to customize them.