Zynewave's Forum Page

Profile  |  Topics  |  Replies  |  Favorites

Forum Replies Created

Viewing 15 posts - 1,786 through 1,800 (of 5,966 total)
  • in reply to: Preview 2.22: UI improvements #16387
    Zynewave
    Keymaster

    @psychesonic wrote:

    Yes. I find that if I have, say, a couple of hours of material – music, or dialogue for example – arranged sequentially on the track page, that if I only want to render a few minutes starting at the 1 hour point, the render process seems to start from the very beginning of the timeline. I once had to edit 3 hours of a forum into individual speeches – you can imagine how long this process took. Is it possible to specify where the render begins and ends… or have I missed something?

    Are you using the “render within punch range” command? The render should start where you set your punch-in position.

    in reply to: Preview 2.22: UI improvements #16386
    Zynewave
    Keymaster

    @swindus wrote:

    Little bug: When using the command ‘crop unique sequence’ the view of an opened sound event editor is not updated correctly. The position of the sound event is wrong (navigator zoom?). After unselecting and selecting the sequence again the display is right.

    The editor is not really linked to the sound event, but is only initialized with the sound object and zoom range once the sound event is clicked. Eventually I’ll change this so that the editor keeps a link to the sound event, and thus will react to changes to the event.

    in reply to: 2.21 #16385
    Zynewave
    Keymaster

    @psychesonic wrote:

    I really like the wav browser on the right hand side – right eyed or whatever. It seems a little cluttered having the Inspectror and browser bunched together. Is it possible to add align right/left?

    I’d like to keep the embedded inspector and browser bunched together. If you prefer a different setup, you can open a browser window and place it to the right of the project window. The F9-F12 key shortcuts can be used to switch between different window layouts.

    in reply to: Key focus problem experienced with certain plug-ins (solved) #16379
    Zynewave
    Keymaster

    I tried the Volcano2 demo. I also read the comment from fabfilter in the topic you linked to.

    Clicking on the plugin Window frame to give the plugin key focus works fine. Podium receives key press messages from Windows (WM_KEYDOWN/WM_KEYUP) and distributes these to the plugin with the editKeyUp() and editKeyDown() VST messages. The plugin can then respond to the key press and return to the host whether it “consumed” the key press. If not consumed, then Podium checks the key for Podium key shortcuts.

    It appears that the when you activate the Volcano plugin editor by clicking inside the editor window, it consumes the WM_KEYxxx messages, which then is never received by Podium. I read their comment about the mousewheel focus, but I can’t see why this should prevent them from letting the WM_KEYxxx messages through to the Podium parent window.

    If this works in other hosts, then it could be because these hosts parse keypress messages before Windows distributes the messages to the key focus window.

    in reply to: FR: Bounce selection/track to a new track #16378
    Zynewave
    Keymaster

    The next 2.22 release includes new bounce options. Check the 2.22 preview topic for more info.

    in reply to: Restricted to Podium license owners
    Zynewave
    Keymaster
    This content is restricted to Podium license owners.
    in reply to: Preview 2.22: UI improvements #16376
    Zynewave
    Keymaster

    Beta 2:

    • Added “export to sound file” to the arrangement editor and sound editor file menus. The commands show a dialog with bit resolution and normalize settings. The arrangement export uses the bounced audio of the master track. An “export bounced audio to sound file” command is also available in the bounce submenu of each individual track.

    • Removed the MIDI and bounce settings from the effect track properties dialog. The bounce settings are now exclusively managed with the track bounce submenu. The MIDI settings are still available in the source track properties dialog.

    • Reorganized the layout of the fader, meter and bounce track submenus.

    • Added “move bounced audio to new track” command to the bounce menu. Removed the now redundant “hide bounce track lane” option.

    The “export to sound file” dialog will in the future be extended with settings for sample rate, dither and encoding to mp3, ogg, flac etc.

    in reply to: FR: slider/fader related #16367
    Zynewave
    Keymaster

    @kingtubby wrote:

    The other thing is, I wonder if it would be possible to have an option to set limits on the range of individual controls. e.g. right click on a slider and choose ‘set control range’ or something. Then you could set an upper and lower limit like 0db and -30db or whatever. Likewise with pan controls left 50% and Right 50% for example.

    It could be represented graphically like so:

    From my point of view it would be useful as I like to mix stuff on the fly and I could throw faders etc, without having worry about going too loud or soft and so on.

    Adding this feature doesn’t quite gel with my current quest for UI simplification :). Perhaps we can discuss this again after I’ve completed my revision of the track header UI.

    Is there a reason why you can’t settle with resizing the track headers horizontally to widen the sliders?

    in reply to: Preview 2.22: UI improvements #16366
    Zynewave
    Keymaster

    @Conquistador wrote:

    Drums 🙁
    I would say (yes I have said it before) that the Midi drum presentation and set up is now just so far behind other parts of Podium (as of 2.22 especially) it really does stand out.

    How about a one click set up?
    I would ask if possible to consider adding a “Drum kit” button to the Presets panel for loaded VSTi’s. Currently the “Use Preset as drum kit” is hidden well out of view. Clicking on that new button should also automatically delete all notes that do not have drum note names as well. Those changes would at least get drum presentation and set up to a far more pleasurable level. More is needed but these two changes IMO are really basic, critical needs for that area of Podium at this point.

    What about this…? 🙂

    Your “critical” priorities are changing almost as frequently as mine :). That updating the drum editor is critical was not on your mind when we had the most recent VIP discussion of what I should spend my time on. The drum editor is scheduled for an update, but I would like to keep that out of the current series of overall UI revisions.

    Zoom Presets

    Studio One has a rather nice little feature which i dismissed the first time I saw it but find it quite slick in terms of its simplification of UI navigation. Its effectively a set of Zoom presets for the Arranger. Any chance of that kind of feature making it into 2.22?

    Not in 2.22. I think it was in the preview topic for the navigator that I mentioned I plan to add a zoom snapshot feature. The blank space to the left of the navigator will hold the controls for the snapshots.

    in reply to: Track Bounce options menu please…. #16365
    Zynewave
    Keymaster

    Please postpone your bounce worries until the next 2.22 beta. The last few days I’ve been working on a redesign of the bounce options. Check back when the next beta is available.

    in reply to: Tutorials #16364
    Zynewave
    Keymaster

    @Malcolm Jacobson wrote:

    Added a new video showing how to assign and record a VSTi, and how to assign a VST effect:

    http://www.youtube.com/watch?v=b0fKhfdxbjk

    Thanks. Favorited. I like that you are keeping the videos short.

    I was surprised that I didn’t get an email from Youtube, even though I’ve subscribed to your channel. Apparently I only see updates to my subscriptions if I log in, and go to the “subscriptions” page.

    in reply to: Podium preview topics #16359
    Zynewave
    Keymaster
    in reply to: Lock loop range #16356
    Zynewave
    Keymaster

    Wouldn’t it be easier to adjust the timeline rulers so that you are less likely to accidentally edit the loop range? You’ll avoid the extra clicks needed to toggle loop lock on/off.

    You can increase the height of the non-loop timeline ruler, or you can visually divide the timeline rulers by inserting space regions between them. You can also disable the default auto-hide option of the loop/punch/segment rulers.

    in reply to: Lock loop range #16354
    Zynewave
    Keymaster

    I would say no, but please explain what you mean with locking the loop range, and why you need it.

    in reply to: Do you think this might work? #16350
    Zynewave
    Keymaster

    If the the x64/x86 versions of a plugin has the same dll filenames, then you can easily exchange them. You just need to move/rename the x86 plugin folders temporarily, so that Podium will not find the plugins when the project is loaded. Then the auto-search will grab on to the x64 dll files with the same names. If the dll filenames are different, then you need to edit the filename in the device mapping properties dialog.

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