Sean Oneil
Forum Replies Created
-
[John Davidson] “Highpoint RocketRaid 1820 (I think) with an 8 bay attachment from the DR Group. “
My Leopard test system has a RR 2224. Be careful about what drivers you have. Download it again today. Highpoint has released at least three different builds of “version 1.10” since Leopard was released. The first two I tried didn’t work. They don’t mention it anywhere on the website that they keep finagling with it.
-
[JeremyG] “I’ll give it a whirl. Is it h264 only?”
Honestly I do not know. Haven’t had time to test everything.
FYI, I’ve only tested film-based NTSC with v6.0.2. But with the previous version (6.0.1 & QT 7.2)I have tested 30fps based sources and had the same problem.
-
[JeremyG] “It was Uncompressed HD upconverted to 720p through Compressor. Worked awesomely. I couldn’t believe it actually. “
I think that is a 720p thing. Throw your Uncompressed video on a 720p timeline in Final Cut (don’t even use Compressor) and it actually works great.
But try using Compressor’s deinterlace filter to convert ProRes 480i into h264 480p. Disaster.
-
[JeremyG] “It doesn’t? What’ wrong with it? I just ran something through COmpressor yestreday for a deinterlace and it look great. I still think revision’s fields kit is top notch.
“What codec was your source? I’m going to guess it wasn’t ProRes.
-
[CoryTV] “I can’t say for certain that I tried this in 6.0.1, but 6.0 and all 5.x made me render avid-codec qts, and as of 6.0.2 play in RT in the timeline, (orange bar) which is very nice. Now, hopefully this wasn’t an accident and now they’ll go back and cripple it on purpose… :-)”
Strange. Since v5, all non-supported codecs always showed up as orange for me. Only exception was Photo-JPEG. It was the only one purposely crippled as far as I knew. Never tried Avid.
-
I worked for about an hour after the update. Didn’t have any problems except one. It told me that the autosave failed (I’m sure all of you have had this error at one point) . It’s probably because there were autosave files from the project already created with 6.0.1.
Gotta say, these new features are a pretty big deal. Honestly I’m a bit put off that they weren’t there from the beginning. Being able to hide the clip names on the sequence (so you can actually see the audio waveform) is one of those things that should have been there since FCP 1.0. The zoom in/out to playhead is a lifesaver. I can’t believe how much time I’ve spent in the past deselecting clips just so I could zoom to where I wanted.
Compressor’s deinterlace filter still doesn’t work.
As far as the OS 10.4.11 update, Safari 3 is pretty cool. Searching is done more like Firefox. QT 7.3 has a different look – no borders on the left and right sides of the video.
-
[climbon321] “As a post house that has been plagued by the lost render files in FCP6 (that the update claims to fix), I would also love to hear if anyone has run into any problems with the update/knows of any reasons to hold off on updating. “
I can’t justify any reason NOT to update. The status quo (OSX 10.4.10 / FCP 6.0.1 / QT 7.2) is not in good shape at all. I’m updating now, will report any issues.
-
Look at the release notes for all the ProApps. My thinking is that we’ve been guinea pigs ever since 6.0 came out. They just waited till Leopard and 10.4.11 were out to fix anything. Now maybe FCP will be stable and reliable again. So I didn’t hesitate for a moment. Installing the updates now.
My only worry is the Kona, but I’m sure they’ve have an update soon.
-
Here’s my FCS2 laundry list. FCS2 has been out for 6 months now and these issues have not been addressed:
– Multiclips ARE broken. No simpler way to explain it. They work at first, but when you start doing things like copying sequences to other projects, nesting sequences, batch re-capturing, etc., all hell breaks loose. And whatever you do don’t send anything that was once a multiclip to Color. It’s hard to pinpoint and explain what’s happening, but basically it seems that once something is a multiclip you can never go back. The XML never forgets – it always remembers the multiclip relationships. And many functions of various workflows cannot handle that.
– The Widescreen filter has a missing/transparent video line (2nd to last line on both top and bottom). Have to use mask shape. This is just annoying, if nothing else.
– Exporting interlaced footage (only tested ProRes NTSC and 1080i) to Compressor is completely useless. The Deinterlace filter won’t work. It combines the wrong fields regardless of the settings. I’m doing more and more web clips for clients, so the amount of time this has added to my workflow is becoming a serious problem.
– The “open timeline” has shortcomings. It doesn’t properly mix NTSC 480 and 486 footage. Final Cut Pro 4-5 did not have this problem. FCP 6 also does not add 3:2 pulldown when placing 24p footage on a 29.97 sequence. Instead it adds 2:2:2:4 pulldown which is unsuitable for any tape master. This is obviously not unique to v6, but v6 was marketed as having an open timeline as a new feature – so I take issue with it not delivering as advertised.
– Capturing 23.98 footage from a Kona 3 is broken if you use ProRes(HQ), but oddly enough works fine with non-HQ ProRes. See my posts in the AJA board – Gary Adcock also confirmed this.
-
I updated to 7.3 on two different systems. It’s working fine.
I had one weird thing where I couldn’t add audio transitions in FCP 6. After trashing the prefs that problem went away.
I’m not saying people should update though. I did it because 7.2 was such a mess I hoped this would work better.