Quote from: SpcCb on November 10, 2013, 12:00:06 AM
This problem is only in RAW video mode: In regular H264 mode (->.mov file) it works fine with last builds; I'v checked it yesterday.
So you should not have this problem since a long time.
The weird thing is... I'm sure I used a build where low FPS override in RAW video was working fine. It was this last summer, with a1ex' builds.
I'm currently checking all builds to find when it was back (take a looong time). Apparently, it's very old, good builds cannot be find anymore in the download page (or I don't see where) and it was before the magical Dual ISO arrived (hard to make a choice!). Maybe during the autoexec unification (?).
Yes SpcCb. This has only ever shown up shooting FPS override RAW. It works perfectly ( atleast for me) with h.264.
However, Raw is an extremely important feature for FPS override as it lends itself so much to landscapes and architectural shoots which so heavily rely on grading.
I also thought it was working earlier but as it only appears to occur below 1.5fps I am tempted to now think that the few times I used it successfully must of incidentally been above the 1.5fps threshold.
I'll have to check the cadence of the frame repeats. I've mainly seen the same 1-2-1-3-4-1 as you SpcCb. However, I seem to recall that I've seen different cadences with different settings in the past.
Is there an official bug reporting procedure with the RAW builds or is discussing it here on the forum actually functioning in that regard? I just want to make sure that I do whatever testing, etc. is most constructive and beneficial to helping the programmers/testers nail this bug.