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

Problems converting big files in Redrushes ??

Red october

Member
Joined
Oct 7, 2008
Messages
17
Reaction score
0
Points
0
Hi.

For some reason i cant open any of the quicktime mov. files that´s bigger than 4gb?

I have coverted the raw files in Redrushes to half res, Prores 422 HQ.

Anyone knows what is wrong?


Kind regards
 
Were they rendered over a san or to a fat32 disk?
 
they were rendered over to a fat32 disk.. Not good?

(I have an Apple Imac 24, 2,8ghz, 4gb ram)
 
You just answered your own question.
FAT 32 doesn't allow for files bigger than 4GB.

I have seen that RC allows us to make those files, though. They're just not readable by anything existing...
 
Thanks Gunleik!

So I have to buy myself a new harddrive or can I change some settings?

I don´t have a clue about harddisks other than that I need at least 7200 rpm.
 
Is it an external drive? I take it you're on a Mac, as you're using RedRushes?
Formatting the drive to HFS+ (without the "extra" option) should do the trick and make you good to go.

If you're only rendering on a Mac and want to continue on a PC, you have two options.
1. Either install MacDrive or something similar on the PC and go the HFS+ route
2. Install something that lets you format, read and write to an >NTFS disk on your mac. There are both free and commercial products available. I have had varied experiences with the free products...
 
Yes, I am using a mac. It´s a external maxtor disk.

How do i defragment the harddisk?

Thank you so much!
 
ok. So can you tell me how I format the disk then.

(I´ll just move the files that are ok (under 4gb) to a another disk, and erase the bigger files and send them back to RR)
 
1. Finnish your backups... :)
2. Go to: Applications/utilities/diskutility - Open
3. Select the disk in question and choose "erase"
4. Select formatting option and hey presto.
5. (you may have to choose some volume/partition schedule, but I guess you just want the whole disk as one volume...)

WARNING - -all files on the disk will be erased! :)
 
Red rushes still won´t render a lot of my raw files. I formatted the disk to mac os extended (journaled).

It seems that the bigger files the more problems... What to do?

Any suggestions anyone?

(My settings: QT, half res high, prores 422 HQ)

I tried again this night, and now all the files are black, but with sound and the files are really small. Around 50-100 mb per mov. file.


I have a deadline that is eating my brain if i can´t solve this problem.

PLease help!
 
Red rushes still won´t render a lot of my raw files. I formatted the disk to mac os extended (journaled).

It seems that the bigger files the more problems... What to do?

Any suggestions anyone?

(My settings: QT, half res high, prores 422 HQ)

I tried again this night, and now all the files are black, but with sound and the files are really small. Around 50-100 mb per mov. file.


I have a deadline that is eating my brain if i can´t solve this problem.

PLease help!

Does it render in redalert?
What resolution and frame rate are the R3Ds?
How long are the clips?
 
Hi,

Maybe you can try out this: http://www.reduser.net/forum/showthread.php?t=20966

Not to say Red Rushes is not as good, but Clipfinder lets you organize your transcoding better, IMHO. It even supports drag n' drop! It's very simple to get to know the program, and you can access its manual by pressing cmd + ? in the program.

Just so you know, Clipfinder doesn't import R3D files if they are present without Quicktime proxies, at the moment. Before the import, just use RA to generate QT proxies if you have any R3D's without proxies.

I think this program will be even more amazing in a few weeks as Hans, who created it, is working to upgrade it.

Hope you find a solution.
 
BTW, the big file bug was fixed in RA/RR/RL 3.60
 
Back
Top