Skip to main content
Question

Packaging up Final Cut Studio

  • February 10, 2011
  • 3 replies
  • 29 views
donmontalvo
Forum|alt.badge.img+36

We just got a packaging request for Final Cut Studio (latest version). I searched the archives and read some old threads. Before I end up knee deep in this, wondered if I could ask you folks:

  1. Is volume license an absolute must, or can we package individudal license and enter licence after it's deployed on first launch (if possible; ala AAMEE)

  2. Is the best practice to separate into separate packages, or can we create a "whole enchilada" package (also ala AAMEE)?

  3. Any gotchas or shudda-seen-that-coming feedback?

I'm checking on whether we have a volume license, but won't know for a while. Figured I'd ping the folks on this list. Thanks in advance for any feedback!

Thanks,
Don

--https://donmontalvo.com

    3 replies

    B
    Forum|alt.badge.img+11
    • Bukira
    • Contributor
    • February 10, 2011

    hi Don,

    I package the whole item, and its huge but thats fine for me as i put into my compiled configuration and it halves the speed anyway, so its not really problem, we only install at imaging

    One think to watch for is when you separate, that all the items like to work together and also like to be in a certain place,

    compressor ONLY works if its directly in /Applications not a sub folder

    Also i had issues with compressor and Qmaster when i installed logic over the top of a final cut imaged mac, it broke compressors link to Qmaster and i had to install over the top again

    So be VERY careful when making a composer package, they rely heavily on each other and core components like the Pro Kit, so Logic and Final cut hare to get working together if you split them

    Also compressor requires bonjour to be on as does Aperture

    So to save you hassle troubleshooting after

    i would 1 package for final cut and 1 for logic if required,

    i also found that the license can get broken if you install final cut and then install logic, so i make a package that contains only the volume license file so i can easily deploy later if i need to fix licensing

    so be careful

    Criss

    Criss Myers
    Senior IT Analyst (Mac Services)
    iPhone / iPad Developer
    Apple Certified Technical Coordinator v10.5
    LIS Development
    Software Management Team
    Adelphi Building AB28
    University of Central Lancashire
    Preston PR1 2HE
    Ex 5050
    01772 895050

    E
    Forum|alt.badge.img+21
    • ernstcs
    • Contributor
    • February 11, 2011

    Volume Licensing is nice. I make one whopper package of it. Criss did well
    with the other minor details.

    Craig E

    B
    Forum|alt.badge.img+11
    • Bukira
    • Contributor
    • February 11, 2011

    Thanks, ive had bad experience with Final Cut / Logic and Aperture in the past, and Compressor only this month, getting them to work together but install separately can be a pain,

    I do

    1. image computer
    2. run composer
    3. install ALL of Final Cut + any software updates, Pro Kit etc as required,
    4. License Final Cut Pro

    5. build Final Cut Pro Package

    6. run composer 7 install Logic Studio + software updates 8 build Logic Studio package

    9 run composer 10 install Aperture + software updates 11 build Aperture package

    This then relies on installing all 3 in the end on the clients

    Final Cut will run on its own, but Logic cant nor can Aperture

    So i then built a Logic ONLY package for Staff to install if they dont have Final Cut

    I then build a license ONLY package containing just the logic and the final cut license files from Application Support,

    I have had situations in the past were all of a sudden the licence file is missing from Application Support, it just vanishes, no one has access to delete it but its gone, so i can heal the computer by just installing the licence file which takes a few seconds

    Criss

    Criss Myers
    Senior IT Analyst (Mac Services)
    iPhone / iPad Developer
    Apple Certified Technical Coordinator v10.5
    LIS Development
    Software Management Team
    Adelphi Building AB28
    University of Central Lancashire
    Preston PR1 2HE
    Ex 5050
    01772 895050

    Terms & ConditionsCookie settingsAccessibility statement