-
-
Notifications
You must be signed in to change notification settings - Fork 60
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Delay8 / FX routing issue? #13
Comments
Setting to channel outs 1-2 was an issue for me too. May be a bug.
Christopher
christopherwillits.com
drip.kickstarter.com/willits
envelop.us
overlap.org
…On Sat, Dec 3, 2016 at 2:11 PM, cameronangeli ***@***.***> wrote:
When i load the Delay8 FX M4L device, it appears to work for a short
period, but eventually it stops. After a few tests, it appears that the
setting the beat_delay knob too high may be triggering an overload of the
buffer. setting a lower max might help this. It's also worth noting that
not only does the Delay8 not work, but the Verb does not appear to have an
effect. If i delete the Delay8, and use the standalone verb, then it works.
I continued testing: I have only one instrument in the whole session,
playing on 1/2. the Delay8 placed on Channel 1/2. When i changed the output
to 3/4, the effect started working. and same thing for 5/6, 7/8, so on....
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#13>, or mute the
thread
<https://github.com/notifications/unsubscribe-auth/APQIh9ZfjVeOLHID9qEOVWGbQN5-pe1tks5rEekagaJpZM4LDbiq>
.
|
hi! thanks, I'll check it out |
Hmm can't reproduce your issues so far. I opened the example Live session included in the repository and it worked right away with outputs 1/2 and has been running for a while now, all seems fine as far as I can tell. Not sure what the exact cause might be, possibly you are starting opening the Live session before starting the server and client? The order should be: server, client, then the Live session. It's not possible to overload the buffer with the beat_delay, but it's certainly possible to overload the gain depending on how loud and dense your sounds are. The beat_delay just specifies where in the circular buffer to start playing back. I did notice there was a limitation on the beat_delay which has a maximum delay setting which by was set to 5 seconds, which is probably fine for most applications, but it looks like that was getting maxed out with higher beat_delay settings, so I changed the /maxdelay to be 2 minutes : ) Like the source reverb, the delay reverb sends it's signal to the reverb bus, which is controlled by the envelop_fx_bus_reverb device. If you don't have one of those in your Live session, the reverb will be disabled (for both the src device and the delay fx). |
When i load the Delay8 FX M4L device, it appears to work for a short period, but eventually it stops. After a few tests, it appears that the setting the beat_delay knob too high may be triggering an overload of the buffer. setting a lower max might help this. It's also worth noting that not only does the Delay8 not work, but the Verb does not appear to have an effect. If i delete the Delay8, and use the standalone verb, then it works.
I continued testing: I have only one instrument in the whole session, playing on 1/2. the Delay8 placed on Channel 1/2. When i changed the output to 3/4, the effect started working. and same thing for 5/6, 7/8, so on....
The text was updated successfully, but these errors were encountered: