Welcome to our community

Be a part of something great, join today!

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

REDcine & QT proxies

D

D.Paccagnella

New member
Joined
May 31, 2008
Messages
4
Reaction score
0
Points
0
hi to everyone, I would like to know which is the procedure to create working QT proxies / reference files from a .r3d files (on the early shots, we didn't selected the camera option to build them...)

I know there are lot of issues with 16:9 footage, but I'm not able to obtain working QT reference files even from 4k 2:1 files.

One last thing: it's possible to extract the audio tracks from 16:9 .r3d files in some way?

Working on Leopard 10.5.3 , FCP 6.0.2 , quicktime 7.5.4

thanks in advance for support
:help: Diego
 
I already know it, unfortunately too late. We've no chance to rebuild the proxies on the 16:9 footage? Redalert crashes trying to open them.. Redcine open them, but no possibility to extract audio, or rebuild the proxies..
I'm very disappointed, if the 16:9 format was not supported at all, why let shooting using it ??? They couldn't just say "ok , for now it's possibile to shoot only 2:1" ? Anyway... thanks for every other help
 
If Build 16 was not right around the corner, I would suggest we make this whole 16x9 confusion a sticky and perhaps something on the Red site. What's happening (and no offense to you D.Paccagnella) is that some are not doing their homework thoroughly enough. This topic has been covered in many places, not just on Reduser.

Hopefully people are not discovering this after shooting a real project. That's unfortunate. I know some have said they went ahead and shot 16x9 anyway, despite the warnings. That is a mistake in my mind. You have to have workflows completely worked out before ever shooting a real project with Red and any other camera. You can't go in blind. Or I suppose you can, and suffer the consequences (which generally just means a lot of extra work).

Again, this isn't an attack on anyone that has used 4K 16x9, just a general observation. I know some of us spend more time on these boards than we care to admit, but the benefit is that we are aware of some of these issue and help each other come up with solutions. That sometimes get's folks labeled as fanboys, but in reality it's often very beneficial to be on top of all the developments as you can then convey information to clients, DPs, etc.

Again, this will be a non-issue with build 16, so probably no need for a sticky (maybe there already is one and I missed it).
 
I'm with you Stevesherrick, I know well what you say. I'm not responsable of the choice to shoot in 16:9, I'm just trying to help some friends, owner of a red one, that absolutely demonstrated unexperience. Anyway, we all hope the Build 16 will solve lot of problems. The guys from Red, I'm sure are doing their best, but they also demonstrated unexperience, i.e. the on starting 16:9 shooting option currently unsupported, even if, one thing is unequivocal: they are revolutioning the cinema, they give a great product and the possibility to do HQ digital cinema at a fraction of cost of every other system. Some years ago this was just a dream. Thanks, and sorry for the bad english
 
D.Paccagnella said:
I'm with you Stevesherrick, I know well what you say. I'm not responsable of the choice to shoot in 16:9, I'm just trying to help some friends, owner of a red one, that absolutely demonstrated unexperience. Anyway, we all hope the Build 16 will solve lot of problems. The guys from Red, I'm sure are doing their best, but they also demonstrated unexperience, i.e. the on starting 16:9 shooting option currently unsupported, even if, one thing is unequivocal: they are revolutioning the cinema, they give a great product and the possibility to do HQ digital cinema at a fraction of cost of every other system. Some years ago this was just a dream. Thanks, and sorry for the bad english
Click to expand...

The thing is, 16x9 is working for some people's needs. For example. Maybe you are shooting some stock footage (no audio, no need to go into FCP from proxies, etc) You could open your shots in Redcine, tweak to your hearts content and then export those files to whatever format you need. This works today. The problem that you can come across is codec errors while shooting, but only with highly detailed, problematic areas in the image (which isn't too often from what I've experienced so far and others have reported). So, although 16x9 has some quirks right now and is not fully supported, for some people it may be serving them well, and that's why I think it makes sense to have it as an option until all this is worked out in build 16.
 
Biba said:
You can export audio from QT proxies , they must work , in QT , but half screen will be black , sow you can export sound from it , i don't remember shoutcut key in QT to export sound.
Click to expand...
thanks, but the problem is that we don't have QT proxies, and no way to build them using redalert, because it crashes opening 16:9 .r3d files
 
stevesherrick said:
If Build 16 was not right around the corner, I would suggest we make this whole 16x9 confusion a sticky and perhaps something on the Red site. What's happening (and no offense to you D.Paccagnella) is that some are not doing their homework thoroughly enough. This topic has been covered in many places, not just on Reduser.
Click to expand...

I guess i'm not following you here- how is build 16 going to fix 16:9 QT proxies? or do you mean future clips shot on build 16 at 16:9 will work correctly?
 
Well, I don't want to be the official word on this but Stuart (and I think Jim) have indicated that Quicktime and Final Cut will support 16x9 come Build 16.
 
You must log in or register to reply here.
Back
Top