Okay, Avid Rangers- mount up.
Imported P2, consolidated media to MediaRaid. Media type in project settings = MXF.
I launch AudioSuite. try to throw down a 'Normalize" effect on the layers. The following error dialog pops up:
AudioSuitePIControler: RequestAudioSamples( )
Unexpected AME status [4].
"Compressor" effect, same error as indicated above. So, created an audio mix-down of the inadequate audio tracks, 'Normalize' that, and I'm golden. What gives?
wish I could say it's gratifying to 'stump the band', but it's not usually the case. No takers?
this is interesting, in an arcane Avid-ish sort of way. P2 clippers might benefit from this tidbit. Imported P2 clips to a bin (not media, just clips) and threw them into a sequence. I'd invoke the "Unexpected AME status" as I tried to render some 'Normalize' AudioSuite effects applied to the audio tracks. SOME of the clips. 60-70% would render just fine.
So I go to the recalcitrant clips and trim back 1 frame from the clip in the timeline. It then renders without incident. Go Figure.
of course, the whole 'Render In/Out' functionality goes out the window, but I can process my clips on the timeline.
There you have it.
Bill:What if you import the media instead of just clips to bin? Do you still have the same situation?
Larry Rubin
Senior Editor
The Pentagon Channel
www.pentagonchannel.mil
Good Question, Larry. I'll try that sometime and report on the difference. I'm conserving RAID space by importing clips, making an edit, and just importing media to those sections of clips needed. My old 'save hard drive space' habits from my 72 gig MediaDrive die hard...
Avid Technology, Inc. brands: Digidesign | M-Audio | Sibelius | Pinnacle Systems | Sundance Digital
© Copyright 2000-2008 Avid Technology, Inc. All Rights Reserved — Legal Notices | Terms of Use | Privacy Policy | RSS Feeds | Site Map