GoPro Hero 7 hypersmooth stabilisation not working with certain default mode option [ New ]

[epicbluff05215]

Hello,

I had the video options set to 2.7k with 60 fps. I also turned on the 'quick capture' option. So everytime I press the button on top of the GoPro, my camera starts recording in video mode, which is what I want. The hypersmooth stabilisation was working at this point.

Later on I set the default mode option, for when turning the camera on, on Timewarp mode. So every time I turn my GoPro on (with the button on the side), the default capture mode is on Timewarp.
This option, for some reason, causes my GoPro to not use Hypersmooth stabilisation anymore for video recording.

I don't know how this is caused and would like to hear if more people have this problem.

[shawnf]

With the Timewarp mode there is no stabilization option.  When viewing the Timewarp Video Settings, select the speed and if you select 5x it states to the left of that "Speed up and stabilize your video by 5x" same thing for 2x and so on.  There is nothing wrong with your camera, there is simply no option to choose the stabilization type.

[fishycomics]

So waht you just said you defaulted to timeWarp. and when switch to video the Hypersmooth is no longer  working

[epicbluff05215]

Yes this is what's going on.
I set my GoPro settings back to factory settings and then there are no problems.

Again I set the default mode on Timewarp and then with video mode (2.7k, 60 fps) the Hypersmooth stabilisation is not working again. Really strange bug.

Please try to set the same settings on your GoPro hero 7 to see if you guys have the same problem.

[epicbluff05215]

This is not the problem. What @fishycomics states is the problem I have.

[fishycomics]

Right I am  trying to understand first.  Set H7  default mode to timewarp. set up my  video settings to "

2.7K

FOV ???
EIS to Auto (hypersmooth)

Protune on or off?  On at what other settings used

Uncertain if Audio is  auto, wind, stereo?

Or are we saying Timearp has no stabilzation?   

why I am trying to understand.  Coffee in hand

[epicbluff05215]

Default mode: Timewarp (4k, 10x, wide)

Video settings:
2.7k
60 fps
Wide view
Protune: off

Quickcapture: on (so GoPro is recording video when using the top button)

The problem is; Timewarp is working without a problem.
Only with the settings stated above, the video recording doesn't use hypersmooth stabilisation.

[fishycomics]

---

@epicbluff05215 wrote:
Default mode: Timewarp (4k, 10x, wide)

Video settings:
2.7k
60 fps
Wide view
Protune: off

Quickcapture: on (so GoPro is recording video when using the top button)

The problem is; Timewarp is working without a problem.
Only with the settings stated above, the video recording doesn't use hypersmooth stabilisation.

---

I did a sample based on the info you  gave. did you forget to say what yourlow level was on or off, why I asked for each setting,   Imagine of the issue lies in preference gps On?   just saying.  I know its difficult to look at the camera and   write it down Lol.. stand by for my sample 

2.7K FOW W EIS HS on  low light off, gps off, VC off. QC used and Mode on used.

Timewarp 4KW 10X default, Mode on time warp , then  swiped to  video and  sampled there as well.  If I left out a detail let me know.

[epicbluff05215]

Haha okay here my settings again;

Video settings:
2.7k
FOV: W
EIS: HS
Low light: on

General settings:
GPS: off
VC: H.264 + HEVC
QC: Timewarp

Timewarp settings: 4k, Wide, 10x


The problem:
When I use QC, which starts video recording, the Hypersmooth stabilisation does not work.

[fishycomics]

See I asked how many times I have already made the video si  its not there if asked  now I have to do it again because we yes I left off low light go figure (ha ha ha)   so could low light be hte issue?  

see if your QC = Video it would not be timewarp.   its video only and timelapse photo only not timewarp.

[epicbluff05215]

Yes I had low light turned on, so that might cause the problem.

[sweetcreek58382]

I can confirm I have the same issue reported here as well.  I tried with both 1080 and 2.7k.  I have protune turned on and ISO is set to 800.  So my low light setting is n/a.  Based on the icon though, it is turned on.  If my default mode is video, there is no problem at all.  However, if my default mode is time-warp.  And I use quick capture to record videos, there is no hypersmooth.  This is indeed a strange bug.  I will test it out with a different ISO so I can turn off low light as @fishycomics showed in the video to confirm tomorrow.  Will report back.

[epicbluff05215]

Please also test it out with protune turned off, with lowlight turned on automatic.
With these settings the Hypersmooth is also not working with video recording. (Default camera mode is on Timewarp again)

[fishycomics]

I'll also do the test again   later  

[fishycomics]

2.7K60f fov wide low light auto  Hypersmooth Auto,  default timewarp, use quick capture  desables Hypersmooth confirmed. now how   is gopro going to handle this.  some one has to address htis to gopro   who do we call  Ghost busters????

see video  anyone else can try it out and see  for themselves.   this must be sent int to gopro not your camera.

[sweetcreek58382]

More like 'GoPro busters' is what we need.  I did a round of 1080 with protune on and off and low light auto vs off on the commute to work.  i haven't check the footage yet as I am at work.  I will do another round with 2.7k tonight on the commute back home.  However, as @fishycomics already confirmed, I am pretty sure my test will just be a validation of the bug.  Should be easy fix for GoPro with a firmware update if they care to address it.

[sweetcreek58382]

Reporting back.  I don't think it's related to low light or not.  I did the following tests:

Test 1:

1080; 60fps; FOV wide; Protune on; Shutter auto; EV 0, WB auto; ISO Min 100; ISO Max 1600; Sharpness High; Color GoPro;

Raw Audio off; Mics auto; Low light off

Test 2:

1080; 60fps; FOV wide; Protune on; Shutter auto; EV 0, WB auto; ISO Min 100; ISO Max 1600; Sharpness High; Color GoPro;

Raw Audio off; Mics auto; Low light auto (on)

Test 3:

1080; 60fps; FOV wide; Protune off;; Low light off

Test 4:

1080; 60fps; FOV wide; Protune off;; Low light auto (on)

Test 5:

2.7k; 60fps; FOV wide; Protune on; Shutter auto; EV 0, WB auto; ISO Min 100; ISO Max 1600; Sharpness High; Color GoPro;

Raw Audio off; Mics auto; Low light off

Test 6:

2.7k; 60fps; FOV wide; Protune on; Shutter auto; EV 0, WB auto; ISO Min 100; ISO Max 1600; Sharpness High; Color GoPro;

Raw Audio off; Mics auto; Low light auto (on)

Test 7:

2.7k; 60fps; FOV wide; Protune off;; Low light off

Test 8:

2.7k; 60fps; FOV wide; Protune off;; Low light auto (on)

The video footage are actually hard to tell as I ride on the street and it's relatively smooth.  However, I have my camera mounted in a fix position on the bike with the frame locked down.  I remove the camera by taking it out of the frame so the angle of the camera never changes.  In all of the above tests, my camera pick up the tip of my aero bar and they are fixed in place in the footage.  Which is the same as if I do normal video recording without stabliziation.  When I record normal videos with stablization on, the camera crop off 10% around the edges and my aero bars are not in any of the stablized footage.

This leads me to believe that any time the camera default mode is set to time-warp, if you use QC to record videos, you loose the hypersmooth stablization.  GoPro needs to fix this!

Before other jump in and question why I would default to time-warp and yet use QC to record video.  That is because my camera is mount in front of the handle bar under my gps.  So I cannot easily look at the screen to check what mode I am in while I am riding.  Having this setup allow me to record video and time-warp easily.  I use QC to record video.  Where as I would turn on the camera and hit record to do time-warp.  At least that's my usecase.  Yes, I can work around this but this is clearly a bug.

[fishycomics]

@sweetcreek58382 @epicbluff05215 @shawnf  

In order to address this gopro needs to be contacted,  @ (Mentioned)  so lets get a Team member in here.   ANd see that they'll  pass it to a  Team to find the naswer later down the road......  

[sweetcreek58382]

@aragon1006  I think here is a team member/mod of GoPro.  Let's see if we can get their attention to address this issue. 

[fredc58037]

Mine also does this. I think it's a firmware bug (I have 01.51) because nothing mentions this in the OM.

so here's what mine does:

If quick capture default is Timewarp, with the camera turned off the quick capture button starts recording normal video using all the last settings except hypersmooth is deactivated. If camera is turned on first, It comes up in Time warp mode. If you press the power button again to select normal video then it will record using last settings and Hypersmooth is active. 

If quick capture default is normal video then Hypersmooth works fine when using quick capture with camera off. 

[fishycomics]

Mods were on today so that means they did not look into  this thread.

[sweetcreek58382]

@fredc58037That is exactly the behavior/bug we are seeing.  Thanks for confirming too.

[mariustanya]

Hello Everyone, 

Thank you for the feedback. Appreciate you doing the tests and presenting your results here. We have reported the matter to the team so they can replicate the issue and see what needs to be done to get this corrected. To sum up, when TimeWarp is set as default mode, resulting recording via QuikCapture does not have HyperSmooth stabilization. This is regardless of Protune or Auto Low Light settings, as well as video resolution used. Is this correct? Also, has anyone been able to check if the same observation holds after a manual firmware update? 

Thanks, 
Marius

[fishycomics]

@mariustanya   My camera was recently updated, so I feel there is no need  for me to  again update firmware again   the  manual update the Op can do for you as this is  not on my Priority list, but wil lget to another test when weather permits as well daylight.  Wil ltry tomorrow again with an update and settings..

[mariustanya]

Got it. Thank you, @fishycomics. We'll be watching out for replies on this thread then. But the issue has already been reported. I will post for updates once I hear back from the team. 

[sweetcreek58382]

@mariustanyaMy camera is also at the latest 1.51 firmware.  And what you summarized is correct.  Please let us know once you have a solution.  Thanks.

[epicbluff05215]

Thank you everyone for doing the tests and thank you @fishycomics for making the video. I couldn't make a video right now because I am travelling at the moment.

It's good the problem is recognized along other people and hope GoPro fixes the bug!

[fishycomics]

---

@epicbluff05215 wrote:
Thank you everyone for doing the tests and thank you @fishycomics for making the video. I couldn't make a video right now because I am travelling at the moment.

It's good the problem is recognized along other people and hope GoPro fixes the bug!

---

NP  I am going  the extra mile on this (old saying) and lets hope to hear what our Mod, and the Team in charge are going to say if they say anything.  so stay tuned for another video that hit me after I retired last night.

[sweetcreek58382]

I did 2 videos recording with the same configuration of default mode timewarp and recording using quick capture.  It looks like the reported problem of not having hypersmooth in the videos are resolved now with the 1v.61 update.  Please confirm and verify.  Thanks.

[epicshore7076]

same here, hero7 black:

NO HYPERSMOOTH on 1.61 at all while launching VIDEO (4k 60fps) with the quick capture button on the upper right side.

Preset is timewarp.

PLEASE FIX.

[troyg75706]

I'm seeing this problem but it only happens on 2.7k@60fps.  My default mode is video, firmware 1.61

https://youtu.be/D9p1Nf1nQVU

[mariustanya]

Hello @troyg75706. There has been another update on the HERO7 Black firmware. Make sure that your camera is updated to the latest firmware version which is v1.70 and observe again. Let us know how it works out. Thanks!

[troyg75706]

Looks like the new firmware (1.7) fixed the issue : https://youtu.be/VGQTURb9hMY

[mariustanya]

Awesome! Thank you for posting back to confirm resolution, @troyg75706. Great to know that the issue is resolved.