Frank Laughlin
Forum Replies Created
-
Anyone have any info. Email requests to Blackmagic have gotten as little response as I’ve gotten here. Thanks in advance for any guidance.
– Frank Laughlin
Digitonium -
Frank Laughlin
January 18, 2011 at 4:50 pm in reply to: To Stretch, Or Not to Stretch (SD in 1080 project)Scott: thanks for your thoughts. No idea what you’re referring to re ‘cards’ or monitoring. Not an issue. Monitoring out to 10-bit HD monitor.
Re pillar box, I agree, but it’s not an option. Producer won’t do something HBO doesn’t do. And I can’t find a single pillarbox in any HBO doc.
-
Frank Laughlin
January 18, 2011 at 3:51 pm in reply to: To Stretch, Or Not to Stretch (SD in 1080 project)Thanks, Scott. But…
Several of the talking heads I’m using are full-frame in SD, meaning if I just scale, I’m going to see eyes to lower lip, maybe just nose. And, as I said, pillar boxing is verboten (with this prod company). In looking at ‘high-end’ docs, everything is stretched. It stunned me, I would have said ‘no way’, but EVERYTHING is stretched, as far as I can tell.
– Frank Laughlin
Digitonium -
Frank Laughlin
January 18, 2011 at 3:31 pm in reply to: To Stretch, Or Not to Stretch (SD in 1080 project)Thanks, but we’ve taken a look at all of the doesn’t-fill-the-frame options. Again, in looking what ‘the big boys do’ (HBO, etc.) there is no 4:3 footage used (in a 4:3 format). I’m not looking for optional ways to stay with 4:3, I’m looking to see if there exists a magic formula for how much stretching is too much, etc.
It looks to my eye that HBO is scaling the video up about 275% and using an aspect ratio (per FC’s aspect sizing) of about 15. Can anyone confirm? Add? Subtract? Scale 🙂
– Frank Laughlin
Digitonium -
Frank Laughlin
January 14, 2011 at 5:54 pm in reply to: Renders for sequence and nested not the sameFor those of you that edit in one big sequence, I have always gotten to a point, after what must be thousands of edis, where the system starts to slow down, throw up ever more frequent ‘preparing for display’ messages, and just doest run as well. How have you ‘one big timeliners’ avoided the system hit?
-
Frank Laughlin
January 13, 2011 at 10:10 pm in reply to: Renders for sequence and nested not the sameShane: Thanks for the feedback. I get your workflow, but I think nests may have changed since the last time you tried.
Nests DO reflect changes in duration – longer or shorter. When I edit a sequence that is nested in the assembly, the assembly changes. Gets longer or shorter. In fact, as far as I can tell, it reflects every change I make in the sequence EXCEPT the renders.
I unfortunately need to view the whole show all the time, several times a day. Producers want to see from x to y, and x and y are often not in the same segment. For me nesting is working great, except for the renders.
As far as I can tell, you and I are actually doing the same thing (editing segments of a show), except I have an assembled sequence I can show upon demand. My only request here is to understand why FC doesn’t connect the renders in the segments to renders in the assembly.
But I reserve the right to be totally wrong and have the whole thing blow up in my face (first time I’m doing this, but loving it so far).
Thanks for your thoughts.
– Frank Laughlin
Digitonium -
Frank Laughlin
January 13, 2011 at 7:42 pm in reply to: Renders for sequence and nested not the sameBret: Your experience mirrors mine. The nesting seems almost ideal, except for the renders. I don’t quite follow your fix for making FCP recognize the renders, though. Are you changing the opacity of the whole nested segment? Or the individual unrendered file inside the actual segement?
Thanks.
– Frank Laughlin
Digitonium -
Frank Laughlin
January 13, 2011 at 7:39 pm in reply to: Renders for sequence and nested not the sameMatt: You are right about the renders, but if I understand what you’re saying, you’re not quite right about the updating.
If a segment of the show is 5 minutes, and I nest it into the ‘Assembly’, and then go back and edit the segment, making it 6 minutes, that change IS updated in the nested ‘Assembly’. The only thing that doesn’t appear to update between segment and assembly are the renders.
– Frank Laughlin
Digitonium -
Frank Laughlin
January 13, 2011 at 7:37 pm in reply to: Renders for sequence and nested not the sameShane: thanks for the answer. Could you give me an idea why this is the wrong way to nest?
Keeping the entire show in one timeline seems far more cumbersome. Thousands and thousands of edits ‘live’ while working on a single timeline. It would seem to me this is the exact reason for nesting: keeping the show cut into 10-min segements and using the assembled nested version for ‘whole show’ viewing, and output to tape.
I’m not disagreeing, I just don’t understand your reasoning.
Thanks.
– Frank Laughlin
Digitonium -
Frank Laughlin
June 14, 2009 at 7:59 pm in reply to: “This project is unreadable or may be too new for this version of FCP”Having the same problem. Could you clarify your post for me?
When you say, “I was able to open the project on a different system (same version software)” do you mean the ‘same version software’ as the original file was created? Or, do you mean the same version software that failed to open on the first machine?
I’ve tried opening my problem project on two different machines both running the same version of FCP (6.0.5) without success.
Thanks!
– Frank Laughlin
Digitonium