Output from AME doesn't seem to respect the umask settings in launchd-user.conf (OS X 10.8 & 10.9).
In order to allow multiple users on the SAN to access and edit files, we set the default permissions to be both user and group writeable - however, output from AME is consistently only writeable for the user who created it. This leads me to believe that AME (or some component of it) is running as a system-level process and disregarding the user application umask settings.
Has anyone else in a shared media environment experienced this issue?