Slalom.Steve

@ColeGiacopuzzi Ah cool, I think you'll be quite happy with it! I've gotten several reports now that with the 14 Pro and 15 Pro, you actually can use the main rear camera (and possibly that it's now inverse and the selfie camera is the shaky one lol), so try both before deciding.

@Mart Easiest and excellent solution is get a Ski-Doc Orbit, use your phone with a holder like this, and record using the PylonCam Pro app. @ColeGiacopuzzi - Are you using PylonCam Pro? What model iPhone? I ask just cause you're getting more shake than you should. Unless it's a 14 Pro or 15 Pro, I'm guessing that's the rear camera? You'll get much better stability using the selfie camera.

@ironhorse @FishFreq I can assure the top minds in both the private and public sector are working on this as we speak. 😂 In the meantime, just released a new update: 1. The zoom setting now saves and reloads even if you completely close out of the app, as requested by @swbca and @Stathis Ventouris 2. The zoom indicator is now more legible (larger font, black text on white background) 3. Removed the "Flash" option from settings. I had put it in just cause it's an option on the native Camera app, but I can't think of any time someone would want to use this app with the camera light on.

@braindamage 99.9% sure the issue is that you have selected for video mode HD120. This records in Full HD (1080p) at 120 frames per second. Apple defaults the playback of 120 fps videos to slo-mo. This is the same as if you go to you native Camera app and select the "Slo-Mo" mode and record a video. Slow motion playback is really the purpose of 120fps though, so if you're just watching back full speed you'd probably be better served at 60fps. You can still adjust where a 120fps video goes into slo-mo though (including not at all). Here's a video showing how.

@Golfguy Hmm, are you able to adjust the zoom in the standard iPhone 'Camera' app? It's the same gesture there as in PylonCam. This isn't problem-specific, but first thing to always try for tech problems: Make sure your iOS is up-to-date, delete and reinstall the PylonCam app, and restart your phone.

@KelliK - What speed trigger do you have the app set at? For 32mph skiing, it should be at a 30mph trigger at most, but try it down to 28mph or even lower if it's still cutting off video.

@Golfguy Two finger pull/drag on the screen.

For now, if you set a zoom in PylonCam, then go back to your home screen or another app but don't actually "close/quit" the PylonCam app (ie it's still in the background), it saves the zoom setting when you go back to PylonCam. PCP (experimenting with an acronym lol) doesn't do any Background App Refresh activities (it doesn't use data or battery or anything) when it's not active, so you could conceivably just never actually close the app and always have your zoom setting saved. But getting a "permanent" zoom lock is on my list of possible future upgrades as well!

@swbca - The fact that the selfie camera is shaky and the rear camera is stable is exact opposite of what I'd expect, but I don't have access to a 14/15 Pro, and Apple did institute "Second-generation sensor-shift optical image stabilization" on the 14 Pro and 15 Pro (but not the regular 15), so maybe they finally got it figured out! (and then maybe moved the old, shaky optical stabilization to the selfie camera lol - they don't seem to say anything about stabilization with the selfie camera). If so, that's even better though because the main rear camera will definitely be higher quality than the selfie camera. That screenshot certainly looks nice, particularly given the zoom! @Shell - Just following up on the shakiness you experienced as compared to Wakeye. Just in case you hadn't seen, the stabilization has been fixed/improved in the latest update and it's quite smooth now! Version 1.0.4 - Give it another try and let me know!

Fastest dismount I dun ever seen 😆 Hazlewood funny.mp4 "When you took a second set even though you told your wife you wouldn't." "When they told you the resident lake gator lives under the start dock."

@Golfguy So like any other app, Apple is supposed to put up a Notification badge on your App Store icon, then you'd click into the App Store and see which apps have updates available, and you click to update them. I imagine you've done that before with other apps. For some reason, it seems like that's not happening with PylonCam Pro, so I just sent a support ticket this afternoon to Apple to sort it out. Maybe it's just on a 24-hour delay or something? BUT, in the meantime, if you go to the App Store and manually search for "PylonCam Pro" again, you should see a button that says "Update" instead of "Open", which if you click will get the most recent version onto your phone.

@mike_mapple - The maximum setting is 40mph right now. I also recommend you set it to 2-4 mph below the speed you're skiing, to make sure it captures everything. ---- Ok, big update news! I just published a new version (1.0.4) that improves the image stabilization. Due to the un-changeable physical/hardware stabilization on the Rear camera (discussed above), in this new version Rear video will likely still be shakier than Selfie video, but compared to older versions of the app, the new-version Selfie video will now be more stable than the old-version Selfie video, and the new-version Rear video will now be more stable than the old-version Rear video.

@BGrow76 If I do one, it won't be for a little while still, sorry!

Tagging some other folks who've expressed interest in the past: @Wish, @skiermk, @BGrow76, @Bbrandau, @nate93, @sunperch, @DanE, @GWaterski, @C5Quest, @Zman, @greghayes, @bkreis, @roda, @nautique1228, @Stathis Ventouris, @ral, @Inboardfix, @SkiRV, @CReckard, @switchbackr, @MattW, @RAWSki, @BobF, @Laz, @aupatking, @Golfguy, @Indyskier, @OK_SKIER, @igkya, @ToddA, @Waternut, @lw_moskier, @Alberto Soares, @TLeach, @lakeho26, @motoskier, @gator867, @Mastercrafter, @JackQ, @mac, @MickeyThompson, @darinmontgomery, @mrawle, @LanceHCook, @Beezer, @MarkTimm, @Sunapee, @tjm, @jercrane, @cp, @Vernon Reeve, @Stefan

@mbabiash @Shell - Alright, that bug has been fixed in the just-released version 1.0.3