Zynewave's Forum Page

Profile  |  Topics  |  Replies  |  Favorites

Forum Replies Created

Viewing 15 posts - 1,561 through 1,575 (of 5,966 total)
  • in reply to: Preview 2.25: Zoom snapshots & revised track height zoom #17320
    Zynewave
    Keymaster

    Beta4 is up:

    The .pod file format is updated with the zoom snapshots, so back up your projects before saving them with this beta, in case you need to go back to 2.24.

    Press Shift+1..9 to recall a snapshot.

    Moved the “follow focus track” and “follow control surface” options from the mixer menu to the editor View menu. This means that the options now apply to both the tracks region and the mixer.

    I’ve modified the way that the zoom range is displayed in the navigator. Hovering the mouse over a snapshot button will highlight the zoom range in the navigator. Let me know what you think of the new style.

    in reply to: Preview 2.25: Zoom snapshots & revised track height zoom #17315
    Zynewave
    Keymaster

    @thcilnnahoj wrote:

    Love the zoom snapshots! It’s great that the vertical zoom setting is also stored – this is extra nice as you can, for example, use one snapshot for precise editing. But to be honest, with the track height setting I used up until now, a maximum of 200% zoom is much too small for this kind of editing.

    My suggestions are these (one for me, one for you :wink:):

    1. I set my tracks’ default height much larger from now on and try to use a vertical zoom level smaller than the default for normal arranging. Then I can zoom in as far as I like during editing. The disadvantage is that I have to set up two extra things, and I can’t use Ctrl-click on the zoom slider anymore.

    2. The max. zoom amount is increased some more again.

    Try the new beta3. The vertical zoom is now exponential, so the default middle position is still 100%, but maximum zoom is 400% instead of 200%. Beta3 also has a small change to the way track height dragging is handled.

    in reply to: Preview 2.25: Zoom snapshots & revised track height zoom #17309
    Zynewave
    Keymaster

    @UncleAge wrote:

    @Zynewave wrote:

    • Added a favorite folder “+” button to the file browser toolbar.

    I clicked the Browser button. The area already had 3 favorite buttons in place. Next I kept clicking the “+” button until there were 9 favorites added, all of the them the same folder. When I did this a couple of things seemed strange.

    1. The “+” button disappeared. Now maybe this is ok since there wasn’t any room left in that area for another button. And I have no problem with the arbitrary number of 9 for favorites, but…

    2. All of the “newly added” buttons were highlighted, seemingly as a group. So selecting any of them selected all of them.

    3. I could not find a way to delete any of the favorite buttons. Any of them.

    Obviously some part of this is a bug.

    Thanks for the walkthrough. Favorites and zoom snapshots can be deleted by Alt+clicking the button, as mentioned in the popup help for those buttons. You can also delete the favorites in the “Favorite Folders” setup dialog. I’ve now made further changes that should make it easier to get through the problems you experienced:

    The “+” buttons for both the favorites and zoom snapshots now only produce a new shortcut button if it does not already exist. When the + button is inactive it is indicated by a dimmed + image on the button.

    The favorite buttons can now be right-clicked to show a menu similar to the one for the zoom snapshots and editor profile bar. In this menu you have a command for deleting the favorite.

    This is available in beta2, which I just uploaded.

    Also in beta2: Clicking a favorite folder or zoom snapshot button a second time will revert to the previous folder/zoom.

    in reply to: Preview 2.25: Zoom snapshots & revised track height zoom #17299
    Zynewave
    Keymaster

    @LiquidProj3ct wrote:

    Ok 🙂

    Left clicking in current selected profile button will select the first profile.. I don’t know if this is a feature (weird!) or a bug

    edit: changed the bug description

    It was a feature, and intended as a shortcut for quickly returning to the first (home) profile. No point in having features that are weird, so I’ve now removed this functionality. Thinking about it I agree that it can be perceived as unexpected behaviour.

    in reply to: Preview 2.25: Zoom snapshots & revised track height zoom #17297
    Zynewave
    Keymaster

    @LiquidProj3ct wrote:

    Please, don’t misinterpret me: I think that they will be useful for other people but not for me, because I use 10-12 tracks as max for a song of 5-7 minutes.

    Thanks for the explanation. Yes, the snapshots are mostly intended for navigation in large arrangements with many tracks. You can create a snapshot where the vertical zoom is at 0%, so that you can quickly get an overview of all the tracks, and zoom in on the area you want to work on. You can also create zoomed-in snapshots of e.g. drum tracks, bass tracks, vocal tracks and so on, so that you can quickly switch between these different sections.

    in reply to: Preview 2.25: Zoom snapshots & revised track height zoom #17295
    Zynewave
    Keymaster

    @LiquidProj3ct wrote:

    I haven’t any comment about navigator/browser snapshots since I don’t use them 😳

    The zoom snapshot is a new feature in 2.25. It just work similarly to the favorite folder toolbar in the browser. Do you mean to say that you don’t find zoom snapshots useful?

    in reply to: Podium preview topics #17292
    Zynewave
    Keymaster
    in reply to: Customising the default MIDI Parameters #17291
    Zynewave
    Keymaster

    @Malcolm Jacobson wrote:

    I thought Podium used to automatically record any MIDI data a controller sent (back around v 2.04)?

    Is it possible to have an option for this?

    To record a MIDI controller, it has always been a requirement that a matching MIDI parameter object existed in the device definition.

    in reply to: Customising the default MIDI Parameters #17287
    Zynewave
    Keymaster

    There’s no way to customize them, but I don’t mind extending the set of MIDI parameters that are created by default. I’ve now added Channel Pressure and Sustain Pedal (CC64). Are there any other common performance parameters that should be included?

    in reply to: Restricted to Podium license owners
    Zynewave
    Keymaster
    This content is restricted to Podium license owners.
    in reply to: Preview 2.24: Embedded plugin editors in the rack #17263
    Zynewave
    Keymaster

    @Conquistador wrote:

    Screenshots as promised… 😉

    This is with ClearType on. Reaper IMO has much clearer text compared to Podium here. I really do not know why Podium looks much less clear compared to Reaper :-k

    Podium is on the left and Reaper is on the right. Look at the “Fabfilter Timeless” text for the inserts.

    But if I switch off ClearType…can you spot the difference between the two applications “Fabfilter Timeless” text now? I can hardly tell them apart…below…

    Podium is far sharper than the first image now that Cleartype is off and matches (maybe even goes further than) Reapers text for clarity in the second image. Quite a difference and quite easy to see IMO with those screen shots.

    So Podium it appears benefits clearly from having anti aliasing disabled for certain areas (inserts on tracks and mixer strips) but anti aliasing is very helpful elsewhere in Podium that is why I think adding some kind of option to disable anti aliasing for the Insert, Source and Input buttons (just for the tracks and mixer strips) will solve this problem.

    I hope that helps.

    Thanks.

    Anti-aliasing of fonts and other graphic elements are two different things. Podium uses its own anti-aliasing routines when rendering buttons and lines etc.

    When it comes to fonts, Podium uses the default smoothing options selected in the OS, such as Clear-type. Podium uses the “Microsoft Sans Serif” font, which is the default Windows font used way back on the earliest Windows versions. Reaper probably uses a different font, since there are small differences in the letters at the small size.

    I’ve done some experiments with alternative fonts. I also tried to set the small font to be aliased, while the normal font is anti-aliased, and frankly I think the two shown together looks horrible 😕

    In a future update I’ll add the possibility for the user to select a custom font in Preferences.

    in reply to: Preview 2.24: Embedded plugin editors in the rack #17262
    Zynewave
    Keymaster

    @H-man wrote:

    At the risk of sounding like a broken record, would this be a good time to add the option of different colours (ie. lighter colours for darker themems) for the markers on the level meters?

    Are you talking about the dark 0, -3, -6, -12 dB indicator lines within the meter? If so, would the solution be to use the configured text color instead of black to highlight the lines?

    in reply to: Podium’s output dB #17259
    Zynewave
    Keymaster

    Maybe some of the sound tools you have compared with apply compression to the output?

    Otherwise I can’t see why Podium should have lower sound output. I have never experienced that problem myself. If you have the opportunity, try comparing with a different audio driver, or with a different soundcard.

    in reply to: 2.24 #17258
    Zynewave
    Keymaster

    @LiquidProj3ct wrote:

    Hi Mr Frits 🙂

    Podium automation doesn’t respect the ‘-inf’ in my project:

    The automation curve on the track is constructed from all the points that are within the range of the curve sequence events. The first -inf point you have highlighted falls before the start of your Level sequence event, and so is not included. You need to place the event snapped to bar 17.

    in reply to: 2.24 #17257
    Zynewave
    Keymaster

    @thcilnnahoj wrote:

    When you change the play/power color, the play cursor head still keeps the old one.

    Fixed. Thanks.

Viewing 15 posts - 1,561 through 1,575 (of 5,966 total)
© 2021 Zynewave