Please ensure Javascript is enabled for purposes of website accessibility Jump to content

litesnsirens

Members
  • Posts

    375
  • Joined

  • Last visited

  • Days Won

    3

Everything posted by litesnsirens

  1. I'm attaching my patch for "where the streets have no name". The snapshots are all synth chords for the intro (I'm tuned down a half step) The offending snapshot is snapshot 8 "no chords" which I hit just before the vocals come in. As soon as I hit it, it changes the song on my iPad which changes the song on my Helix, so now I have the wrong lyrics and the wrong guitar tone. I can't see anywhere that this is embedded into the preset or the patch in general for that matter. Unless snapshot 8 is somehow triggering foot switch 2 from stomp mode. STREETS NO NAME.hlx
  2. It's sending a midi message to my bandhelper to choose the previous song. Which in turn sends a midi message to helix to pull up a different preset. In the midi messages that I have programmed intentionally, bandhelper responds to midi notes for the commands. I have set it up to use midi notes 48 through to 53 to control the six functions within bandhelper. The midi note number that I have assigned to the offending footswitch in stomp mode is note 53 (F3) but bandhelper seems to be responding to note 48(C3) which I have assigned to a different footswitch in stomp mode. Other than this anomaly... The footswitches are performing all the programmed functions. It's just this added one I can't get rid of... I'm at work now but I'll attach the preset when I get home.
  3. I have several footswitches on my helix dedicated to control various functions in bandhelper which is an app on my iPad. This is done via midi over usb. I don't often use snapshots but there are a few tunes. On one particular patch the I do use snapshots there is one snapshot (8) that seems to be sending a midi message to my ipad. But it's not the same midi message that is assigned to that footswitch when I leave snapshot mode and I have no midi messages assigned to any of the instant commands. I can't figure out where I would even look to try to edit that to see if I can find a hidden midi message in there. Anyone have any ideas?
  4. Now you see... I’ve been tinkering with the idea that if the 10.2s can cut it without the subs I might be better with a pair of 8.2 vs the 12.2 as my second pair. i guess i’ll see in a few days.
  5. For live use I run direct and use in ear monitors so I don’t have any backline or wedges on stage but I still wanted something quick to be able to plug into if I didn’t need or want to set up the whole PA in the rehearsal space between gigs. I originally bought a powercab for this purpose but I found that it didn’t translate the presets I had created on FRFR speakers even when it was on the FRFR setting. So I got rid of it and bought a pair of QSC K12.2 speakers. They sounded great in fact they were great for putting the whole band through at rehearsal even without subs. In monitor position on the floor direct in from Helix it sounded better than the powercab for my use but not quite the magic I was looking for. They sounded much better at rehearsal than my Bose F1 PA setup so I decided to switch over. Sold the Bose bought the QSC subs for live but thought the QSC K10.2 might be better with the subs for live, less boomy and wider dispersion. So I bought a pair of those. I haven’t tried them live yet with the subs but they sound way better than the K12.2 with the Helix direct. This is what I was looking for in a full range speaker for my Helix. All my presets just sound great through this box. Which means I no longer have to set up the whole PA to craft presets I can trust that they will translate to the full PA. So far I will keep the 12.2 for any live venue that I wouldn’t take the subs to, and for rehearsal. But I think I’ll try the 10s at rehearsal to see how they cut it. Who doesn’t want smaller and lighter wherever you can get it.
  6. Do you have the LA Studio compressor after the amp and cab blocks on any of the patches that are randomly quieter. If so, you will have to turn off the compressor until Line 6 fixes the issue with that compressor. You may have to add a gain block to match any volume difference the compressor was making.
  7. There's a bit of a gap between your intention and your execution. There's no question that it was deliberately misquoted but that's pretty much how you left it and I'm not just not sure how to interpret that as honest. Agreeing with your delibertate mis-quote does nothing to right the ship. Although the original is there to read IMO any time you strawman someone it's a dishonest approach unless it's an honest mistake.
  8. Exactly what I was thinking, talk about a dishonest approach. If you're going to quote someone and leave out parts of it to change the meaning, you're basically on the same level as a trash magazine.
  9. Also this one was particularly crucial that you get the detailed instructions right since they were updating the whole platform. Let’s see if future upstates are this difficult although they may be or at least there may be two sets of instructions depending on whether you’re updating from 2.7 to 2.9 or 2.8 to 2.9 (or whatever the update happens to be named)
  10. I don’t think it’s something that is unique to hi-gain. It’s probably more noticeable the more you saturate the tone. When you are setting the EQ on your amp model to get your patch to sit nice at rhythm volume and then pump it up to lead volume it’s going to change. All the frequencies that are making your rhythm cut through get exaggerated when you crank it for the solo. I play mostly classic rock and whether I’m using a classic rock crunch or something a little more overdriven, if I’m using the bridge pickup i pretty much always have the tone control on my overdrive set somewhere between 0-3 for lead tones. And I use an over drive even if i’m not adding much in in the way of gain just for that reason although I suppose you could use an eq block. I just find it simpler to just turn one control down.
  11. None of the methods I've tried have worked so...I guess I'll add it to ideascale .... It just takes so long to get where you want to get to...
  12. Just a quick question. I can save a preset and whatever block I have highlighted when I save the preset is the block that's highlighted when I recall that preset. Is it possible to do the same thing with the hands free edit? So for instance, if I wanted to enter hands free edit mode and as soon as it opens, I'm on a parameter that will allow me to adjust the volume of the patch. Such as the channel volume of an amp model or the gain setting on the output block.
  13. 1 Footswitch looper bug: If I set up the 1 swtich looper, I can punch in fine and then punch out. I think the problem is with the double tap to stop the loop. It seems to have trouble reading that and just goes into record for an overdub. then if you do get it stopped after a few attempts. If you long press to erase the loop the led stays lit. So in general there are some things going on in there. This acutally got me thinking. It would be nice if Line 6 could offer long press and double tap as an option for programming footswitches. Especially for command centre which I use to control my voice live rack for vocal harmonies etc. It would be really nice to have the harmonies set to momentary... but double tap would turn them on and off all on the same footswitch.
  14. Hmmm, I didn't notice you were using the stomp. It's a newer product and may have been closer to the the new core based code that they moved the helix floor to. Which means the issue may have been in the 2.71 firmware of the stomp but not in the 2.71 version of the helix floor. Once the floor got moved to come in line with the stomp, the issue was became evident in the floor as well. Just conjecture, as I don't really understand what changes have gone on under the hood, but my understanding is that it's something along those lines.
  15. I have no doubt that you were having issues... I'm not challenging that at all. I'm saying that I've tested this and that although you were having issues with the same comp, it might not necessarily be the same issue that some of us are experiencing with the comp and 2.8. There is something going on in 2.8 that's definitely doesn't like this compressor.
  16. No it's definitely 2.8 related and it's definitely the LA studio comp. If I roll back to 2.71 no issue... Back to 2.8 the issue is there again..
  17. For now I'm just going to disable or take the La studio comp out of the mix so I can stay on 2.8. once the issue is resolved I can add them back in.
  18. 5th block from the left top level of path B, just before the first delay block. What’s that?
  19. Is that Dynamic block in path B the LA comp? If so see this thread I just started, or just turn it off and see what happens.
  20. It appears that there is an issue with the LA Comp. You likely won’t notice it if you use it before the amp block as it doesn’t do much to the over all volume in that position. However if you put it after the amp block it will affect the volume of the patch and as a result depending on how it’s feeling when you load the preset you may get full volume and you might get less than full volume (as I said it’s random). I started using the compressor at the end of the chain after watching and following along building a patch from a Jason Sadites youtube video. And it 2.71 it worked great. In 2.8 LA comp seems to have an issue loading. If I take it out of the signal path the preset will consistently load at the same volume if I put it back in and keep re-loading the patch after less than 10 re-loads (most often less than 5) the patch will load at a lower or higher volume. I also tested with leaving it in the signal path and just disabling it which has the same effect (as expected). When Line 6 answers my support ticket, I’ll just point them to this thread as I know there are others who have put in a support ticket for this issue.
  21. I rolled back it was easy. Just make sure that you close down HX edit then when you open up the updater it will show you a list of firmware options. I actually re-installed 2.8 a second time to see if maybe on this install it would fix the issues but it didn't work. I have a about a week and a half until my next gig so I'll see if there is a solution before rolling back to 2.71 again.
  22. Cool ... I will wait to hear from them... hopefully they will figure it out from your back up and be able to fix it. I’m dreading the idea but I may have to roll back. I have a bit of a break as I don’t have another gig until August 2, so if there is a solution before then I won’t need to. Back to the actual issue I have noticed that it doesn’t seem to happen to any of my patches that don’t have an amp/cab block ie: my acoustic patches. They are just an IR with some EQ and mild effects. Also, although I don’t know actually how loud the factory presets are supposed to be, it doesn’t seem to happen with those. I’ve kind of gotten used to hearing it happen when I swtich patches. When I’m hooked up to HX edit, if a patch loads quiet I can just hit the enter/return key on my computer to re-load the patch and eventually it will load at proper level. Although there are times I have to go to a different patch and back to get it to work.
  23. I've noticed the same thing. It's really apparent when using the 1 step looper. In fact, now when you clear the loop by doing a long press after stopping the loop. The ring stays lit. Last night after clesring then doing new loops a few times I heard a pop and then no sound from helix at all. After restarting the helix the sound came back. Phew!
  24. He's monitoring through a powercab which takes care of the cab emulation but also has a setting to turn off the tweeter and just use it as a 1x12.
×
×
  • Create New...