@Zynewave wrote:
There are new submenus for: “Assign Input”, “Assign Output”, “Assign Effect”, “Assign Source” and “Insert Effect Track”, depending on which track you click on.
The “Assign Source” submenu includes all device mappings that produce sound, i.e. instruments and bus returns.
I’m going to extend this menu with “New Parameter Track” and “Assign Preset” submenus. This should then allow you to do everything on the track headers, without having to use the track inspector.
Very good!
Just a small thing but would it be a good idea to include configurable “Favourites” items under the “Assign” menus?
For example:
Assign source ->
Unassign: Anysynth
Is it possible to understand what I mean? Could be “Recent” items too but I would personally prefer “Favourites”.
Edit: Perhaps there already is some other way of doing something similar?
/SQ
Am I missing something or doing something incorrectly? Whenever I try a new beta (just by replacing the 1.94 build .exe with the new one) I get this.
There are some differences, like the look of the track lane, but the panning and gain faders are the same 😕 Do I need to do anything else? Or do I have to start a new project? I’d think replacing the executable is all that needs to be done. So what’s happening?
Thanks in advance.
Zsolt
Thanks very much. I’m sure it was posted somewhere in this thread; I must have missed it. 🙂
@swindus wrote:
a. When using the command ‘Hide Tracks in Group’ on a bounce track the plugin mapping and the fader of a child track is shown on the bounce track header.
I’ll look at that tomorrow.
c. Moving the first effect track in a track header with the submenu command ‘Move Track’ above the next effect track does not work, moving below works.
Fixed in the new beta 13.
One question: Is it possible to deactivate the automatic track header sizing when opening/closing the mixer? Would be great because all the optimized track header sizes are ‘lost’ after opening the mixer view.
Not currently. I’m planning to change how the track resizing works. With the new compact headers there are more information shown on the headers, and it may then be undesirable that the tracks resizes when the entire tracks region is resized.
The new beta 13 has further changes to the track menus, including submenus for presets and parameters.
@soundquist wrote:
Just a small thing but would it be a good idea to include configurable “Favourites” items under the “Assign” menus?
With a bit of manual work, you can arrange your plugins into favorites folders on the project start page. If you mean that Podium should automatically maintain a list of most used plugins, then that is not something I’ll implement this time around.
@Zynewave wrote:
With a bit of manual work, you can arrange your plugins into favorites folders on the project start page.
Or pre – arrange them on your hard drive to taste, *before* you import them, that way Podium will correctly maintain the folder layout of your plugins after import.
@Zynewave wrote:
The new beta 13 has further changes to the track menus, including submenus for presets and parameters.
Looks good!
B13 thoughts…
Podium is so much easier to navigate and use now. It is a really strange thing but those preset and parameter sub menu’s just make it so easy at track level to work very quickly now. Great idea. It is a joy to work at track level in 1.95. Love it.
z3ta+ presets using the new submenus:
Sonitus Compressor Parameters using the new submenus:
Those little additional graphical touches just give it a very refined, polished, stylish and elegant look.
While it is necessary to give feedback on problems when they occur so that they can be identified and fixed or refined…I think some really positive feedback is due here.
I really have to say Podium using Compact mode in 1.95 is a really nice experience. It really does feel very different to 1.94, it’s much easier to use, with more features and allows for a much quicker work flow. Excellent!
Thanks Frits. 🙂
@Zynewave wrote:
The new beta 13 has further changes to the track menus, including submenus for presets and parameters.
You said “including” so are there other undocumented changes in B13 as well?
It’s very nice now! I like it! Really good work Fritz.
Hi Frits and Posters,
Fist, really dig the changes comming through. I’ve been tracking the Betas since Beta 7 and am stoked with the changes and new layout. 8)
I wanted to raise a couple of issues that I think affect appearance and work-flow. I accept in advance that these are not really ground-breaking but think that raising this after the release of 1.95 (feels like 2.0 don’t you think?) would be worse.
First, can the background to the Volume/Pan faders and the buttons X,R etc. be left in the default background colour. Minor I know but when you’re using my colour scheme …well, there’s alot of orange.
Second, like the (new) default heights for the automation tracks, could it be possible to have the track ‘windows’ expand automatically to show all VSTxs on the track? (See above pic again)
Third, I note that a default track height can be set for all which is cool however I would like to raise the issue of why the tracks are so expandable (See Pic). Edits are done via the piano roll / list editor / sequence editor anyway right? So couldn’t the tracks start at a sensible minimum (ie. high enough to show mapped plugin and input) and grow automatically to show all plugs on that track as you can drag-n-drop a parameter any where on the track and it will jump nicely into place.
Then I guess the idea is that you build the tracks, roll them up and use the group panel and group menus for changes/access to effects & instruments.
I suppose all of this could be customisable through the ‘Tracks Region Properties’ under ‘view’ in the Inspector but I’m interested to hear anyone’s ideas on the above.
And finally, awesome stuff Frits 😀
@H-man wrote:
the release of 1.95 (feels like 2.0 don’t you think?)
Personally (I guess you did not direct the question at me 🙂 but…) I think 1.95 is many levels above any of the updates for Podium since the first beta (0.90) came out years ago…but…without Rewire, time stretching and other refinements to plugin handling on the project start page, it’s not 2.0 calibre just yet IMO.
There is definitely some ground left to cover before 2.0 and I suspect Frits agrees or 1.95 would be 2.0 by now. Exactly what ground that is (specific features) only he can say for sure, but people expect the three things I mentioned in hosts now, talk less of some time in future.
Podium remains a powerhouse but expectations still remain for key features especially considering how long the competition has had those features for. Years in most cases.
First, can the background to the Volume/Pan faders and the buttons X,R etc. be left in the default background colour. Minor I know but when you’re using my colour scheme …well, there’s alot of orange.
Unless I have missed a colour option that address it…I would agree with your suggestion. Pick the wrong colour and that is the kind of result one would want to avoid. It does not look good. An option to change that or a similar solution would be nice.
And finally, awesome stuff Frits 😀
Indeed! 🙂
Thanks for the positive feedback everyone. It’s encouraging to know that these track layout changes are worth the development time I’m putting into it.
Beta 14 is up.
The track menu is now almost done. The track header right-click menu is now the same as the popup menu of the chain panel. New commands are “New Track” and “New Child Track” on group tracks. The track clipboard commands now also works with the compact layout. The commands are moved to a “Clipboard” submenu in the track menu. The new “Replace Effect Chain” command makes it easy to copy an effect chain from one track to other tracks: Select a track where you have set up a chain that you want to reuse on other tracks. Copy (Ctrl+C). Select the new track. Replace Effect Chain (Ctrl+Shift+V).
Still missing are the track template menus, but I’ll probably wait with those until after 1.95 is released. Dragging effect tracks in the chain panel will also come after the 1.95 release.
could it be possible to have the track ‘windows’ expand automatically to show all VSTxs on the track?
I’ll work on this on a later release. It requires a change to the way that track heights are stored. Currently track height is stored as a scale factor relative to the total region height. Hence when you drag the mixer up, all tracks scale accordingly. I’ll probably change this so that track heights are stored as a pixel height, which allows for precise sizing of the tracks to the contents of the chain panel.
Thanks Frits,
Perhaps it could be that the ability to ‘lock’ the track height could enble both types of behaviour with the defaut being locked?
That is, you could unlock the track, minimise the mixer and have your unlocked track expand nicely. Lock it again and jumps back into shape.
Just a suggestion, anyway thanks for the response 🙂
I must say that midi-routing options and time-stretching as per CQSD’s post would be pretty high on my (if not everyone’s) list for upcoming updates.
Rewire I could care less about. In fact if Re-birth had shipped with a VST version all though years ago we wouldn’t even be discussing this.
😛 (I just know someone is going to take offence to that!) 😛
On to Beta 14it is.