Is Oliver Peters wrong?

[Rafael Amador]

[Paul Dickin] “It is the job of an GUI to present complex mathematical data in a user-friendly way – 1 frame at a time if its rasterised video, and 1 pixel etc..
But because of the need to have sub-frame/sub-pixel accuracy the GUI needs to hide the 1.000000000 nature of one video frame, whilst letting me make a sample-level audio edit at 1.123456769 or whatever.
(Being of the same mind as Rafa means I have no off-the-top-of-my-head notion of how many significant digits I need to specify an audio sample accurately – that’s the GUI’s job…)”

I’m not questioning the way FCPX manage time. I question how the GUI manage what is a “1 frame duration” and specifically in something where is not involved any Time base (stills). The Project time base dictates the Frame duration.
High precision is needed in “video signal managing” (video processing, effects, color), but on timing you can’t go (you don’t need) further than a “1 frame” (well 1 field).
Audio doesn’t need any Time-base. His very Sample rate is the best time-base and allows a “1s/48.000” accuracy on editing.
We know how buggy has been (is) FCP, assigning the default “Sequence Preset” to any imported audio file
(https://library.creativecow.net/lyon_matt/fixing-fcp-assets/1)

[Paul Dickin] “The best thing to be said about a mid-life crisis, whether from internal or external circumstances, is that it is just that – mid-life. Life goes on… 🙂
/GlassHalfFull mode”
I wish I’ll be in my “mid-life”, but I’m barely 6/8 years from retirement. Sure, that’s a factor when i consider getting in deep with FCPX, but not the main. I work alone (fired my last assistant 3 years ago) and I do everything from shooting to delivery (scripting, Color grading, commercial and driving too). I have always new things to learn: Filming, lighting, color Grading (I want to buy me a PANA AF-100 now. Cine-like; very different of what I’m used) learning a new NLE makes no much sense for me. I would take the challenge (there are things in FCPX that I like badly) if I’d think that was of any help, but starting by the fact that I can’t get tied to a computer/storage system, FCPX is not an option.
rafael
PS: The Indian Nagas are an ethnic group (I’ll love to visit Nagaland), while in Laos they refers to some legendary giant flying snakes living in the Mekong. here they are convinced they exist 🙂

http://www.nagavideo.com

[Rafael Amador]

[Jeremy Garchow] “What do you use out of the revision offerings?”
I have FieldsKit and RelSmart Motion Blur.
I was waiting for Twixtor to be 10b.
Another great plugin gone is NeatVideo, although they have a discount for PP migrants.
I passed from top analog system to a MB.667 (TiBook. Still working!!) and a SONY handycam (DV), so for me trying to extract the best of those short means has been almost an obsession.
I could afford spend a lot of time learning and then applying (here clients don’t push you, but the opposite 🙂 those long, boring processes (Chroma smoothing, de-noising, rendering to 10b -on short performance machines- and CC) and techniques (avoiding re-compressions and color field changing) but in the end all that effort really paid back. For years I’ve been getting the best jobs around because the picture from my DVcam looked better than any other in the country (nothing better than a PD-170 around till I bought my EX-1).

[Jeremy Garchow] “[Rafael Amador] “I’m pissed also, because Apple NOW release information that have been holding for years just to discredit FCP in front of FCPX:
WHITE PAPERS FCPX for FCP Editors Pg 20: Export QT Movie is 8b ( I guess means QT Conversion). I wanted that statement few years ago.”
This has been known, though for a long time. It’s really easy to test.”
Yes, WE new and we avoided QTConversion, but Apple has never stated that in any user manual or so. It may be in some deeper technical publication, but for years they have been thousands of questions (at least in the COW), and Apple kept the mouth shut.
For years Apple kept the mouth shut about too many issues (10b rendering when broken, gamma issues,..).
(Few years ago I was very pissed when people of Adobe, started to pop in the FC forum Sorry Dennis Radeke). I thought those guys went there just to sell PP; but now I really appreciate that somebody came down to the arena . In the end they were compelled to answer questions)

[Jeremy Garchow] “[Rafael Amador] “FCP has had only problems to mix video standards and to identify files Time bases but FCP never had any problem to manage any time-base. ”

I find this to not be true. FCP Legacy improperly tagged frame rates all the time on audio files (even ones with tc) causing major sync issues. It said you need a frame rate of 23.98, but really 23.976 is needed, and that causes issues as well. X intends to shore up that problem. It rounds to the frame for display (as do cameras) but the timing is way more accurate. This is good. The old method started with a tc number, then did the math in frames, which is less accurate and not as good. Here’s a discussion on it:

https://forums.creativecow.net/thread/335/16076“

You are right Jeremy, but all that was due to a poor Apple job. Proper TC tagging was a mess, so was Interlacing.
But I’m with you that we have to move on. TC was implemented 30 years and now is limiting.
I was complaining just about the “Still frame duration” setting in FCPX. Even if FCPX uses a different method for timing, the GUI could have been easily set in Frames. This would make things easier for users. In he end we are working with few standards (23.976/24/25/29.97/30).
FCPX doen’t needs a big data-base to keep in mind the effective duration of “1 frame” in the different standards, and multiply that value by a certain number of frames.
rafa

http://www.nagavideo.com