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 :)

render quits at 2 gigs

ThomtheEditor

Banned
Joined
Apr 1, 2008
Messages
262
Reaction score
0
Points
0
Location
Los Angeles, CA
hey guys, the computer i installed the rocket on would occasionally quit red rusing at 2 gigs, what causes this? it's doing the same thing with renders from rocketcine now as well; i was hoping this would be solved by now?
 
  • Thread starter
  • Banned
  • #3
i did some research and found that it's still being limited to 2gigs across a network when rendering qt based material, i would just render to a local sata drive; but rocketcine seems to want to kick any drives off the sata card that are being used by other programs
 
I actually was having the same problem. But instead of doing a batch I just did one and it rendered out to 2.5 GB. I also had a batch just render out 545MB. So it seems a bit glitchy. Not sure what the solution is.
 
The two places where QT renders get limited to 2GB are Fat32 and AFP mounted volumes.
 
I originally thought this was a problem with spanned clips or related to the source. But after some research it does depend on the destination volume being an afp mounted share.

Our studio setup is a central RAID shared over AFP. What is the reason for quicktime rendering to AFP shares being limited to 2gb? This seems to be a limitation specific to Red Rushes - final cut etc do not have this problem?

I'm sure there is a good reason for it just wondering what it is.

It's not really viable going from machine to machine manually setting off renders to local hard drives, and having to copy the files over afterwards.
 
Back
Top