To create this empty xml file that you speak of ( that carries all the Emaps) do I have to take every single track out of their folders before I save it? Or are you saying everytime I work on my big template I also save an additional version of it with everything removed (ie select all, delete, save as) and then import that empty whole project (by ticking all boxes in import track archive dialog) before I then start to import the individual track archives from the same big template? What if your big main template consists of many nested folders. I just recently moved from Reaper only because of ATMOS and expression maps and I’m beginning to regret it. What a pain, and so ignorant of Steinberg that this has carried on for so long. A pain I know, but really only needs to be done once. I don’t know why this is necessary, but I noticed it doesn’t export correctly with the maps unless I do this step. You can disable them again before export. Once all the maps are in your project, just delete the archive tracks and save as a template and you never have to do it again, unless you add stuff to the template that you’re pulling from.ĬAVEAT: Before you export as an XML file, make sure you enable any disabled tracks. Once the maps are in a session, they automatically assign to whatever you pull in from your template. You’re only importing the XML containing all your template tracks into a project for the expression maps they contain. It sounds a bit confusing, but just think of it like this. It will look like blank project upon opening but it will have all your expression maps that will automatically re-attach to whatever you import from your template. To prevent having to do this each time to avoid lengthy load times, you can just delete all the tracks you just imported from the track archive (which moves all the Emaps into the project), then save that as a project template. You don’t have to do anything one by one. So now if you select any tracks (including folders) to import from your template session, it will import the tracks with folder structure and re-assign automatically all the expression maps to whatever you just imported. So if you take an entire template session and export all tracks at once as an XML file, then import THAT file Xml file into a new project (file-import-track archive), then delete what you just imported, the project will still retain all the maps you just imported. The act of Importing track archives (that have tracks with expression maps), also imports the Expression maps into the project you’re working in. How to import tracks a la carte from a template, with expression maps and with an intact folder structure. Yay! It takes only a little bit of work on the front end, but then you can save as a template. I have a solution that is not too tedious and you can import tracks along with their corresponding Expression maps loaded with your folder structure intact.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |