Zynewave's Forum Page

@ninjawarrior wrote:

If i can suggest, do something about those faders. To me, they don’t even look like a faders.

I didn’t design them with real physical faders in mind. The fact that they are translucent came in handy for the new compact design. Otherwise I would not be able to overlay the faders on top of the meters, and so the strips could not be zoomed all the way down to 25%.

Also you could try to put fader center and left channel output meter goes left side on fader, and right channel output meter goes right side on the fader.

That would pose problems with mono and surround meters. The current design scales easily no matter how many channels are shown in the center meters. Having the L/R meters on either side of the fader would also mean it would be hard to distinguish the meters from the previous and next strips. The distance between the R meter of one strip and the L meter on the next strip would be closer than the distance between L/R on the same strip.

@thcilnnahoj wrote:

Sigh… I think I’m over the initial shock now. That was quite something.

Cheer up. Try the new beta2 😉

I guess there’s no way you could be convinced to make the button roundness setting also apply to all the things on track headers, mixer strips, and the rack…? I understand the implications it would have.

Explain why you preferred the old style?

@Zynewave wrote:

I’d appreciate your feedback on the new design.

– I find it weird that buttons on track headers, mixer strips, and in the rack don’t have (noticable) shadows anymore, whereas all other buttons still do. Personally, I liked it better with shadows, as in 2.35.

I felt that the shadows around all the controls within a track header were a bit too much. By toning it down I feel it’s easier to distinguish the track headers from each other. That’s also why I added the 1 pixel rounded corner to track headers.

– What happened to the frame on mixer strips!? 🙁 Personally, I don’t care whether the selector buttons overlap the frame, or the frame overlaps them – I don’t want to have to look at the top of mixer strips every time to see which one is selected. Besides, it looked really neat. 😉

It looked horrible when used on the new narrow strips. It was difficult to tell apart shadow, meter, slider groove, and the 2 pixel focus frame. In beta2 I’ve gone back to painting the entire strip background with the select color. The reason I changed it to the frame some time ago, was because the old flat track controls did not blend well with the select color. Since then the new track chain panel with real buttons has been implemented. I think this works better with a full select color background. If no one objects to this, I’ll do the same with the track headers.

– I don’t like that the space between the input/source selectors and effects is gone.

It’s back.

– It’s funny that the gain/pan fields now always use that small font, even though you said before that better readability compared to the small font on faders was one of the fields’ main advantages. 😉

If I remember correctly, that was done before the new chain panel with the smaller font was implemented. I felt it looked a little out of place with the large font in between all the small font texts. I think it’s ok to use the large font for the track name.

– I think a logical consequence of mixer strip resizing is that the BSMR buttons should just be centered when they are drawn on top of the meters. I’d say this should also happen on MIDI tracks (that have no meters).

They are now centered. Note that the pixel width of meters are uneven, and buttons are even, so they cannot be centered exactly above the meter.

– There’s some space wasted where the B button usually is. Maybe this space could be reclaimed when you don’t actually have a track visible on which bouncing is enabled. If there is one, it would push down the SMR buttons so they’re aligned again on all tracks.

I can remove it if there are no bounced tracks at all. I won’t remove it if just the currently visible tracks don’t have a bounce button. It would be very confusing that the BSMR buttons would jump up and down as you scroll along the mixer strips.

– I think hiding the handles in the zPEQ editor miniature when reaching a certain zoom level would be worthwhile. That way you could at least see the EQ curve (you can’t reasonably edit it anyway using that tiny editor).

Good suggestion. Implemented in beta2. If you move the mouse over the EQ display, the nearest handle will still appear.

– Have you ever thought about using dials for pan again? It’s just easier to see, and definitely easier to adjust values on small strips. Unless everyone hates dials. 🙂

I like the symmetry of the slider.

@Trancit wrote:

For me the size of the level meter drops down to soon to make place for the Solo/Mute/Record buttons…

I’ll see if I can optimize this. Note that if you have enabled RMS metering on a track (click the meter to toggle this), then the RMS level indicators are drawn on the right side of the meter. That’s why there is a space between the meter and the BSMR buttons.

@thcilnnahoj wrote:

The mixing chapter should be mostly finished now, apart from a few fixme’s and those inevitable things that I forgot to mention.
I haven’t touched the levels section because it seems to be a mix of general mixer stuff, parameter automation, and of course relics from extended mode. 🙂 As such, I don’t know what to do with it yet.

Many thanks. The guide is catching up with the Podium development. :D/

Alas, the next 2.36 release will feature some graphics changes that makes your nice new mixer screenshots somewhat outdated. 😳

When it’s done I’d like to try my pen on the sequence events chapter.

It’s all yours.

Oh, and I think, when everything else is finished, we could do with a chapter for all things related to surround sound. You know what wouldn’t hurt either? A Zynewave surround panner. O:)

Good idea with the separate surround chapter.

I’m about to create a new preview topic for 2.36, so perhaps we should continue the discussion in that topic.

@thcilnnahoj wrote:

Also, Alt+clicking doesn’t unassign auto-assigned inputs.

Correct. Would you expect Alt+Click to disable the “auto-assign to focus track” menu option? If you move focus to another track, then the auto-assign will thus no longer be effective.

Edit: Also also, what about the source/track menu mixup (the last fixme remaining)?

I haven’t looked at this yet. Perhaps it’s best to make the shown menu a full track menu instead of a source menu?

I’ve now read the track inspector chapter, and I think it’s excellent. This would have taken me days to write myself. I hope I can repay you for your efforts with some cool new features in the next Podium release 😉

When embedded plugin editors are enabled, a show/hide button appears to the right of each selector that holds a VST plugin (or hardware definition?).

Only VST plugins. You can delete the hardware definition question.

Note: The first MIDI input device detected by Podium is configured to be auto-assigned in newly created projects. (Or is it arrangements?)

I would say “is by default configured to be auto-assigned in newly created projects.”