francois.
ConquistadorNice updates Frits…and guess what? 😉
The very thing I was asking for is inlcluded in 1.70 🙂
Track level editing of Track Templates. That is all I wanted from this feature 😉
Right now I can do exactly what I wanted to do, I tried to explain this in the now ‘Epic’ Template thread 😆
My usage of track level editing with Track tempaltes:
Any changes I make at track level within an arrangement (not a Track Template arrangement) are simply saved to another Track Template, a slight downside is that Podium does not overwrite an existing Template if a new one is saved with the same name, for instance saving a document in Word will simply replace an existing file with the same name.
This would eliminate the need to have to delete Track templates that are no longer in use (from the track templates arrangement).
Podium currently will save two track templates with the same name. Is there anyway to currently
1. Overwrite an existing template with the same name?
2. Stop Podium saving two templates with exactly the same name?
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.
Even when a group template is not collapsed when saved, Podium will still hide the Parent Track after it is saved.
With no numbers or names to identify tracks it is difficult to know which is which.
@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 very strange as it appears to be working when recalling a group Template or inserting a new track…but only with the zReverb but not the zPEQ. ❓ ❗ ❓
Preset changes are saved with the reverb but not the EQ. Very strange. Gotta be a bug as it should of course recall changes for both, no?
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.
So Track templates (currently anyway) are Per project Track templates? If they are it may be best to describe them that way or it might confuse new users.
While the current implementation of course is fine as it is, I was a bit confused about Track Template usage with other existing Projects after reading Podianers question.
Your description does give the impression that they are available for use with existing projects as well. Per Project Track Templates I think makes it much clearer. As that is exactly how they have been implemented and work perfectly well that way.
It is really funny after all this time to have no Project Wizard in Podium. He he. 8) Better without it now though. 😉
acousmodHi,
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 Podium is restarted, the same place runs fine.
It is not the computer that I use in general, but I have used it during the last week without any problem with the same arrangements.
I don’t know if this can help, but there is sometimes an error message :
ModName : ntdll.dll
ModVer : 5.1.2600.2180
Offset : 00010f29
ZynewaveOverwrite 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.
ZynewaveSince 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?
ConquistadorGood 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.
Cheers! “Major features” sounds good to me 
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.
Thanks for clarifying 😉
acousmodWhen you say “start” button I assume you mean playback start? Does the crash happen also if you manually activated monitoring before pressing play?
By monitoring you mean Podium’s engine ?
In all cases it was already active.
By “start” I was meaning “play”.
I have uninstalled the 1.70 and installed the 1.69.
No crash up to now, but it is perhaps a coincidence.
I am not totally confident in this computer since it uses ASIO4All.
acousmodQuote:
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.Cheers! “Major features” sounds good to me Mr. Green
😛 😛 😛
acousmodI have uninstalled the 1.70 and installed the 1.69.
No crash up to now, but it is perhaps a coincidence.
I am not totally confident in this computer since it uses ASIO4All.
I have had one crash with the 1.69 too.
So there is something in this computer that Podium doesn’t like very much…
No need to investigate for this.
Zynewave@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.
Conquistador@Zynewave wrote:
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.
As always, thanks for quick fixes! 8)
PodianerI am testing and testing the new template feature and I love it!! 😆
But it would be great if colors would be recalled, too! I have coloured all my template tracks in order to have some visual help. When I use these templates in other arrangements, the color is not recalled. Perhaps this is on purpose, but it would be great to have the same color for certain fx chains e.g.
What do you think about it?
ZynewaveBut 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.
Podianer@Zynewave wrote:
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.
Could this be possible in the future? Because when we use the tamplate arrangement to visually categorize and sort the templates, coloring them inside the template arrangement is highly useful imo.
Max
ZynewaveBecause 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.
ConquistadorCould this be possible in the future? Because when we use the tamplate arrangement to visually categorize and sort the templates, coloring them inside the template arrangement is highly useful imo.
+1
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.
Not sure if that is exactly what Podianer wanted, but IMO it is a very useful idea 😉