Has FCP and RED 2k QT's changed.

[Mark Toia]

Can anyone answer this problem for me.

We have the latest builds now in 2 of our cameras the 3rd camera we have left as build 15.

We cannot edit Build 16 2k QT's in FCP without the FCP drop frame window popping up every 5 seconds. Our sequence time line is at low and unlimited RT has been turned on. This has been our normal process now for the last 6 months without any problems at all. All has been working fine to date.

The crazy thing is all build 15 stuff shot on the same day is playing fine in the same time line, all the build 16 footage is giving is hell.
Is the Build 16 making more complex files bigger, more data.....
I'm trying to cut here and cannot go forward.

Any answers from the RED TEAM or fix finders out there.:help:

 

[Snow R. Shai]

Preferences

Preferences

Hi Big T

Try opening file > user prefs, and deselect "report dropped frames on playback".
This option keeps a good, sustainable playback, no matter how many frames you drop...
You might have tried this before, but i hope this simple solution solves the problem.

 

[Mark Toia]

Thanks Snow,

Yes have tried that, just so I keep editing, but still very rough playback.
It's like build 16 is heavy, Our Build 15 footage in the same timeline plays perfectly.

Shits me that the work flow is getting worse. For the last 5 months I have a had a flawless work flow. Now i'm having nouthing but problems with play back, having to render stuff to veiw etc etc... :ranting2:

I so hope RED isn't going backwards. it's starting to drive me and my clients away.

thanks snow.

 

[William Wedig]

Try REDrushes. I know it sucks to have to convert the footage before you edit, but it'll give you something easier for FCP to deal in (DVCProHD, ProRes, etc).

 

[Thomas Koch]

i noticed the same thing on my 8-core 2.8ghz Mac Pro. In build 15 2K played back fine. In build 16 it would not.

I changed from 2GB of RAM to 8GB of ram and I now get real time playback of 2K. Try adding RAM.

 

[Jeremy Newmark]

We are seeing the same thing on an 8 core 3GHz MacPro with 8 gigs of RAM and a very fast RAID array. However, this has only been on 25fps sequences. 23.976fps sequences still seem to playback fine.

 

[Craig Schober]

i noticed the same thing on my 8-core 2.8ghz Mac Pro. In build 15 2K played back fine. In build 16 it would not.

I changed from 2GB of RAM to 8GB of ram and I now get real time playback of 2K. Try adding RAM.

i have the same config and the same playback problems from build 15 to 16. but i had 10 gigs of ram all along so a lot of ram did not help me.

 

[Mark Toia]

Ive got 16 gig of ram and going through RAID 1 raid 24 terabyte raid system.
But still build 16 4k 2:1 QT's in FCP jerk and fart around.
Build 15 footage is perfect.

BLOOODY HELL!!!! WTF! :ranting2:

Just shot with another camera, build 16 WTF! and it works fine in the same time line yet the 2 other cameras with build 16, and the footage plays like crap.
It's completely got me stumped.

I'm sure there a good cameras and bad cameras.
LUCKY DIP!!!

 

[Snow R. Shai]

Causes

Causes

Hi Big T
The problem persists... sorry to hear.
check your RT menu for low quality on timeline, codec should be prores, not Redcode [for rendering].

Sounds like this can go much deeper than sys prefs, RT menus or more RAM.
What are other post differences between build 15 & 16, that can cause this type of playback ? anyone?

 

[JoshBertrand]

Any resolution to this issue yet? It's very slow for me as well in a 2k timeline on a similar Mac Pro.

 

[Dan Graetz]

Same issues here - between 15-20fps playback on .H Quicktime proxies - where before build 16 all was smooth as butter. We're mostly shooting 25fps - could that be the only problematic base framerate? (and not enough Aussie's are complaining?

It's a pretty major blow to what was previously a brilliant time-saving workflow...and no answers seem to be forthcoming.

Rob? Stuart? Anyone??

 

[NateWeaver]

No, build 16 is slow here in 23.98 land as well.

RedRushes is the new tool I'm using to work around.