Dragonfly Hall Reverb

[Michael Willis]

(04-13-2018, 12:05 AM)Samulis Wrote: Yes, it's normal to be a .dll.

I tried it in Reaper and Finale, but it wouldn't even get recognized by the plugin scanners. I don't know if there's a log somewhere for those, but no errors came up.

Thanks Sam, I'll see what I can do about that. By any chance did you try the Mac version?

[Nayrb]

No luck with FL Studio, either. Hope you can get a Windows version working, though. I would love to test it out.

[Michael Willis]

(04-13-2018, 01:18 AM)Nayrb Wrote: No luck with FL Studio, either.

Yeah, it's clearly broken. I've reached out to the author of the framework I'm using, who has apparently had it work cross-platform.

[Michael Willis]

I think I might have a working Windows version now, please try this:

https://github.com/michaelwillis/dragonf...v0.9.1.zip

[Nayrb]

(04-22-2018, 01:40 AM)Michael Willis Wrote: I think I might have a working Windows version now, please try this:

https://github.com/michaelwillis/dragonf...v0.9.1.zip

Unfortunately it's still not recognized by FL. Maybe others have had luck with other DAWs on Windows?

[Mattias Westlund]

It works in REAPER 4.78 x64 on Windows 7 Ultimate x64! Nice

[Michael Willis]

It works in REAPER but not in FL? That's weird, I thought it would either work everywhere or nowhere.

Mattias, I'm excited that it worked for you! Like I said, this is mostly just Hibiki with a new face and much fewer parameters. The hidden parameters are either fixed defaults (for example, the early send is fixed at 20%) or derived (the base decay time is the room size divided by ten). I'm wondering, from anybody who has used Hibiki, did I grossly oversimplify the parameters? I had somebody suggest that I could design it such that the DAW can control more than are shown in the graphical interface, as a sort of "advanced mode".

Nayrb, does FL have any kind of log about why the plugin failed to load? I'm really flying quite blind here, I'm using a cross-compiler to build the Windows version on Mac or Linux, and then I'm testing it using a plugin host called Carla that does some black sorcery to load Windows VSTs.

[Nayrb]

(04-22-2018, 01:09 PM)Michael Willis Wrote: Nayrb, does FL have any kind of log about why the plugin failed to load? I'm really flying quite blind here, I'm using a cross-compiler to build the Windows version on Mac or Linux, and then I'm testing it using a plugin host called Carla that does some black sorcery to load Windows VSTs.

I got it to work. It didn't show up in the Plugin Manager after the scan until I searched for it. Then it was in "error" status because it didn't know whether it was an "effect" or a "synth." I manually applied the designation as "effect" and then it was functional.

So it works! Looking forward to messing around with it. I appreciate the more friendly interface.

[Paul Battersby]

I tried out your reverb on Reaper using Windows 10. Reaper had no problem recognizing or loading it. I'm actually running 32 bit Reaper and it still had no trouble with your 64 bit plugin.

I tried some of the presets. I like the sound of the reverb. I could see myself using this in the future. I doubt I'd play with the controls much. I don't know much about configuring reverb, but there are enough presets that I can probably get the sound I want in a given situation from just choosing the right preset.

One problem though, is that your plugin is always on top of everything else on the screen. Even when Reaper is not the active application. As I'm typing this, your plugin is covering part of my browser. Other plugins in Reaper will cascade properly. The most recently clicked window/plugin becomes the top window.

Another small problem I noticed, when compared with other plugins within Reaper, your plugin doesn't support the undo command. If I move a dial or slider in other plugins, then press Ctrl-Z, the previous setting is restored. Your plugin does not restore a previous setting after pressing Ctrl-Z.

[Michael Willis]

(04-22-2018, 07:01 PM)Nayrb Wrote: So it works!

That's good to hear, although I wish I knew what I could do to give FL the hint that it's an effect rather than an instrument. Feel free to give me more feedback after you've had some time to play around with it. I still have yet to make a proper v1.0 release, so I'm still open to suggestions, particularly regarding changes to the presets, or if there are additional parameters that would be useful.

(04-24-2018, 11:35 AM)Paul Battersby Wrote: I'm actually running 32 bit Reaper and it still had no trouble with your 64 bit plugin.

That is kind of amazing, maybe there is no trouble because you are running a 64 bit OS? I have no idea, but I'll take it.

(04-24-2018, 11:35 AM)Paul Battersby Wrote: One problem though, is that your plugin is always on top of everything else on the screen.

I haven't had that problem, but I can imagine it being irritating. I'm not sure how other DAWs manage plugin interfaces, but from my testing with Ardour on Mac and Linux I am able to either minimize or close the plugin window when I don't want to see it anymore. Does REAPER force the plugin window to perpetually stay open? Or is this more a matter of you want the plugin window to be open, but you want it out of the way when you are doing something else?

(04-24-2018, 11:35 AM)Paul Battersby Wrote: Another small problem I noticed, when compared with other plugins within Reaper, your plugin doesn't support the undo command. If I move a dial or slider in other plugins, then press Ctrl-Z, the previous setting is restored. Your plugin does not restore a previous setting after pressing Ctrl-Z.

The framework I'm using doesn't have any support for undo, it's really minimalist, but this is a good feature request. It may require some significant redevelopment of the code that manages setting the parameters; maybe it's something that I can work on for a 2.0 version.