codamedia

What have I missed, or what don't I understand? I thought this thread was about a "path" within a preset that stops working, this seems to describe something completely different. Not to mention it makes no sense to read it. Why is there a solution to get D working again when A, B & C are the ones that stopped working in your description?

Interesting.... Every one of my patches includes the LA Comp near the end of the chain and I have NEVER experienced that using 2.71... or any firmware before it. That would lead me to believe it might not be the LA Comp on it's own, but a more specific interaction between the LA Comp and something else in the chain. note: I have not updated to 2.8 so I can't verify this problem even exists on my LT yet.

Troubleshooting 101.... roll it back and see if the problem goes away, then bring it back to 1.8 to see if it returns. I'm not suggesting your problem doesn't exist... I'm just suggesting you run a couple more tests to make sure :)

Do you want L6 to see it or not? They don't take feature requests through the user forums.... they take them through ideascale. It doesn't matter if you agree with that method or not... that's how they do it!

I see more than the amp changing state with that snapshot change. I could be wrong but it looks like you may have a delay (lowest path) and a compressor (highest path) also changing state. Have you eliminated those as the problem in your troubleshooting.... or are you just assuming it's the amp change? IME, it is very important to eliminate ALL possibilities.

Great troubleshooting... I'll be watching this thread for updates as this is how I use the LA Comp, on all of my presets. Hopefully a hot fix will correct this, or I'll be waiting for 2.9 before I can update.

This problem used to exist (same or similar) on the HX Effects... I think with the 2.5 or 2.6 firmware then it was corrected. I have not updated to 2.8 yet on my LT because I am in the middle of a busy gigging schedule and want to avoid stuff like this :) I use all 4 paths in a giant SERIAL chain. Nothing goes parallel on my live patches so even when I get to test this it may not be the same. I do know that if "path b" stopped working on my patches I'd be dead on a gig!

NO! You install the HX Edit 2.8 update which also includes the correct drivers and installer. You run the INSTALLER to update the Helix.... and you must do that WITHOUT HX Edit being open.

Update to 10... there won't be an 11 any time soon. Windows 10 get's semi-annual major updates (March and Sept)... this is done to prevent the need of a completely NEW OS every few years... sort of like Mac did with OSX. Isn't that a little confusing? You don't update with HX Edit... you update with the installer that also got installed with that package! If HX Edit is open while updating, it actually causes problems with the installer. That's the one thing I don't see written out very clear in the instructions. DO NOT OPEN HX EDIT BEFORE OR DURING AN UPDATE USING THE INSTALLER!

There is nothing wrong with that patch - it works fine on my setup (direct)... but it also doesn't seem to separate outputs like you were describing earlier. Are you saying this lacks tone and volume? If so.... maybe it's the monitoring setup from your computer. To be honest, I was hoping you would share a patch that you were trying to separate the outputs for the AMP and Computer separately.... to see if it looked right and routed correctly. This patch seems pretty normal... and sounds OK with my Tele. I'm not saying it's "perfect" for my tastes (tastes are very subjective)... but it is certainly in the ball park... maybe even in the in-field :) It's a warm sound.... Keep in mind that every cabinet you load will load a different mic. All cabs and all mics have distinct characteristics. When in doubt (ie: if you don't know the differences) stick to the default cab with the amps... they are normally a common match. Experiment with the mics and distance! TIP about mics.... Mics all sound different... some bright, some dark, and everything in between :) Compensate those differences with distance Most mics will have less low end the further you move it back (eg: 1" is darker sounding than 6")

Something isn't right.... I suspect something is not setup right in the configuration... OR you adjusted your tones with no cabinet (that would have resulted in removing too much high end) and tried to add the cabinet later in the process. Can you export and share your patch so we can check to see what might be amiss?

Understood... but the HX Effects was released with the firmware version "in line" with it's bigger brothers as was the Stomp and we now learn that "effects / stomp" ran a different core than their older siblings. Since the CORE is now unified between all Hardware, Edit and Native... what's wrong with sharing the same rev number? FYI... I am not in the least bit worried about this, hence the title and my continued notes that it really isn't important :) The math might be really simple... but it's still unnecessary math (IMO) to make sure all my products are up to date.

These are general signal chains... not intended to be a definitive chain as there are always variances. The point is to show the discrepancy between the player and the intended listener. Shouldn't the goal be to get the best possible tone to the intended listener? (I am quite aware that for some, the intended listener is themselves) LIVE TONE Guitar choice Effects Amp Speaker Cabinet (1 speaker, or multiple speaker cabinets) (note: 3 and 4 can also be a combo amp) THIS IS WHAT THE GUITAR PLAYER HEARS 1 mic placed about 1" away from 1 speaker (regardless of how many speakers the cabinet(s) have) capturing about 1 square inch of sound based on the mic position on the cone. Console Input including a low cut filter Console EQ Outboard Effects (reverbs, delays) Depending on the system and sound tech... possible varying degrees of compression PA Speakers / Clusters THIS IS WHAT THE AUDIENCE HEARS NOTE: #5 and #12 are dramatically different. The player hears all speakers he is using plus the cabinet tone.... the audience only hears the MIC which captures a fraction of a single speaker and little to zero cabinet. RECORDING TONE Guitar choice Effects Amp Speaker Cabinet (1 speaker, or multiple speaker cabinets) (note: 3 and 4 can also be a combo amp) Multiple mics placed on the cabinet(s) and in the room to try and capture the full tone of the amp Now for each microphone used.... Console Input including a low cut filter Console EQ Outboard Effects (reverbs, delays) Multiple levels of compression through all stages of the recording stage (not optional like it was in the live setup.. there will be compression used) THIS IS WHAT THE PLAYER MAY HEAR THROUGH HEADPHONES, and the ENGINEER/PRODUCER HEARS THROUGH STUDIO MONITORS (a player can also stand in the control room and hear the studio monitors instead of wearing headphones) Final mixing and mastering as monitored through several sets of studio monitors Additional implementation of gentle EQ, Compression and Processing Dithered to CD/STREAMING Qualiity THIS is what the buyer gets to hear The joy of the Helix is that it can do everything in each chain... it doesn't stop at the amp/cab! Most guitar players struggle with what happens "after" the cabinet (that starts with mic choice/position) because they are not familiar with those stages... even though that is what they hear on recordings and many/most live shows Guitar players get used to a sound (see live setup step 5) and often INSIST that is what a guitar should sound like. There is nothing wrong with that... but they should be considering the next stages as well. Myself... I try to create the best sound for the intended listener and to do that I like to create my tones from the listeners perspective in those above lists. My live tones (that I hear) do not suffer from that approach... if anything they are better and more consistent from room to room, stage to stage. YMMV

Not sure that it's truly worth a submission but I guess it can't hurt :) Done! https://line6.ideascale.com/a/dtd/Please-Unify-the-Revision-Numbers/960096-23508

This really isn't earth shattering, or important. But I was just wondering.... If the 2.8 update is meant to UNIFY everything, why is Helix Native only at 1.8 I do realize that Native came later than the floor/rack/LT.... but it's been around longer than the Stomp (and possibly even the Effects) yet both of those are at 2.8. It can't be because it's software... HX Edit is 2.8 I would think if you were going to unify everything, you would start by giving everything the same revision number so identifying different versions would be extremely obvious.

I'm an LT user.... but I've always found the 6 block limit on the Stomp to be an odd number.. and very limiting. Even though I don't own a Stomp.... I will upvote your idea.

I see... just open springs on the back. Since it's a build.... have you considered a small rout for a 9v?

I love reading a post like this because it means you "get it". You might not know how to accomplish your goal yet, but that will come now that you understand the process. Thank you for keeping an open mind... not everybody does!

I own a 300 and never got along with the neck. I replaced it with a mid 80's maple telecaster neck I found and it made a world of difference. Far less expensive and much easier than a complete transplant :) BTW: Thanks for the update on your status... glad to hear it all worked out fine.

I.T tech here.... changing ports, uninstalling old drivers, different cables, etc... etc... is definitely the most common problems/solutions related to any USB device. It just may not have been YOUR problem.

The warning from the manufacturer is correct and will apply to either product... but it really doesn't effect the HX line at all. Phantom power will not DAMAGE the HX, it just degrades the tone. At worst.... the HX won't sound it's best for the first 5 seconds. That warning applies more to something like an old ribbon mic that would DIE immediately if it saw any power. I'm sure you know this.... but just in case :). The Stomp uses TRS, not XLR so first you will need a TRS > XLR adapter... then attach the phantom power blocker to the XLR end - not directly to the stomp. The mic cable will then connect to the Phantom Blocker.

The short answer is ... no. The Line 6 Variax guitars (at least the 1st gen guitar... not sure about the later ones) could be powered by an XPS Box through a stereo cable so you didn't need to consume batteries. I assume it is something like that you are talking about. You could likely wire your guitar to use something like the XPS, but since you are looking to avoid the extra box we are back to the short answer.... The Helix does not provide 9 volt power through a stereo cable. There is a long answer, but I don't recommend it. The Helix Floor/LT/Rack all provide an VDI port - and that VDI port does supply 9v. in theory, you could likely build a cable that pigtails to utilize the power of the VDI. If successful, your guitar will forever have to be used ONLY with the Helix. If unsuccessful you could damage both the Helix and your pickups - throwing any warranty on either product out the window. IMO - neither of those sound very good to me. This confuses me. You use the trem so you can't use the cavity as a battery holder (I get that part).... but you also say you don't like the "back plate". Are you saying you built a strat with a trem that doesn't use a back plate... or you don't want to use the Fishman's replacement backplate that includes a rechargeable lithium battery pack? If it's the latter, I need to ask why? IMO that is a very practical solution that keeps the guitar self contained.... without the need for a dedicated power source AND a TRS guitar cable.

After loading the preset did you restart the Helix? If not.... the preset will not have been updated from it's original version to the new format.

That is definitely the 300... Even with a 300... 1: You should have gotten an XPS MINI power supply and TRS cable (I think the 600 uses a standard XPS, not the footswitch version) 2: You should have gotten the 6xAA battery cradle 3: I am not 100% sure... but I believe you should get the VDI to USB adapter... otherwise there is no way to edit it without a qualifying POD.

As stated above.... if you are trying to update your Helix to 2.8.... follow the instructions, don't try and go it alone! If you are not trying to update to 2.8 and have other intentions... I suspect you may have downloaded the Windows versions to your Mac.