Problem summary
Copying sequences between two or more projects internally within NukeStudio will break the copied sequence. It will not allow you to edit the clips inside the copied sequence and causes issues with the colorspace, versioning and metadata when opening the project.
Customer reported version
nuke.10.5v2
Customer reported platform
Linux
Steps to reproduce
1) Open a new NukeStudio script
2) Import footage
3) Create a sequence from the footage
4) Create a new project inside of NukeStudio
5) Copy and paste the sequence and footage from the original project to the new project
6) Save the new project
7) Close and open NukeStudio, and open the saved project.
Result: The track in the sequence will be broken, so you can't change the colorspace or scan for versions.
Workaround
- Re-import the footage into the same sequence, from the same project, then it doesn't seem to encounter the same issue
- Replace the clip with the same clip appears to fix the issue, although you will get a duplication of clips in the project bin.
- Export sequences as XML's and making a new sequence from these imported XML's
Reproduced by support
This has been reproduced on:
Nuke 11.0v2 - Windows 7 - CentOS 6.9
Nuke 10.5v6 - Windows 7
Nuke 10.5v2 - Windows 7 - CentOS 6.9
Nuke 10.0v4 - Windows 7
Nuke 10.0v1 - Windows 7
Nuke 9.0v9 - Windows 7
Nuke 9.0v1 - Windows 7 - CentOS 6.9
Earliest Tested Version
Nuke 9.0v1 - NukeStudio was not available before this release.
Expected behaviour
For the copied tracks to retain the ability to version up and the ability to edit the copied sequence like normal.
Actual behaviour
The sequence would not allow you to edit the clips inside the sequence once copied, breaking the versioning, metadata and other operations.