linedef-5 wrote on 2023-09-17, 03:25:Hi Falcosoft, this is great and could be an easier starting point for people who want to try various Roland/Yamaha VSTs. […]
Show full quote
Hi Falcosoft, this is great and could be an easier starting point for people who want to try various Roland/Yamaha VSTs.
Feedback and possible bugs:
- Window positions aren't saved.
- "Always on Top" isn't saved (main window and "activated" VST window).
- "Save Settings" button doesn't work ("activated" VST window).
- The "configure" VST window doesn't show "Always on Top" or "Save Settings". It automatically saves any VST changes, which is fine, but maybe not expected or desired.
- The "configure" VST window doesn't update in response to music playing, e.g. the bars that appear when parts are playing.
- If the "configure" VST window is open and music is played, the "activated" VST window pops up so now both are showing. Why not combine these into one window?
- Maybe borrow from your FSMP VST plugin window (autoload settings checkbox, load/save buttons).
- If I send music to the VST driver, the driver has to load the VST on demand. Unfortunately, Roland SCVA has a very slow initialization which means there is a long delay. This can even cause the sending application to momentarily freeze until the VST driver ready. For some reason, this delay also happens when unloading the VST on shut down (FSMP can shut down immediately). Would it be possible to have an option to load the VST into memory on Windows startup, and keep it active at all times?
- How about a "Default" entry in the sample rate drop-down list, like FSMP?
- I'm confused by the separate 32-bit/64-bit shortcuts since they both seem to load any VST type. What's different here compared to FSMP? And would it be possible to bring that convenience back to FSMP so only one version is needed (e.g. 64-bit FSMP for everything)?
Hi,
1. Window positions saving has been already implemented and will be in the next version:
https://github.com/Falcosoft/vstdriver/commit … 54b0a2fab0f0c11
2. It works as intended. The whole point of always on top state is to prevent dialogs to open up behind other windows at start time. The checkbox is for turning this state off if it is disturbing after start time. So it is intended to start dialogs always in the on state.
3. It works for me in every plugin I have tried. I need more details ( 'button does not work' is not enough, at least you should tell the error/success message you got after pressing the button). Have you seen this remark in the readme?:
Be aware that it is possible that you cannot save plugin settings from the editor at runtime while you can from the configuration dialog.
It's because the configuration dialog runs with elevated administrator rights while the driver does not. So make sure to give write permission for normal 'Users' to the plugin's folder (this usually has to be done for plugins located in Program Files (x86) or Program Files).
4. It works as intended. There is no need for always on top switch on the VST editor at configurtation time. Its state depends on the main config dialog's state and always opens up in front of it since it is a modal dialog in this case (contrary the driver's VST dialog is modeless). And saving settings is automatic since it is the only purpose of the config utility. Also it has been working this way from the beginning (before this fork even existed) so changing this would be the disturbing aspect for long time VST driver users.
5. It works as intended. Have you used the original VST driver before this fork? If not, then here is a short histrory: At config time you open a VST dialog version that is totally independent from the driver. It is only for saving settings. Originally only this config time dialog existed. When you opened the driver from a Midi client there was no visible dialog. This fork added the option to display an editor dialog when the driver is active but the 2 versions are totally independent. The config version does not know anything about the state of the driver at all so it has no chance to display anything playback related.
6. Look at the answer above. It's because it's not poosible currently. The config part is totally independent from the driver. Actually the configuration part is an independent project/application that works even without the installed driver component. Its only purpose is to save settings to registry/.set file that the driver loads when it is opened by Midi client/Windows. So there is no point in opening the config utility and changing settings in config utility when the driver is active since the changes made by the config utility are not reflected in the driver's state real time.
7. Currently not planned, maybe later.
8. No, it is not possible. This is a driver not an application. The driver part can only do things that respond to Windows requests. Windows does not start the driver until a Midi client requests this and the driver has to close when Windows tells it to close itself.
9. WaveOut has no default sample rate. In FSMP WASAPI is used through Bass and Bass/WASAPI has such option (look at this thread why using Bass is problematic for a driver like this).
10. Besides WaveOut the driver now also supports ASIO output. There are ASIO drivers that are either 32-bit or 64-bit only
and 32-bit config dialog does not necessarily enumerate the same ASIO drivers as the 64-bit one and does not reflect what ASIO drivers 64-bit clients see.
(E.g. on 64-bit OS Steinberg products typically install "Low latency Generic ASIO driver" that is 64-bit only).
FSMP has no ASIO output support so there is no such problem. If you do not use ASIO then you can use either the 32-bit or the 64-bit config utility, they do the same.
An example (as you can see the same selected driver is available at different Ids on 32-vit vs. 64-bit):
The attachment asio1.png is no longer available
BTW, many of the above answers can be found on the Wiki page or in the release notes in more detail:
https://github.com/Falcosoft/vstdriver/wiki
https://github.com/Falcosoft/vstdriver/releases