Offline processes are missing when Copying events from project to project

Does anyone have the same issue as the offline processes on your events won’t follow when you are trying to copy events from a project to another?
I tried using both drag/drop and copy/paste, none of them work…
Please help!

What you mean?
Offline processes are stored in the project file.

I mean when I open two projects and tried to copy some events with some offline process on those events to another project.
Only the events themselves got copied, but not those stored offline processes.

They are associated with the project.
If you need the processing applied to the audio files, you must make the processing permanent.

You need to understand the idea behind non-destructive editing.

1 Like

Yes. The DOP files are in the Edit folder. While the unedited event is in the audio folder. You cannot copy the event with the processes.
This is “non-destructive editing”

1 Like

You have to first make the “offline process” permanent, into its own audio file.

You might also try importing tracks from the project into your new one. That might bring across the DOP.

Thank you all.
I now understand why it’s not followed with events.
However, I think it would be great if Nuendo can figure out a way to make it possible.
I was a legacy Fairlight user and it’s really intuitive to do this kind of job.
I can borrow audio clips from another project and paste them to your working project.
It even links the cursor position to let you paste them at the same TC.
I have no idea why Fairlight could do this and keep the DOP on audio clips.
If I make the offline process permanent in advance, I then cannot edit them which is not what I want.
I now use xml to import the section, but that’s not a time saving way and sometime I just need maybe couple of clips from the project.
My understand is that if Nuendo could let you open multiple projects and do copy/paste, it should consider people wouldn’t want to just copy audio event without DOP on it.

You might consider reading the Library section of the manual. It might work the way you want it to.