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

Batch Capture brings up Log & Capture NOT Log & Transfer

roryhinds

Well-known member
Joined
Jan 15, 2007
Messages
2,144
Reaction score
0
Points
0
Location
Vancouver, BC, Canada
Website
www.minefilms.com
Going on the FCP White paper they detail the r3d workflow going to ONLINE.

What I can't seem to solve is in step 6 below right clicking the sequence and choosing Batch Capture brings up the Log & Capture window (as its always done for me) and not the Log & Transfer window.

Anyone got this working with the Log&Transfer window?

---------------------------------------

When the Media Manager operation finishes, you need to change the ingest options
of the Log and Transfer window before you begin to actually ingest media:
5.1. Open the Log and Transfer window, and choose Preferences from the Action
pop-up menu (the menu with the gear icon).
5.2. When the Import Preferences sheet appears, choose Native from the
“Transcode to” column corresponding to the RED Plugin.
5.3. Close the Log and Transfer window when you’ve finished.
6. Lastly, right-click the new offline sequence that’s been created, and choose Batch
Capture from the shortcut menu. When the Log and Transfer window appears,
reingest all necessary footage from your archived RED media directories.
 
Going on the FCP White paper they detail the r3d workflow going to ONLINE.

What I can't seem to solve is in step 6 below right clicking the sequence and choosing Batch Capture brings up the Log & Capture window (as its always done for me) and not the Log & Transfer window.

Anyone got this working with the Log&Transfer window?

---------------------------------------

When the Media Manager operation finishes, you need to change the ingest options
of the Log and Transfer window before you begin to actually ingest media:
5.1. Open the Log and Transfer window, and choose Preferences from the Action
pop-up menu (the menu with the gear icon).
5.2. When the Import Preferences sheet appears, choose Native from the
“Transcode to” column corresponding to the RED Plugin.
5.3. Close the Log and Transfer window when you’ve finished.
6. Lastly, right-click the new offline sequence that’s been created, and choose Batch
Capture from the shortcut menu. When the Log and Transfer window appears,
reingest all necessary footage from your archived RED media directories.

Haven't tried it, but I'm told that it only works if your offline files are prores files done in log and transfer.
 
hmmm if this is the case then its not much use as most productions do the ProRes renders using REDrushes or REDCine.
 
FCP is generating IDs for the files internally, and when these are missing, the round-trip by media manager doesn't work as expected.
Use Clipfinder instead if you need other formats!
 
FCP is generating IDs for the files internally, and when these are missing, the round-trip by media manager doesn't work as expected.
Use Clipfinder instead if you need other formats!

Do you know any of the specific on these IDs that FCP generates?
Is there a way to trick FCP into opening Log and Transfer?

you say to use Clipfinder but that doesn't help the issue of using Clipfinder to generate ProRes files and then reconforming those files to RED QTs to go to Color.

I'm afraid it's another instance of the software being kinda half-assed in implementation.
 
Hello Rory,
I'm sorry but post WAS the thorn in RED's heal.
What is so difficult about: shooting RED, editing proxys, sending to Color, CC in Color with the Native .R3D files, then either send back to FCP as uncompressed 10bit or Export DPX for DI.
If you have more $$ and want to use Scratch, it's even easier!
What's so complicated?
 
Proxy's are buggy
ProRes is no way of linking back to the r3d with out something like Crimson.
Native isn't native at all it regenerates data requiring more storage
Color only has half debayer

half-assed in implementation
 
Proxy's are buggy
-Not for me... I've been editing proxy's for a while now (i use the _M for 4k material) and haven't had one problem yet.
ProRes is no way of linking back to the r3d with out something like Crimson.
-don't need ProRes, the proxys are fine.
Native isn't native at all it regenerates data requiring more storage
-so what? when you shoot film and then telecine to tape, you then have to capture the footage from tape to edit right? i don't see the problem here.
Color only has half debayer
-well, i guess this is a personal thing but it worked fine for me, i just finished my film in Color and mastered to HDCAM. It's been playing at festivals and all i get are compliments on how great it looks... that it doesn't look like video and such.......

I guess i'm just easier to please! :)
great shooting!!
 
you say to use Clipfinder but that doesn't help the issue of using Clipfinder to generate ProRes files and then reconforming those files to RED QTs to go to Color.

Load the sequence in clipfinder.
Do the 'replace MOV with R3D' option.
Drag the entire list of R3Ds to a new directory.
Log and Transfer that directory to Native wrappers.
Reconnect manually the sequence to the Native wrappers.
Proceed as normal.
 
Maybe I haven't explained this in sufficient detail, but you can actually use Clipfinder to conform from ProRes files to either P/M/H/F-proxies or wrapped Quicktimes without the need for a manual reconnect of each file.

To conform to, say, H-proxies,
- select "replace with H-proxies"
- select the directory that holds the matching R3d clips as "clip directory"

To conform to wrapped Quicktimes see this post: http://reduser.net/forum/showthread.php?t=22562

I am working on a way to avoid copying R3Ds for the ingest by L&T.

Let me know if I have missed anything.

Cheers,
Hans
 
Also, if I'm not mistaken the RED FCS whitepaper explains in detail how to replace ProRes files with native-wrapped log and transfer files. But clipfinder is free and something that should probably be used anyway.

Thanks for the awesome and free software, Hans.
 
Also, if I'm not mistaken the RED FCS whitepaper explains in detail how to replace ProRes files with native-wrapped log and transfer files.

The whitepaper method does not work if you did not originally create the ProRes files with Log & Transfer.

Which is why we love Clipfinder!
 
Going on the FCP White paper they detail the r3d workflow going to ONLINE.

What I can't seem to solve is in step 6 below right clicking the sequence and choosing Batch Capture brings up the Log & Capture window (as its always done for me) and not the Log & Transfer window.

Anyone got this working with the Log&Transfer window?

I have not seen a case where L&C opened rather than L&T but...there was a software change made between the beta version and the first release whereas clips ingested with the beta version and taken offline cannot be batch recaptured with the release version. It was a change in time/date format. This doesn't sound related to your problem but it's the closest thing I've seen.

Craig
 
Craig, L&C will pop up if the referenced media was created by RedRushes/REDCINE/Redline - L&T only comes up if the original process was also through L&T. There is no workaround other than the Clipfinder method posted earlier.

Unless you can work some magic over at Apple.
 
I have not seen a case where L&C opened rather than L&T but...there was a software change made between the beta version and the first release whereas clips ingested with the beta version and taken offline cannot be batch recaptured with the release version. It was a change in time/date format. This doesn't sound related to your problem but it's the closest thing I've seen.

Craig

I'll just second the post that says if you create ProRes via ANY other method that Log and Transfer then FCP will open the Log and CAPTURE tool when trying to batch in the method outlined in the RED - FCP white paper.

IF you could work with us to confirm / deny this issue Craig it would be a HUGE help to a lot of us working in ProRes.
 
Proxy's are buggy
-Not for me... I've been editing proxy's for a while now (i use the _M for 4k material) and haven't had one problem yet.

Ricardo,
so you can get full resolution, full frame rate playback of the proxy files?

You have no issues with stuttered playback? No dropped frames? Full 24 fps you can add transitions, effects and make multigroup clips with no dropped frames or rendering required from the proxy files?
 
Back
Top