"Does this mean that if I have an external drive with material I've ama'd to and I bring that to another bay this bay will rebuild it's own ama database when I mount the ama files?"
In my experience, running EditShare in Avid "Unity" Style mode, yes. This is tedious."What if I'm opening the bin I had originally mounted the ama media in from the other bay?"
"Does each local station come up with an identical media database for the files so the original bin has a fighting chance?"
"If the ama media databases are unique on each system I can't see how that could work in a shared environment like you have said here."
On Mon, Jan 13, 2014 at 4:49 PM, johnrobmoore <bigfish@pacbell.net> wrote:
"As far as I can tell, this managed AMA is nearly useless, especially in shared environments, because it stores the database files on the local drive."Does this mean that if I have an external drive with material I've ama'd to and I bring that to another bay this bay will rebuild it's own ama database when I mount the ama files? What if I'm opening the bin I had originally mounted the ama media in from the other bay? Does each local station come up with an identical media database for the files so the original bin has a fighting chance? If the ama media databases are unique on each system I can't see how that could work in a shared environment like you have said here. Hmmmmmm, I'm not on V7 yet so I can't tinker.
--- In Avid-L2@yahoogroups.com, Mark Spano <cutandcover@...> wrote:
>
> I just ran into this exact problem and (think I) fixed it.
>
> Does the console show something like 'failed to scan PMR' or something to
> that effect? This would be a little bit earlier in the list, before you
> tried to AMA. If so, then there is something corrupt in the AMA DATABASE.
> It's getting corrupted on our systems pretty easily as well. The error that
> pops up on an AMA to QT file is "There was an error linking AMA files".
>
> Solution:
>
> Go to /Users/Shared/AvidMediaComposer
>
> delete the AMA Management folder.
>
> As far as I can tell, this managed AMA is nearly useless, especially in
> shared environments, because it stores the database files on the local
> drive. At least in my experience. One of the many PMR files in this folder
> was corrupt, and it wouldn't allow me to link anything. Deleted the
> databases, and it rebuilt them, allowing me to link once again.
>
>> On Mon, Jan 13, 2014 at 4:03 PM, <Greg@...> wrote:
>
> >
> >
> > One of our 8 seats absolutely refuses to AMA anything. I've done
> > everything I can think of - I'm guessing it's something obvious that I'm
> > missing, BUT -
> >
> > Mac Pro 5,1 dual 6-core, 16g ram, OSx 10.8.5
> >
> > I did the 'long' uninstall, completely removing everything avid and
> > digidesign before re-installing 7.03; Re-installed all the latest
> > 'not-installed-by-the-MC-installer' AMA plugs, including XDCam, P2, etc.
> >
> > When I attempt to AMA to an XDCam, for example, and I have 'create a new
> > bin' selected, the Avid will even create the new bin correctly - but NOT
> > AMA the files. The console even shows that the sony XDCam MVP plugin
> > was used, but there's nothing in the folder.
> >
> > In the case of QT files (that contain DNx or other media) the error
> > message is simply 'there were errors linking AMA files' and the console
> > only shows ----- AMA Link To File(s) -----
> >
> > All the same files AMA normally on every other machine in the building.
> >
> > Next step is to rebuild the system drive from a blank SSD, but that's a
> > pain and there's a lot of stuff on there I don't want to have to redo if
> > I can avoid it.
> >
> > Before I flash this system drive into oblivion, anyone have a clue
> > what's happening?
> >
> > GH
> >
> > -------------------------------------
> > Greg Huson
> > Chief
> > Greg (at) SecretHQ.com
> > www.SecretHQ.com
> > DigitalServiceStation.com
> >
> >
> >
>
__._,_.___
| Reply via web post | Reply to sender | Reply to group | Start a New Topic | Messages in this topic (4) |
.
__,_._,___
No comments:
Post a Comment