Zynewave@H-man wrote:
@Zynewave wrote:
As 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?
This sounds awesome! Couple of questions tho…
Would I be right in assuming that the new Templates function would be available from the right-click menu on the actual track?
Groups, tracks and effect tracks can be turned into templates?
Custom patches (not saved to instument or .fxb) would be retained?
and,
Big YES for still being able to save events/clips as well.
Also great additions for this release (I must have said that many times now 🙂 since 1.77).
Yes to all those questions.
ZynewaveHi Michael,
if I drag Stylus RMX onto a track, then right-click “Create Bounce Track” it creates a parameter track If I try to delete this parameter track using the menu, it creates a second one. No more, and I can delete them with the delete key, but this only happens with Stylus…
Strange. I would appreciate if you could email me the project file so I can debug what is going on.
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.
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”? 😉
ZynewaveZynewaveAs 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?
Zynewave@aMUSEd wrote:
tbh I don’t know what punching in and out is 😳
Enable popup-help, and hover the mouse over the punch in/out and punch range controls in the transport toolbar. If you e.g. start playback a bar before you want to start recording on a track, you enable punch-in and set the punch in position to the desired start time.
ZynewaveI meant do I also need to drag out the red and green sliders or just the empty bounce track?
Only the event on the bounce track. If you have enabled the punch in/out buttons the bouncing will be limited to the punch in/out range, so in that case you also need to adjust the punch in/out range.
Zynewave@aMUSEd wrote:
Can you tell me if I want to make the bounce the same size as the midi track do I need to drag out the track and both selection sliders of just one of them?
I don’t understand. Please elaborate.
– I’m not sure what the red and green sliders are for.
The red bar is the punch in/out range. The green bar is the loop range.
Zynewave@aMUSEd wrote:
tbh I still don’t really understand the function of the master track that bounces get rendered into. I don’t get why it’s always a fixed length and why it can’t automatically set itself to the same length as what I’ve just recorded. You’d think it would be obvious that if I’ve just recorded a midi track of a certain length that normally I would want to render it all unless I chose otherwise, and certainly wouldn’t want to render just some arbitrary chunk of it.
One of the things on my future plan is an option in the track properties to auto adjust the length of an event to the length of the entire arrangement. That can be useful both for bounce tracks and parameter tracks.
Also I don’t get why it’s so hard to change the length of it manually. Often it won’t drag out all the way on the first attempt – it only goes as far as the Window edge so you have to go to the scroolbar at the bottom and move the track along and then drag out a bit more of the master track – so fiddly. And grabbing the red and green selection bars or whatever they are at the top is even harder. I think you have to change tools for each of them and again they only go so far at a time and since one covers the other you have to do each in turn.
The upcoming Podium 2.00 has support for drag-scrolling. You can download a 2.00 beta in the VIP lounge if you want to try it out.
Zynewave@sam c wrote:
frits, it does appear to be PC 3.01. and, it is not a consistent problem. do you have any idea what they might have done?
I have no idea. Check the powercore forums to see if others have the same problem.
ZynewaveZynewaveZynewaveAfter a long night of debugging I have now finally figured out why Podium 1.98 and later versions can crash on Win9x. I dug out my old Win98 harddrive from the back of the closet and replaced it in my old Pentium3 PC. I got the crashes with 1.98, but not with 1.97.
The problem is related to the limited number of system resources that W9x can handle. Googling reveals that it is a very common problem for larger applications. This page has a good explanation:
http://apptools.com/rants/resources.php
The thing that happened in Podium 1.98 was that I created the resizable toolbars. This required allocation of an extra set of large bitmaps that is used when generating the resized images. These extra bitmaps has pushed the number of bitmaps beyond what Win9x allows. If you e.g. delete the edit toolbar in the arrangement editor profile before entering the arrangement, you won’t get a crash when opening the arrangement editor because Podium doesn’t need to allocate the bitmaps for the edit toolbar.
I could spend a lot of time trying to reduce the number of bitmaps that Podium uses, but in my opinion that is a waste of time. It will restrict the things I can do to improve the UI in future Podium versions.
So unfortunately I’ll have to drop the claim that Podium is Win9x compatible.
ZynewaveIn older Podium versions you would get a lengthy stickie note with explanations on how to create arrangements etc. The latest Podium version only creates a note with e.g.:
“Project created: 25-05-2008 18:42:30”
There is no option to not create this note, but you can disable the “Popup project stickie note…” option in preferences.