Santiago Gutierrez
Forum Replies Created
-
I do this every week and have never had a problem with fields. I have edited in DVCPro HD 1080i and done this with no problems as well. Usually these days I’m using ProRes in HD. But I’ve never seen field problems on the downconvert and these shows are packed with graphics that are moving, so it would be obvious if there were field problems.
Santi -
The rendering slowdown is because FCP is set to render all Motion ‘movies’ at Best quality by default, regardless of the setting you have specified inside of Motion. To fix this in FCP, open up your sequence settings and go to the “Always Render Movies in Best quality” setting. This will now make FCP look to whatever you’ve set up in Motion (usually Normal quality).
This will fix your slow rendering problems. However, I’ve had nothing but trouble whenever I do opacity changes on Motion projects, such as a cross dissolve. I get these purple flashes where the whole frame gets colorized for the length of the dissolve. It happens randomly and usually when clients are in the room. Because of this, I’m rendering all files inside of motion and bringing the Quicktimes into FCP. A real PITA. This is on a Mac Pro with the X1900 XT card. -
Switching your Render Quality to Best from Normal will get rid of the aliased edges. This can be found under the “View” menu. Of course the render times go way up, but the tradeoff is that graphics are properly rendered. I was dealing with this all last week on logos. The reason it looks good in FCP is that FCP defaults to the Best rendering quality by default, you can check this in your sequence settings under ‘Render Control’ in FCP 6.
Hope that helps,
Santiago -
I have this issue also every time i send from Color to Final Cut Pro. What works for me is as suggested above to Command-Tab to the Finder, but wait until the Kona 3 switches to the Multi Pattern, or Color Bars, or whatever test pattern you’ve got set up. I do this immediately once the XML import finishes in Final Cut Pro. I do no operations in FCP until I’ve done this. Once the test pattern goes on in the Finder, I then switch to FCP and work as normal, no need to quit Color. This works every time for me.
Santiago -
AJA is aware of this issue. I notified them about it a few weeks ago. If you email support about it, they’ll email you the proper preset file needed. This only affects the 525 29.97 ProRes HQ preset. But you can make the 525 ProRes HQ preset for yourself by duplicating the existing ProRes 525 (non HQ) and switching the codec to ProRes HQ. Do that in both the capture settings and the sequence settings and you’ll be set.
Santiago -
Regarding the general errors, are these by any chance multiclips? I was just working on some sequences today in the Offline RT format that were multiclips and was having the same ‘general error’ when I would go a quicktime export. After a little trial and error, I found that the only way that I could get it to work was by collapsing all the multiclips in the sequence and then doing the export.
I also had a multiclip sequence spontaniously change the clips that were part of the multiclip and the timecode that had been edited into the sequence. When I was scrolling through the sequence that had been completed in FCP 5.1.4, I realized that a bunch of shots were of completely different footage than they should be and other shots had moved the edit points, so that sound was now out of sync with picture, etc. I reopened the original FCP 5.1.4 project and looked at the original sequence and everything was fine, so I copied that sequence into my FCP 6 project and replaced the corrupt sequence.
That’s why I cloned my FCP 5.1.4 drive, so I could deal with these problems as they come up in FCP 6. Looking forward to the .01 release although FCP 6 is remarkably stable for me, hardly ever crashes.
Hope that helps,
Santiago -
Hi Sean,
I’ve seen this as well in FCS2 when opening a 5.1.4 project. It was also a 1080i project, but I’m working at 60i not 50i. All my motion effects were down to 2 or 3%. Definitely a bug I think. However, I also have opened many Standard Definition sequences and all the speed effects are correct. So maybe it’s a 1080i bug. As an aside, I had mastered this sequence a couple of weeks ago and made an XML of it then. I imported the XML into FCP 6 and all the speed effects had been switched from constant speed (5.1.4) to variable speed (FCP 6), but played the correct duration and overall speed. Very strange. Hope they fix this one. I also reimported the sequence with Automatic Duck and it came in correctly in FCP 6. So there are workarounds.
Hope that Helps,
Santiago -
Cinema Tools 3 will do this for you. You just need to import the .ale file as a ‘Telecine Log’. This will set up a database of the footage for you.