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

boynigel

Members
  • Posts

    420
  • Joined

  • Last visited

  • Days Won

    6

boynigel last won the day on August 6

boynigel had the most liked content!

Profile Information

  • Registered Products
    4

Recent Profile Visitors

3,174 profile views

boynigel's Achievements

Proficient

Proficient (10/14)

  • Dedicated Rare
  • Week One Done
  • One Month Later
  • One Year In
  • Reacting Well Rare

Recent Badges

52

Reputation

  1. I use an H90 w/mine too. just out of curiosity, are you controlling it via midi? asking because i currently have an open support ticket w/L6 regarding some midi communications issues that they've acknowledged as legit and are working to fix. Maybe your H90 is getting a pan command in error? if not, see if the panning issue persists outside of the Stadium on another piece of gear if possible? Or maybe do a factory reset on the Stadium, after a backup of course, and see if the problem persists after doing so?
  2. a key point i left out is that i use the 11.5 khz high cut in my Global as part of a multi-step "formula" to dial out the sizzle. that said, this is something that got carried over to my stadium xl from my OG LT presets...on which i definitely preferred to have said cut applied. when i migrated all my LT stuff to Stadium, i never A/B'd the global EQ (creature of habit). Maybe the new Augora amps that i'm now using w/my presets won't require it though? I'll A/B when i get home tonight.
  3. as far as not using global EQ on the XLR outs, i've always employed Global with a high cut at 11.5 khz (6db/octave), w/everything else on the global left flat. never had any issues or complaints from sound guy. am i missing something or were you just speaking more to not using global EQ with busier, more aggressive cuts/boosts?
  4. Ben from support actually returned my message last night after close to two weeks of radio silence. Apologized and said that their service manager abruptly quit, and they're trying to play catch-up.
  5. If the manual gives a value or suggestion, shoot me- because i can't find any such info in there. I've been running everything at -6.0, that way i have somewhere to go volume-wise, if need be, but i'm wondering if it's recommended to be closer to 0.0 for any reason?
  6. do you recall if it was Ben? he was very responsive initially and then vanished off the face of the planet. he'd be great on CL.
  7. because that's not what i was told in their first response. if waiting for the next update is the reality, fine, tell me that. i'm a big boy, i can handle it. i'm still using it every day with workarounds.
  8. i posted here deliberately because i know there's more visibility, and my question was regarding L6's tech support response time. i've had posts on the Stadium forum go days without an answer, where here i can get many within a couple of hours. way more OG Helix people. for now.
  9. LOL. i left out that they said they'd get back to me. they haven't. 10 days out. legit question. what do i expect? idunno, maybe, "hey, this is taking a bit longer than we anticipated. just wanted to let you know we're still working on it". that's how i treat my customers anyway. i'm not impatient but you sure are when it comes to jumping to conclusions and passing judgement.
  10. i've been having some midi bugs w/my stadium xl, got no answers on this site, so i opened a ticked. reported the problem, they promptly acknowledged that they were able to recreate it on their end too, and were surprised they hadn't seen more widespread reports of what i was experiencing. they said they'd work on it, but after a week with no response i sent a followup just to make sure my ticket didn't fall through the cracks, and now it's been over 10 days. in the past w/my LT, issues were typically solved quickly, so maybe this is to be expected when they're truly stumped with an issue?
  11. that doesn't work for me because all my foot switches are spoken for in terms of assignments...the majority of my foot switches add/subtract gain stages (or other effects) so when i A/B the speakers, speaker A could have more or less drive than preset B, and vice versa, depending on the preset. any other ways? i don't want to get into disabling other assignments for the sake of testing. i suppose in a pinch i could copy the preset and disable the other assignments on that preset for a/b testing.
  12. i've started playing around with adding a 2nd cab to some presets but when i go to A/B, by bypassing the newly added cab, it's bypassing BOTH. is there a workaround to this that would allow me to instantaneously turn just one cab off?
  13. I'm looking to go out to an external amp's effects return for stage volume (w/no cab modeling), and then send the speaker cab signal out to the house, but in this particular preset i don't think i can unless i'm missing something. The first, topmost path is my guitar's magnetic pickup signal, the lowermost path is my piezo signal. in a perfect world i'd be able to insert a split at path A's final output, one w/the speaker block and one without, but can't. can anyone see a workaround to this?
  14. Aah, i did hear something about that. i had another ticket w/line 6 that was about a day from being auto-closed, so i responded to that ticked w/the new problem, explaining why i had to piggyback an unrelated issue. hopefully they'll respond.
×
×
  • Create New...