+An aside -- when nesting and unnesting clips to take advantage of this feature, names of the media can lead to some confusion. For example, if you nest a clip, the new name in the Media folder is the word \textit{Nested} followed by an underscore with the date and timestamp, another underscore, and then the clip name. Then when you unnest this Media folder clip via the \textit{EDL to clip} option, the name will be changed in the Clip folder to the next available Clip \#. However the comment field will reflect the nested clip name from which it was derived. To avoid confusion you can easily change the name for these clips in either the Clip or Media folder because they are not real files at this point. To do so, highlight the clip name in Resources, click on Info and type in a new name.
+
+For additional safety, the \textit{Open EDL} feature includes additional backup capabilities. Automatically \CGG{} saves a backup when certain changes are made or you can always use the shortcut "b" to do one yourself, although keep in mind it will be overwritten whenever \CGG{} wants to do another backup. Now there is a shortcut for the backup shortcut "b" so you can keep your hand on the mouse instead of the keyboard. Just click on the \# in the upper right hand corner of the main window. If \# is at 0, it backs up to backup.xml, if at 1, it backs up to \texttt{backup1.xml} and so on $\dots$ up to \texttt{backup9.xml}.
+
+When \textit{Open EDL} is invoked, the current EDL and current undo stack are both \textit{pushed}, and the active session EDL is replaced with the target clip/nested edl. A new undo stack is created, and the active \texttt{backup.xml} file name is decorated with the stack level. So, \texttt{backup.xml} is \texttt{backup1.xml} when your edits are at stack level 1, \texttt{backup2.xml} at stack level 2, and so on. This means that if you \textit{load backup} at stack level 1, the session will reload from history at stack level 1, not the main session.
+
+\subsection{Editing with File by Reference}%
+\label{sub:file-reference}
+
+It is sometimes handy to have EDL assets not as a copy, but as a reference that is
+automatically updated into your project. Suppose you have several short videos that at
+the end have the same credits which include the current year such as 2019. But now it
+is 2020 and all of the videos would have to be individually updated with the new date.
+By including a \textit{Referenced File} as the EDL file type when you create each of the videos,
+you can just change the one credits xml file and the next time you load one of the
+videos and render it, it will now automatically have the updated information.
+
+The purpose of this feature is to be able to rework a smaller section of a global
+master project at any time, which can be done by an "assistant" and then this work
+is automatically reflected in the global master project. It is for \textbf{advanced usage only}.
+
+Up until the addition of this feature, \CGG{} has always used copies and no
+direct reference in order to ensure original data is never compromised. In the
+usual case, subprojects as xmls are copied into a master project where subprojects
+had been inserted, so that if you change something in a subproject or delete a subproject,
+it would have no affect on the master project. But now with \textit{File by Reference}, any
+project that uses a referenced file will automatically include any changes made to the
+referenced file when loaded. At the same time, if you use the EDL file NOT as a
+referenced file in a project since it is then just a copy, it will not be updated.
+Because of this difference, the user needs to be very aware of what using this feature
+could do.
+
+\textbf{Use with extreme caution}. However, there are several built-in safety features
+and a warning that should never be turned off even though it gives you the option to do so.
+These include: