I skipped feedback on shortcuts as I am not a shortcut kinda guy 😉 probably just as well considering the length of this post. 🙂
The arrangement properties dialog has a new “track layout mode” option which can be set to “compact” or “modular routing”. The modular routing mode is the same as the layout used in previous Podium versions. The new compact mode presents the tracks in a simpler form.
Perhaps “Advanced” and “Beginner” modes make more sense. Modular and compact I think are too confusing for a new starter. Even as a user for some time now I don’t like those descriptions.
I really think “Advanced” and “Simple” modes are much clearer descriptions. They also immediately convey the message you are trying to get across with these two modes…that one is for Advanced users and the other an easier entry level access point for Podium usage.
Really Frits please do consider this. Keep things as simple as possible.
Podium has a lot of power under it’s hood now. A lot. It’s uniqueness can be a weakness if delivered the wrong way. That unique aspect and power (with a careful choice of words) can be unravelled to a new user in a nice measured way…a wrong choice of words can give the wrong impression.
I used to think only Apps Like Live and P5 were quite obviously very different, but Podium’s unique approach somehow (especially after trying the beta) is now much more visible. Podium really does have yet another unique workflow to offer. Well done. I use P5 and Live so the this is real world user feedback here not guess work.
In compact track layout mode, all parameter tracks are shown at the bottom of the track chains. Parameter tracks controlling plugins further up the chain is shown with the parameter name followed by the plugin name in parentheses.
I like seeing the name of the Parent plug for parameters in brackets but…is that easier than the Modular mode? I don’t think so.
In Modular mode one can see the parameter tracks directly under the parent or Plugin that owns those parameters. Easy and logically placed. In compact or simple mode these parameters (for different plugins) are all placed under the same track.
Much harder to distinguish if you ask me. Not easy or logical at all. You could have parameters for 3 – 5 plugs in one chain all sitting below the first plug in the chains track. It is far more intuitive and easier IMO to see parameter tracks under their own track. I am not sure there is any need to change this. Why change it at all?
The tracks in the group panel are divided into blocks for each effect chain (e.g. master chain, group chain and audio/instrument chain). Each block has a menu button with shortcuts for selecting and creating new tracks within the parent group. At the bottom of the menu is a “move track” submenu, which has commands for moving the selected track within the parent group, moving the track to a different group, and moving a range of tracks into a new group.
Sub Menu’s can travel across the screen when you want to “Move track” then “Move to new Group” / “Move Group” I really like this idea though. Safer for new users definitely. It should be difficult to mess up the hierarchy in the easier mode with this feature.
I think it would be a good idea to have a tutorial done to explain what the gaps are for in the GP, in a bit more detail . I imagine a short Wiki article would do. My understanding is that they are there to provide a visual indication as to what tracks flow to where but also what tracks are on the same level or not. (Correct me if I am wrong) It’s such a radical approach but once you get it, it’s seriously clever and easy to follow. Unique.
The track context menu in the group panel has been redesigned. New commands include “new effect track”, “new bounce track” and a “move track” submenu which allows moving tracks around in the chain.
Provides further focus on the GP for track management. Nice but I suspect many (like I did) might expect those options to appear at track level as well. The GP is unique but having options like these that do not appear at track level at all…don’t know about that. I guess Podium can be different to other hosts and can have a central advanced track manager that leaves track level controls lighter and simpler.
That is an idea that maybe needs to be highlighted in a big way for new users. This is certainly the way I see the GP in Podium. It’s strength is how it brings Podium track level features into a single central focus point for simple and advanced track management. Ahhhh I feel better about it already. LOL! New users need to get that message. It is also how I see the GP going forward.
“Move track” is a great idea, very nice. Now we have another way to ‘see’ what goes where in Podium.
Added “use as group track” option to the track properties dialog. Group tracks will be available in the new group panel menus with commands for managing tracks in groups. Note that normal tracks will appear as group tracks, if you have used modular routing mode to set up more than one child track.
I like this idea. It just makes the impact and management of Group tracks clearer. Am I right in assuming that when you click on this menu the child track being processed is always the track that is selected (has the tick mark next to it) by default however many Parent / Group tracks it has?
It does look this way. Probably not a bad idea. I think I might want to move the key or source track instead of FX tracks around in Podium, but of course I can still do that as well by selecting a different track.
The “hide track lane” track option is now available for all tracks in compact track layout mode. This makes it possible to e.g. hide the track lanes for bus returns, if you prefer to adjust bus returns in the mixer. Setting up busses in the new arrangement dialog now by default hides the bus return track lanes.
Hide track lane really does totally hide it. Great.
“Setting up busses in the new arrangement dialog now by default hides the bus return track lanes”
But it will by default show them in the mixer in Beta 2 which is good to see. Less to see track wise to start, but the info is there in the mixer already.
Specifying a color for a track will apply to parent tracks in a track chain if a color is not specified for the parent tracks.
I do like this. Works as advertised Mr Nielsen.
The buttons in the track headers are tinted with the track color.
Hmmmm I might need to chew on this one a bit longer. One has to be careful to choose a colour that works. I would like an option to not have to use this but graphically it could help differentiate one track from another…a bit more, but not essential. There are far more pressing needs in Podium IMO.
Added “black/white key intensity” setting to the piano roll properties dialog. Setting this to 100% will paint solid black/white keys.
Finally yes! It’s buried a bit (the option) but then it would be a set and forget options anyway for me. Nice thanks.
The project name written in the browser page tab will blink once, as confirmation when saving the project.
Works. But is so quick it could be easily missed. Three flashes would work better. It’s too quick with one flash IMO. We do not need a fire engine siren type of indicator of course 🙂 but I *really* had to look carefully to catch it. It’s supposed to provide a short sharp distraction / notification to a user. One flash does not do it IMO. 3 flashes should be fine.
Changed the track luminance offsets in the color setup dialog to apply to group, bounce and parameter tracks. The luminance offsets are now also applied to the track headers, so that track header and events on the track are coloured identically.
Not a bad idea. More graphical options.
Deleting a track automatically deletes any child parameter tracks.
I like this idea but…in Compact mode *any* parameter tracks are deleted. So if you have a chorus FX processing a Compressor track the parameters for the compressor and the Chorus will disappear. This is another reason why having parameter tracks visible under their parent FX track (in Modular and Compact modes) is a far better idea IMO. A bug?
Deleting a track in compact track layout mode will delete all tracks in the chain.
Below it in the chain? If so AFAICT it does not work in Compact mode this way….only the FX track is deleted in a chain. Everything else is left intact.
The old “delete track” context menu command is divided into specific commands according to the clicked track. New commands are: “delete effect track”, “delete bounce track”, “delete group track”, “delete group and child tracks”.
Nice additions.
Changed the track header context menu to only show relevant options for the track type.
Some things are not available on track types now. Makes sense.
Other issues…
In Compact mode if you select a track and want to drag a mapping to it you cannot.
OK this may be done to avoid messing up the hierarchy (fair enough) but…if you select a track it remains highlighted, then go to the Map panel and click on a mapping, the track gets de selected (the highlight is gone).
This makes it very confusing in a busy project when many tracks are visible. Surely if one selects a track it should stay selected especially if a user wants to add a mapping to it. No?
I would add this point as well…
…unless adding a simple chainer with support for automation e.t.c would require a total rewrite of Podium I do think in future you should not drop the idea of a chainer completely.
I still think it would be easier to use than the current solution in Beta 2. It’s much easier (GP), unique among hosts, and I would defintely keep it given the choice, but really an FX chainer would still have been all that was needed IMO to simplify things.
Another way to see it…
If anything I see what you are trying to achieve here with the GP and I agree with it.
The GP gives podium something I have not seen in any other host. The Advanced track managment (simple things as well) is slick, fresh and new especially in beta 2… but please consider a chainer in future if only to provide a simpler approach to the current Beta 2 option and provide something more familar for new users to get into as it would mirror other workflow options elsewhere.
The GP as of Beta2 is great, but I really had to think pretty hard to ‘get it’ in beta 2. I love using it but a new user would need a video and plenty of documentation to really enjoy it IMO.
You need this kind of feedback as well Frits. Few potential customers would post thoughts like that here. They would most likely move on to the next demo.
GP + chainer = Low level entry and advanced Track managment.
The GP is a unique Podium feature, logical at first glance, in compact mode (can be mastered with some videos, more docs) but an Fx chainer will give new users an even easier low level ride into Podiums workflow.
So effectively you would provide the best of both worlds. FWIW I would want to see the automapping issue addressed before a chainer arrives in Podium but…a chainer would be something to think about post 2.2/3 Automapping is post 2.0 🙂
Things are far simpler and accessible in Beta 2, so job done and things of course will I assume get easier still. So there is plenty to look forward to.
Nice work overall. It looks like it was a massive effort. 😉
.
