@ronin wrote:
Hmm I think the source & input buttons are too big..
Do you mean the height of the controls, or the extra space used by the rounded edge?
I’m going to remove the object icons (‘fx’ etc.) shown in the mixer selectors, so that there are more room for the name of the object.
I also have plans for adding a strip width zoom button to the mixer left edge panel. Clicking this button will swap between two zoom settings. Dragging the button will adjust the width of the mixer strips.
@LiquidProj3ct wrote:
Thanks Frits, it seems nice… and thanks by full colour the mixer tracks! 😀
The colors setup dialog has been extended with settings for “rack/header/strip opacity” and “lane background opacity”. These settings have thus been removed from the tracks region dialog, as they are now applied globally. It also means that the rack, track headers and mixer strips will always have a consistent and similar look.
I think you must round the right side of mute buttons [X] also, since they will give more empty space between mixer strips.
I’d like them to appear similar to and horizontally aligned with the BSMR buttons below. That’s why I made them square in the mixer.
@Zynewave wrote:
I expect to have a beta with the first mixer changes ready this weekend.
I ended up rewriting more than first planned, so I don’t quite have a beta ready yet. Here’s a screenshot of my progress so far:
Please post your comments on the new design.
Notice the old +/- track group icons are replaced with new round buttons.
I am undecided whether the slider knobs in the mixer (and rack and track headers) should assume the color of the background, or if they should be the default button color. What would you prefer?
Thanks for all the bug reports. I’ll get back to them soon. I’ve begun the redesign of the mixer. I wanted to make sure the chain panel code can be modeled to work on the mixer strips, before I start chasing bugs. I expect to have a beta with the first mixer changes ready this weekend.
Beta 8:
Renamed “Group Panel” to “Rack”. Calling it “Rack” will of course make more sense once I implement the embedded plugin editors.
Added a “Lists” option button to the inspector. This will toggle the object assignment panels at the bottom. If anyone has a better description than “Lists”, let me know. I prefer it to be a single word and short.
The track select button no longer doubles as track menu. Instead right-clicking on the selector will open the track menu. That way the effect track menus are also available on the track headers and eventually in the mixer strips.
The tracks region options are also done. You can select to show: gain/pan/send controls, effect chain, source selector and input selector.
Question to you all:
2.23 is turning out to be a major face-lift of the track UI. I’m guessing I need a couple of weeks to update the mixer to the new chain design. I wonder if I should delay the release of 2.23 so that it includes the changes to the mixer?
@thcilnnahoj wrote:
@Zynewave wrote:
In beta6 the effect record buttons are finally gone. The track lane record button will also record enable all plugin effect tracks.
So if I got this right the correct way to record only automation now is to either just bypass the input (from my experience, auto-assigned audio inputs don’t overwrite anything anyway), or create the parameter track in advance and set it to record by itself?
Yes.
I can’t find the post anymore, but you said something like you were planning not to display effect chains on the track headers, and instead add a button that would open an overlay for track management. Are you still considering this or do you think the new GP should be generally used for viewing and rearranging effects? I think if I want to see a track’s effect chain in the arrangement view, I’d prefer this overlay box to zooming in or resizing the track.
I mentioned that idea before I started working on the new chain panel design. I think I’ve managed to simplify the chain management significantly, so I no longer feel it’s necessary to add a popup panel with larger and more spaced out controls. The new track inspector group panel does that job well, I think.
I’m keeping the controls on the track headers for the same reason, and also because the elements now are shown/hidden depending on the zoomed track height. It is no longer partially cut, as would happen with the old design. The tracks region options I’m currently working on will enable you to hide some or all of the controls on the track header, if you prefer a clean design.
Another thought I have about the future mixer redesign:
I plan to take the same chain panel that is now used in the inspector and track headers, and use it in the mixer strips as well. The bottom part of the mixer strips will remain largely as it is, but the entire top half where you manage plugins and sends will be replaced by the new chain panel. The button design will be slightly different to accomodate for the narrow space of the strips.
I think it is more user friendly that you use the same type of effect/track management in the inspector, track headers and mixer strips. With all the recent changes to the inspector/track headers, the mixer is in a state of limbo at the moment.
@thcilnnahoj wrote:
Edit: Ooh, there’s drag-and drop rearranging of effects on the track header! If possible, pop-up help should close as soon as you start to click-drag an effect track, otherwise you can’t see where you’re dropping it.
That’s fixed in beta7, which is now uploaded. Also the dragging up/down is modified slightly.
And something a little off-topic. I recently wiped the dust off an old laptop computer; it has a native screen resolution of 1400×1050… on a measly 14″ screen. 🙄
Text in Podium is awfully small that way, and changing DPI settings in Windows doesn’t help. This is no request – I’m just curious – have you ever thought about changing Podium’s font for a heavier one, or using the system’s font?
I am keeping in mind that, at some point I need to provide an overall size scale setting for the UI elements. Personally I’m excited about the new multi-touch capability of Windows 7. My next PC purchase will support some kind of multi-touch, either as a laptop/tablet, or using a standalone multi-touch monitor. In the wake of the Windows 7 release, there are a lot of new devices coming out that supports multi-touch.
So to be able to comfortably work with finger touching, I’m going to implement an overall “finger size” setting in Podium, which will adjust the size of all buttons. That way the user can easily adjust to whatever screen DPI is used with the touch interface. That is one of the reasons why I’m substituting the old flat group panel with the new resizable button style.
View menu -> Customize editor profile
Select the region below “Tracks” in the list.
Click “insert new” -> scrollbar
The horizontal timeline scrollbar has been replaced by the new navigator in the default setup. You can get back the old scrollbar by adding a “scrollbar” region in the editor profile properties dialog.
@thcilnnahoj wrote:
@thcilnnahoj wrote:
Podium lets you have pretty much an unlimited number of effect tracks! If you want 8 effects, just add them…
To be fair, this is not entirely true, maybe simply due to a bug: If I keep adding effects, at a certain amount the new effect tracks will not be added into the chain correctly. It’s best to try and see for yourself what happens. 😛
Also, if you were to have a mad chain of 30+ effects, at some point the group panel will start to extend beyond the screen. The scenario is unlikely, I’d say, but maybe a little “show/hide effects” button or a scrollbar would be in order in the GP.
The 30+ limitation will be removed at some point. It was necessary back when we had the expanded track layout mode.
And I’ll add a scrollbar to the group panel (rack) later on, when I implement embedded plugin editors. The scrollbar will of course only show if the rack does not fit in the inspector.
@LiquidProj3ct wrote:
About CPU usage. Podium, at least with one track, only use one core in my PC. Take a look to this screenshot, where I use Nithonat, Toraverb and Redoptor with maximun quality settings:
(click on picture until you see it at real size)
edit: I’m on Xp home, 32bits
It’s impossible for the host to split up the processing of a single plugin, or even a chain of serially connected plugins. The host asks a plugin to process a buffer of samples. It’s not possible for the host to split this up into smaller buffers, and then ask the plugin to process these simultaneously, because almost all plugins requires that samples are processed serially. Even a simple EQ plugin requires the processed result of the previous sample in its computation of the next sample.
If a single plugin should utilize multiple CPUs, it needs to be implemented in the plugin, which knows what parts of its internal processing can be performed in parallel. One example is the latest version of the NI Kontakt sampler. I remember reading that it now supports multiprocessing internally. It makes sense for a multitimbral instrument/sampler, because each voice could be processed separately.
@ronin wrote:
@Frits: The “new” multiprocessing works nice here. I’m noticing less spikes and seem to have a better overall performance.
Great. Which Windows version are you running?
@Malcolm Jacobson wrote:
I agree with others comments that the “Add new effect” button should be above the existing FX, and that the new effect should be added at the top, so the behaviour in the Group Panel matches the order of the Mixer.
By popular request, the “add new effect” (or “+”) button is now placed at the end of the chain.
I don’t understand the need for the Tick button. I like the information about the effect to be shown in the Inspector as soon as I click on the effect name. I don’t like having to click the “Tick” button as well. Can we add an option to hide this button and have the information automatically displayed?
I can’t see how I can avoid the tick/select button. There need to be an indication in the group panel of which effect track is selected, and thus which track is being edited with the object lists at the bottom of the inspector. I can’t see how I can combine this into the selector buttons. The selectors already use colors to indicate plugin open/close state. Clicking selectors are used to open menus or open/close editors, and you don’t always want the track to be automatically selected when you just want to open a plugin editor.
@LiquidProj3ct wrote:
@Zynewave wrote:
In beta6 the effect record buttons are finally gone. The track lane record button will also record enable all plugin effect tracks.
I love those minor changes that simplify Podium workflow! I was trying it and I saw this:
Since green inputs are the same that red input, the green inputs hasn’t too much sense, I see them as a waste of space and an unnecesary interface overload. Unless you have another plans for them, I would hide them from children tracks.
Thanks, that’s a bug. The fader, source and input selectors should not be shown at all on parameter tracks. Only the parameter selector should be shown. I’ll fix it for the next beta.
2. I can’t help but to think those shadows look a little exaggerated on brightly colored backgrounds, like the default blue for selections on Vista. I don’t know about your UI rendering engine, of course, but is there any way you could try something similar to rendering shadows with a different blend mode? You know, Like in image editors – multiply, screen, overlay… A “simple matter of programming”, surely. 😉
I agree that the shadows are a bit too agressive. I’ve toned down the button shadows in the new beta6.
In beta6 the effect record buttons are finally gone. The track lane record button will also record enable all plugin effect tracks.