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

Some New software on RED website

Ed Blythe said:
Stongbad_2Z, you should have a sniff around Cineform's ideas on the matter. You apply looks to the files directly in the OS (non-destructive, lotsa options) and then that gets applied in your NLE - without rendering. And then you can CC on top of that if you want - or go back to the files and change things around there (and save looks too). Sexy time. Hopefully something to look forward to.
Click to expand...

I saw that too. But that's if you want to go cineform. Or on the mac side, if you want to go Prores. Personally, I don't want to do either. But my clients do. So, it's good having many ways to skin this cat.
 
So, this plugin does a conversion from the quicktime proxies to prores?
 
We tried deleting the proxies from the shot folder and only importing the R3D files into log and transfer. The clip plays from the raw file only, so it appears that it isn't referencing the proxies.
 
bobbyd said:
We tried deleting the proxies from the shot folder and only importing the R3D files into log and transfer. The clip plays from the raw file only, so it appears that it isn't referencing the proxies.
Click to expand...

But it still could be using the exact same code that's used to generate the images in the proxies, so this doesn't really tell you anything about what quality it's working at.

I suspect from, the speed and the fact that it can only transcode 2K at 1K, that it's doing a half-resolution extraction.
 
PROBLEM SOLVED (Steps):

1) 'Log and Transfer'
2) Click on 'Add Folder' icon (Top Left)
3) Choose a folder and click 'Open' but be careful renaming folder names. The plugin needs the .RDC extension on folders, without this extension it doesn't works (This was my problem).
4) Choose in 'Preferences' (Top Right on Left Window) ProRes 422 or ProRes 422 (HQ).
5) Choose an IN and OUT point, Import Settings (Video/Audio), Name...
6) Finally, drag the clip or clips you want to convert to half resolution (4K->2K and 2K->1K) to the 'drag media here' area and that's it.

Clips will open automatically in browser as a ProRes clips. This clips will be physically located in the Final Cut Pro 'Capture Scratch' folder.
 
Chester said:
3) Choose a folder and click 'Open' but be careful renaming folder names. The plugin needs the .RDC extension on folders, without this extension it doesn't works (This was my problem).
Click to expand...

That was my problem too. Thanks.
 
Has anyone tried converting 4k 16:9 stuff? I keep crashing the program when I try and convert it. I crash the program when i select 3k 48fps stuff also, I don't even see the file in the viewer.
 
Does not work with 4K 16:9...
 
I noticed that it will at least bring up an image in the viewer for 16:9, although it only shows top half and bottom half is scrambled like quicktime proxie. Varispeed stuff crashes Final Cut though, right away.

Obviously this way uses the quicktime proxie and not the r3d itself.

I'm really hoping for all format support in quicktime very soon.
 
ChristopherKenworthy said:
Please tell me it's doing a full debayer. Otherwise I can't understand why it's so slow. A thirty second clip takes about 5 minutes to load, even on the newest Intel Mac. If it isn't doing a full debayer, it would be quicker to manually drop the H QTs into FCP.
Click to expand...

No, it's make ProRes files off the proxy information. The difference is that it converts the proxies over to ProRes--that's why it's so slow. However, FCP is much more responsive when editing with ProRes over the proxies.

Matthew
 
ChristopherKenworthy said:
Please tell me it's doing a full debayer. Otherwise I can't understand why it's so slow. A thirty second clip takes about 5 minutes to load, even on the newest Intel Mac. If it isn't doing a full debayer, it would be quicker to manually drop the H QTs into FCP.
Click to expand...

I found a 1 min clip took around 3 mins to import on an 8 Core Mac Pro 3.0

Ben
 
Ditto

Ditto

beneditor said:
I found a 1 min clip took around 3 mins to import on an 8 Core Mac Pro 3.0

Ben
Click to expand...


Ditto... I'm seeing a 3 min import from a 1 minute clip too... has to be 2:1 though.. they'll fix it. Just give them time. Hey, this is very bleeding edge guys, and it will come in fairly short order I figure. LOTS faster than REDCINE...

ALSO... if you're mac is running an upgraded version of FCS or Leopard instead of a clean installation, you'll probably see some yuck... do a clean install if it's not as I'm describing... a slower machine will be slower, but the speed in working in ProRes offsets that in a heartbeat.

Jerry
 
I'm pretty sure that varispeed stuff is also not able to be transferred with final cut.
 
isnt this the same as converting the proxies to ProRes via Compressor, with the disadvantage that i cant put the pro res files onto an external drive and edit where i want, and its not a full debyer?
the only huge advantage i see is, if you have broken proxies generated in the cam, this is a way to get audio out of the r3d file....even more important when using 16:9 footage which doesnt have the proxies, ergo the only way to extract the audio.
 
You must log in or register to reply here.
Back
Top