Can anyone else confirm that the input and output slider in Helix Native are not saved/recalled with presets??
How would compatibility between hardware and software be broken?Yes. And I think it's the only correct behaviour. If they were saved, compatibility of presets between hard- and software would be broken.
They are saved with host projects and presets, though, so nothing is lost.
How would compatibility between hardware and software be broken?
I take your point, but the Helix Native "only" experience is actually pretty degraded because of this. Also, if you think about it... as soon as a user tweaks one of these faders, their expectation has been set. Moving one of those tweaked presets to the hardware, is nearly always going to sound incorrect in terms of gain-staging.When you alter the input trim fader, anything dynamic to follow (compressors, drives, amps - obviously I don't need to tell you) would be affected and perform differently, compared to the fader at 0dB. Now, as the hardware doesn't have that input fader, those dynamic changes would be lost in case you've dragged the patch into one of the HX units.
I love your amps!!!The Budda is going to be used by guitar 2 with an HXFX.
but the Helix Native "only" experience is actually pretty degraded because of this.
Moving one of those tweaked presets to the hardware, is nearly always going to sound incorrect in terms of gain-staging.
It is not really feasible to expect people to constantly have to remember what they've set the I/O sliders to, each time they load a project.
HX Native doesn't lack an input trim, what are you talking about? The input slider IS your input trim. The output slider IS your output trim.Because of the lack of an input trim? Seriously?
Please see the very first post, where @James Freeman has tweaked his HX Native internal input trim.Not in case you've adjusted a basic channel strip once, following the recommendations in this thread. My patches now transfer wonderfully well either way.
I'm not using DAW channel strip presets, and I don't want to. I'm just using one instance of HX Native. I expect my trim settings to be carried over from project to project; which to me is the only sensible expectation here.You don't have to do that. As said, the slider settings are saved just fine within your DAW projects, channel strip presets and what not. They're just not saved with internal HXN presets as there's no equivalent for them inside the hardware. That's all.
Thanks!I love your amps!!!
What Helix amp model would you suggest as close as possible to the Budda Superdrive 18?
Is it maybe in the Vox/Matchstick camp?
I remember I tried that Budda amp once many many years ago: I loved it, but at that time I didn't understand, yet, the real importance of a good amp. It was the rack guitar rigs era!
HX Native doesn't lack an input trim, what are you talking about?
or else, I need to go into each instance in each project, and write down the trim, and transfer that to a new project.
I'm not using DAW channel strip presets, and I don't want to.
The Helix hardware could easily ignore these two parameters, and the experience for an end user would be no different.
Scenario 1 (not saving the parameters in the HX preset) - I do some preset design in HX Native - I set the trim. I like the sound. I move the preset to the hardware. It doesn't sound right, because of the input trim difference.
Scenario 2 (Saving the parameters in the HX preset) - I do some preset design in HX Native - I set the trim. I like the sound. I move the preset to the hardware. Hardware doesn't support those trim parameters, so it ignores them. It doesn't sound right, because of the input trim difference.
Not suggesting our decision is infallible, but the primary reason Helix Native has an input slider is because so few people have the right kind of instrument input on their interface. And if they do, they don't set it up correctly. If someone owns both Native and Helix/HX hardware, in a perfect world, they'd set the input level to match so they sound the same.Being able to use a preset in HX Native across different DAW's and new projects is my concern.
Not suggesting our decision is infallible, but the primary reason Helix Native has an input slider is because so few people have the right kind of instrument input on their interface.
Yeah I get you. I may do that with these presets (volume block to do my attenuation) because I want these specific patches I've made to always sound the same with the right-guitars; hardware kinda be damned.Not suggesting our decision is infallible, but the primary reason Helix Native has an input slider is because so few people have the right kind of instrument input on their interface. And if they do, they don't set it up correctly. If someone owns both Native and Helix/HX hardware, in a perfect world, they'd set the input level to match so they sound the same.
So it's not an input gain as much as it is a compensating trim.
I can totally see a Global Setting in Native where one can set the default input trim so that any future instances would also be optimized.
In a pinch, one could add a Volume/Pan > Gain block at the beginning if they needed per-preset input gain.
Sascha is expecting me to use another plugin or my DAW's channel strip preset functionality for that, and I just don't wanna because it breaks the entire flow state having to mess around with extra functionality in the DAW.
Nope. But hey... you're always right about everything, and everyone has to work the way you work, or else they're an idiot. I get it. More power to you. Keep rockin' in the free world, etc etc etc, yadda yadda yadda, blah.Just that it doesn't because you do it once and forget about it afterwards.