Topic: 1.55

Viewing 9 posts - 1 through 9 (of 9 total)
  • April 5, 2006 at 14:22 #784
    Zynewave
    Keymaster
    • The Podium installer now includes the zPEQ plugin. The plugin is installed at “Program FilesZynewavePodiumVstpluginsZynewave Effects”. When using the project wizard to ‘scan & import all plugins’ Podium will search this folder in addition to the user specified Vstplugins folder.

    • Importing a stereo effect plugin will create an additional mono mapping if the plugin reports it also supports mono processing. The zPEQ plugin has been updated to report mono compatibility.

    • Imported insert plugins no longer have the string ‘Insert’ appended to the plugin mapping name. Instead mappings for global plugins are now always named with ‘(#1)’, ‘(#2)’, etc. at the end of the plugin mapping name. Previously global instance number one did not have ‘(#1)’ in the name.

    • Added extra security during plugin preset recall, to maintain compatibility with e.g. the recently released Luxonix LFX-1310 v1.1.5.
    April 5, 2006 at 22:04 #6473
    Max
    Participant

    Thanks! LFX-1310 presets recall now working fine. Do you have any plans to add the ability to change installation path for zPlugins?

    April 5, 2006 at 22:25 #6474
    Max
    Participant

    I hate to say it, Frits, but you were right saying that recently added extra security during plugin preset recall can break the compatibility with other plugins. Synth1 presets recall is now broken 🙁

    http://www.geocities.jp/daichi1969/softsynth/

    All other plugins seems to work fine.

    April 6, 2006 at 00:09 #6480
    Zynewave
    Keymaster

    I hate to say it, Frits, but you were right saying that recently added extra security during plugin preset recall can break the compatibility with other plugins. Synth1 presets recall is now broken

    One major downside about the VST protocol is the vague developer documentation which results in plugin/host developers having different interpretations of even the simplest things.

    I’ve now added a further condition to the fix for the LFX-1310 plugin preset recall. This works with both LFX-1310 and Synth1. Fingers crossed that the remaining 17346 VST plugins are compatible.

    Do you have any plans to add the ability to change installation path for zPlugins?

    I’d like to keep them installed in the same user-specified location as Podium, or else updating Podium and the plugins can become complicated. You can copy the installed plugins to your main vstfolder if you like, but then the plugins will not automatically be updated when installing new releases of Podium.

    April 6, 2006 at 01:07 #6481
    Zynewave
    Keymaster

    I’ve changed my mind. I dislike having to put code in that changes the preset recall behaviour depending on the plugin. Luxonix emailed me an updated 1.1.5 version which fixed the problem in the plugin. I’m assuming they intend to release this in an update. I’m now removing the LFX-1310 fix I introduced in release 1.55, and so everything will return back to normal.

    April 6, 2006 at 10:52 #6482
    Conquistador
    Participant

    @Zynewave wrote:

    I’m now removing the LFX-1310 fix I introduced in release 1.55, and so everything will return back to normal.

    Hi Frits,

    Have you made this change in the 1.55 installer that is currently available already or should we wait for 1.56?

    April 6, 2006 at 11:05 #6483
    Zynewave
    Keymaster

    Have you made this change in the 1.55 installer that is currently available already or should we wait for 1.56?

    The LFX-1310 fix will be removed in 1.56.

    April 6, 2006 at 11:28 #6484
    Conquistador
    Participant

    OK thanks!

    April 6, 2006 at 11:32 #6485
    Max
    Participant

    @Zynewave wrote:

    I’ve changed my mind. I dislike having to put code in that changes the preset recall behaviour depending on the plugin. Luxonix emailed me an updated 1.1.5 version which fixed the problem in the plugin. I’m assuming they intend to release this in an update. I’m now removing the LFX-1310 fix I introduced in release 1.55, and so everything will return back to normal.

    That’s the best solution of cource.
    @Zynewave wrote:

    One major downside about the VST protocol is the vague developer documentation which results in plugin/host developers having different interpretations of even the simplest things.

    Unfortunately that’s right… But it’s the most popular musical technology.

    So, Luxonix finally solved their problem. Fine.

    Thanks for your help, Frits!

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