Topic: 1.09

Viewing 2 posts - 1 through 2 (of 2 total)
  • July 19, 2004 at 00:59 #252
    Zynewave
    Keymaster
    • To simplify things and reduce possible conflicts, preset objects are now only assignable directly on tracks with mapping objects. Previously you could have multiple preset objects on child tracks of a mapped track, which could cause conflicts during playback.

    • Track error popups will appear if more than one VST program preset or more than one library preset is assigned to a global plugin instance. This is due to limitations in the VST specification, which does not allow VST programs and library presets to be associated with MIDI channels. You can still assign MIDI program change presets to each MIDI channel mapping of the plugin.

    • Drag and drop of preset and parameter objects are now blocked on tracks with incompatible mappings.

    • A pin button is added to the preset panel. This enables auto-selection of presets when navigating in the preset list.

    • When enabling ‘use preset as drum kit’ in the preset properties dialog, a message box will appear asking if default drum key presets should be created.

    • The plugin editor ‘E’ key shortcut now works if focus track is a subtrack of a plugin track.

    • Modified name formatting of mappings created when importing multitimbral devices. MIDI channels are written as (01) .. (16) at the end of the name. Multiple instances of global devices are written as (#2) (#3) etc. at the start of the name.

    • The global instance number setting in the device mapping properties dialog is now used for external hardware devices as well. This allows coordinated latency compensation of all mappings linked to an external device, similar to how global plugins are handled.

    • Fix: MIDI mappings of a global plugin/device are no longer allowed on sub tracks of a track with an audio mapping of the global device. This could in certain situations cause instability and incorrect latency calculations.

    • Fix: When editing notes in the drum editor, Podium would crash if there were no drum key presets inside the kit preset.
    July 19, 2004 at 01:07 #3656
    Zynewave
    Keymaster

    A few technical details:

    Some of the updates in this release are made in preparation for implementing bussing in the mixing engine. As a result of the extended error check on preset objects and global instance mappings, your old projects may show some new track error popups. Follow the description in the popups to resolve the conflicts.

    If you have used global plugins in your older projects and have placed MIDI mappings on subtracks of a track with an audio mapping, you need to move the group of MIDI tracks up on a level outside the plugin audio track.

    The reason for this restriction is because tracks with MIDI and audio mappings of a global plugin need to be compensated with the same latency delay. If you in previous Podium versions would insert a plugin with latency delay between a parent track with an audio mapping and a child track with a MIDI mapping of a global plugin, the latency calculation routines would fail.

Viewing 2 posts - 1 through 2 (of 2 total)
  • The topic ‘1.09’ is closed to new replies.
© 2021 Zynewave