-
Notifications
You must be signed in to change notification settings - Fork 404
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
AMP EG - too fast??? #7018
Labels
Comments
Isn’t your delay inline in rack with 100 pct mix and is a send position in the vst? |
I made the Delay Mix in rack 100% the same as the vst. Am I misunderstanding something? |
OK I took the Delay out of both vst and rack and now they are comparable. What did I do wrong? |
So, no bug then it seems! Will close the ticket. 🙂 |
This was referenced Mar 5, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi, having questions about the Amp EG in the standalone version
Version: Surge XT 1.2.git-no-branch.git-no-commit
Build: 2023-04-12 @ 00:00:00 on 'hci-snode2-m0/local' with 'GNU-13.0.1' using JUCE 6.1.6
System: Linux 64-bit Standalone on Intel(R) Core(TM) i7-8700 CPU @ 3.20GHz
Sample Rate: 44.1 kHz / Process block size: 32 samples
I am trying to reverse engineer the Factory Pad "Canadians" into the VCV Rack version. After not getting the same 'noise' between the two synths I noticed that the standalone version does something 'weird'. The AMP EG has an attack value of ~1.5secs. But as soon as I press a note on the keyboard the volume is nearly max immediately.
x-2023-05-08_10.13.04.mp4
Whereas in my Rack equivalent I get an attack time I expect -
x-2023-05-08_10.24.15.mp4
Either the attack on the standalone's AMP EG is wrong OR I am misunderstanding the signal path in Surge and my VCV patch is wrong. I have read the manual's technical stuff (honestly!) but I am curious as to why the standalone attck is so fast.
The text was updated successfully, but these errors were encountered: