Samuel Frazier
Forum Replies Created
-
Now that is a fine list!! I’ve been missing a lot of those things since I switched from Sony Vegas, though it has it’s own failings and I wouldn’t go back. IMHO things like Track FX in Video and Audio are nearly a must have at this stage in the game. A lot of NLEs even have a motion/ pan & crop feature for video tracks and this too would be nice. But, numerical reading on audio meters is a necessity today.
Some people have mentioned time remapping, and currently it is pretty terrible compared to what most other options can do. But since STP can already remap audio w/o distortion (within reason as all audio programs do), why not ask for this feature with a decent video remap in FCP? It is a nice time saver to adjust the speed of a clip and have the audio and video perfectly in line as you do it. This is something other NLEs have had for a while, Vegas for 2 years now. -
Mac sucks with USB 2. I’m told that firewire is always better than USB2 for video capture/editing anyway, but apparently Mac is also much slower with USB2 than PC. Perhaps with the switch to Intel this will change. But, unless it does this is a huge drawback.
-
Never had a problem with mine either. Bought an extra one that’s still in the packaging until I upgrade my mini to a G5 (hard to turn dowm $780 direct from Dell).
I don’t mind barefeats reporting a possible issue, actually I’ve very glad they do this kind of thing as it generally keeps us informed and up to date. But their language was poor in my opinion. Think it said, “but, there is a problem” in their summary and link. I would rather they had said there might be a problem. Much more accurate summary.
As far as the Dell 30″ goes, my first question would be is it also made by Compaq like the 24″ LCD. The specs sound different. -
While we’re on the subject of sort of alternative ways to go, how about this way?
-
Just exported a self contained version of the online movie (keeping the settings unchanged as 23.98 10 bit uncompressed) then opened that file in Compressor. This time, no aliasing. I’m still a bit confused though. Does this make sense to anyone?
-
Yeah, this does get confusing, so don’t feel bad. But, I think you’ve been given a pretty complete picture here and it sounds like you’ve gotten a hold of it now. The only other reason to edit from a 23.98 timeline other than what has already been mentioned is that you’re supposed to get slightly better mpeg2 encodings from progressive materials. The idea being that mpeg2 was developed to encode film originated material, which is of course progressive. I haven’t done any tests, but this is what I’ve read.
Still, this wouldn’t be enough to convince me to edit 24pn stuff on a 23.98 timeline. It seems to me that if you wanted to go that path then you should have shot 24pa in the first place. 24pn was meant to be edited on a 29.97 timeline and, unless I had some kind of unusual workflow or need, I would definitely edit it on a 29.97 timeline. -
So, do you not want me to mention my old editor? That would be kind of strange, especially as I was only pointing out what is a universal trick.
-
29.97. 24pn is captured as 29.97. It’s 24p stuff with pulldown added already so it’s 29.97 but looks sort of filmic. But that’s a whole different discussion. Anyway, just edit as 29.97. I’m absolutely sure about this and am sorry you got conflicting reports before.
-
I’ve been using Sony Vegas for a while and there’s a well known tip in its DVD authoring program to prep your audio for DVD to -31 something or other. Perhaps this is the same thing you’re talking about.
At any rate, 0 is cutting it a little close. But, I can’t think of a reason to put it too far off 0. The safer you get from 0 the more audio fidelity you lose. And, unless I’m wrong, there are no set rules or standards for DVDs, so close to 0 is advisable. Think someone once suggested -.3 unless that’s just in my head. -
I’m just checking into this myself. I believe fcp will only edit up to 24 bit. I did email Wes at Automatic Duck and I believe he was able to make his software work with my 32 bit files, but that was when I sent him a 32 bit file (not a file from a FCP timeline). I’ve been meaning to email him back to see if there was any way to get Automatic Duck to preserve the full 32 bit depth. If I can find a solution, would you want me to post back to you here, or is this a workflow that’s just too much trouble, or expense, etc for you? Just let me know.