codamedia

That's odd.... I thought this was suppose to be one of the features/fixes with 2.8.... That behavior has been there all along, but 2.8 was suppose to make it truly transparent. From the 2.8 release notes... The Global Settings > Preferences > Tap Tempo Pitch (Authentic, Transparent) setting now also affects tempo changes taking place across snapshot changes, not just when pressing the TAP switch

@datacommando... Great video, thanks for posting that. I didn't realize that they (for the most part) manually create these models.... I though it was more automated than it is. I got into a heck of a debate a while back about volume... I was trying to explain that whenever I feel disconnected with my tone I would turn up my monitor a little louder and that solved my problem. The other party insisted that the modeler doesn't change with volume and was adamant that I had no clue about what I was talking about. Myself? I knew that I simply wasn't conveying what I actually meant but I couldn't figure out how to explain it. Confirmation bias alert! @12:17 of this video that topic comes up and it is described perfectly. Finally... re-enforcement from the model creator himself that I have not lost my mind (yet) and I am not reacting to some placebo effect. With your monitoring turned up to a natural level it directs you to set the amp models more like the real amp... and forces you to play with more dynamics as you naturally would.

Not that this matters, but out of experience.... I used to own an HX Effects (with scribble strips) and now own an LT (performance view) and I don't miss the scribble strips at all. Others may differ in opinion, but I feel scribble strips would be one of the least important reasons to choose a Floor over an LT. One caveat to that statement.... Stomp Mode in performance view is a thing of beauty on most stages, but is difficult to view in the sunlight.

I suspect there are unexpected midi messages being sent by the iPad causing erratic behavior at various times. Connect it all up at home and monitor the communications between "setlistMaker / iPad" and the HD. If you are just changing sounds (I assume you mean presets) the iPad should only be sending PC messages... if you see other types (CC's in particular)... that's the problem.

Thanks for the info.... this is how I would approach it. PATH A: Guitar The normal Guitar output > Input L > Effects in Path A > Send 1 to Amp (Dry out) > wet effects in HX effects > Output L (Wet Out) PATH B: Bass The Guitars bass output > Input R > Effects in Path B for Bass > Output R (to bass amp). Make sure your input split is set so INPUT L & R are routed only to their paths (A & B respectively) Make sure your Output Merge is set so PATH A & B are routed only to their outputs (L&R respectively). There are certainly limits to this type of setup... and some additional steps may need to be done to fully suit your needs.

Any feature requests need to be done at ideascale, they don't accept them here because these are user forms. http://line6.ideascale.com That said, I'm not understanding your setup based on what you are saying.... In what way are you forced to use stereo effects? Wet Dry is certainly possible if you utilize a SEND (dry out) wherever you want in the path. Please clarify the "guitar path" you would like... maybe there are already options to free up path B for the bass only.

Here is what the floor has over the LT.... if you want or need any of these you should get the floor, if you don't think you will ever need these then the LT will get it done. Floor has an AUX Input. Floor as a MIC input (XLR) w/phantom power Floor has 2 additional Loops (sends/returns). The LT has 2, the floor has 4. Floor has spdif in/out Floor has 2 external EXP jacks, LT has 1 Floor has dedicated amp ctrl jack (lt is shared with it's 1 exp jack) Floor has a dedicated headphone volume The floor has the option to re-assign the "bank buttons" to stomps. Floor has scribble strips... the LT gets around that with Performance View on the big screen which the floor does not have. Floor is a stronger build, but that's not to say the LT is cheap or weak... the floor is just really heavy duty. IMO.. if money is not a concern then there is no need not to get the floor. You never know when you might need the extra features. BUT - if you (like me) has to watch the cash flow and can get by without the extras the LT is a great option that doesn't compromise tone in any way. Under the hood they are the same.

Did the videos get swapped out since you posted this? They don't sound bad at all on my setup... the first one is actually quite good. The tone in the intro... and the solo beginning at 2:58 in the first video you posted? I don't use my HD500 anymore since I got a Helix... I can point you in the direction I would go. That's a warm, thick, beefy tone.... immediately reminiscent of early Van Halen. Try some of the Van Halen "Brown Sound" patches that are available... they will get you close to this.

Your setup is already a decent way to do this. Their are two things to watch for.... Make sure you pan the paths LEFT/RIGHT accordingly and use the correct outs for the correct locations Make sure you plug a dummy plug into the unused 1/4" output otherwise both sides will SUM to the one you are using. This does not happen with the XLR outs, just the 1/4" outs. If the amp models are nothing special and you are generating most of your tone from the effects prior.... you can do away with the "pre-amp model" and just plug that side directly into the front of your amp. That will give you full volume/tone control on stage without the need to bend over and edit the HD. This is all dependent on how you are using it.

#2.... If you don't use the effects loops you can use the returns as 2nd and 3rd inputs. You can place the blocks anywhere in the chain you want them... including on a different path. You don't get variable impedance or a noise gate but they do have a variable input level that can be cut or boost. I use my returns in this manner - they work great.

I'm seeing a trend with some of the problems people are reporting. Many of them are problems that have been reported with the HX Stomp and HX Effects in the past which were built on the new core to begin with. With this update, the Floor/Rack/LT users seem to be inheriting their bugs. As I mentioned earlier in this thread - the disappearing path used to occur on the HX Effects. Even if it loaded properly.... as soon as you used the tuner the path would disappear. I'm sure the Stomp also had this problem but with only 6 blocks even fewer people would split paths on it.

Aha moment... It all begins to make sense now! I didn't realize you were using a STOMP. The STOMP and EFFECTS were built on the new core and they just updated the Floor/Rack/LT to use that core with this update. We now have your bugs! Come to think of it... when I had the HX Effects, Path B would sometimes go silent - which is another BUG some users are reporting on the Floor/Rack/LT with this update.

I suspect the other owner broke the USB jack.... slid it back in place and shipped it to you like that. First use is fine... then the jack "appeared" to break when you removed the cable. As for the modeling not working... It sounded like you didn't have a cab. Are you accidentally loading the "pre-amp" versions of the modeling rather than the full versions. Without a cab loaded it will sound like crap direct.

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.