[Daniel Frome]

Super old post! Unfortunately I haven’t used FCP or TitleExchangePro in many years. I frankly don’t remember how it all worked. Sorry about that.

[Daniel Frome]

download the x264 quicktime codec:
https://www.macupdate.com/app/mac/20273/x264-quicktime-codec

Then export directly out of Avid using single pass “quality based” with automatic keyframes and datarate.

This produces excellent visual results, exports faster than any other method of creating H264, and also uses all your cores (or, at least most of them).

[Daniel Frome]

– Put the 4×3 video on v1

– Add a 3d warp effect and use the scretch properties to make it 4×3 with black bars at the sides

– now “step in” (bind this to your keyboard if you dont have it).

Once you step into the effect you will see your video on v2, with a blank v1 (the v1 represents the ‘black’ behind your movie). We are now going to fill that blac with something else. Place your background on v1 and make sure it’s identical length as the above v2 track.

Now “step out” and view your normal timeline — you should see your 4×3 video with the BG on the edges. If you need to add FX to the background at all, step back in and mess with it.

You can now add your title on v2 and carry on.

[Daniel Frome]

[Charlie Austin] ” It seems to me that’s the same as any previous mac pro right?”

Actually it doesn’t. Other macs have a dedicated line-in jack, and another audio-out jack. The new Mac Pro, on the other hand, only has two output jacks:

1) “Combined optical/digital audio output/analog line out minijack”
2) “Headphone minijack with headset support”

Not sure why they had to do it this way, but it does indeed equate to no inputs, unless you count the “with headset support.”

I’m still curious if Avid starts up fine if you simply have an iphone headset plugged in. It very well might.

[Daniel Frome]

Hmm, odd, because PAL DVCproHD is indeed 1440×1080 (it’s 1280×1080 for NTSC).

[Daniel Frome]

Is your project settings set to the exact settings for DVCPROHD? Check The format tab > Raster Dimension and make sure it’s 1280×1080.

[Daniel Frome]

iphone mics have a different configuration than a stand mic input that we’re used to seeing on every other computer. If you look at an iphone headset, you’ll notice 2 stereo notches on the plug (just like any other stereo headset), plus a third notch: that’s the mic input.

So… the mac pro has no standard line-in at all? Only input from the “3rd notch” Apple mic?

You should plug an iphone headset into the mac pro… I bet Avid might start up then..as it might ‘see’ an input. Oh…this is too funny.

[Daniel Frome]

Try going to Bin 1 and pretend to link to new AMA files (the same files already in the bin). That might fix the links for Bin 1.

As for relinking a sequence to AMA files:

1) highlight all your AMA master clips (put them all into 1 bin to make it easier)

2) Use this relinking method (picture): https://readysetdit.com/wp-content/uploads/2013/02/Relink_Settings.png

Note: Instead of relinking to “source file id” like the image says, you may have to choose “source file name” depending on what kind of AMA files you’re dealing with. You can try both and see if it works.

3) the result will be a new sequence that should have been relinked to the AMA files you had highlighted!

[Daniel Frome]

If you’re on 7.03, the ability to relink AMA files en masse has been temporarily lost (I heard this from Avid directly, an admitted mistake).

Here’s what I’d do, and I can only confirm this works for 7.03: open the bin with your AMA material, then right-click in the bin and choose AMA link. Basically, pretend you are relinking to some brand new AMA files. Now find your identical files, wherever they are now, and AMA link them. Avid should realize these are the same files as before, and your old AMA master clips suddenly ‘update’ to the new location.

[Daniel Frome]

Do those clips have a green dot on them at all?

Also, check your media creation settings and make sure they are set to the same codec as your sequence (DNx120 ?). Possibly also go to render settings check on the “same as source” box.

You’ve probably tried all of these already. I use MC7 and have performed the same QT reference workflow as you. It doesn’t give me problems so long as the media doesn’t need any transformations with frameflex, etc. So… I think you’re assumptions are correct that it should be working.

That being said, half the time I just export a same-as-source quicktime in full to avoid any trouble. Especially since AMA doesn’t allow the QT reference workflow I’ve been using it less and less.