Ron James
Forum Replies Created
-
I think he means you cut and/or finish in a 16:9 sequence, export in 16:9 (make sure you select 16:9 in compressor) and create a 16:9 DVD. Any DVD player I’ve encountered has been able to automatically display properly, depending on what it’s playing through, though I’d test first.
The only thing that still confuses me in this process is whether to use a 16:9 or 4:3 menu. I guess if you know you’re ultimately viewing on 4:3, go with the 4:3 menu. I’ve tried with a 16:9 menu, but it displayed stretched on a 4:3 TV. Could’ve been a mistake on my part, though.
I guess I’m going into DVDSP forum territory, now.
-
[boydmcc] “Probably the only real hair pulling experiences I had were when someone would express 3 distinct thoughts, requiring at least 3 English sentences, in only 3 Chinese words, taking less than a second of screen time. Argh!”
Ah, that’s cool. I worked on a film in Canada here that required a lot of Inuit translation. Thankfully, I didn’t have to get involved with that, but sitting on the sidelines, watching all the debates about what this meant and that meant and the translators saying the Director was manipulating things to make for better soundbites…I couldn’t help but wonder how much truth actually made it into the translation in the end.
Thanks a lot for the subtitling tips. That’s great stuff to know. The marker idea sounds like a great one, actually. I guess you want to make sure you mark the clip, not the sequence? Good luck with it!
-
Could it be too much juice for the battery backups? I thought I read something similar to this about a month ago around here.
-
Not a 100% sure, but I think they’re referring to “an ATTO issue with their fibre channel card” as Walter mentioned above.
-
I could never go without a Wacom tablet again! I use it not only in FCP, but for almost everything else, too, especially web browsing. It allows you to move very fast.
The only glitch I’ve personally come across in FCP is when trying to select filters in the filters tab of the Viewer. For some reason, I can’t get them to stay selected sometimes (say, if I want to delete it) so I have to just right-click with the pen and cut it. I tried it with the mouse, though, and it seemed clunky to me, so I don’t think it’s a Wacom problem. One other thing…on a few older G5’s, I’ve had freeze-ups when using the Canvas shuttle slider with the pen. Works absolutely fine on my iMac Intel, but it would just freeze (for about a minute or so) on these G5’s. One was a dual and one a single G5, but both had stock graphics cards, which I’m thinking could be the incompatibility? Walter has mentioned in the past that he’s never come across this.
All in all, the tablet rules! I had a Graphire, but ultimately ended up with an Intuos (thanks to Walter) and it’s worth every extra penny.
HTH
-
It occurred to me after posting that you must mean rendering inside the nest and then getting more RT b/c the renders are preserved. That’s definitely a useful thing.
I can’t imagine subtitling four hours of interviews…you must have great patience! (That’s a compliment, btw)
I wonder if there’s any better app you could use for subtitling that isn’t too expensive. I think there are a few that subtitle quicktime movies, but I can’t remember the names right now.
The updating problem with nests, as far as I know, is just buggy behaviour. I’m not sure if it’s much of a problem in the latest versions of FCP, but in past versions, it was a good idea to yank the opacity bar on the nest up and down (or click visibility on and off, if I remember right) anytime you made changes inside the nest. Nesting is most definitely (IMO) a must-have feature, don’t get me wrong.
-
“My problem was when we played back the timeline with the nests,
audio files were clipped on interviewees on crucial dialog lines,
too much randomity.”Ahhh, what you want to be doing in this case is mixing down audio. The nests are adding additional tracks to your audio RT overhead, and it’s bogging down. You can also set the quality of playback in your preferences. I leave it at lower quality and then do mixdowns for high quality.
“The reason I nested was I have eleven chapters in my Doc.
It was mainly in the interest of saving time, getting from
one section to another.”Now, this is what I wanted to find out!
What I’d do in your case is start out by editing in chunks, all in seperate seq’s, if you like to keep things seperated in chapters like this.
Then, when it’s time to do your fine cut or whatever, copy/paste everything into a master sequence.
Important Part Comes Here…
When you copy/paste the chunks into your timeline, leave gaps between each section. Keep it that way as long as you want to keep these sections seperate. Make sure you don’t have or create gaps anywhere else in the TL, only between these sections. This way, you can easily jump from section to section using Shift-G and Option-G to go forward and backward. Simple! And absolutely no need for the clunkiness of markers and nests.
What I was saying about nests earlier, is they should only be used for specific purposes related to fx building (IMO) b/c there are other ways to do practically everything else you’d want to do.
-
I’m a long-form editor and I rarely use nests. I find (but this is just my opinion) they’re too clunky for non-specific purposes. It’s just a question of why do I need to add another layer to navigate? It sounds to me like you’re using it more for finishing than for cutting. It would personally drive me nuts to have to dig into a nest every time I wanted to make a change. More importantly, though (and this might be baggage from older versions) I’d be seriously worried about the nest updating properly, which is the reason, I’m guessing, this thread started in the first place.
[boydmcc] “The doc I’m working on is incredibly graphics intensive – in a very simple way, it’s entirely subtitled using FCP’s outline text. If I laid the whole thing on one sequence, I’d be in rendering hell, even using unlimited RT (I have a Quad, but with the stock graphics card).”
I’m curious, though, are you saying that Nesting reduces your RT overhead? You get more real-time layers when you use Nests? I wasn’t aware of that. Is that correct?
-
You can mark the individual clips, but I’m guessing that won’t help you? Are you using them to locate clips or mark specific points in the timeline?
I don’t think there’s anyway to have timeline markers move with the clips. Not sure how you’re repositioning them, but the fastest way is probably to copy the timecode for the new location, then open the marker you want to move and past the timecode into the marker timecode field. I can see that this would get very tired very fast when you’re having to move multiple markers all the time.
What specifically are you marking?
-
Oh, I see.
What I would do if you’re trying to preserve markers is…
1) duplicate your sequence and store the original away safely.
2) start cutting in the duplicate, which will still have all the markers.
Duplicate as many times as you need. That way, you’ll also have previous versions stored away in case you need to go back.
Am I on the right track?