An even BIGGER mystery...
The direction keys do not have to be constantly pressed for the juddering to happen!
Pressing the direction keys at any frequency has the effect that the "advance mechanism" seems to miss a beat every so often and jump a frame or two in the opposite direction - causing the juddering.
All Raid arrays are working correctly at about 200MB/s
Does the sequence match the frame rate of the media?
Have you tested with any other media?
Yes, the frame rate is correct - 1080p25.
I don't have any other media to hand at the moment.
Just noticed too...
...When the advance missed a beat, the timecode does not advance either - so it appears to be an authentic non-advance, rather than a display issue - if that makes sense!
See if you can do a Google search. There's raw media all over the Internet.
I've loaded an old CS5 HDV project that has both HD and SD sequences. They both behave in the same incorrect way.
I'm convinced it's a 6.01 issue.
I will have to load the project onto my editing laptop that still has 6.00 installed - to confirm my suspicions
I'm just not seeing it myself, but I have only one monitor and no BM to work with, so...
Okay, I'm wrong - I apologise for casting aspersions on the wondrous 6.01.
This behaviour is now present on 6.00 with and without Blackmagic drivers.
I cannot understand what's happening. It's not a new camera; neither are the PC and laptop. I've just finished a long edit session with assets from the same camera on 6.00 on the laptop and PC - and this behaviour wasn't present.
On the laptop, it's almost as if there is a flash frame at the point of judder!
Very strange indeed.
On the PC, this behaviour appears to be attributable to a custom workspace spanning 2 monitors. When I return the workspace to the factory-shipped default, the shuttle juddering vanishes. Even with the Blackmagic viewer to the external monitor enabled, shuttle behaviour is normal.
I rebuilt the custom workspace and all was fine for a time, but the issue returned.
Laptop: Althougfh only a single monitor, it is a custom workspace. I have yet to load a project and reset it to default.
Steven Pribilskiy, in his thread, http://forums.adobe.com/thread/1008195 has correctly identified that the problem appears to arise when the reference monitor displaying scopes is ganged to the program monitor.
We are both using nVidia drivers.
In an earlier post, I said this does not happen in CS6. I was mistaken. It does.
Bug Report Submitted.
the problem appears to arise when the reference monitor displaying scopes is ganged to the program monitor.
It doesn't for me. (Using one monitor).
I can replicate the juddering each time I invoke the scopes on the reference monitor on my (1) 2- monitor PC with FX3800 and BM Intensity Pro and (2) single monitor FX4000M laptop.
The reference monitor does not even have to be the active - or visible - panel. Even when it's hidden behind another panel, the juddering occurs.
It is only error free when the refernce monitor is closed.
Any non-Quadro computers around? I just don't get that error at all.
This "juddering" issue when scrubbing the sequence timeline remains wth CC. It still appears to be Reference Monitor related, as reported last year (see earlier in this post).
Scrubbing material in the source monitor is unaffected.
I have swapped out the Quadro for a GTX 680, so it wasn't specific to that card and have the latest BM INtensity Pro driver.
Has anyone else now experienced this?