Zynewave.
Zynewave2.21 is continuing the UI improvements started in 2.20. So far there are only minor stuff on the change log:
Beta1:
• Changed the transport toolbar buttons from rectangular to rounded shapes to unify the appearance of all toolbar buttons. Changed the layout of the transport toolbar in the default setup.
• Changed the way that toolbar buttons are spaced. Buttons placed next to each other will be joined into a button bar. Buttons can be separated by inserting a space element between the buttons in the toolbar properties dialog.
• Added “restore default editor profiles” command to the Setup menu.
• Added “Customize Region” submenu to the editor view menu for quick access to the properties dialogs for individual regions. Removed the region properties shortcuts from the various editor context menus.
• The menu button in the mixer is renamed from “view menu” to “mixer menu” to avoid confusion with the view menu in the editor.
• The name entered in a project or sound properties dialog is now linked to the filename. When a new project is created, the project properties dialog shows “Project name (used as filename when the project is saved)”. When the project has been saved the name field is made read-only and the caption reads “Project name (same as filename)”. The same applies to the name field in the sound properties dialog.
• Creating a new project from a template will show the project properties dialog.
I’m now going to start on the main 2.21 feature, which will be a new track toolbar. In the default setup it will sit right below the navigator. I’m considering several new toolbar elements, such as: New track, Marker lane toggle, Tempo lane toggle, global bounce/solo/mute/record buttons, and a new “track filter bar” which will behave similar to the 2.20 editor profile bar. More about that later.
pj geerlingsSo many changes – and I’m sure they are all moving in a good direction!
But …
Where are they documented other than in these forum pages?
with respect,
pj
Zynewave@pj geerlings wrote:
Where are they documented other than in these forum pages?
I’ve been neglecting the Podium guide, if that is what you mean. The video that accompanied 2.20 is a good way to illustrate new features I think, so I’ll probably do one for 2.21 as well.
soundquistWhat’s the procedure for safely trying out Betas? The download is just a executable, should it be run from the Zynewave folder?
Zynewave@soundquist wrote:
What’s the procedure for safely trying out Betas? The download is just a executable, should it be run from the Zynewave folder?
You can run it from anywhere you like. If you want to ensure that the “program files/Zynewave/Podium/VSTPlugins” folder is detected when Podium starts up, you can copy the beta exe to the program files/Zynewave/Podium folder, next to the installed Podium.exe.
soundquistOK, thanks.
/SQ
pj geerlings@Zynewave wrote:
@pj geerlings wrote:
Where are they documented other than in these forum pages?
I’ve been neglecting the Podium guide, if that is what you mean. The video that accompanied 2.20 is a good way to illustrate new features I think, so I’ll probably do one for 2.21 as well.
Yes – it is very difficult to re-ignite my passion for Podium given the number of (new/modified) features that remain (largely) undocumented in the manual.
with respect,
pj
H-manI like the new button shapes on the toolbar(s) but the edit icons get blury when the toolbar region height is increased.
IMHO the default size is too small which is why I changed them in the first place.
H-man@Zynewave wrote:
• The name entered in a project or sound properties dialog is now linked to the filename. When a new project is created, the project properties dialog shows “Project name (used as filename when the project is saved)”. When the project has been saved the name field is made read-only and the caption reads “Project name (same as filename)”. The same applies to the name field in the sound properties dialog.
• Creating a new project from a template will show the project properties dialog.
Nicely done Frits, very happy with these changes/additions here. The processes around Project Templates is more structured/guided now. I hope this minor loss of flexibility doesn’t cause inconvenience to others. 🙂
ConquistadorLoving the focus on more UI changes thanks! 🙂
Love the new look buttons. That brings a lovely UI consistency to Podium.
I’m now going to start on the main 2.21 feature, which will be a new track toolbar. In the default setup it will sit right below the navigator. I’m considering several new toolbar elements, such as: New track, Marker lane toggle, Tempo lane toggle, global bounce/solo/mute/record buttons, and a new “track filter bar” which will behave similar to the 2.20 editor profile bar. More about that later
.
Even more goodies on the way 🙂
That “track filter bar” sounds very interesting indeed. Might be the solution to some of the track issues I have had with the hierarchy recently. Guess I need to see it first but its sounds like it could work very well in theory.
If it behaves like the Editor bar then I am really looking forward to it. That was a superb addition to Podium. The toggling of lanes and global buttons for BSMR will be very welcome indeed! 🙂
thcilnnahoj@Zynewave wrote:
I’m now going to start on the main 2.21 feature, which will be a new track toolbar. In the default setup it will sit right below the navigator.
Hmmm, let me ask… Do you have anything else planned then for the big empty space right above the track headers?
Why insert a whole new toolbar, eating up space, just for a handful of buttons, while the most ‘natural’ location (in line with the track-level buttons), where also quite many other programs – Cubase, Logic, Pro Tools, Studio One – place these functions is left unused. In my hopefully perceived and accepted as humble opinion, it’d be the best place to put those SMR buttons. But I’ll look forward to the next beta to try anyhow. 😉
I’m also not keen on the bean-shaped 80’s sci-fi device look and placement of the transport bar elements. This time there’s no way to keep the old setup, so I guess I’ll have to get used to it…?
ZynewaveBeta2:
• Added a title bar at the top of the project window. This holds the menu buttons that previously were placed between the inspector and project page tabs.
• Moved the browser page tab next to the inspector tab. Selecting either the inspector or the browser will automatically hide the other.
• Moved some of the commands in the Setup menu into a new Window menu.
• Updated the button layout in the inspector and browser pages.
Zynewave@H-man wrote:
I like the new button shapes on the toolbar(s) but the edit icons get blury when the toolbar region height is increased.
IMHO the default size is too small which is why I changed them in the first place.
That’s not new for 2.21 though. The tool buttons are actually a bit wider than previousy when they are joined in a button bar. I agree with the blurry tool icons. Unfortunately they were created in a small resolution, so I will need to redraw them in high resolution to get rid of the blur.
Zynewave@thcilnnahoj wrote:
@Zynewave wrote:
I’m now going to start on the main 2.21 feature, which will be a new track toolbar. In the default setup it will sit right below the navigator.
Hmmm, let me ask… Do you have anything else planned then for the big empty space right above the track headers?
No, not besides the display of the marker name, tempo, time-sig and scale info that is currently displayed there. You’re of course free to remove the track toolbar, or move it directly above the tracks region. I think the track filter feature will justify using up space for the new track toolbar, but I need to experiment with that.
I’m also not keen on the bean-shaped 80’s sci-fi device look and placement of the transport bar elements. This time there’s no way to keep the old setup, so I guess I’ll have to get used to it…?
Specify please: Is it the fact that the buttons are no longer rectangular, that they are joined in a button bar, that the elements in the toolbar have been rearranged?
ZynewaveBeta 3:
• The title bar has an auto-hide option button when the window is maximized. When auto-hide is enabled the title bar can be shown by moving the mouse cursor to the top of the screen.
This makes it possible to reclaim the added vertical space occupied by the new title bar. I added the title bar because it was getting a bit overcrowded with the menu buttons in the middle of the inspector, browser and project page tabs. The new layout is a bit cleaner. I also didn’t like the fact that the menu buttons were moving around when you opened/closed the inspector.