waymda

Name your presets with a prefix that manages the sort and actively manage that naming - eg 001 Preset 1, 002 Preset 2, etc Sorry, but thats the only way I know of if ordering is important to you. I used to do that, but moved to approaches that used lookups to manage the relationship between songs and presets (ie name independent).

I would physically inspect the 'problem' JTVs VDI output jack for any obvious physical issues, and clean it with isopropyl alcohol to ensure it doesn't have some sort of gunktm build up. I would also try another cable to be sure its not that cable's connection with that guitar causing the issue as the other guitar may have damaged the cable in a way they work fine together, just not with new freinds. I would also make sure I have a high quality VDI cable not the thing they come with thats like a network cable as they're pretty average. I've had one line 6 branded VDI cable go bad over many years, and it was giving flakey connections before it fully died. Also, whilst you're not getting sound, does the Helix power the problem JTV via the VDI cable (ensuring there is no battery in the JTV)? If not on plugin, does it power it after changing the Helix Patch or pressing the JTV model button? All things to try to isolate the issue.

When I first started using in ears I was using a system called Posse. Not sure if you can get them still, but it allowed me to mix the Helix, a vocal monitor send from desk, and built in stereo romm condensors. It was cheap portable, easy to set up, and sounded great. Not as great as a proper monitor mix, but pretty damned good. If you're in Australia I can sell you a second hand unit as I had enough for my whole band at one point. https://www.zzounds.com/item--POEPOSSE This isn't exactly the same, but will work. This

This is a complete guess, but... the product description say it is 1) loading the guitar pickups properly with the same loading as your guitar would see if plugged into a tube amp and 2) converting the signal to low impedance, driving the line so it is the least susceptible to environmental factors that might alter the tone Have you played with the input impedance setting of the Stomp, and does it make a difference? The Stomp Manual says the below - does that mean there's some form of double impedence loading going on, and your mention of microphonic feedback suggests too much high end being passed. 2 1 In-Z HX Stomp has an impedance circuit on its Main L/R inputs that affects tone and feel by loading your guitar’s pickups as they would by an effect pedal or amplifier. A lower value will typically result in some high fre- quency attenuation, lower gain, and an overall “softer” feel. A higher value provides full frequency response, higher gain, and an overall “tighter” feel. The “Auto” option allows the impedance to reflect the impedance of the first block in the signal path—also see the Auto Impedance option in “Global Settings > Preferences” As in the first line this is just guessing as I am no electrical engineer.

Its someone's truth. Only you will know what works for you as this is entirely subjective, and it sounds like you're looking for affirmation on your need to satisfy GAS. May your pedal choices be sound ones!

I reckon I know less than both of you put together about the genre, but the freebie's of these have to be worth a shot. https://line6.com/customtone/search/?submitted=1&family=&sort=rating&sort_dir=desc&search_term=black+metal+helix If they don't use lots of blocks/DSP the Helix ones might work in the stomp - you can check them here https://dbagchee.github.io/helix-preset-viewer/ or in Helix Native, which you can use to edit them to fit the stomp.

Thanks everybody. TheYoulean Loudness meter plugin would only work with Helix native, right? No - the assumption is you are routing hardware outputs to a DAW or stand alone version of YouLean. If you have a Helix you can do this direct via USB or through a audio interface. Whilst you can use Native and share presets between Native and hardware there are lopts of gotcha's with input levels, impedance, etc Still a little confused about power amps. So, back in the day, the old Fenders and Marshalls had no gain knob or master volume. That would imply that the power section was always maxed, right? Yes Most Helix models have a drive knob, a channel volume knob and a master knob, although a couple don't have a master volume. So does the master volume of the amp model have any effect on the tone? Yes - it simulates the impact on power sections as opposed to pre-amps. Some amps are great flat out, some distinctly not (IMHO). Or are you saying that the channel volume affects the tone but not the master volume of the model? No - the Channel volume only changes the output levels. You will perceive tones differently as they are louder/softer but that's a percepton issue and won't translate across playback devices. I have an Egnater MTS amp that uses the synergy tube preamps. I am trying to compare the helix to that and maybe that is unfair. Each preamp has a drive and a Master and then the amp itself has a master volume. Would that be similar to the Helix models? It is weird that there is a channel volume and then a master and then the Helix itself has a master and then the power amp also has a volume. I am just struggling to get my head around all of these volumes so please be patient with my questions.... Each Helix amp has a models a single pre-amp (unless jumped versions) and poweramp combination. The drive affects the pre-amp, the master the output section and the channel parameter the overall volume. Think of channel as the leveling tool you wished you always had on and amp. In the context of useing external power amps with the Helix, the external power amp should be as transparent as possible and only add volume (unless you deliberately want a specific colouration of tone) rick

It really depends on the bass combo, how you set it up and how much volume you need. Why not just try it? I'm assuming the send is not powered - that'll blow the amp.

I use a UI24R and linked stereo channels with my Helix. No problems to date, but depending on the age of the UI24R see reports of chanels failing in the Farcebook communities. I find I run very little channel gain as the UI see's the Helix as hot, even with mic output levels. I've also seen reports of maxing out the UI input gain levels causing system reboots - so its a sensitive thing. I'd test using: different linked chanels a fresh/clear scene (have seen references to chanel programming getting messed up over time) the bottom row of inputs vs the top noting the top row has combi inputs the Helix XLRs into a phatom power filter (even if the UI says phantom is off) the Helix 1/4 inch outputs into a DI

This path is likely your problem. I do this as Guitar >> Helix >> Mixer (XLR) Laptop (with audio) >> Mixer (USB) Mixer >> Heaphones Set the mixer as the USB playback device in Windows, and trim inputs from the Laptop and use the faders to set the over relative volume - then use Patch changes to adjust the Helix output levels. I normally do this with both my mixer and Helix connected via USB but the Helix USB only being used for edit. This approach allows both the channel input levels to be monitored and the relativities of patches to pre-rec music - noting that pre-rec audio may vary in loudness as well.

I'm not near my gear atm, and haven't run speaker models for quite a while. However, when I did I ran through the multi output. Worth a try?

Does the label say dryclean only? But, no I don't know for sure and would be concerned about damaging my washing machine with its size and external zips, along with how the internal padding would come out the other side once it got wet.

If I read this correctly, you're expecting the Helix to change to the USB input mode, AND retain the settings for the Multi/Helix input mode for when you switch back. Whilst I understand why you want to do this I can't think of a way the Helix would achieve this, short of retaining parameter settings independent of selected input choice, which would require some sort of input mode related memory provisioning and management. I suspect its dropping all parameters not relevant to the selected mode (ie Variax model settings) as it no longer 'needs' or can use those parameters. I would also expect that the output block behaves the same way with any patch specific settings for PowerCab and DT amps when USB is selected as well as the Multi block output levels. This would explain why the other snapshot parameters remain in place - nothing has changed to wipe them. Think of these blocks as behaving like any other block and the input/output sources as being a new model dropped into the block. To do what you want, Multi input would accept any of the USB inputs (not just 1/2) as well as guitar/variax, and Multi output would allow selection of USB 7/8 within the DAW, but it doesn't look like its engineered that way. This might be worth putting onto IdeaScale, after checking it hasn't been done already.

Well yes and no, as you'll need to consider stage real estate, not getting in peoples way etc. Having undertaken a long journey of using IEMs and other monitoring since using a Pod HD500x, my experience is: all monitoring is a compromise adding ambient stage sound to direct IEM mix is much harder to control/manage than you expect - and can have perverse results (for example being flooded by bass through conduction) that are really hard to track down. Its just not as obvious as you might think when you're sound checking etc I used stereo condensers for a while, and franky they made it more problematic than not having them Good IEMs make all the difference, and the amount of bleed you want/need varies from stage to stage (event) I have good molded 64 ears and the Sensaphonics and each is different (not better just different) and I vary what I use depending on the event controlling my IEM mix has proven more important that adding ambience to get the sweet spot I want/need But finding what works for you is the real challenge.

That sounds like a recipe for a feedback loop. Bass >> HX >> mains to Desk >> Desk FB to HX in >> HX mains..... you can see where that's going. To achieve HX to desk without a loop would require an output pre the return of mix from desk that is routed to your IEMs. I have a Helix but I'm sure there's a way of sorting that routing for the HX at the expense of blocks. TBH - even with the full Helix I run the IEMs from the desk back to a dedicated headphone amp with my guit in the mix. I have a strong preference for separation of hardware functions reducing decencies and complexity, and allowing fallback solutions. But YMMV.

I'm not sure it is. The kicker will be the low range frequencies from the Nord and the bass. Getting them loud and clean takes a lot and most FRFRs and not designed for truly full range. I'd be guessing that's what craps out the QSC10.2. A single 10inch speaker (with horn) can't cover that frequency range AND volume for a sustained period. Guitar targeting FRFRs will likely be worse as they are designed for a narrower band of frequencies. A reasonable compact powered sub with appropriate crossover could give you that range with the addition of one box for keys and/or bass gigs. Alternatively a compact bass combo sitting under the QSC.

Get a set of these and hear the stage sound properly as you move around. https://www.sensaphonics.com/products/3dme-custom-tour-gen2-music-enhancement-iem-system Easily supplements a proper IEM mix (which your suggested solution will not obviate the need for).

Now I'm gonna have to test that. For a while I was having issues with patches before realising I'd dropped mono gain blocks at the end instead of stereo (I run dual amp setups). I don't do it anymore, but now you have me wondering if they were all turned on when they caused the issue.

Following - can you please confirm if you fixed this. I'm still on 3.70, but if what your describing is a bug in 3.71 it would break me (well lots of my patches).

So DC plays back your entitled BS line that demonstrates that you don't read the manual and you want to have a shot. There's no exchange of views to be had on this topic, it's a technical answer to a technical issue on some highly technical hardware. You made your view very clear, it's the manufacturer's problem that you don't understand the product. My view, I wish to exchange, is RTFM so you have at least a minimal understanding of what you're talking about. A quick look at your previous posts suggests doing your own homework is an anathema to you, and you think an end-user forum should be your personalised help desk. Best of luck with that.

An alternate approach to the routing is us a send block before the cab block as a tap for the poweramp/cab. Set it with 100% passthrough so signal still goes the cab block. You could assign a pedal to turn the send off for recording, stopping any signal to the power amp with a single click. It does mean you need to use effects you want in you amp/cab pre-speaker block, but it can also provide a really versatile solution for post-cab-block effects being recorded and not impacting on the amp/cab, which could then be mic'd up and added to the recording/mix. For example room reverb and/or compression. Another suggestion is as you get your routing as you want it, save as a template so you just change component blocks for future patches. Your approach may change over time, but many templates is possible. My standard routing has amps and effects that run before amps on path A, effects that are post amp and/or cabs on path B (A routes to B). This seems to give me the best balance of CPU load across the 2 CPU and allows for complex patches, ymmv.

A thought - if you can establish the optimal input gain for Native you could normalise the recorded dry tracks in the DAW to that level. I'm not Reaper user, but my DAW allows selection of individual tracks and normalisation to predetermined levels.

Maybe - Unity means exactly what you've said no gain added (or removed) the maybe is because different elements of DAWs may add or remove gain at what appears to be a 0 setting. They shouldn't, but....... This might be a useful reference for recording and levels https://mojosarmy.medium.com/recording-and-mixing-levels-demystified-151ec65705fa

Some observations: the I/O with Native vs the Helix as described is fundamentally different so I would expect different sounds the Helix is being fed an unamplified instrument level guitar signal, your DAW is recording a line level signal which is then being 'reamped' this is not the same as recording the dry output from the Helix via USB - those levels are very low and often a cause of consternation for new users hence, the input levels for the hardware and software versions is not the same - at the very least you'd need to match the input levels you mention setting parameters and gain leveling to 0DB, but this has nothing to do with the recorded level - you should be aiming for -13dbu (if not less, many aim for -18dbu@peak) for any digital recording to ensure no digital clipping in the recorded signal - the digital signal can be increased without increasing the noise floor so no need to record hot there are both input and output gain settings on native that are independent of the patches created on the hardware - these will be your friend is there a single simple rule/approach to use across all DAWs and hardware/DA scenarios? No, you're adding complexity/hardware/driver/software layers so the solution will be complex and bespoke.

This is the only way I can think of as changes to the Variax model on either path are applied to both input paths (the Helix is forcing the Variax to apply settings not processing the Variax within the Helix). No idea how precedence is achieved but you can't (for example) have Path A having a variax with every string at full volume and Path B with just the 6th string at full with an octaver applied.