Zynewave's Forum Page

Profile  |  Topics  |  Replies  |  Favorites

Forum Replies Created

Viewing 15 posts - 961 through 975 (of 5,965 total)
  • in reply to: Making a donation #19212
    Zynewave
    Keymaster
    in reply to: Bouncing problems #19209
    Zynewave
    Keymaster

    Does the tempo change problem also exist if you use realtime bounce mode?

    in reply to: Making a donation #19208
    Zynewave
    Keymaster

    I scrambled my account name, at the request of Conquistador in the above post. You should replace AT and DOT in the name with the corresponding characters.

    I just experimented with creating a “Donation” button using the PayPal tools. This forum is not set up to allow HTML code, so I can’t paste the button in here, but this link should take you to a secure page where you can enter a donation amount:

    https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=UZNSUKDD4A9E6

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

    Beta4 is up. It has bug fixes and more refinements to the graphics. The track header BSMR buttons and the group bars (with the collapse buttons) now resize with the button size setting. The blank bounce button row in the mixer is removed if there are no bounce tracks.

    Tomorrow I’ll start implementing the slide and zoom tools for the mixer.

    in reply to: Your one stop .pod shop?!!? #19196
    Zynewave
    Keymaster

    If you can provide some example projects, I could easily set up a demo project page in the wiki section. The project file can be uploaded there, along with a short description. Similar to how the the current color setup page works:

    http://www.zynewave.com/wiki/doku.php?id=colorschemes:index

    Building FTP upload into Podium is a bit of work, so I would put a low priority on that.

    in reply to: Note entry problem #19195
    Zynewave
    Keymaster

    It defaults to “snap to closest grid line”. Enable the “snap to previous grid line” mode in the snap menu.

    in reply to: Runtime error #19194
    Zynewave
    Keymaster

    @andyy815 wrote:

    Frits! You have to create an SF2 player for Podium :):):)

    I’d like to, but that’s quite a big project. Maybe some day when the Podium featureset is more complete. Although, if I were to to create a simple sampler for Podium, I would base it on the open source sfz file format. There probably are a lot of converter utilities that can convert soundfont to sfz format.

    in reply to: Runtime error #19187
    Zynewave
    Keymaster

    @andyy815 wrote:

    Yes I have a freeware SFZ+ but it doesn’t work properly on any of my three computers,

    Ok, I saw you mentioned “sfz” in a previous post, so I thought you hadn’t tried the “sfz+” plugin. These are two different plugins.

    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.

Viewing 15 posts - 961 through 975 (of 5,965 total)
Β© 2021 Zynewave