Skip to main content
MyerPj
Community Expert
MyerPjCommunity Expert
Community Expert
April 12, 2023
Answered

Using Productions - Trying to get my head around it

  • April 12, 2023
  • 4 replies
  • 1001 views

I'm trying to work out how to use Productions in as beneficial a way as possible for a single editor with various clients.

 

While contemplating it, I was thinking I'd have a master Production with shareable things, like just say for instance a Sound Effects (SFX) project. I was figuring that would be used in all other projects/Productions. So, an overall set of reusable projects to be inherited by other Productions. But now I'm thinking more that I need a Production for each client, otherwise Everyone would be inheriting Everything in all my projects Everywhere - all at once? 🙂

 

I'm trying to figure out how 'reusable' is used. In fact I'm guessing now that each client would need their own "Production" and then the shareable items for just them (logos, etc) would of course be in that Production, but overall shareable projects like the SFX project would not actually be shared but would simply be copied in. (as its own project of course).

 

This would mean it's not shareable in the way I was thinking. As it's simply a copy. So, what if I get some new cool SFXs? I can't copy them into one project only, I'd need to put them into each clients own SFX projects. So, not really sharing, which would be if I put them in the 'master' (OMG can we still use 'master' around here?) SFX project and it would be inherited by the 'copies'.

 

So everyone has the same copy of the SFX project in their own overall Production. And the copies are just that and updates to the original are not shared/reusable/inherited.

 

@Bruce Bullis  @R Neil Haugen 

This topic has been closed for replies.
Correct answer R Neil Haugen

Hey there! Productions for me has been a huge improvement! I would never ever go back to stand-alone projects. Period.

 

I've been running my one-man shop in Productions, in my third year now. It's fantastic because ALL my sound library, b-roll, template projects/sequences, and graphics, are available for any project I'm working on.

 

I use the recommended structure of folders for main things with subs. So each client or major project is a subfolder off the main production folder. They all show in the list so it's real quick to move from one to the other.

 

And there are NEVER any problems from having multiple projects open, or duplicating assets when using in a different project ... it's slick.

 

Within each of those subs, there are subs as needed for organizing that project. And in those subs, the project files of the project.

 

They recommend you set up a different and perhaps parallel folder structure on disc for storing the media, rather than having it actually reside in the same folder of the Production.

 

So I have an overall "2023 Production folder" on disc.

 

Inside that I setup the Production, and Premiere created the actual Production folder.

 

I also set up an Assets folder in that top level folder, and that's where I've built my asset storage. 

 

It's worked very well.

 

Neil

4 replies

MyerPj
Community Expert
MyerPjCommunity ExpertAuthor
Community Expert
April 20, 2023

Hey Neil, thanks very much. I got it now. I was making it harder than it was, and it's even better than I thought. I was thinking some kind of top-down sharing, but it's actually share anything in the production with anything. Really cool. I'm getting everything setup now.

 

thanks again.

    R Neil Haugen
    R Neil Haugen
    Legend
    April 21, 2023

    It's actually pretty "ordinary" after you get used to it. And ... it's just so much easier to do.

     

    Neil

    Everyone's mileage always varies ...
    MyerPj
    Community Expert
    MyerPjCommunity ExpertAuthor
    Community Expert
    April 13, 2023

    Interesting Neil, So the way you do it you do get to share an overall project like SFXs that goes into your "2023 Production" (folder), and you have next level down Project folders for each client - this being the key:  

     

    "So each client or major project is a subfolder off the main production folder."

     

    I think I missed a step in my head, but it's sort of the way I thought it should work. In the docs I was seeing 'you can have unlimited productions' (of course) ‘but only one can be open at a time’ so I was thinking they are recommending to have a production for each client. But having those Folders under a main production means you can share SFX, b-roll, etc, and various projects and customer files live in that main production (2023) FOLDER. Cool, just one folder to backup.

     

    Thus McDonalds and Jack in the Box would both be neighbors sharing in the one overarching production (2023). They share SFX, b-roll, etc. And they live quietly together? If I have those cool new SFX, then obviously they go into the one master SFX project which is in the first level of the 2023 Production. If you are importing that already created SFX project, then imported one now becomes the master... I can go with that.

     

    Let’s say you get a new customer, Chipotle 😊 Will having all the McDonalds and Jack in the Box projects in just the one Production, slow Chipotle down? Does PP check each of those (other) projects when starting the Production or when a project is opened?

     

    Sounds good. If it's agreed that Jack, Mac and Chipotle can and should all live together, I think that would answer the question. And thus it would work in the original way I was thinking. And that would be cool.

    R Neil Haugen
    R Neil Haugen
    Legend
    April 13, 2023

    Adding J-I-T-B won't slow anything down. The issue with slowdown is about how much data Premiere needs to load to RAM/cache files. In standalone projects, it loads the entire data from the file, including all the meta for every asset in the project, into RAM/cache.

     

    In Production, it only deals with the currently active project. Even when pulling assets from other projects.

     

    So they recommend multiple projects per ... "project". Maybe on project for assets whether video/sound/whatever, another for sequences. The sequences project can access the asset meta as it needs it, but doesn't have to load the entire meta for every frickin' thing into RAM/cache files.

     

    I will normally have a subfolder setup under any one client, that has the projects in particular subfolders of that client folder.

     

    Neil

    Everyone's mileage always varies ...
    Remote Index
    Remote Index
    April 13, 2023

    "In Production, it only deals with the currently active project."

     

    Neil,

     

    I don't think this is correct. I believe Premiere Pro loads all necessary data for all open projects (not just the "currently active" one). If you have more than one project open, that means multiple projects are loaded / active in RAM.

     

    There's more detail in published docs (Best Practices & Workflow Guide For Long Form and Episodic Post Production) but it's unclear:

    "In a Production only the clips and sequences that are open are using system memory and processing power." p.60

    It's not at all clear what is meant by "open" clips and sequences, but I think the implication is that all clips and sequences in an open project. (If not, the implication is that the above is not true for stand-alone projects ... which would be weird.) Some clarity would be good on this from Adobe.

     

    MyerPj,

     

    If you haven't read that section of the guide you might want to take a look.

     

    One consideration is that Adobe seems to issue software updates about 4 times a year - so if you've got multiple projects (productions?) in different states, they may be dependent on different versions. Alternately, if everything is in one production you will have to assess whether or not to update everything with each software update.

     

    R.

     

      R Neil Haugen
      R Neil HaugenCorrect answer
      Legend
      April 13, 2023

      Hey there! Productions for me has been a huge improvement! I would never ever go back to stand-alone projects. Period.

       

      I've been running my one-man shop in Productions, in my third year now. It's fantastic because ALL my sound library, b-roll, template projects/sequences, and graphics, are available for any project I'm working on.

       

      I use the recommended structure of folders for main things with subs. So each client or major project is a subfolder off the main production folder. They all show in the list so it's real quick to move from one to the other.

       

      And there are NEVER any problems from having multiple projects open, or duplicating assets when using in a different project ... it's slick.

       

      Within each of those subs, there are subs as needed for organizing that project. And in those subs, the project files of the project.

       

      They recommend you set up a different and perhaps parallel folder structure on disc for storing the media, rather than having it actually reside in the same folder of the Production.

       

      So I have an overall "2023 Production folder" on disc.

       

      Inside that I setup the Production, and Premiere created the actual Production folder.

       

      I also set up an Assets folder in that top level folder, and that's where I've built my asset storage. 

       

      It's worked very well.

       

      Neil

      Everyone's mileage always varies ...
        Bruce Bullis
        Bruce Bullis
        Legend
        April 13, 2023

        [I've solicited better-informed opinions than my own, from the team...]

          Terms & ConditionsAccessibility statement
          Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices