pernst.
acousmodHi Frits,
The only way that I have found to import an arrangement from a project to another one is :
– delete all the other arrangements in the first project, with taking care that all the audio files are in the arrangement folder (if no, all the audio files are lost when importing, nevertheless they are exactly in the same relative path in the other project)
– import the pod file in the other project
The problem is that all the devices of the first project are imported also in the second one.
If I delete this new Device folder, all the inserted mappings disappear on the imported arrangement.
Since I use this method between different versions of the same project, and since they share exactly the same audio files and the same devices list, it makes doubles and becomes very confusing if I do this several times.
Would you consider to add an option to save and import only an arrangement instead of a complete project ?
Or to allow like in other hosts to copy / paste from a project to another one, or from two opened instances of Podium ?
Thanks.
druidThis definitely sounds like a good idea, in my opinion.
rinxai@acousmod wrote:
Would you consider to add an option to save and import only an arrangement instead of a complete project ?
+ 1
pernst+1
UncleAge+1
ConquistadorYes I agree as well. This comment here is a definite worry and not a small problem…
@acousmod wrote:
The problem is that all the devices of the first project are imported also in the second one.
If I delete this new Device folder, all the inserted mappings disappear on the imported arrangement.
On another note…
It’s interesting because importing an arrangement into another project is IIRC an effective workaround for the limitation we currently have with track templates, as they cannot be used in another project.
One can get around the track template limitation (I think) by importing an arrangement into another project that has the track templates a user wants already there.
Then any track templates within that project should be accessible to that imported arrangement but even that workaround is let down by the way devices are currently handled when importing an arrangement (based on acousmods quotes above). 🙁
Zynewave@acousmod wrote:
Hi Frits,
The only way that I have found to import an arrangement from a project to another one is :
– delete all the other arrangements in the first project, with taking care that all the audio files are in the arrangement folder (if no, all the audio files are lost when importing, nevertheless they are exactly in the same relative path in the other project)
– import the pod file in the other projectThe problem is that all the devices of the first project are imported also in the second one.
If I delete this new Device folder, all the inserted mappings disappear on the imported arrangement.
Since I use this method between different versions of the same project, and since they share exactly the same audio files and the same devices list, it makes doubles and becomes very confusing if I do this several times.Would you consider to add an option to save and import only an arrangement instead of a complete project ?
Or to allow like in other hosts to copy / paste from a project to another one, or from two opened instances of Podium ?Thanks.
I’m currently implementing a “Merge Project” command just below the “Open Project” command in the project menu. I think this will solve the problem you describe.
The merge command will import the project into the current project and search the current project for mappings that match those in the imported project. If matches are found Podium will delete the device mappings in the imported project and replace the assignments on the tracks with the matched mappings in the current project. If there are any device mappings in the imported project that is not matched in the current project, these objects will be added to the end of the device list. Thus you won’t end up with two device folders.
The merge project command can also be useful if you e.g. have created a new project template with a different plugin layout, and you want that layout propagated to older projects. You could simply create a new project with this template and then merge it with the older project. The result is a project where all arrangements are reassigned with the objects in the template.
acousmodYes, it seems to be a very good solution !
Thank you very much for all of you have done, are doing, and will do 😛
Conquistador@acousmod wrote:
Yes, it seems to be a very good solution !
Thank you very much for all of you have done, are doing, and will do 😛
Totally agree! 🙂
On a side note the Merge Project feature should now extend the functionality of track templates to problem free global status /usage if I am not mistaken as importing an arrangement will now make any track templates in the destination project for a merge, available to any imported arrangements, but without creating two device folders. Great! 🙂
pernstThank you Mr. Nielsen!