Red Rocket errors with 3.2.16 / 3.2.13 clips

[Christopher*Seguine]

Clips captured at 5:1 or 3:1 with Epic 3.2.16 or 3.2.13 have decode errors using Red Rocket (Driver: 1.4.27.0)
Clips playback/transcode fine using software decode (rocket disabled)


Not all clips exhibit this problem, only when there is a large change in the scene, rack focus, etc.


Verified problem on multiple rockets/workstations - its thankfully not the dead rocket for no reason problem.
3:1/5:1 clips from 3.07 seems fine with the rocket.


Trouble ticket filed, and problem verified, hopefully this will be fixed soon.

[mickpacifici]

I am curious if anyone else has experienced this issue with the Red Rocket and 3.2.16?

Chris do you have any follow up?

I would really like to use 3.2.16 on a shoot that starts next week. It seems solid to me in my initial tests.

Thanks in advance.

Mick

[Shane Kelly]

I shot 2 cameras for 4 days solid last week on the latest build. No problems on several terabytes of footage.
Major commercial client.

[Christopher*Seguine]

Red support duplicated the problem I am seeing, No it has Not been fixed.

I only see problems at 3:1 and 5:1, and only when using the rocket, and again not every clip - only highly detailed clips with significant motion.

So if you shoot with compression ratios greater than that or are not using the rocket you are ok, probably.

They have not said if its a problem with rocket software or the camera firmware.

We almost always shoot 3:1 so this is a big problem for us.

Just did some some tests with the F65, may start using that for awhile, if only it wasn't so big.

[Paul Russell]

I've had lots of problems rendering out 5K footage shot on 3.2.16 at 7:1 using Premiere CS6 or AME on W7. Slow renders and frequent hangs mid project, regardless of whether rendering to H.264 or Cineform codec. The only plugins being used on the footage are the native source adjustments and curves. It's very annoying when you've set a bunch to render overnight and the next morning you find that the first one jammed halfway in and stuck the whole queue.

[Josh Wallace]

Anyone confirm if this issue is still with us v3.2.19?