Topic: A little DASHSignature daHornet GUI bug.

  • This topic has 5 replies, 3 voices, and was last updated 19 years ago by Max.
Viewing 6 posts - 1 through 6 (of 6 total)
  • #673
    Max
    Participant

    Hi Frits.
    I’ve discovered a little problem with free DASHSignature daHornet VSTi. I can hide keyboard using arrow button on the face of synth or using context menu, but I can’t make it appear again. It’s not a big problem, because if I turn the keyboard on and re-open the GUI, the keyboard gets back. But it’s not very comfortable.

    Works fine in other hosts.

    You can find daHornet here: http://liqihsynth.com/catalogue.htm#free

    #5593
    Zynewave
    Keymaster

    Hi Max,

    I’ve debugged the daHornet plugin to see what’s going on. The VST spec defines a feature called ‘sizeWindow’ which is a way for a plugin to ask the host to resize the plugin window. Podium replies to the plugin that it supports sizeWindow. Strangely, if I disable this feature, then the daHornet plugin will resize the window by itself, which will work both with hiding and showing the keyboard. When Podium reports that sizeWindow is supported, the daHornet for some reason don’t call this function when pressing the button to show the keyboard. This appears to me as a bug in the plugin. If I disable the sizeWindow support, then there are other resizable plugins that won’t work, so I’m afraid we will have to live with this daHornet bug.

    Frits

    #5595
    super_crunchy
    Participant

    I’ve emailed the guy who made daHornet to see if he’ll look at the bug… he might not, because it’s a discontinued product, but there’s no harm in asking πŸ˜‰

    (I sometimes use daHornet myself, but I never use it’s keyboard)

    #5598
    Max
    Participant

    Thanks Frits.

    Strange, but daHornet works fine for me in other hosts πŸ˜•

    Anyway, it’s not so terrible to live with this.

    Unfortunately, last night I’ve discovered another strange behavoir of the VSTi. I don’t want to create new topic for it.

    I use Antti Taurus for the basses (free (donationware). Taurus uses host’s default GUI. When I import taurus.dll in Podium, I can’t tweak the first 4 parameters of the plug (Play Mode, Octave, Decay On and Glide On). I’ve checked out the VST parameters of Taurus in the plugin definition and see that Podium on incomprehensible reason uses “range from 0 to 0” in the “Value definition” for this 4 parameters. Actually, the problem solved – I’ve just edited the “range from” like “0 to 3” or like this and saved the new definition for the Taurus. Now it works alright. But anyway it’s strange because this parameters works fine by default at least in energyXT demo!

    Here is the link for Taurus: http://www.smartelectronix.com/~antti/

    #5602
    Zynewave
    Keymaster

    Strange, but daHornet works fine for me in other hosts

    I would guess that these hosts don’t support the ‘sizeWindow’ feature then. As I said, I could get daHornet to expand/collapse correctly in Podium if I disabled this feature. This is a good example of how difficult it can be to support all plugins correctly, due to different interpretations of the VST standard.

    When I import taurus.dll in Podium, I can’t tweak the first 4 parameters of the plug (Play Mode, Octave, Decay On and Glide On). I’ve checked out the VST parameters of Taurus in the plugin definition and see that Podium on incomprehensible reason uses “range from 0 to 0” in the “Value definition” for this 4 parameters

    I tried it, and it works for me. You just have to drag the mouse a little further to make the value change. The reason for the 0 to 0 value range is explained at the bottom of the Parameter Properties section on this page.

    #5605
    Max
    Participant

    @Zynewave wrote:

    I would guess that these hosts don’t support the ‘sizeWindow’ feature then. As I said, I could get daHornet to expand/collapse correctly in Podium if I disabled this feature. This is a good example of how difficult it can be to support all plugins correctly, due to different interpretations of the VST standard.

    Yes, I see. As I said before, this daHornet bug is not a big problem. Thanks for looking into this.
    BTW, I’ve recently tried it in energyXT demo and got the same behavoir as in Podium.

    I tried it, and it works for me. You just have to drag the mouse a little further to make the value change. The reason for the 0 to 0 value range is explained at the bottom of the Parameter Properties section on this page.

    Sorry, this is my fault. But there’s so many features in Podium so I just can’t learn all the Podium guide πŸ˜‰ Thanks for helping.

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