[Eda]

Hey Matt,

I just went in and it turns out that the output reference on the deck was incorrectly set. Looks fine now.

I’ll spit out the show on Monday.

Thanks for your hard work!
El

[Eda]

[Les Kaye] “Yes they do. However it is a VERY meager substitute for the more powerful (and foolishly neglected by Avid) feature of a viewer waveform that scrolls to follow a playhead indicator, and which allows for more accurate audio editing.

Much like Avid’s knucklebrained approach to handling alpha imports, this lack of implimentation (that most other NLEs now offer) is another one that defies logic”

An Avid WILL scroll the waveform in the timeline to follow the playhead indicator, if you have that option turned on. Frankly, hitting the button to turn the timeline into a source viewer is no different to me than FCP’s way of clicking on a tab to reveal the waveform. As far as “more accurate audio editing”, I do very complicated dialog and music editing on Avid’s all the time, so I’m not quite sure what your concerns about
the accuracy are.

As for Avid’s approach to alpha channels, if you had worked in film first and dealt with mattes, Avid’s approach makes perfect since. Avid was, originally, a film assist tool, not a video makers tool, and many of
it’s ways of doing things reflect that. Photoshops “backward” way of doing alpha channels was criticized widely when it came out. Eventually, Adobe’s mind set won out, and Avid editors just had to make sure to remember to invert.

[Eda]

Well, an Avid won’t show a waveform in the source viewer, but you can always switch your timeline to show the source (the little two tv icon near the lower left side of the timeline. ) Then show your waveforms in the timeline (from the Fast Menu aka the “Hamburger”) in the timeline. AFAIK all current Avids allow this.

HTH,
eda

[Eda]

Ok, one off the wall thought here –

We recently had to bring in some HDV footage via a Miranda bridge after getting a new firmware
upgrade from them. It wouldn’t work (broken time code message) until we got the offset set correctly.
Now it will capture 80% of the time. We turned the “warn on timecode breaks” to “warn after” and it captured
everything correctly. (Even the 20% that it says have timecode breaks)

Maybe try playing with the offset in the machine controll settngs?

Like I say, off the wall thought.

eda

[Eda]

Hey Walter,

FWIW we have posted about 12 productions using HD-SDI since migrating to FCP 5/FCP 5.2 and Kona2 and have not had any of THESE problems. However we are doing everything in 1080i, and using Xserve Raids.

Are you taking 1080i material and trying to capture it at 720p? If so, I can try to test this workflow next
week and let you know what happens. Since we don’t have any 720p material, I can’t offer to test that for
you.

It concerns me that you are having these problems, as I have always considered you the HD Kona guru! I
know that this is not just a RTFM issue that you are having, so I hope we can help you solve it.

Best,
eda