David Cherniack
Forum Replies Created
-
[gary adcock] “That you recaptured material on the same machine twice via FW does not mean that it is frame accurate for editing, Not for a professional editor. It does mean that your machine can recapture the same content in the same manner from the same device consistently. Move that content to a different machine or transfer that as an EDL to some other machine – and I have more than serious doubts that it would have the same accuracy.”
Gary, in fact the downconverted and HDV clips were captured on different computers. PPro and the Z1 were the same, however, so you may well be right that different software and decks will do things with varying degrees of accuracy. My experience however, would seem to invalidate your general statement that capturing via firewire is not frame accurate.
[gary adcock] “And it is not a MAC vs PC debate –it is a hardware issue independent of both of those things.”
I don’t recall bringing Macs or PCs into it. I did mention reading (on the HDV forum) that FCP may have accuracy issues with capturing via firewire. Or maybe it was specifically with the Z1 . But surely we can mention apps without raising platform issues.
David
AllinOneFilms.com -
Gary,
The proof, as they say, is in the pudd.
In my tests I captured from the Z1 via FW a DV downconvert, then captured via firewire the same material – pans of birds in flight – as HDV. Frame Accurate every single time.
This is to Premiere Pro though I seem to recall rumblings from FCP users about frame accuracy. Perhaps you’re referring to that.
There’s no inherent reason why captures from firewire, mpeg or mjpeg shouldn’t be frame accurate. The t/c is inherent in the signal.
Inserts to firewire devices are a different story.
David
AllinOneFilms.com -
[gary adcock] “it is not frame accurate for editing in its native space.”
I don’t know why you say this. My tests with HDV and Matrox Axio show frame accuracy on re-ingestion.
There are issues with the Sony camera if you ingest over camera turn offs with quick record on. In taht case there is a gap on the tape time code on the far side may be off depending on how your NLE registers timecode on ingesting. But if you don’t croos those time code gaps when ingesting the t/c is frame accurate.
David
AllinOneFilms.com -
[Jiri Vrozina] “At least Your Director has got some common sense.”
And the depth of pocket to actualize it.
David
AllinOneFilms.com -
Hi,
I may as well answer it here. It doesn’t support frame buffer from AE yet. But it’s obviously something Matrox is working on at high priority.
David
AllinOneFilms.com -
And I should have added an Undo list that will survive a crash!
David
AllinOneFilms.com -
[Mike_S] ” if you want to escape PPro. They’re all just tools to do a job …”
Sorry..I guess I didn’t make myself clear enough for you. I don’t want to escape PPro. I want it to become an efficient NLE. It’s not that far off. 2.5 should do it, if the designers will listen and prioritize that as a necessary goal. (I’m starting to get the impression that 2.0 will not provide any major improvements along that line.)
David
AllinOneFilms.com -
[Aaron Strader] “It’ll be nice to have, but I doubt I’ll use it.”
I’m sure I’ll use it…maybe one or two times….
Don’t get me wrong, I’m all for added functionality, but not at the expense of fixing the design mistakes in PPro. If they’ve done that as well, I’ll have little to complain about aside from the 18 months they’ve forced us to live with those dumb design mistakes. If they haven’t addressed at the very least:
– the project window
– keystrokes assignable to every single function within the app
– the stereo audio fiasco
– proper project management – that doesn’t require multiple renders of the same thing inside and outsie a sub-timelinethen I’ll be very pissed.
There’s also a lot more streamlined functionality that can be added to timeline editing, particularly how some tools are invoked ( the mouse hovering over the yellow line should immediately invoke the pen tool, alt and ctl modifiers should temporarily invoke the other tools, rather than being forced to switch tools just with with letter keys that require more focus to find, and have to be switched back), ranges that can be manipulated, and how tracks are locked/unlocked ( or armed disamed as an alternative metaphor ) but I’m willing to wait for those.
But not another 18 *&^%ing months!
David
AllinOneFilms.com -
Fabulous! Just what I need to deliver my shows to the broadcasters! I’m sure they’ll be thrilled to hear they have the option of having it in Flash 8.
If that’s what’s delaying the release of PPro 2 then these people (substitute whatever demeaning nomenclature first pops into your head) just don’t have a clue about the broadcast post industry. By all means let them integrate whatever kitchen sink aquisition they want, but if they hold up the new release of their core post application for months because of it, they just don’t get what’s necessary in the broadcast NLE marketplace. Their commitment to it would appear to b little more than lip service.
David
AllinOneFilms.com -
[Aanarav Sareen] “Every NLE has its own set of problems. If you have a minute or two to spare, take a look at either the Apple forums on their site or even the Avid forums and you will see threads spanning over various pages that essentially just complain about the NLE.”
Aanarav,
This is true but the design flaws and missing features in PPro make it compare poorly at the present time to Avid and FCP. Because PPro came to the ball late, it had a chance to see what gowns the others were wearing. It tried to copy the best features of both but somehow didn’t notice that it left a lot of ugly seams unstitched, revealing that it couldn’t really dance without tripping over them every now and again. Fact of the matter is, they should have really hired a better gown designer.
Forgive the strained metaphor, but you can get the idea 🙂
David
AllinOneFilms.com