Allow input levels and input impedance to be saved per patch

Currently the input levels and input impedance parameters are global. This makes it difficult to use the same input with different guitars in different patches without having to adjust the input level. It also makes it difficult to set the input impedance in a scene based on impedance sensitive blocks such as fuzz devices.

I often use two guitars on gigs, one with single coil pickups and another with humbuckers. I would like to be able to use them into Input 1 and adjust the input level for each guitar and save it in guitar-specific patches. This is not currently possible because the input level is global and isn’t saved with the patch. There needs to be an option to configure the input level for global or per-patch.

Some devices, often fuzz pedals and some Wah pedals have low impedance inputs. The interaction of these devices with the guitar pickups and guitar volume control is an important part of their effect. I would like to be able to use a footswitch or create a scene so that when for example a fuzz block is on, the input impedance is lowered from say 1M to 200K. This will shift the resonance peak for the guitar pickup and improve the tone of the fuzz. This is not currently possible because the input impedance is global, cannot be changed with a footswitch or scene, and cannot be saved with the patch. There needs to be an option configure the input impedance for global or per-patch.

I made a similar feature request, but I think you worded yours better so I’ll upvote it. Thanks!

1 Like

exactly ! would love to see that as well

This is essential when playing a guitar with pickups with have very different output levels.

Really great would be adapting the AxsFx solution to define different global input configs and use one of these in the patch, so we wont have to do it for again for every patch and one could easily adjust to another guitars output level.

1 Like

Would be a nice update to have the INPUT PROFILE, for every guitar a person has, you could create an INPUT PROFILE to the relative guitar,
so you just swipe down to the I/O page and clicking on the INPUT you have a list of preset/profile you have saved to choose and every preset has his input level.

5 Likes

I use quite a few different guitars with different pickup configurations, and I have to edit the input every time I change guitar to get the input level right between single coils, humbuckers etc. It would be good to have a global ‘input’ preset (maybe with additional EQ) that I could select and would apply to all my presets

I have this exact same problem. I am forever tweaking my input settings, especially for my guitars with active pickups. Input profiles would be an amazing feature.

The Headrush has this feature and you can save diferent presets to load… Save parameters of each guitar/bass you use and you can assign it to the different scenes. Just change you instrument and play it.

Something like that will be great

3 Likes

Request for introduce a dedicate instrument input level per patch to match diferent pickups outtput level.

Very tedious now always to have in mind to change the input level if you change guitar.

1 Like

Is using the gain block (utility) right after the input block an option for you? I think you are going for the perfect signal-to-noise ratio but using the gain block cloud be a workaround for you in case you just want to adjust the input gain.

2 Likes

Noticed a few related feature requests around this topic- merged them all here for more visibility

When live or recording it is really annoying to have to go into the input section and change gain, fantom power, mic, instrument etc, every time I switch between electric guitars, acoustic guitars and mics. Ideally I would love the option to be able to store those input settings in the preset. It avoids the need for me to take photo’s of the input settings of each instrument, mic combo I want to switch to. I am hoping I am not the only one with this need. A ‘do you want to store input settings per pre-set’ functionality shouldn’t be too much of a development challenge right?

I vote for this option as well. Another reason besides the ones already named, is amp change - using QC as effect processor with real amp complicates my life due to the fact that effect loop of each one has different signal. To save the levels within each of the presets would be great and easiest option. :metal::wink::+1:

Definitely a huge oversight and needed.

Another vote for this. I’m having a nightmare switching instruments live due to impedance / gain issues.

2 Likes

Vote for this too! with 3 guitars it’s a nightmare…
My Boss GX-100 (3 times cheaper) is able to save different guitares input level globally but in each preset you can choose the saved ones…

2 Likes

Another vote from my end. I’m using the quad cortex for guitars (acoustic and electric), vocals, and saxophone, they all need different setups…

Another vote for this. I use my Quad Cortex in 3 different bands, with 3 different guitars that have pretty wildly different output levels (low output P90’s in one, super-high output humbuckers in another, active bass in the third).

I have specific presets set up for each band, so being able to link some kind of input profile to presets would be very handy. In the rush to set up for a live set, it’s easy to forget to adjust the input - and if it’s set for my lowest output guitar, but I’m playing the high output one; I’m gonna clip the input.

A possible workaround (at least for the volume) if you are using different presets for different instruments, until this gets addressed by neural, would be to place a gain block at the start of your presets that you set to compensate your different instruments output levels. Another would be to just build your presets while leaving the input at 0 (the amps are all modelled to take the input level as a real amp would when input gain is at 0) all the time and just compensate within the preset by using amp or output volume (long press the output). If you are using the same preset with different guitars that would of course not be a solution.

1 Like