Conquistador.
ZynewaveA beta version of Podium 2.00 can be downloaded in the VIP Lounge. These are the changes so far (beta1):
• Support for drag-scrolling in the editors when dragging the mouse outside the display area. The scroll sensitivity can be adjusted with two new settings in the preferences dialog: “Drag scroll acceleration width around editor” and “Drag scroll maximum pixels per second”.
• Added “Merge Project” command to the Project menu. The contents of the selected merge project file is imported into the current project. The merge project file is not modified. Imported arrangements are modified to use the device objects found in the current project. If the merge project contains device objects not found in the current project these are added to the end of the device list.
• Collected all project template menu commands from the Project menu and moved them into a “Project Templates” submenu.
• Added “Load Device Setup” submenu to the Project Templates submenu. This can be used to replace the device setup in the current project with the setup from a project template.
• Added “Explore Templates Folder” and “Update Templates List” commands to the Project Templates submenu. These replace the old “Delete Template” submenu.
• Added “Explore Projects Folder” command to the project menu.
I believe the merge project feature is complete, but there may be cases I have overlooked. Please make backups of your projects before trying these new features. Check that the arrangements in the project are still playing ok after you have used the merge or load device setup commands.
About the “Load device setup” menu:
This is implemented using the new merge project feature. Instead of merging the selected project into the current project, it will load the template project and then merge the current project into the template project. The new combined project is then replaced as the current project. The result is a hopefully seamless replacement of all device mappings in your projects. With this feature you can: Replace audio and MIDI mappings when you move projects to a computer with a different soundcard. Create template projects with alternative arrangements of your plugins, and quickly swap these while working with your projects.
Please post your experiences with these new features.
acousmodWhen I import a project, if there are some missing plugins they don’t appear at first.
But when I open the arrangement that has been imported and return to the start page, there is a now a new Devices folder like with 1.99, and the missing plugins are shown.
Edit : sorry, I have used the “old” (?) import command.
But with the “Merge Project” command a new Devices folder appears too.
Podium also simply quits very often when merging.
Sometimes folder devices appear in the Arrangement s & Sounds section instead of the Devices (Audio Inputs folder).
acousmodSupport for drag-scrolling in the editors when dragging the mouse outside the display area. The scroll sensitivity can be adjusted with two new settings in the preferences dialog: “Drag scroll acceleration width around editor” and “Drag scroll maximum pixels per second”.
Hurrah !
Zynewave@acousmod wrote:
Podium also simply quits very often when merging.
Sometimes folder devices appear in the Arrangement s & Sounds section instead of the Devices (Audio Inputs folder).
Please send me the two project files you are trying to merge.
acousmodZynewave@acousmod wrote:
@Zynewave wrote:
Please send me the two project files you are trying to merge.
Done.
Thanks.
Your projects had a number of customizations that uncovered a few cases I hadn’t considered. You have for example moved some plugins out of the “Devices” folder and into the project root folder. I have uploaded a beta2 that fixes the crash bug, and which has further improvements in the merging of MIDI/audio/bus mappings. Please let me know if you find issues with the project merging in beta2.
acousmodNo more crash !
You have for example moved some plugins out of the “Devices” folder and into the project root folder.
Yes, it’s easier to pick them from the Inspector (but I would even prefer to have two distinct “Devices” and “Plugins” sections. It would be so obvious for users…).
ZynewaveAs a natural extension of the new merge project feature, I’m now experimenting with creating a new track template system that is file-based. The benefit will be that the track templates can be used across all your projects. Saving a track template will then no longer create a template arrangement in the project, but instead save the track in a .pod file in a new “Track Templates” folder in the library. The paths to the project template and track template folders will be settable in the preferences.
What do you think. Would you mind that the old track template system is removed in favor of a new file-based template system?
acousmodWhat do you think. Would you mind that the old track template system is removed in favor of a new file-based template system?
Yes 😛
UncleAgeAre you saying that you could give us the ability to save the state of the track (not actual clip content though), plugs and all the plug settings associated with it as a template?
If this is what you’re saying then I say YES-YES!
Zynewave@acousmod wrote:
What do you think. Would you mind that the old track template system is removed in favor of a new file-based template system?
Yes 😛
Do you mean “Yes, I would mind” or “Yes, I prefer file-based track templates”? 😉
Zynewave@UncleAge wrote:
Are you saying that you could give us the ability to save the state of the track (not actual clip content though), plugs and all the plug settings associated with it as a template?
If this is what you’re saying then I say YES-YES!
That is what I’m saying. I may even add the option to save the track clips as well, since that is possible with the current template system.
Saving a track template will save a project containing only the device objects used by the track(s) and a single arrangement with the actual template tracks. You’ll be able to open a track template file as a normal project if you want to edit the template.
When the user selects a track template in an arrangement, Podium calls the newly implemented merge project feature on the track template file, strips out the arrangement from the template and copies the template tracks to the arrangement.
acousmodDo you mean “Yes, I would mind” or “Yes, I prefer file-based track templates”?
Yes, the second yes 😉
pavouk100Yes, please, this sounds simply awesome! (I mean file-based templates :lol:)
