Steven Sanders
Forum Replies Created
-
I think one of our three HDW-2000’s is the cause of all this. Digitizing with the other two results in sync sound, only number three gives me trouble.
Time to put this issue on the sony forum, huh?StvN
-
Hi Guys, Im back with the results of our test.
The first thing we did was remove the Blackmagic codecs / software from the machine, but leave the card in the slot. We repeated the rendering tests and no matter how much we tried, we could not force FCP to crash while it was rendering. Installing the codecs back, and the problem came back. Well, well, well…
Installing the Kona codecs and the cards resulted in a stable system.We directed the problem towards the people from Blackmagic and their answer was that it was Apple’s fault. Not very constructive. So we decided to swith to AJA. It seems to work in my system and that’s the most importing thing for me, as I have to meet deadlines almost every day.
Greetz
StvN
-
You are absolutely right,
I must have been typing my previous post while I was listening to the director, cuz that color management thing does not even excist I think, what I ment was match legacy. Sorry for the “verwarring”.
StvN
-
I sure will,
Tomorrow or the day after I will replace the Blackmagic with a Kona 3. If I still have the same problem, then I guess we’re just gonna have to wait until the solution comes in the form of a new OS (soon to be released) or less evasive: FCP 6.0.2., also on the way.
I’ll keep you all posted.StvN
-
That’s super,
By the way, it also seems to work for me when I just check the preserve RGB box in combination with the color management box. Give that one a try as well.
Veel plezier,
StvN
-
Hi everybody,
I’ve been having the same problems. 8-core, blackmagic, HD prorez, first 4, then 8 gigs of RAM. Only we narrowed the problem down to the capture card.
We changed the plugins, we changed the MAC (from 8-core to Quad-core), we changed the RAM (from 4 to 8 – with 8 all of a sudden I had realtime downconversion to SD when a 3 way CC was applied), we reinstalled pretty much everything… always a crash after a relative short while of rendering.
So then we took out the capture card.
No problems
Put it back in: crash
We did this with an 8-core and a quad-core, with native plugins and third party plugins.
So I guess that nails it down to one bad guy, doesn’t it?
The only problem is the previous posts of people saying they got the same problems with an AJA card…
So the problems are related to the cards, or the slots, or the way FCP 6.0.1 is handeling these cards, or the OS, I don’t know… anyway: no card, no problem.
We’ll keep you posted, cuz the investigation isn’t over yet.StvN
-
Happy to be of service, and o, I forgot to ad: don’t forget to check the Match Legacy box in the project settings, otherwise you’ll have that darkening effect again.
By the way, is there anybody who can open up his brain and shine a light on the technical side of these issues? I would very much like to understand why exactly this solution is working.Thanks in advance!
StvN
-
Well, after a few more experiments I think I found the solution to all of this. It’s really a workspace issue within AE8. When you have a mac, you have to set your project to Apple RGB. Interpret the footage the same way and render the whole thing out in Apple RGB.
After importing it back into FCP, colors and luminance were the same.
I can’t say I fully understand the whole mechanism behind it, but for now it seems to work for me. If you, however, wish to render a movie out of after effects to be used in a different app, or to give to a client for normal quicktime viewing, this working method is not the preferred one. Your rendered movie will appear lighter than it should. In that case you better choose a different workspace. So it’s all about choosing the right workspace for the right kind of platform/application. Trial and error, I guess. But at least I know now which buttons to push.
Cheers.StvN
-
Thanks for the post. I did try that, but it made no difference. I did run some more tests though. It seems that the rendered quicktime file is displayed with a darker gamma ONLY in Final Cut Pro. I managed to simulate this by opening the rendered movie with the quicktime player and changing the settings of the color compatibility with final cut studio. So it has something to do with the way FCP, MY FCP anyway, displays this piece of rendered footage. So, what’s the difference between the captured file and the AE modified file? Well, the first is captured with a Blackmagic card, the other is not. I now may sound like an idiot, but could it be that these clips have a different color profile?
Maybe this has become a post for the FCP dudes.
Thanks for your time though. Suggestions are still welcome. -
Well finaly someone who shares my problem. Insert on my system is a big no no as well. Same stuff going on: two duplicated fields on the first frame I dump to tape. I (kinda) resolved this issue by trying to insert on a cut, but it did not make me happier. Now that I bought a new mac pro and I’m planning to do an entire show in HDCAM I discovered that I cannot edit to tape onto a Sony HDW-2000 without having serious green digitale noise in the picture. When i crash record, everything’s fine, but when I edit to tape the picture is FUBAR. I’m still searching for an answer, but I believe it has something to do with either the videodesktop thing or the RS-422.
Sorry for the rant. Just to tell you I share the same issues and I did not find a solution. At the end the solution will probably be called “AJA”StvN