Topic: Preset names being cut off

Viewing 3 posts - 1 through 3 (of 3 total)
  • October 11, 2006 at 20:23 #1009
    Conquistador
    Participant

    This bug kept slipping my mind…

    1.When I put together the 51 presets for the ZPEQ I noticed that while Podium would save a preset with the correct name, If I loaded up the preset, some of the letters on one or two presets were cut off.

    No warning from Podium about any limit on characters used for Presets. Is there a limit or is this a bug?

    An example is the Trumpet and Sax high Shrill preset. This appears as Trumpet and Sax high Shr so it is cut off. I think I saved it that way because it was being cut off when viewed in the Preset panel but somehow Podium will allow it to be saved fully, but just not show all the characters in the Preset Panel.

    A Bug?

    2.Also Frits were you able to extend the ZPEQ bank capacity to 64 programs?

    October 11, 2006 at 22:22 #7988
    Zynewave
    Keymaster

    The VST .fxp file format can store max 24 chars in the preset names. So when you export a preset with a longer name to fxp, the name is cut off.

    Also Frits were you able to extend the ZPEQ bank capacity to 64 programs?

    I think I’ll leave zPEQ as it is for now. Importing your preset files as library presets works quite well I think.

    October 12, 2006 at 09:31 #7993
    Conquistador
    Participant

    @Zynewave wrote:

    The VST .fxp file format can store max 24 chars in the preset names. So when you export a preset with a longer name to fxp, the name is cut off.

    Ah ok…that explains it thanks. 😉

    I think I’ll leave zPEQ as it is for now. Importing your preset files as library presets works quite well I think.

    Agreed it does work very well I only brought it up as it was your suggestion not mine. You suggested it and asked me for my opinion on it which I agreed to on this thread…

    http://www.zynewave.com/forum/viewtopic.php?t=947 (second post)

    I simply thought you might have forgotten about it. 😉 But yes the current import process is indeed absolutely fine ‘as is’. 😉

Viewing 3 posts - 1 through 3 (of 3 total)
  • You must be logged in to reply to this topic.
© 2021 Zynewave