2020. 1. 24. 04:23ㆍ카테고리 없음
Hello Everyone,I am deploying Avid Media Composer with JAMF Casper JSS Server 9.8.1 to 100+ OX 10.10.3 machines.Tried to snapshot. Tried extracting the installer pkg from the DMG and deploying it via policy. Also pushed the factory DMG to the system drive and then launching via installer command.In all cases after the JSS installs the package, the software runs and work fine with the exception of some additional background rendering services.
Feb 3, 2019 - Intro - Avid Media Composer might be a bit more complicated than. This folder must be set on a (fast) media drive at the top or root level. Write access with Avid Media Composer on samba shares fails Seems to be. MC is first looking in root of the share for directory called 'Avid. 3 - MC will automatically create a single folder called 'Avid MediaFiles' on the root level. DO NOT RENAME or MODIFIY THIS FOLDER.
Avid Media Composer Root Drive In Pc
(A server that runs separately from the application and handles rendering and transcoding) They only run under the admin account created when installing the os. In all other accounts, administrator or standard, the services will not launch and run.If I install the software by running the installer manually from the logged in user account, I am prompted once for admin password as usual and the software and background services work fine for all users.To test I built a clean install of OS 10.10.3. No JSS software installed.I used terminal to install MC manually. If I use sudo in terminal to install Media Composer with root access using ( sudo installer -pkg /“Install Media Composer.pkg” -target / )MC installs but Background Services/DMFService will only start up and run under the admin user account.
Other users cannot run it.If I use terminal and login as root ( su installer -pkg /“Install Media Composer.pkg” -target / )MC installs and Background Services work fine under all users.My guess is that JSS is not using root for every process in the installer pkg. “sudo” is allowing the installer to run as root, but the root privileges are not being passed/piped on where needed to other installers in the Install Media Composer package.How can I ensure that the entire pkg installs under root authority?Any help greatly appreciated.
I had a similar issue with the bg rendering in MC for users other than admin, not specifically related to imaging but similar nonetheless. I was able to modify the permissions on the client bg rendering folders that MC creates. Once I modified the permissions for those directories, the bg rendering was able to work again. If that could work for you, you could configure a policy or script to modify the permissions on those directories for the applicable user account. I know this doesn't answer your question directly but thought that it could help. I have deployed Media Composer From version 7.x to now 8.5.2 to over 150 clients (in our environment) without issue using a standard JSS policy.
I have not had to modify directories (YMMV). We have deployed on 10.9.x, 10.10.x, and now 10.11.xMy standard MC policy includes (5 total packages):-Avid supplied packages. Avid Media Composer Install Package (Latest version we support). Avid AIR Creative Collection Effects Package (Latest version supported by MC). Avid License Support Package (App Manager Latest version)-Custom supplied packages.
App Manager Preferences (Custom Prefs/Restrictions for our environment). AMA Plugins (Custom for our cameras). My expirence is if the user is a Standard usr which all of our students are Avid Media Composer will start however M.C. Will throw an error regarding not access to the hard drive. During installation in /Users/Shared/Avid/GlobalControl is created.After installation upon running Avid the first time, /Users/Shared/AvidMediaComposer with the folders Avid FatalErrorReports and Avid Users is created.
I didn't have the correct permissions on these folders last year and Avid would complain that it couldn't write to the FatalErrors folder.Using Composer I captured these folders separately. I changed the /Users/Shared folder permissions to everyone and deploy to my machines. Without changing these permissions Avid will complain and not start.My package installs Avid fully licensed as we use a Floating License Server and no need to reboot.My Permissions package adds the following folders under AvidMediaComposer:AMA ManagmentAvid AtticAvid SearchDataDSMLogFilesShared Avid ProjectsSynced Avid ProjectsIf these folders get deleted avid will fail to launch.
On a PC I'd suggest MDV as a free option for managing the media but unless you boot camp not a solution on a Mac.You could look at media mover that allows you to manage media by project.But sadly the Avid media tool has no real media management capabilities beyond deleting media and dragging master clips back into projects.You could copy all the media to the new drive.Then on the old drive use the Avid emdia tool to delete all the media related to the current project. Then remove the old drive and put back the new drive and use media tool to delete all the media not related to the current project.Clunky but it shoudl work. I've done something similar as follows yesterday1 close down avid2 copied the avid mediafiles folder, project folder and in my case an omfi mediafiles folder from the media drive to the root of the new drive3 renamed the avid mediafiles folder and the omfi mediafiles folder on the internal media drive so avid can't see them4 started up avid, opened the project on the external drive, all master clips automaticly found their links on the external drive.5 in your case, after copying and making sure alle links are still there and functional, open media tool to delete the ones you don't need. If it doesn't work as above all will still be there in the original project, linked to the original driveNOTE 1: I always give my masterclips a source/tape name, even if tape is a thing of the past. It still is a variable Avid media management relies on.NOTE 2: I run MC 7.0.2NOTE 3: All my mediafiles were transcoded from AMA to DNxHD. Maybe it's dodgy but I tick 'delete original media files when done' on consolidating, to avoid having '.new' clips.Or maybe even more dodgily, close Avid and delete all the databases before dragging and dropping whole folders from drive to drive (or partition to partition) on the desktop. Avid Media tool is useful for 'gardening' or tidying up assets for individual projects into specific partitions, before doing that - and likewise checking what's where, when it's done.But if some of those other applications are safer/tidier-minded, that's great!