[Erik Mickelson]

Edit: After the latest Apple update, I am able to render my minuscule timeline with only the Apple Ram (2gb). I will re-install the DMS memory and test for all of you who are having this problem.

////////////////////////////////
Thanks for the update on the software update.
So Apple DID do it!
Oh that’s right, you didn’t disagree:)

On the subject again.
My project is only 3 minutes long and the FCP filr is only around 2.5 MB. I still get the HUGE ram usage and then crash after crash.

Dual Core 2 Duo 3.0Ghz, 6GB ram, 2x500GB Raid, Tiger 10.4.11, FCP 5.1.4

[Erik Mickelson]

Exactly the same number for me!!!
16,777,216.00TB of real memory on my system too!!!Strange to have the same number on both systems for sure. I have the original 4×512 sticks of ram from Apple and another 4x1GB sticks from DMS Memory. I can render with just the Mac installed memory. I remember back in the old days that Apple released a software update that reported other manufacturers ram as bad, they were told “that’s a NO! Bad dog!” by the government powers that be. Do you think Apple is writing code again that wrecks third party ram and tells the system that it’s junk.

What is going on. I have been through three sets of ram from DMS and they do not know what is going on either. Strange things are afoot.

Dual Core 2 Duo 3.0Ghz, 6GB ram, 2x500GB Raid, Tiger 10.4.11, FCP 5.1.4

[Erik Mickelson]

It seems that my Boris filters went to the User/Library~plug-ins folder somehow. I moved them back to the regular System/Library~plug-ins folder and the whole shootin’ match seems to be running up to speed. No more problems the last hour or so. I wonder how that could happen. Computers, they are just …good.

Dual Core 2 Duo 3.0Ghz, 6GB ram, 2x500GB Raid, Tiger 10.4.11, FCP 5.1.4

[Erik Mickelson]

Thanks for the reply Walter.
I have a question. Does FCP play well with PICT files? This is my first time using them and the BAM! All this starts happening. I have been using this system for quite a while now with no problems. I did install the Noise Indudtries dome. Any problems there? Maybe that’s it! It says right on the site-plays well with FCP Studio 2 only! What do I have? Hmmmm FCP 5.1.4 comes with what package? Motion 2…yup. Hmmm…I’ll have to check. I think I have FCP Studio1. I’ll delete Noise Industries and report back.

Dual Core 2 Duo 3.0Ghz, 6GB ram, 2x500GB Raid, Tiger 10.4.11, FCP 5.1.4

[Erik Mickelson]

Comes out of the back of the mac. 1/8″ to stereo then to a Crown D-75 amp then to a pair of JBL 4206 near field monitors. I suppose I could have the audio come out to my MOTU then the Crown amp.

How about a Kona or Black Magic something or other.

Oh, I also hear a zipping type of sound when scrolling web pages too.

I think it has something to do with EMF and croostalk within the Mac architecture. Strange for sure.

Dual Core 2 Duo 3.0Ghz, 6GB ram, 2x500GB Raid, Tiger 10.4.11, FCP 5.1.4

[Erik Mickelson]

Nope, no funny business here. I would shoot with the ability to add or remove headroom. Options are good in this sense. What you could do is have a photoshop file that corresponds to your crop. Provide that to the editor. You could just tell the editor to mask say 96 pixels top and bottom. Then you end up with the same crop you shot at. Does this make any sense?

Dual Core 2 Duo 3.0Ghz, 6GB ram, 2x500GB Raid, Tiger 10.4.11, FCP 5.1.4

[Erik Mickelson]

Hi, I will try to help. First off, DO NOT shoot with the top of your viewfinder/lcd screen on the camera as the top of your frame. What if the editor wants to show more sky? Nothing there eh. Try to tape over the top and bottom of your lcd viewfinder with the same width of tape(preferably gaffers tape or something that does not stick permanently or leave sticky residue). Measure this width so you can do it again if needed. So basically you will be cropping the top and bottom of your viewfinder so that there is equal stuff out of frame at the top and bottom of your clips. The editor can then move some up or move some down to fit the edit. Much safer than just taping off the bottom of your frame. Same results, just one way leaves more options. Sweet!

Dual Core 2 Duo 3.0Ghz, 6GB ram, 2x500GB Raid, Tiger 10.4.11, FCP 5.1.4

[Erik Mickelson]

It doesn’t matter if fields are turned on or off, it just does not matter. I was just messing around and found this. Like I said before, the issue is not fields but that I can put anything on the timeline and get RT performance as long as the canvas window is cropping the image. I just included whatever I had selected at the time I wrote the post. There is no relevance to the timeline specs except for the 8-bit 4:2:2 codec. It really just shows the independence of FCP, being able to preview even when there is a red line above the timeline. Is this hard to understand/explain? I am wondering of this is normal for FCP?

Frame Size 1280×720 HDTV, 59.94fps(29.97 doesn’t matter), Uncompressed 8-bit 4:2:2, Pixel aspect(square or NTSC-CCIR 60 doesn’t matter), Field dominance none(upper/lower doesn’t matter). There – I switched it – same outcome as before.

Dual Core 2 Duo 3.0Ghz, 6GB ram, 2x500GB Raid, Tiger 10.4.11, FCP 5.1.4

[Erik Mickelson]

Yeah, probably should be upper field. How about setting the fields to “none”? What are your thoughts on doing that?

Thanks

Dual Core 2 Duo 3.0Ghz, 6GB ram, 2x500GB Raid, Tiger 10.4.11, FCP 5.1.4

[Erik Mickelson]

It’s not the mismatch I am commenting on, sorry if that was not clear.
I am commenting on the fact that I get RT performance and not the blue Unrendered screen as long as I make sure that the Canvas window is overlapping the viewable area. I still have the red line over my footage in the timeline, but I get to work as if it is an RT yellow line.

Just wondering if this is an undocumented “feature”.

Dual Core 2 Duo 3.0Ghz, 6GB ram, 2x500GB Raid, Tiger 10.4.11, FCP 5.1.4