Move/Copy Sequence to new project - Why isn't this working?

Question

Hello all,
I'm experiencing an issue that I can seem to get to the bottom of. I have two open projects and would like to copy a sequence from one to the other. When I drag to the new project I get the + indicating I should be making a copy but nothing happens. I am able to copy individual clips this way, but not sequences. Any ideas?
 
I suspect I can use Media Browser but that's such a slog and I have done it the other way 10k over the years so hopefully I've got a setting off or something.
 
running PP 25.1 but had the same issue in the last version or two of 24. On an Intel iMac. Cleared the cache and reset the preferences...

Kyle Kramb · Accepted Answer

Hey, totally sympathize. When you're working stuff supplied by others, and they do "interesting ... things, well ... yowza, that's a problem.

I've worked a couple projects that had to be outside my Production due to the issues of the client ... which had intriguing issues that caused major headaches. And even been queried to potentially take over couple projects, one of which sounded initially kinda glitzy cool.

But the lead producer had done much of his own setup/initial editing, and it was now down to try and find a way to take the hot mess he'd made, of this massive project for the total assets involved, and get a final edit/color/sound done. After a few questions, I politely said no. As in no way in Hades was I gonna touch that project.

I think in your case I'd sill use Media Browser to import the sequences into the project. Cleaner if slower workflow.

Not so far along in this one that I need to punt but it does make more work for me than I expected. Hopefully Adobe can work on this – certainly not a Resolve fanboy but I feel this would not be in issue. I wonder if there is some sort of work around RT'ing with Resolve but probably not.

**edit: unchecked "automatically hide depended clips" and now it works but brings in all the individual clips - which are already in my project, and orginized. Argh

Mod note: Moved your solution to the latest post so it can be marked as correct.

R Neil Haugen · Answer

One of the reasons a Productions workflow is vastly superior to older stand-alone projects. And I'm a mostly one-person shop with a number of internal and external 'clients' to produce for. Slick & spiffy.

As I have all my broll, audio libraries, specially built sequence templates, everything, available for any project for any destination without duplicated references or messed up project files. I'd never go back to stand-alone projects except for specialized testing of workflow/media issues.

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.