Welcome to our community

Be a part of something great, join today!

Log in
  • 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 :)

Big Proxies Problem - Please Help

D

dori_bashan

Well-known member
Joined
Feb 13, 2008
Messages
68
Reaction score
0
Points
0
Hi

I've got a big problem.

got footage shot in 4k 2:1 24-fps, and whenever i try to import the proxies the FCP just crash immediately. no warnings, no nothing, the FCP just disappear. working with FCP 6.0.2 and QT 7.3.1, i was thinking about upgrade to QT 7.4.5 but how can i know if the Mac OS is Panther or Tiger? (it's not my mac)

please help.

Dori
 
is it important to leave the main folder (the folder that include the *.r3d file and the proxies) on the root of the hard drive? or can i can arrange those folders the way i want under alot of subfolders?

Thanks

Dori
 
I have the same problem with my new camera's proxies. I've even upgraded to Leopard and QT 7.4.5 - the same. If I try to open proxy with QT sometimes it opens half of screen normal another half some electronic noise, then crash. I've tried to open r3d files in REDAlert - it crashes. If I try to open some downloaded files it's ok. It seems to me, that camera's software somehow incompatible with my mac. Camera's firmware is build 15 (came preinstalled just a few days ago). Please help anyone.

P.S. RedCine opens the same r3d files just perfect.
 
Have you guys installed the REDCODE codec?

Dori - you might want to try updating Quicktime.

Also, which proxie are you trying to import into FCS? What are you system specs? Help us help you...
 
I have the Redcode installed, and about a two weeks ago everthing was ok an i was able to run the proxies with no problem, i will try to install it again, maybe something got curropted,

i'm running a Mac intel with 2x2.66 Ghz proccesors with 8 GB of ram and mac OS Tiger FCP Ver 6.0.2 and QT 7.3.1 using Blackmagic Decklink card.

i've tried both the _M and the _H proxies,

any help will be great

Dori
 
try regenerating new proxies in red alert (create a separate folder for the new ones) and see if the new proxies also crash.

You should know that f proxies are created but not supported in fcp

Was the footage shot rc28 or rc36

That might also help you troubleshoot.

David
 
msadauskas said:
If I try to open proxy with QT sometimes it opens half of screen normal another half some electronic noise, then crash. I've tried to open r3d files in REDAlert - it crashes. If I try to open some downloaded files it's ok. It seems to me, that camera's software somehow incompatible with my mac. Camera's firmware is build 15 (came preinstalled just a few days ago). Please help anyone.

P.S. RedCine opens the same r3d files just perfect.
Click to expand...

Is this 4k 16:9 footage by chance? It's a known bug and should be fixed on the next build. We've seen this on both rc28 and rc36 4k 16:9. Have never seen it with 4k 2:1.
 
msadauskas said:
I have the same problem with my new camera's proxies. I've even upgraded to Leopard and QT 7.4.5 - the same. If I try to open proxy with QT sometimes it opens half of screen normal another half some electronic noise, then crash. I've tried to open r3d files in REDAlert - it crashes. If I try to open some downloaded files it's ok. It seems to me, that camera's software somehow incompatible with my mac. Camera's firmware is build 15 (came preinstalled just a few days ago). Please help anyone.

P.S. RedCine opens the same r3d files just perfect.
Click to expand...

That sounds like you shot in 4K 16:9.
The release notes clearly state that those proxies do not currently work in QT, FCP, nor do the R3D's work in REDALERT.

Read the manuals people!
 
battistella said:
try regenerating new proxies in red alert (create a separate folder for the new ones) and see if the new proxies also crash.

You should know that f proxies are created but not supported in fcp

Was the footage shot rc28 or rc36

That might also help you troubleshoot.

David
Click to expand...

If you plan to use onboard recorded audio (i.e audio you recorded onto the RED) export the audio from the proxies using compressor to wav/aiff BEFORE you regenerate the proxies using REDALERT. REDALERT does not pass through Audio information, neither does REDCINE, so if you loose the audio, you'll have a fun time recovering it.
 
dori_bashan said:
I have the Redcode installed, and about a two weeks ago everthing was ok an i was able to run the proxies with no problem, i will try to install it again, maybe something got curropted,

i'm running a Mac intel with 2x2.66 Ghz proccesors with 8 GB of ram and mac OS Tiger FCP Ver 6.0.2 and QT 7.3.1 using Blackmagic Decklink card.

i've tried both the _M and the _H proxies,

any help will be great

Dori
Click to expand...

Perhaps you should also consider upgrading to Leopard as well.
 
indeed it was footage shot on 4k 16:9. problem solved.
 
Ed Watkins said:
If you plan to use onboard recorded audio (i.e audio you recorded onto the RED) export the audio from the proxies using compressor to wav/aiff BEFORE you regenerate the proxies using REDALERT. REDALERT does not pass through Audio information, neither does REDCINE, so if you loose the audio, you'll have a fun time recovering it.
Click to expand...

This is why I suggested creating the new proxies in a new folder so as not to overwrite the ones generated be the camera at the time of recording.
 
You must log in or register to reply here.
Back
Top