You can edit your “mixer” editor profile and add a standard edit toolbar which will have the menu buttons. You can access the “editor profiles” setup menu in your main window.
Instead of using the view menu, you can also press F8 to select the next editor profile.
Hi Paul,
You need to import a device definition that matches the device you have connected to your midi out ports. In release 1.69 you need to use the old project wizard (ctrl+w). Open the ‘hardware mappings’ panel and follow the instructions there. Please ask again if you need further directions.
In release 1.70 the project wizard has been removed, and the definition import can be done through shortcut menus on the start page.
Frits
This has occasionally annoyed me too, but somehow I never got around to fixing this bug :oops:. I’ll fix it for 1.71.
Because when we use the tamplate arrangement to visually categorize and sort the templates, coloring them inside the template arrangement is highly useful imo.
So, you want the template tracks to inherit the color from the template parent track when copied to another arrangement? If so, that should be easy to do.
But it would be great if colors would be recalled, too!
The colors on the actual tracks copied to/from templates are recalled. Colors you define manually on the “template” placeholder tracks are not used when you insert new template tracks.
@acousmod wrote:
But the current state of an inserted plugin is not saved with the template, like it is when we copy/paste a track.
Could it be the same for the templates ?
This is now fixed. It was because the plugin current settings was not retrieved before copying the track to the template. As a workaround, You can save the project to force an update of the preset with the plugin current settings, and then copy the track to the template.
Since I have updated to 1.70 this morning I have had several crashes.
They happened when pressing the start button, but in different places and in different arrangements.
When you say “start” button I assume you mean playback start? Does the crash happen also if you manually activated monitoring before pressing play?
Overwrite an existing template with the same name?
Good suggestion, but I’ll put it on hold for another time. I’m trying to reduce the todo list on my notepad, to get ready for some of the major features.
Also in the track Template arrangement Podium hides the Track Template header or parent track by default. I think to allow for quick identification of Track templates the parent track really should be visible by default otherwise one has to click on each track template to identify it by name.
I’ve now changed it so that the template track group is collapsed instead of hidden.
So Track templates (currently anyway) are Per project Track templates?
Yes.
I suppose that you have planned in the future to show the Plugins Parameters in the Devices list, as sub-branches of the plugins ?
Not really. Instead I was planning on extending the functionality of the parameter panel in the track inspector. Likewise with the preset panel.
Not really necessary, but in the graphic line of Podium for the 2.0 version ?
Right.
@Podianer wrote:
So there is no chance to transfer a set of template tracks to another existing project? 😥
Not currently. This may be improved in future updates, but for now I need to focus on to other more important features.
So this does not work for offline bounce.
Offline bounce will solo the track you bounce, so this will mute other tracks in the arrangement. You can see the solo/mute buttons change during the bounce. The soloing is done to skip CPU consumption on other tracks. If you manually activate solo on e.g. return tracks before doing an offline bounce, they will be included in the offline processing.
@Podianer wrote:
Nice! Is it possible to just copy the template arrangement to other projects, or do I have to set everything up again?
If you copy the template arrangement, open another project, and paste the arrangement in, you will lose all device, preset and parameter assignments on the template tracks. If you build up a set of templates in a project, you could save that as a template for new projects.
@Podianer wrote:
ok, I accidentaly pressed enter inside the sticky note, that was why the menu was looking strange. Works fine now!
I’ve now changed it so that only the first word in the stickie note needs to be “Template”.
Right clicking an existing bus mapping gives you the ‘new instance’ command. You mean a shortcut to create busses in projects where all bus mappings have been deleted? I could add a “new bus instance” command to the device list top menu.
