[John Pale]

Phase cancellation caused by improperly wired mikes?
Can you play one channel at a time?

[John Pale]

To give a little more info…what Job says is correct. The Nitris DX is not supported with the new Mac Pro. Dave C from Avid has stated on other forums that it doesn’t work reliably and there will NOT be a fix as it is a hardware incompatibility. In your case, it seems to work okay with older MC software, but it may fail with other projects. The Mojo DX, however, is supported with Thuderbolt adapters. If you want to use your Nitris DX, you need to use your old Mac Pros or get an approved PC. Or get a third party I/O device.

[John Pale]

Assuming you have not ingested any footage via import or tape capture, it’s fine, except for the caveats Michael mentioned. If you have, that footage is now SD and won’t simply switch to higher resolution. It will be upconverted SD. Avid is not resolution independent.

[John Pale]

[Trevor Asquerthian] “May be unrelated but I have had this issue with built in RTAS plug-ins in v6 and v7

Workaround is to switch workspace to a different setting (eg audio editing) then back again

“

Thanks. Didn’t work, but appreciate the suggestion.

The Avid supplied plugins work fine. I don’t have any other third party AAX plugs to test.

[John Pale]

Job,

I have the L2007 from Massey and it’s not working properly in 8.1, even though I have the AAX version of the plugin. The plugin applies, but the interface doesn’t appear. I contacted Massey about it and they are investigating.

[John Pale]

What is your project setting?

Mixing frame rates is not normally a problem with Avid, but if you are having performance issues, you can transcode to your project frame rate on ingest.

I would AMA link to the files and then transcode everything to Avid DNX HD. In a 29.97 fps project (1080i 59.94) you can use DNX 145, 220 or 220x. Most of the broadcast work I do is at 145. If your system can handle 220 (it sounds like it might have problems), then go for it.

I would prefer using AMA and then transcoding, rather than importing. This usually alleviates any issues with color shifts that occur using legacy importing, which are caused by the ancient QuickTime components.

[John Pale]

Not sure what causes this, but I have seen it happen too, on unity systems. If you know what bin the clip is actually in, open it and see if it regains its marbles.

[John Pale]

You need OSX 10.8.5 or 10.9.4. Lion won’t work. You can download older versions of Avid software with your license, I believe (they show up in my account, anyway), if you cannot upgrade your OS for some reason.

[John Pale]

iPhone and other phones shoot variable frame rate, which might cause some issues. Not familiar with CS5… Does it have the option to Interpret footage at a specific frame rate? If so, do it at your sequence frame rate.

[John Pale]

“I used a custom layout in FCP7 and I basically have the same layout in PPro. I use a different layout for Avid because Avid just works differently. Sometimes I’ll take a screen shot of the keyboard layout and print that off for reference if I’ve been away from a particular NLE for a long time.”

Agree with Andrew here. I think FCP classic and Premiere Pro have a great deal of similarity in approach, so you can probably customize your keyboard to be close to the same, however if you try to do that for Avid, you will not be able to get the most of out of it. It will eventually lead to a lot of frustration. I am long time Avid user and also used FCP a great deal from version 1-7. I edit completely differently on Avid and FCP. You can edit like FCP in Avid, but it’s really like having one hand tied behind your back, and works against Avid’s strengths.