Very nice. I printed out the Podium guide last year sometime, but this way it will be much easier! Thanks 8)
@Podianer wrote:
I don’t know how hard a ReWire implementation would be, but it would highly push Podium’s sells, imo.
As I said, just a little reminder 😀
I agree. 8)
I think even if it really does take a very long time (I can only guess of course) it is an expected feature in any host now. I think in a strange way Frits, Podium’s current feature set is just so good and well implemented that I think many will simply assume it has rewire already. 😐
I think it is on the future map anyway but as Podianer said…a little reminder. Thankfully I still have a workaround -ish, for now but rewire in Podium? Well that would be another huge selling point surely. 😉
I am sure you have set structure for certain forthcoming features, so just consider our reminders as two small nudges and two winks 😉
FWIW the pace and implementation of features so far has been just right IMO, which is even more remarkable for a single developer!
@Podianer wrote:
Thanks for clearing things! 😳 🙂
🙂
But one thing: I already tried that.. Create the aforementioned template tracks (without mappings attached, because you want empty tracks, I guess) and copy the whole group. This is possible with the current implementation. You can paste these tracks in any existing project’s template arrangement. This of course only works for empty tracks, as the tracks loose their mappings when copying to another project. Is this some help? 😛
The loss of mappings is a no go for me. In any case the right click option is still my preference 😉
Again, sorry for the misunderstanding
No problem! 🙂 this whole discussion provided a good exchange of ideas for Podium 8)
@Podianer wrote:
You should read my posts more thoroughly! 😉 I suggested that Frits could implement a “default template arrangement” which already has the tracks mentioned before. This default template arrangement would be created everytime we create a new arrangement. Thus you have them in every project and we do not have to create them by ourselves! 🙂
he he a slight misunderstanding here. 8)
I read your post properly….I responded to this statement…
If Frits would put some template tracks in the template arranger by default,
At this stage of your comment you clearly are implying that Frits could create some template tracks, that would appear in the track template arrangement by default. (Fine).
However based on this comment above…as we both know, any thing created in an existing track template in Project A, cannot be copied to another project or Project B. Or another existing project.
That suggestion would only work for a single project, or for the project currently in use. Or any *new* projects, but not across any projects as based on your comment above they would be created within a track template arrangement, which right now would guarantee they would not be available to copy to another existing project 😉 That is why, that was my response.
You then said…
you could easily “load” them (without mappings attached) by clicking under “create child tracks”.. With a submenu, which can easily be created by putting the tracks in a group beforehand,
Which is absolutley correct and would work, thats why I then said
“Your suggestion is brilliant for a single project but cannot be used for other projects or copied to other existing projects.”
So it appears what you meant to say first time around was for any *new* projects your suggestion would work. Because any track templates created by Frits into a default template arrangement would not be available in any other existing project only new ones.
New projects yes, any (inlcuding older projects) no. 😉
But now you have added a bit more detail… 🙂
You should read my posts more thoroughly! I suggested that Frits could implement a “default template arrangement” which already has the tracks mentioned before.
Yes, you said that but…not this…
This default template arrangement would be created everytime we create a new arrangement. Thus you have them in every project and we do not have to create them by ourselves!
Now you are clearly saying that the default template arrangement (I assume with the track templates Frits could create already in place) would be created every time we create a new arrangement. You did not say that before in the post I responded to, that is why I misunderstood you 8)
he he again just the use of words caused a little confusion. 8)
So you are referring to *new* projects only, I am referring to how your suggestion will not work for older or existing projects.
Your suggestion as I said earlier cannot work with any project, it will only work with new. Which I think is what you meant to say. My FR for this thread is now definitely different to yours as it would work with new or any existing projects…:)
A bit of a muddle there for a minute 😆 I hope that helps. 8)
@Podianer wrote:
Perhaps I’ve put it the wrong way 😳 Actual quantization is not useless for drums. You can quantize hard, but in terms of humanization of a drum track, there is nothing in it.
Gotcha. I thought that is probably what you meant to say. 8)
For drums most people use short midi notes, and as Frits stated some time ago, the midi randomization does not work on such short notes. That’s what I meant 🙂
Agreed and your FR in your first post would work very well and fill a weakness in this area. 😉
@Podianer wrote:
I think we mean the same 😉 If Frits would put some template tracks in the template arranger by default, you could easily “load” them (without mappings attached) by clicking under “create child tracks”.. With a submenu, which can easily be created by putting the tracks in a group beforehand, this feature seems to be exactly what you suggested, unless I am completely misunderstanding you. But I think I got you right. 😉
Correct. You got me right 🙂
That is a very clever way to acheive my FR 😆 But…because track templates cannot be copied or used in another project my FR still stands why? If implemented it would be available in any project, existing or new.
Your suggestion is brilliant for a single project but cannot be used for other projects or copied to other existing projects.
The Track template a user could build, based on your suggestion (with a previously saved number of tracks to be recalled) can only work with that specific project.
My FR would work in any project new or existing as a right click option.
I think Frits explained what he plans to do to get around the template limitation between projects issue in the 1.70 thread. Once he has done that…your suggestion would easily work across new and existing projects. 😉
While we wait my FR would have to still stand. It would still be my preferred option in any case. 😉 Ideally having both would be even better. 8)
@Zynewave wrote:
Correct. But it is possible it will support this in the future. I need to extend the .pod file format so that you can export part of the project (such as the template arrangement) and have it store references to objects outside the exported part such as mappings, presets and parameters. These references would be stored as a path/name text instead of the actual object. When you import this .pod file, Podium would then try to relink the path/name references to the objects that are already in the project.
Sounds good to me. 😉
@Podianer wrote:
Perhaps Frits could help here as the new track template feature is implemented now.
Frits could by default create a template arrangement, that also by default holds a group track named “several tracks”. This group track holds track templates for e.g. “5 Tracks”, “10 tracks” and “15 tracks”. This is how I have changed my template arrangements.
So the old feature from the project wizard would find a new home in the template feature.
That sounds like a good idea…a sort of ‘starter’ group of templates, yes why not. It would certainly help. Having said that I think my initial suggestion is not really the same thing as your suggestion (which is a good one) if anything because of recent changes in Podium since I first made the “insert x number of tracks” feature request, it is probably now better implemented as an extension of the existing New Track and New Child Track right click options within the ‘main’ arranger not the track template arranger.
So clicking on any of those two, would bring up a small option box giving the user a number field to specify how many they want.
Your suggestion is very good for Track templates but the FR I suggested for this thread is quite different as it would operate with the New Track and New child Track options when right clicking a track in the ‘main’ arranger (not the track template arranger).
@Podianer wrote:
A shortcut for “save sound as” would be very appreciated. so without using the sound editor, just by selecting a sound object and the pressing the shortcut.
+1
Perhaps even a right click option as well. I think even extending the feature to Midi objects or clips would be very useful. That way by simply right clicking on and audio object or midi object one could save it and name it very quickly. 😉
@Podianer wrote:
Podium lacks some quantize features in my opinion. Perhaps a basic groove feature would do the job for the start. Non-destructive of course. I mean Podium already has quantize features, but for drums they are useless.
Yes a groove feature of some sort would be nice unless Podium has it already and I missed it. IMHO the quantize features are not useless for drums at all, but of course everyone has their way of working with their own preferences, but your groove suggestion would be a definite step up from the features we have now IMO. 😉
But this should of course be after the lond awaited audio fade feature! 😉
Just reminding you…
Max
Agreed, after that please. 8)
I must admit, I am longing for a change in the actual system of template tracks, that allows me to copy the template track to another project.
Agreed. 🙂 I think however that Frits wanted at least something or some level of track Template implementation in place now, but I think he will certainly improve on it in future. I am glad (as I am sure you are) that he has at least has gone this far, as it creates the foundation for further improvements in future. 😉
@duncanparsons wrote:
Voting has opened..
http://www.kvraudio.com/developer_challenge.php
DSP
Finally! Here we go then… 🙂
@duncanparsons wrote:
Over at KVR there has been a ‘Developer Challenge’ going on for a few months. We devs have finally all crawled out of our caves, and the fruits of our labours have been released onto the world…
http://www.kvraudio.com/developer_challenge.php
http://www.kvraudio.com/forum/viewforum.php?f=91
There will be voting opening in a few days.. go see!!
DSP
Thanks for the heads up Duncan! Some great entries in there! 🙂
@Zynewave wrote:
This has occasionally annoyed me too, but somehow I never got around to fixing this bug :oops:. I’ll fix it for 1.71.
😕 This caused me confusion at times as well, thanks for fixing it!