Arturia Forums

Software Instruments => Analog Lab V => Analog Lab V - Technical Issues => Topic started by: khalo on June 21, 2021, 04:26:37 pm

Title: every time Reverb 100%
Post by: khalo on June 21, 2021, 04:26:37 pm

Hej,

why, on every sound where I play the reverb level is on 100%. When I push it back - 1sec - 100%

All latest Version Cubase, MidiControl, FW, Keylab Essential, MacOS

Title: Re: every time Reverb 100%
Post by: LBH on June 21, 2021, 11:37:10 pm

Hi.

When you push what back? A screenshot can help.
What do you mean by "1 sec - 100%"? And by "every time"?
Keep in mind that the presets have the effects that's added in the original applications where they where made.

Title: Re: every time Reverb 100%
Post by: khalo on June 25, 2021, 03:26:44 pm

Hej, it's only in the VST Plugin of AnalogLabV . In the Standalone version is no issues.

Perhaps you can see it on the Video:
https://drive.google.com/file/d/13cw4MNcgStCsnuY72s89LTkVHWBCCPMV/view?usp=sharing

Open AnalogLabV VST Reverb = 100% Move the Rotary on my KeyLab Essential to Zero % automatically the Reverb jumps to 100%

Title: Re: every time Reverb 100%
Post by: LBH on June 25, 2021, 05:08:33 pm

Hi,

This does'nt look like a Analog Lab issue.

Are you sure you have set up your controller correct in your DAW?
And are you using the correct mode on the controller - Analog Lab/ User mode?
Is something else sending data to the parameter?
I think you need to test things like this.

I have no chance to see what's going on. I can't even see which DAW you use.

If it work with the standalone version of Analog Lab, like you say it does, then it does'nt look like there is anything wrong with your Keylab Essentials encoder.

FYI: I don't own a Keylab.

Title: my workaround
Post by: khalo on June 29, 2021, 06:38:47 pm

thanks, I found for me this solution:

I use Cubase on Mac: deactivate the Mackie HUI Midi Output in the setup prefs

thanks again

Title: Re: every time Reverb 100%
Post by: LBH on June 29, 2021, 09:37:38 pm

Hi,

Your welcome.

It's good to know, it was a setup issue. I will not call that solution a workaround, as that setting apparantly is important in Cubase. Good you found out. Thanks for reporting back.