I too noted an increase in bus errors around 2.5, BUT I've got to say I get them in other programs too. Word X, which is not Intel code, seems to crash way too often. Yet, FCP never crashes. In short, old old code WITH newer (when Intel support was added) versions of OS X seems to be far more prone to Bus Errors. I'm thinking it might not be "bad instructions

That makes perfect sense -- if you are aware that MC has this capability. I don't remember this being documented in the CC section. Perhaps it's covered under Filler.

I said it wrong. Only V1 had content. V2 was empty. Never in a million years would I have thought that if I CCed a clip on V1 -- that the CC would add Filter to V2 and then, somehow, color correct the filler and not the clip. I'm still not sure HOW Filler, which I assume is nothing, could be altered. Even more strangely, I think I saw the CC take effect

You nailed it. V2 was empty but still active. Thank you.

1) Single video track. 2) Switch to Color Correction tool 3) Make an adjustment 4) MC auto-adds a video track above the current video track 5) The new track carries the correction. I don't remember this from Xpress Pro and I don't see anything in the docs. Is this the only way MC works?

YOU ARE GOOD! Never ever would have thought that this setting would have anything to do with scopes. My video is 16:9 so all three monitors are 16:9. Anyway to get a 16:9 "monitor" to display a true round vector scope?

When I choose the CC Toolset, the three monitors appear. I use the Pulldown to select one of the scopes. Nothing happens. The chosen Scope is checked, but the image remains that of the video frame. None of the multiple scopes on any of the three monitors will appear. I assume the Pulldown is what Avid calls the Source selector. I'm also assuming that

Well said! 1) Using a current Intel system -- HDV edits no differently than ANY HD format. In fact, because of the low disk bandwidth, it edits just like DV. It is a myth editing is "slower." If it's slower you've got a slow computer. 2) There is NO quality increase from wasting the time and disk space to convert HDV to anything. All work that involves

Not being able to output DV suggests that your VTR my not be setup correctly or the VTR Template may not be setup. For example, have you been inputing from a different FW VTR? You can output any HDV you can input.

2.7.7 -- I don't remember ever having this problem last summer which would have been about 2.7.2. Also running 10.4.11.