despite the incredibly high cpu-use with augustus loop due to the fact that my video card doesn't handle its open-gl gui well, i decided to have another go at it. reaper has a switch to turn off a plugin's gui and just show a standard list of parameters and sliders, so i can get around somewhat in there. kind of a pain, but at least my fan doesn't run at full speed when i bring up the plugin. i also figured i could just map some parameters to my midi controller and not even have to look at the gui at all, but i discovered something annoying: when the delay time is mapped to a controller, it doesn't control the range from whatever's set in the minimum and maximum delay settings, but rather from 0 to the plugin's max delay time of 3600 seconds. i don't know what 3600/128 is, but it makes for pretty crappy resolution when trying to change the delay time with a controller. any way to make cc data from 0-127 for the delay time control what's set by the min and max delay limits instead?
and also, i know 3600 seconds of delay sounds cool, but is there any chance of making a version with a more practical delay limit? make just 30 or 60 seconds? i ask because again, due to the way windows handles the gui or something, it's impossible to set the min and max delay by typing in values and i have adjust them with sliders in reaper's generic gui. this is a problem because the delay range is so huge that it doesn't allow for very much accuracy in setting the min and max delay even with a mouse.
augustus loop has 90% of the features i've been looking for in a delay/looper, so i really want to pay up and try using it full time, but these little things and the fact that it seems not really ready for windows are keeping me from doing so.
thanks for listening!
augustus loop requests
-
- KVRian
- 886 posts since 2 Jun, 2005 from Hawaii
-
- KVRian
- 1417 posts since 22 Mar, 2002 from UK
Hi,
if you take a look at page 27 of the manual, you'll see that everything works pretty much as you want - but only for the Audio Unit version. There's a MIDI CC that controls the delay slider (between the set min & max values), and some parameters use NRPNs for extra resolution.
To be honest I can't remember why I didn't do the same for the VST versions (Windows and Mac). I'll have to look into it.
As regards not being able to type in values - this is a recognised bug with certain Windows hosts. Ableton recently acknowledged and addressed it (it affected some Native Instruments plug-ins too), so you just need to nag the maker of your app of choice to do the same.
if you take a look at page 27 of the manual, you'll see that everything works pretty much as you want - but only for the Audio Unit version. There's a MIDI CC that controls the delay slider (between the set min & max values), and some parameters use NRPNs for extra resolution.
To be honest I can't remember why I didn't do the same for the VST versions (Windows and Mac). I'll have to look into it.
As regards not being able to type in values - this is a recognised bug with certain Windows hosts. Ableton recently acknowledged and addressed it (it affected some Native Instruments plug-ins too), so you just need to nag the maker of your app of choice to do the same.