Welcome to our community

Be a part of something great, join today!

  • Hey all, just changed over the backend after 15 years I figured time to give it a bit of an update, its probably gonna be a bit weird for most of you and i am sure there is a few bugs to work out but it should kinda work the same as before... hopefully :)

Redcine 20.0.0 export to ProRes 422 (HQ) "Failed to write frame" error

ericyoung

Well-known member
Joined
Dec 29, 2006
Messages
4,735
Reaction score
0
Points
0
[EDIT: Doh! Just realised what I was doing wrong - my Nexto DI destination drive is FAT32 which has a 4GB file size limit! Moderators please delete this thread as it's not a real fault or bug!]

Redcine export to ProRes 422 (HQ) to give to an editor - getting "Failed to write frame" error on clips longer than about 3 min.

Rendering the longer clip in two shorter sections by setting shorter in-out points succeeds.

Not sure if related to above, but at least one of the failing longer clips also fail when trying to Log & Transfer to ProRes 422 (HQ) in FCP. The biggest ProRes file that succeeded with Log & Transfer was 3.96GB, so doesn't seem exactly the same as the 2GB limited render to network shared drive bug mentioned on another thread.

Source Red Drive connected via Firewire 800 to MacBook Pro
Destination NEXTO DI 500GB drive in USB2 hard drive mode

Any ideas what I'm doing wrong? Or is it a known bug?

Thanks for any help!
Eric

MacBook Pro non-unibody
2.5GHz Intel Core 2 Duo
NVidia GeForce 8600M GT 512MB
HiRes 1920 x 1200 display
4GB 667MHz DDR2 SDRAM
OSX 10.5.8

Final Cut Pro 6.0.6
Quicktime Pro 7.6.4
Redcine Beta 20.0.0
Camera Firmware 20.1.3

Redcode 36 Max
4KHD 25fps
to Red Drive
 
Back
Top