It doesn't look like I can achieve this by editing a config file. Something more hacky?
The main thing would be for init to load Transpose:0
Edit the init patch in Bazille & Zebra
-
- KVRist
- 67 posts since 13 Apr, 2014
The nearest things are making a default patch or making my own init in the user folder?
It doesn't look like I can achieve this by editing a config file. Something more hacky?
The main thing would be for init to load Transpose:0
It doesn't look like I can achieve this by editing a config file. Something more hacky?
The main thing would be for init to load Transpose:0
-
- KVRAF
- 26963 posts since 3 Feb, 2005 from in the wilds
IIRC, there is a way to do it.lokio wrote: Mon Sep 26, 2022 11:11 pm The nearest things are making a default patch or making my own init in the user folder?
It doesn't look like I can achieve this by editing a config file. Something more hacky?
The main thing would be for init to load Transpose:0
But I have forgotten since Bitwig allows one to make a default preset for every plugin so I have those all set up. Now I don't remember how to do it in the u-he plugins themselves.
-
tasmaniandevil tasmaniandevil https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=62450
- KVRAF
- 2171 posts since 22 Mar, 2005 from a planet called u-he
It's possible to change the startup preset, but not the init preset.
For the startup preset:
Just create a preset with the settings you want, then save it with the name "default" to the main "Local" folder (not to the main "User" folder).
This preset won't show up in the plugin's preset browser.
Instead, it will be loaded as the startup preset when you load a new instance of the plugin.
Init preset:
If you want a custom init preset, just save a preset with the desired settings somewhere, e.g. in the main User location.
For the startup preset:
Just create a preset with the settings you want, then save it with the name "default" to the main "Local" folder (not to the main "User" folder).
This preset won't show up in the plugin's preset browser.
Instead, it will be loaded as the startup preset when you load a new instance of the plugin.
Init preset:
If you want a custom init preset, just save a preset with the desired settings somewhere, e.g. in the main User location.
That QA guy from planet u-he.
-
- KVRian
- 814 posts since 18 May, 2007 from Berlin
That would be "HS The Default Position" in the Pianoids folder.
-
- KVRer
- 18 posts since 17 Jun, 2014
This doesn't work for me using Bazille 1.1.2 (VST2 or 3) in REAPER on Windows 10 x64. Bazille just ignores my custom patch (default.h2p). I've confirmed correct location, refreshed the presets, etc. Any ideas?tasmaniandevil wrote: Tue Sep 27, 2022 5:03 am Just create a preset with the settings you want, then save it with the name "default" to the main "Local" folder (not to the main "User" folder).
This preset won't show up in the plugin's preset browser.
Instead, it will be loaded as the startup preset when you load a new instance of the plugin.
-
tasmaniandevil tasmaniandevil https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=62450
- KVRAF
- 2171 posts since 22 Mar, 2005 from a planet called u-he
Have you loaded a new instance of the plugin after saving your default preset?
The new startup preset will be loaded with each new instance of the plugin.
This is not replacing the init preset you load by clicking in the main data display.
Maybe you already had saved a default preset for Bazille in Reaper itself?
This would then be the one that's loaded with a new instance of Bazille.
The new startup preset will be loaded with each new instance of the plugin.
This is not replacing the init preset you load by clicking in the main data display.
Maybe you already had saved a default preset for Bazille in Reaper itself?
This would then be the one that's loaded with a new instance of Bazille.
That QA guy from planet u-he.
-
- KVRer
- 18 posts since 17 Jun, 2014
Thanks for the rapid reply! I hadn't thought of a REAPER default, but it wasn't that. Turns out to be user error of some sort, since today it's working exactly as documented! Obviously I needed a reset. Thanks again!