Larry Asbell
Forum Replies Created
-
If I am correctly reading the 6.0 release notes, the LHe card requires no firmware update with 6.0, although the Kona 3 card does.
-
Wow, I had the same problem and finding your post saved me. In my case the 720 footage was shot at 30fps. After import the video was about 10% slower than the audio so it rapidly drifted out of sync.
I thought I tried everything but I didn’t find the “Remove Advanced Pulldown” checkbox under the little gear icon, so thanks!
The FCP software team should be ashamed of themselves for leaving such a land mine hiding in there.
As far as I can tell, this setting is not changed by anything you set in Easy Setups or Audio/Video Settings. And I have not had the problem when doing importing before. Maybe what’s different this time is that I had to trash my preferences yesterday. If that is what caused the checkbox to be checked that means the FCP default for this setting is the way that caused the bad import. How do they justify that?
-
How would you like to work on a system that:
1) Had faders that couldn’t turn anything up? Or,
2) Recording an unexpected loud sound blew through the roof with no headroom?
If the audio tracks in your editor were at the level of a produced CD that’s what you would have. Remember digital audio has no way to represent levels higher than the range provided for.
Both FCP and Avid capture and work with audio below that level. That’s why you have +12dB gain possible on your faders.
So it’s not just that commercial recordings are produced with dynamic range compression and maximum volume. It’s that the rest of your audio in your FCP or Avid is not at the same full level.
– Larry Asbell
-
The message about mismatch may come because without dragging the sequence to the ETT window it defaults to trying to lay the contents of the viewer window to tape. Now that’s real logical!
It seems that everyone learning FCP can’t make Edit to Tape work at first and needs to be pointed to the non-intuitive “right way” to do it.
-
The patcher does not work for me but I guess the problem is different than I described.
The serial number I have was supplied with the BCC AVX 4.1 CD that came with my Avid Media Composer. The CD has no Mac version installer on it.
After reporting this problem earlier I was given a link to a download installer, file name BCCAVX421Full.dmg. This installer worked on a G5 but we are now upgrading to an Intel Mac. The installer runs but the plugins are not seen in the Avid.
The patcher that you pointed to is looking for 4.1 plugins and will not work on what I have.
Sorry this is so complicated, but it all arises from the fact that there is no Mac installer on this (early) 4.1 CD.
I’d be grateful if you could sort this out and point me to what I need.
– Larry Asbell
-
Hi –
I’m another BCC AVX owner who’s upgraded to a Mac Intel and need the 4.2.2 patch.
The location above no longer has the 4.2.2 patcher.
Would you please send a valid link.
Thanks,
-
Not the low/no cost solution you wanted but you should know that with Google Earth you can setup a move into any point on the globe and as you go in the detail actually improves. If you haven’t seen it yet you’ve got to try it.
It’s free to use but requires a $400/yr Pro license to record your move as an animation.
-
Do you have a chance to view the NTSC signal right out of your
card onto a better NTSC monitor? If you could you will probably see that the problem is not there.David may be right, but it’s possible that your problem is something different.
In analog video it’s called ringing or overshoot. You see it when the signal tracing a given scan line transitions rapidly from a high(video level) to low or low to high, which each scan line does as it makes a vertical edge. Lower quality or older processing circuits in vtrs, monitors, encoders, switchers, DA’s etc. add overshoot to your signal which shows up as you describe. For example a white letter against a dark background will have a brighter left edge where each scanline has overshot the brightness it was supposed to rise to. Sometimes just to the right of that is a darker “trough” where the level goes bit low before it settles down to where it’s supposed to be for the white letter.
I don’t know the quality or condition of your gear but I’m sure that if you make a VHS dub of your program and play it back you will see what I’m describing. If your monitor or something in your NTSC signal path is in poor shape you may see this without the VHS dub.
– Larry Asbell
-
Colin –
If it helps, a client of mine who ordered a Mac Pro with the nVidia 8800 a week ago from Apple’s site just got notice that it shipped on Friday.
I read in another discussion group that the shipping holdup was due to a needed point release in software related to enabling the PCI 2.0 bus that this card uses, rather than a supply problem with the cards.
Good luck with yours.
– Larry Asbell
-
If alternate scanlines of progressive converted to interlace do not look different you’re not looking close enough. True they don’t look radically different. That’s why it’s good. Don’t look for nasty interfield jitter, it’s not there.
And stop saying “because both fields looked the same (as they had to, since the original footage was progressive).”
Look more closely, and see that all the scan lines of a progressively shot image blend together nicely (to make the clearest possible picture of a moving object) – but they are not the same.
– Larry Asbell