Zynewave's Forum Page

Profile  |  Topics  |  Replies  |  Favorites

Forum Replies Created

Viewing 15 posts - 976 through 990 (of 5,972 total)
  • in reply to: Preview 2.36: Extended UI and mixer resizing. #19185
    Zynewave
    Keymaster

    @thcilnnahoj wrote:

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

    I was thinking more of centering them inside strips, not around the meters, unless the minimum size strips themselves have an uneven width.

    The meters are centered horizontally in strips, so centering the BSMR buttons will make them appear centered above the meters. I was just pointing out that the buttons will appear to be a pixel misaligned, due to even/uneven pixel widths. And yes, mono/stereo strip widths are always uneven, to ensure meters are center aligned.

    There is a new beta3 up. I’ve rolled back some of the changes I made in the previous betas.

    The menu buttons are now rounded corner, instead of rectangular. The old larger drop shadow is restored in the inspector rack, and on the BSMR buttons. I’ve kept the smaller shadow on the chain panel controls in the track headers and mixer strips. The old focus frame is restored in the mixer.

    Furthermore in beta3:

    Added “show frame around focus track” option to the mixer region dialog.

    Fix: Resizing the channel header panel in the sound editor did not update the wave display area.

    Please give it a try, and let me know if there still are some design issues that needs tweaking.

    in reply to: Preview 2.36: Extended UI and mixer resizing. #19184
    Zynewave
    Keymaster

    @Trancit wrote:

    After a closer look to the mixer, I have to say, you should definetely work on the Solo/Mute/Record buttons… πŸ˜€

    Especially when resizing the mixer channels, they are far to big and “ugly”…

    I think they are by far not so important to take so much space…

    I think there are plenty of users that would say solo/mute/record are quite essential in a mixer. Making them smaller would go against the button size conventions I use throughout the Podium UI. I’ve tried my best to make them not look “ugly”. Do you have any suggestions to what should be changed?

    Did you change the colour of selected track in the new beta??? Especially the mixer channel this blue is so dense and bright, itΒ΄s hard to see any details anymore and this bright colour doesnΒ΄t fit the rest of the colour scheme…

    I did in beta2, and I gave my reasons for this in my previous reply before your post. Anyway, in the new beta3 I’ve changed it back to a thin frame.

    in reply to: Preview 2.36: Extended UI and mixer resizing. #19183
    Zynewave
    Keymaster

    @druid wrote:

    So, before I start, I will say that I use a 40″ LED TV screen, full HD (1920×1080) and my eyesight sucks, so I have Windows 7 set to … 125% text size, I think. Windows 7 then increases the size of most text, scrollbars, icons etc. You *could* look at this in Windows also, to determine how you should size the interface. It would allow Podium to be more compatible with general system settings.

    I could understand why you might not want to bother with such a thing, but as a steadfast user of larger-than-100% font/scrollbar/icon/etc size in Windows now (on my laptop too) it’s sure nice when other programs, like internet browsers, recognise this setting and render the text larger for me too.

    Currently only the button size is scaled with the new adjustable setting. In a future update I’ll experiment with scaling font sizes.

    in reply to: Preview 2.36: Extended UI and mixer resizing. #19182
    Zynewave
    Keymaster

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

    in reply to: Runtime error #19181
    Zynewave
    Keymaster

    @andyy815 wrote:

    Which soft sampler is best for SF2?

    Have you tried sfz+ ? It has recently been converted to freeware:

    http://www.cakewalk.com/products/SFZ/

    I demo it using a soundfont in this video:

    in reply to: Preview 2.36: Extended UI and mixer resizing. #19167
    Zynewave
    Keymaster

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

    in reply to: Preview 2.36: Extended UI and mixer resizing. #19165
    Zynewave
    Keymaster

    @Trancit wrote:

    Another question:

    Because the midi preview works so well, especially with in sync to the project, do you plan rex support with same preview features from the browser, that would be so cool and would bring Podium at the same level with Reaper in this point…

    REX file support is not on my time plan. There are a lot of features I want to work on before looking at REX support.

    in reply to: Preview 2.36: Extended UI and mixer resizing. #19164
    Zynewave
    Keymaster

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

    in reply to: Podium preview topics #19150
    Zynewave
    Keymaster
    in reply to: Preview 2.34: Minor consistency updates #19149
    Zynewave
    Keymaster

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

    in reply to: Zynewave, your Vid for Drum templates #19148
    Zynewave
    Keymaster

    I’m not sure I fully understand. Can you describe what you want in more detail?

    You cannot route audio from a parent track to its own child tracks. Everything flows upwards in the hierarchy.

    in reply to: Preview 2.34: Minor consistency updates #19144
    Zynewave
    Keymaster

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

    in reply to: Latency compensation questions #19143
    Zynewave
    Keymaster

    Yes, I understood your description of the two types of latencies from your first post. What was the question again?

    I think recorded material should be compensated so that when played back, it is reproduced as it was performed, and not as it was (or if it was) monitored through Podium. The only case where it would make sense to compensate the recording to the monitored signal, was if the performer actually sang/performed ahead of time, to make his/her own monitored signal sound in sync. That surely is not the best way to go about recording.

    in reply to: Mixer Zoom #19142
    Zynewave
    Keymaster

    @ninjawarrior wrote:

    May ask, there where is tracks, editor, mixer etc. buttons and if you click mixer, it naturally open mixer. But same time you lost VSTI’s editor button on playlist view. This is pretty stupid. Need to click “tracks” again to get editor button visible, which takes unnecessary time.. Too many clicks..

    That’s a setting you can change in the mixer region dialog. I disabled the controls in the mixer default setup, because the mixer has all the controls normally on the track headers, and I wanted to show that it’s possible to configure the layout of the track headers. I’ve now removed that customization in the default setup, to avoid confusion.

    in reply to: Mixer Zoom #19141
    Zynewave
    Keymaster

    @LiquidProj3ct wrote:

    If you’re working on mixer gui maybe it’s the right moment to ask for wider resizable meters and ctrl+alt+mousewheel as shortcut to zoom mixer strips as we do in arrangement and editos.

    Resizable meters won’t make it into this release, but the slide and zoom tools will.

Viewing 15 posts - 976 through 990 (of 5,972 total)