I am having much fun capturing my gear and so on and so far I am pretty excited.
There is one MAJOR problem for me though and I wanted to ask if there is a fix or if anyone experiences this.
I know swithcing delays are a thing when swithcing presets. That is not ideal but ok for me.
BUT I also experience very audible and obvious switching delays in sound when i am in SCENE MODE and as an example have one block with amp, IR etc and 2 different Distortion pedals i wanna switch between. Like Button A for instance is Metal Muff with my Amp and Button B is a HM2 or so with my Amp.
I recorded it, too so itās not my mind playing tricks on me. It;s VERY obvious and when you are switching sounds on the beat itās Off/delayed. Itās super annoying and for me a reason to return the QC because it would make it unusable in a live setting.
The CPU by the way was at 25%
You can listen to it here:
I am super grateful for all sorts of help and insights. Thank you very much!
I believe NDSP recently addressed that small dropout issue- certain amps (not all of them) may cause that. It was either have an audible noise when switching, or that tiny āduckingā audio dip so they opted for the dip. It doesnāt seem to happen with every chain, only certain high-gain/heavy-DSP-using amps (although Iām not positive- it may be more common than most of us who donāt rapidly switch between tones realized)
We talked about it on Discord a few weeks ago (this is from a different user who talked to NDSP Support):
"Neural says the dropout issue is by design and DOES happen on all scene changes. Here is the exact response I got: Thanks for reaching out.
This isnāt a bug. This is how we have handled switching between amp blocks and amp captures via scenes for several CorOS versions. We implemented a split-second crossfade to avoid noises when switching between different amp models. If we didnāt add that crossfade, you would hear a loud noise when switching between the two amps."
Wow, that is pretty disappointing. I donāt know if you have heard my sound sample (link in the original post) but that is VERY extreme I think. And unfortunately that makes the whole QC pretty unusable for me .
To be clear: all the Amps are all my own CAPTURES and so are most of the pedals.
I am a touring musician (worldwide) and I would not care if the unit would be mostly for songwriting/recording. But itās a 100% live thing for me and I was hoping to get rid of my 3 Amps and 3 cabs plus huge pedalboard on stageā¦ Bummer.
Yes, two different Overdrive pedals. And in scene mode I am switching different scenes to switch between the different pedals in front of my amp. The preset is not ready yet. I am still testing how it all works as I am new to all this. And this is unfortunately the first thing that I have noticed.
The preset is not ready yet. I am still testing how it all works as I am new to all this. And this is unfortunately the first thing that I have noticed.
I guess I need to figute out how to upload a presetā¦ Any help is welcome (sorry, guysā¦ Analog guy trying to chance this lifeā¦ jeez)
thank you for sharing your preset, weāll all take a shot at it and see if anything can be tweaked but Iām afraid for your particular case this may not have an acceptable workaround. Weāll try though!
Thank you very much! I am just so confused that such a powerful unit, which endless possibilities eventualy might now work for me because of THAT. One would think that this sould no be an issue with a power tool like that.
I am very surprised that this is not a dealbreaker to so many other users as wellā¦
Building and changing my blocks in scenes to operate like classic effect chains like I used to do on my pedalboards is the main reason for me to use the QC.
Stomp mode is not an option for as tap dancing is something I hacve always tried to avoid. On my pedalboard I have all my pedals in loops taking them in and out of the chain with just one click.
I personally donāt see any significant latency in scene switching. Sometimes the difference between the sound of one amp and another causes something similar to latency (due to the simple fact of completely changing the sound), but the sounds you use are similar.
In any case, in the audio sample I do not see significant latency. Could you put another one?
HI. I will try that right away. But can you be a bit. ore precise? Where exactly do i set the volume? The only thing i can see in the settings/parameters of the pedal is a Volume knob at 0.0 db. If i turn it down to -24 dc there is still the signal of the other pedal pedal that is supposed to be āoffā heard in the effect chain. It ios just lowering the overall volume of the other pedal.
And to clarify: BOTH distortion pedal captures are in the same āblockā. Like as they would be in a analog pedal chain. as well in front of the amp.
OK I see. What do you mean same āblockā? Same path on the grid?
Within the same path I donāt see how to accomplish that, maybe others can chime inā¦
My idea was to put the ODās on different paths, volume block on each path to control that path volume. Iām not with a QC right now, maybe I can try something when I have the chance.
By the way - accessing your preset on Cloud gives me this:
One could also assign the A/B mix of the merge point of the two paths to scenes (scene 1 = 100% path A, scene 2 = 100% path B). That way you wouldnāt need two additional volume blocks.
With the feature requested in the thread I linked above it would be possible without an extra path, please vote for it
Iām experiencing the same in a preset I have just created with the new SLO100 plugin components. When I enable or disable the overdrive in one scene change, I get this switching latency or dropout in the sound.
