|
|
11-20-2008, 10:35 PM
It would be great if RedRushes included an option for setting the Reel Name in the exported quicktimes to a name that matches the Log & Transfer setting in the new Final Cut Studio plugin. This way, RedRushes can be used to create rushes that are then 'onlineable' back to RAW via L&T in FCS.
11-26-2008, 12:31 PM
YES! I Second this.
I want to be able to still do REDRUSHES at 1024x576 Qtr Res for offline with my burn in then match back to my R3Ds to do an online in color!
Currently with file A001_C001_1124FM from Build 17,
FCP will make the Reel Name A001_1124
Red Rushes with FCP 8 Character Reels: A001_C001
Please sync these up Deanan!! Thanks!
11-26-2008, 02:54 PM
use Clipfinder..... it takes three mouse clicks to conform.....
11-26-2008, 04:01 PM
Hey Guys,
So I think the problem goes deeper than just reel names. I've run some tests and I can get the reel name to change in FCP no problem by just going down the line in the bin and copy-pasting the reel that L&T would give that stuff. In my case A003_1121 is what the Reel would be called if I did a native ingest. Te problem becomes this, when I do a media manage as per the white paper released recently, and I go to the sequence to do a "batch capture" it automatically looks for a Deck in Log and Capture rather than popping up the L&T window. Now- this could be a isolated issue that someone might be able to clarify to me but if I'm not mistaken, the original media must have been captured via L&T and not imported as I did with my Rushes from RedRushes....anyone have any ideas??
11-26-2008, 04:24 PM
I don't know who wrote the whitepaper but this has never, ever popped up L&T - ever. FCP has no way to force it to do so, either.Originally Posted by R3D2
11-26-2008, 05:32 PM
The white paper is correct. If the edit you are confirming contains transcoded Red footage done with L&T, FCP will indeed pop up the log and transfer window and 're-capture' the clips. If however the clips were transcoded another way eg RedRushes they are not tagged as being from a file based camera, so Log and Transfer can't be launched.
Clipfinder gets round this problem.
11-26-2008, 09:38 PM
:angry03: It isn't a case of "can't", it's a case of "won't" - there's no way to tell FCP any other way.
Bah.
(I should clarify, I'm angry at Apple here, not any posters in the thread. Clipfinder saved my arse on the job in question.)
11-28-2008, 03:17 PM
Just an update here--
The work around is
1.)import your rushes then rename reels in the Bin.
2.)cut your rushes.
3.)Make a new bin and set as Logging bin then do a batch capture of all your media using L&T,
4.)Media manage your cut and make offline
5.) Reconnect Media and point to your capture scratch
6.) It'll prompt you that the Reel name doesnt match (because it's hard coded in the UUID, regardless of what you change in the FCP bin). The TC and Filenames WILL match though..
7.) Boom- migrate to color and back in 2K.
or....just use clipfinder, but Hans- your app only seems to work intermittently for me on both my MacBook Pro and MacPro 3.0GHz
Cheers,
Tim Fassnacht
11-29-2008, 02:27 AM
Tim,
Can you give examples of scenarios where Clipfinder works and where it does not ?
I'm happy to work with you on resolving those issues.
Send me an E-mail with whatever information you have and I'll get on that case right away.
Cheers,
Hans
11-29-2008, 10:07 PM
Hey Hans,
I've finished all my rushes with RedRushes already- I used your app for the visual framing reference though for the crop, it's a fantastic feature. Unfortunately, after Reel 3 I couldn't get CF to execute a render after hitting go. I got a crash with a log after just quitting when those renders didn't work; didn't think to grab it. I'll fool around some more and send you the log if I get an error. I plan to use your workflow for the conform process to Native in FCS. I've run tests and it works beautifully. I will keep you posted on how things go.
Cheers,
Tim
| « Previous Thread | Next Thread » |
