Zynewave's Forum Page

@thcilnnahoj wrote:

– I see the SMR buttons are colored again… I got used to the ‘clean’ buttons in beta 8 and I’ve actually very much come to prefer it that way.

Glad to hear it. It was just an experiment. I’ve reverted to the non-colorized buttons.

– Speaking of, the B button still comes after SMR in the mixer, directly opposite to where it is placed on the track headers – strange, I think. If you’re concerned about the B button pushing the SMR ones out of line across all mixer strips, then maybe just moving them down a bit would help?

I’ve now tried to put the B button at the top.

I’m also yet undecided on the changed lighting angle of the SMR buttons in the mixer.

Another experiment. I didn’t like it either, so I’ve now gone back to the horizontal bump.

– Will the different fader style options still be available or are you planning to clean up and unify the design?

Some of the old options will be removed, but I haven’t decided yet what options should be kept.

– I find the half-circle button to be a little vague. In my opinion, it’s just not self-explanatory enough to realize what it’s supposed to do.

Click on it a few times, and you soon realize what it does :wink:. It also has popup help.

Below is a screenshot with the latest refinements. I’ve removed the 5-pixel shadow spacing between the strips. The strip separation is still good I think, now that the strips are colorized.

@Tony Bodoczky wrote:

Hi Fritz!
Integrating fixedly would be good the zynewave eq-t onto all of the channels of the mixer(as the inspector shows). The masterre too.

Fix integrating:cubase,sonar,nuendo,dp,record.

In a later release I will implement embedded plugin editors in the chain panel. This will be available in both the rack and the mixer strips. So you will be able to show for example a miniature zPEQ display with draggable curve handles embedded in each mixer strip.

@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.

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.

@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:

@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.

@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?