Not sure I understand your original issue...
However, you may import PrPro project (or just selected sequences from PrPro project) into another PrPro project.
Thanks for the reply....I did import the project and then copy/pasted into the timeline but didn't work, maybe I'm not doing correctly. Basically what I did was import project 2 into project 1. Project 1 was the place where I want to paste all projects into. So after importing project 2 into 1....I went back to project 2 and copy/pasted edited clips in that timeline and brought into Project 1.
But the transitions didn't copy/paste.....
The issue again as mentioned in first post =
Is there any way to get premiere to copy/paste transitions from one set of edited clips in one project and bring those edited clips into another project??
Basically, the whole intent behind this is to speed up rendering/exporting time. When I render the timeline first...then export - it's faster. I want to bring the 15 or so video's I edited in diff projects --- into one project....then render.....and export from there.
If anyone has any suggestions in terms of any other tricks to speed up exporting....let me know.
Sure there is.
Just create a temporary Sequence, Paste there the copied clips+transitions, then cut'n'paste this Sequence into another Project and finally cut'n'paste the clips from the Sequence.
By mentioning your original issue I meant I'm not sure that rendering preview can boost your final output rendering...
Anyway, when you import PrPro project into another PrPro project, you don't need to get back to your project 2 so as to copy clips from and then paste them into your project 1.
If you import PrPro project into another PrPro project as a whole, all the sequences with all your cuts and transitions (as well as the rest project structure) are safely transferred into a targeted project.
If you import just selected sequences, those selected sequences with cuts, transitions and utilised assets are transferred into a targeted project.
All you need is to simply open up the necessary sequence to see it in the timeline...
rendered the work area...then exported. It was much faster
Overall, it would actually be about the same time. Yes, the export part of it can go faster if you check the Use Previews box, but when you include the time it takes to render, it adds up to about the same, so you're not really saving anything here.
Jim - I think it is in fact faster....going to test again but exported regularly and took 2hrs 50min's for each video....then rendered and exported - took prob around 2hrs total - including rendering/exporting.
I edit audio and when I have a bunch of clips in the timeline, and export regularly - it takes about 10X as long as when I render, then export. That's if I have maybe 7-10 tracks within the project timeline.
But whatever, I'm going to test again - it's rendering, and has been for a few hours....so I didn't get a chance to test yet on CS5 - in terms of the suggestions.
So you guys are saying I can import project B into project A and just drag project B's sequence to project A's panel to create a new sequence. Then copy/paste the contents of project B's sequence into the Project A's sequence and keep all the transitions?
Steven - how do you copy a sequence - right click in project panel and copy or ctrl C? then just paste into new? and do the rest...
Thanks guys - let me know as soon as you can
Personally I'm saying you can import project B (C, D etc. - as many ones as you want) into project A and then in Project panel just double-click an imported sequence to open it up in project A timeline so as to make sure all cuts and transitions are preserved...
exported regularly and took 2hrs 50min's for each video....then rendered and exported - took prob around 2hrs total - including rendering/exporting.
That seems unlikely. If anything, the separate render/export should take slightly longer (though not that much) as you may also have to transcode the preview files (depending on your preview codec) during the render, as well as decode them for the export. Besides adding an additional layer of compression, it also adds time. Here's what I mean.
1. Decode original media
2. Render new frame based on sequence, effects, titles, etc.
3. Transcode that new frame to the export codec of choice.
Render (1-3) /Export (4-5)
1. Decode original media.
2. Render new frame based on sequence, effects, titles, etc.
3. Transcode that new frame to the Preview codec (if anything less than Uncompressed, this adds time and potentially degrades quality)
4. Decode the rendered frame (if not Uncompressed, which adds time)
5. Transcode that (decoded) render frame to the export codec of choice.
So you see, the render first process has two extra steps which add time, one of which could also introduce additional artifacts (depending on your preview codec).
Yes, you can copy the sequence in the Project panel in Project1 and then paste it into another Project2, but I'm not sure whether it will retain rendered effects.
After pasting the sequence in Project2, Premiere will link the files which are already in the Project2, but if they aren't there, it will paste the media assets into the root folder of the Project panel.
It is more reliable and maybe faster than using Dynamic Link to import a particular sequence, but then you may have a mess in the root folder in the Project panel.
After selecting "Import Selected Sequences" radio button in the Import Project dialog and pressing Ok button, Premiere launches another instance of itself - a process called PProHeadless, you can see that in the Windows Task Manager on Windows or Activity Monitor on Mac. In the "Import Premiere Pro Sequence" dialog you can see a label in the bottom left corner of the window which says "Connecting to Dynamic Link server".
Importer's call for dynamiclinkmanager doesn't mean you create any Dynamic Link while importing PrPro sequences into another PrPro project... However, if you mean that call per se... Not sure it is even called if one has an individual application, but not Production Premium or Master Collection, earlier than CS6...
I'm sorry it's not meant exactly Dynamic Link as it is used to be when importing a project into a different kind of application. As Fuzzy_Barsik correctly said - Premiere's Importer uses Dynamic Link Manager and a new instance of Premiere Pro (PProHeadless or probably Window-less) in order to see the contents of the Project. It's unusual way to import objects of the same application. Thanks to fast PCs, cheap memory and SSD drives that's not a problem nowadays.
Guys...thanks a lot for your help - your solutions worked - importing project and double clicking sequence - and then copy/pasting in. Kept the transitions - so.....sweet!
Thanks so much - I really appreciate it.
Tested more exports and rendering before export definitely is faster than straight export. I appreciate the logic and how things should work...in multiple tests though the rendering before exporting is faster.
Jim - I'm curious to hear what you'd have to say as to why audio rendering/export times are so much faster doing what I described. Rendering Audio first...then exporting....compared with just exporting.
We've touched on the video stuff. I'm absolutely certain that doing what I just described when it comes to audio exports is much faster. Why is that?
Maybe it is faster because the rendered staff is on the same drive with the exported audio, and it is slower because the render is on a local drive and the originals are on a nerwork or a slower drive.