Hi Os,
I'm working on a new and more simple live setup based on Augustus. The idea is to use 2 instances of Augustus, like 2 unsynced tracks, both independently controlled by a midi controller. I could do that with Mobius and although Mobius works, I prefer delay type of loopers for Ambient because of the filters. I have a few questions:
midi.lua: I have found the midi.lua file in the component package. Can I change the original or should I copy it to a different location?
Multiple instances: I suppose each instance uses the same midi.lua and midi channels? I was wondering how to setup 2 instances but it looks like I have to use OSC for that. I never used OSC so far, and I'm wondering if there aren't workarounds to give each Augustus instance its own midi channel.
Freeze loop issue - For short loops, say a few seconds, it works fine but for longer loops, eg 30 secs, the feedback seems to have influence. What I would expect is that freeze loop acts like 100% feedback, but instead, the loop slowly fades away. Augustus version is 2.1.2 (latest) .
Fade in/out feature request - is it possible to increase the value to 300 seconds? Would love that because that's what I use on stage and it would be great to have this in Augustus too.
Thanks,
Sjaak
Augustus
-
- KVRer
- 5 posts since 28 Jan, 2009
-
- KVRer
- Topic Starter
- 5 posts since 28 Jan, 2009
Os,
The issue with the multiple instances is solved within Mainstage. The solution was to setup two aux channel strips with Augustus and route the different CC's to the different Augustus channels. The sidechain input is used as audio input. In addition to that, I have set the dry level in Augustus to 0% and I use the input level to fade in audio content. Seems to work, will test it out before I go on stage
The issue with the multiple instances is solved within Mainstage. The solution was to setup two aux channel strips with Augustus and route the different CC's to the different Augustus channels. The sidechain input is used as audio input. In addition to that, I have set the dry level in Augustus to 0% and I use the input level to fade in audio content. Seems to work, will test it out before I go on stage
-
- KVRian
- 1417 posts since 22 Mar, 2002 from UK
You can do either. If you use a copy and call it 'midi.lua' it will be used instead of the original. If you call it something else it will be used as well as the original.Sjaak wrote:midi.lua: I have found the midi.lua file in the component package. Can I change the original or should I copy it to a different location?
MIDI routing is controlled by the host (as you found).Sjaak wrote:Multiple instances: I suppose each instance uses the same midi.lua and midi channels? I was wondering how to setup 2 instances but it looks like I have to use OSC for that. I never used OSC so far, and I'm wondering if there aren't workarounds to give each Augustus instance its own midi channel.
Mmmm - it shouldn't. NB check that your 'max delay time' is at least twice your loop length (so 60s for a 30s loop).Sjaak wrote:Freeze loop issue - For short loops, say a few seconds, it works fine but for longer loops, eg 30 secs, the feedback seems to have influence. What I would expect is that freeze loop acts like 100% feedback, but instead, the loop slowly fades away. Augustus version is 2.1.2 (latest) .
Certainly possible - I'll put it on the wish list.Sjaak wrote:Fade in/out feature request - is it possible to increase the value to 300 seconds? Would love that because that's what I use on stage and it would be great to have this in Augustus too.