Simon,
I just watched the video again, at 2:30(ish) I see where you were descending (rapid, probably due to seeing the oscillations and wanting to get it down quickly). I don't have any video of mine doing this act, but I have encountered this same act nearly every time I've made a rapid descent. Once again, I believe it comes down to the settings. I'm not OVERLY willing to try mine in a rapid descent (Tarot), but I"ll try and record my Disco doing it tomorrow (only because I've done zero-throttle descents and I know I've got it set at a comfortable level where it will maintain self-level).
In the instance you are referring to (2:30) I really believe that the settings are too high, granted, not exactly knowing how the settings impact the results, it could be they are too low (you mentioned 100's previously and are not much higher). I look at it like this, you are giving the NAZA it's "Left and Right limits". Telling it how far it can go in either direction. If they are too wide (figuratively) then it may respond too slowly (the aircraft will pitch/roll too much to allow the motors/props to recover it), where as if it were set too narrow it would be like a professional ping-pong competition, the FC is slamming the motors full throttle (left/right or up/back) to attempt to recover/keep the craft level, these oscillations become too great/fast that eventually when one side spools up and creates thrust, the FC is already behind the power curve (one reason why people are flocking to the NAZE32 FC) and the Naza cannot now correct because it was too much/too late hence the increasing throttle/wobble you experienced.
Personally if I experienced what you did, I'd have restored the power to 50% (Appx hover power), this SHOULD have narrowed the band that the NAZA was trying to correct within. This is a theory anyway, I'd believe that by bringing ALL the motors to 50, the power swing and application would be much smaller (vs the 25% or so you probably had to "land" the craft, this would require the significant increase in power (from the flight controller) to attempt the recovery). The other motion I probably would have done is given it some directional flight (IN THE DIRECTION OF PITCH/ROLL!!! - more later). Two reasons for this: #1 Vortex Ringstate (Settling with power). Its a situation where a helicopter "Settles" into its own downwash. I'm a helicopter pilot, and this stuff is for real! Our full size aircraft with over 20,000 shaft horse power will fall out of the sky faster than you would imagine.
The second reason: That downwash you are descending into doesn't provide "clean" lift, so now, even what the FC is TRYING to do (with theoretical numbers DJI programmed into it) are only a "ball park figure" because they will figure a descent with even thrust on each motor SHOULD develop level descent, but if that air is disrupted, that one motor/side will not develop the thrust it "should" develop, so the FC will increase the thrust on that motor to correct, now you are getting that rocking motion... There are a lot of other aerodynamic principles that are involved (Induced thrust, drag, AOA, Relative wind, and even crazy stuff like stall regions of the rotor (reverse flow, negative stall, negative lift, positive lift, positive stall. ALL of this changes hundreds of times per second, every second. There is no way DJI (or any flight controller would "KNOW" what will happen in every instance (different wind directions, modes of flight etc.) They just have to figure it out on the fly.
Now quickly, why would I have given it directional flight in the direction of the motion?? Specifically because let say your craft was going left/right (opposite yours in the video ie: fore/aft). If it was rolling left and you gave it a hefty 30-45% left direction with moderate application of 50% throttle, you have completely eliminated the need for the FC to "figure out" what to do, now it's thinking "GO LEFT"... Huh... I AM going left! COOL! With that the FC is no longer "panicked" and not going to induce too much power. With that in mind, slowly bring it out of the left motion and recenter the sticks, slow your craft down and make a SLOW descent. I'd also recommend keeping some motion in until you get closer to the ground to reduce the possibility of damage, keep a slight motion going (brisk walk) until you get a couple feet from the ground.
OK, the point of that...
I'll take my 690 out this weekend (weather dependent) and give it a couple adjustments and flights, I've already given my baseline numbers and had a completely successful (3 minute) flight. Since I only have a couple 5000mah 4S batteries, I'm limited in what I can fly. But, I'll record my current numbers, including a couple rapid descents and I'll try Info@key-photo's settings. Especially since he has had success with his.
I'll report back in about 18hrs (its nearly 10pm Korean time on Friday) 1250Z Friday
Corey