MASSIVE playback issues

[Uli Plank]

When you’re saying “downrezed” are you talking about the ProRes codec only or about image size too? If the are truly gigantic, FCP won’t handle them. It’s limited to 2K, AFAIK, and you’ll need ore RAM even for that.

Regards,

Uli

[Aaron Zander]

[Uli Plank] “When you’re saying “downrezed” are you talking about the ProRes codec only or about image size too? If the are truly gigantic, FCP won’t handle them. It’s limited to 2K, AFAIK, and you’ll need ore RAM even for that.

Regards,

Uli “

No they aren’t really huge, they are only 1504×1128

and rendered out super low res proxie h.264’s (like 45 megs for some of the big ones) and STILL playback issues. and i tossed these onto my internal sata drives. So now I am just out of ideas

[David Roth weiss]

2gb of RAM pretty much makes your MacPro into a girly-man when running FCP, especially when dealing with lots of big stills. The stills are RAM hogs and are making your machine call to the hard drives as virtual RAM, and thus creating a huge bottleneck for your way slow hard drives.

Your raided firewire drives are giving you just 52.2 mb/s, thats less than a single SATA drive. Come on, your Mac has room for at least three and even four striped SATAs, use the technology, whip out that credit card and get yourself 4gb of RAM and at least two more SATA drives. Stripe three drives together and start living life.

David Roth Weiss
Director/Editor
David Weiss Productions, Inc.
Los Angeles

POST-PRODUCTION WITHOUT THE USUAL INSANITY™

A forum host of Creative COW’s Business & Marketing, and Indie Film & Documentary forums.

[David Roth weiss]

[A.Zander] “and rendered out super low res proxie h.264’s”

You’re editing h.264 on the timeline???

That’s a big no-no too.

David Roth Weiss
Director/Editor
David Weiss Productions, Inc.
Los Angeles

POST-PRODUCTION WITHOUT THE USUAL INSANITY™

A forum host of Creative COW’s Business & Marketing, and Indie Film & Documentary forums.

[Aaron Zander]

I tried the h.264’s just as sized with no key-framing, but it happened with prores. Doesn’t have ANY issues in the clip playback window. And yes I would love more ram. If you would like to donate some, i will happily take it, or If you would like sony to finally be happy with the cut of a corporate video I am working on, and pay my boss the LARGE sum of money on delivery, that works too. but for now, 2 gigs and my girly man machine is how it shall stay (Going to grab another 4-8 gigs as an early xmas gift for my self)

The tiffs aren’t anything bigger than I have worked with before. AND i switched to my sata drives and no difference at all. Id stay on them If i wasn’t dragging this project around to 2 locations.

-sorry this came off a bit harsh, Thanks for the insight. but it’s already been tried. and according to the kona tester, My average read speed on my INTERNAL sata drives are 53.7mb/s for one of those tiny clips

[David Roth weiss]

[A.Zander] “sorry this came off a bit harsh”

No worry! And for the record, I was just yanking your chain. Trust me, I understand that money doesn’t grow on trees these days.

David

David Roth Weiss
Director/Editor
David Weiss Productions, Inc.
Los Angeles

POST-PRODUCTION WITHOUT THE USUAL INSANITY™

A forum host of Creative COW’s Business & Marketing, and Indie Film & Documentary forums.

[Aaron Zander]

[David Roth Weiss] “No worry! And for the record, I was just yanking your chain. Trust me, I understand that money doesn’t grow on trees these days.
“

it used to? I know I’m young but i dont recall my mom ever recounting any tales of going to the money tree as a kid?

[Uli Plank]

I’m not surprised you have stutters with H.264. That’s not an editing format.

Stick with ProRes, get at least 4 GB RAM and set up a RAID0 of two SATA disks (minimum) and it should be smooth in that resolution.

Regards,

Uli

[Aaron Zander]

JUST TO CLEAR THIS UP, THIS HAPPENED WITH EVERY FORMAT I’VE TRIED, not just pro res.

so once again

dimensions are 1504×1128

its not the drives, or the formats I think Its just the ram.

[Walter Biscardi]

[A.Zander] “so once again

dimensions are 1504×1128”

It’s not the frame size, it’s the dpi of the original files which is making them much larger than they need to be. We work with files this size quite often and FCP handles them just fine. A 1504×1128 400dpi file can be as 25MB or larger while a 1504×1128 72dpi file can be 1MB or smaller. What you want to do is retain the frame size, but make the file sizes smaller so FCP can work with them.

Take one of your Tif’s into Photoshop.

Bring up “Image Size”

I’m betting it will show up between 200 and 600dpi.

UN-Check “Resample Image”

Change the dpi to 72

Save it as a copy or overwrite the original, your choice.

Repeat for all the files.

This retains your frame size, but greatly reduces the file size of each image. Now you can work in FCP.

DON’T work in an H.264 timeline. This is a finishing format only. You can work in a ProRes or Uncompressed timeline just fine with these newly saved Tif’s.

Walter Biscardi, Jr.
https://www.biscardicreative.com
HD Editorial & Animation for Broadcast and independent productions.

All Things Apple Podcast! https://cowcast.creativecow.net/all_things_apple/index.html

Read my blog! https://blogs.creativecow.net/WalterBiscardi