feffa86

That was a mindblowingly good conceptualization!

I got mine from thomann in the UK, but I'm over in Europe. You should find them easily online. Amazon has tons, but maybe someone else over there can make a better suggestion. https://www.amazon.com/s/ref=nb_sb_ss_i_2_15?url=search-alias%3Daps&field-keywords=2u+sliding+rack+shelf&sprefix=sliding+rack+2u%2Caps%2C285&crid=2RBRYJGHJT369&rh=i%3Aaps%2Ck%3A2u+sliding+rack+shelf That picture is kinda old, my rack looks a little different now, but that was a really sturdy shelf. I think I paid like a 150 just for the shelf. It was pretty damn good, but I ended up not liking having the control on a shelf. Better to have it all the way down on a floor. I got a board for it. When it was on the shelf, the movement I had to do with my foot would lollipop with my playing so I couldn't use it while actually playing. It also made it difficult to time start and end points on the looper. Just mentioning it for your consideration. I'm using a more light-weight shelf further up in the rack now for pedals in the FX loop.

https://www.facebook.com/groups/line6helixusergroup/permalink/1117241541792851/ If this is true, wow If you are a non FB user, this is why you have FB

Sounds like we're actually in agreement on most points then, however, if there is no optimization, consider this: "Way too obvious (regarding the meters). Helix Core, however, will improve GUI performance so meters are no longer off the table." It says it right there. GUI performance. Allows new features that weren't previously possible on the GUI (visual representation) level. Here's another non-guess: that also, at the veryleast, opens the door for any other visually oriented feature you can think of. Isn't a performance improvement per definition an optimization? Sure, they could go out of business before we see another patch and the earth could get hit by a meteor, but assuming the status quo they have confirmed meters, more amps, and more future updates. I guess the only reason I'm replying is to point to the fact I didn't actually make any specific guesses that weren't rightfully inferred from the posts they made.

Imagine Beardmatching someone elses beard, saving a profile and then just running that lollipop across your face for a perfect length beard with custom sculpting. And if you get a base hair trimmer without that thing you attatch at the end you can make beard IRs to compensate. "That's the cleanest beard I ever saw. Lowing the bottom end."

It is really not just blind guessing. This is a system-wide optimization pass to prepare for the next big thing. I do not agree that it is blind guessing. Guessing what card out of the 52 you are thinking about would be. Assuming what the exact feature the next patch has will be would also be a blind guess. But assuming that a large operational software restructuring is meant to prepare for a large software feature(s) is a given. Frank from Line 6 also specifically said in the thread that 2.80 was cool, but that 2019 will be big. And that this operational update enables a lot of GUI stuff like meters. He ALSO said that another thing this does is to make it easier to put out future updates)(plural). What do you make of those statements? Another stomp and a new flanger? We're getting something more than a few amp models. I don't merely just think that any more than I just think that my science book was right that the sun is in fact a star. I haven't actually been to the sun either. Maybe it's all voodoo.

Hot diggity, this is so fricking exciting. This is huge news. Read between the lines. They are basically updating the whole engine, allowing for more GUI options. They said meters can come. Well, so can probably stuff like visual EQ curves and other cool stuff. I mean, they mentioned meters specifically, but what this implies is that they can add more moving stuff to the screen. More interactive visual features. And that's only the GUI side. This is really huge imo. Way excited.

Yes, there are many ways you can route this to achieve your goal. I would use path 1a as a stereo path and split it to two outputs at the very end, to go to each amp's input. Then from fx send of each amp into paths 2a and 2b, treat those as mono paths, but join them into one path at the end, with a single stereo output. If you place stereo effects before the split on path 1, or after the merge on path 2, you will retain the true stereo effect. If you want the same effect in both amps, place it on path 1 before the split,or on path 2 after the merge. If you want separate effects to each amp, place them on path 2a or 2b before the merge. Pie.

Preset wont help if its something with the unit. Can you make a clip of what it sounds like? I'm intrigued.

Add option to apply global EQ to digital output (say, if you are using Powercabs and L6 link) https://line6.ideascale.com/a/dtd/Global-EQ-also-applying-to-digital-output/945225-23508?submitted=1#idea-tab-comments

I have found a bug. I am running version 2.70 of the firmware. I have two Strymon pedals connected via MIDI. When I set up two footswitches to use as bypass buttons for the Strymon pedals, the commands get sent out whenever I change snapshots. I am not setting them up as instant commands, I am setting them up as footswitch commands, yet somehow the MIDI command gets sent to the Strymon pedals when I change snapshots.

"Pages" feature for Helix footswitches A feature that would let you set up different pages with different sets of footswitches within a preset, and use one footswitch to scroll between them. https://line6.ideascale.com/a/dtd/Pages-feature-for-Helix-footswitches/943245-23508 Edit: alright, after I made the suggestion and thought of the tags to put on it, I browsed those tags, and now realize someone suggested this two years ago: https://line6.ideascale.com/a/dtd/Stomp-Mode-Additional-Pages-Sub-Menus/833042-23508 https://line6.ideascale.com/a/dtd/MODE-Button-Switches-to-10-Additional-Stomp-Mode-Switches/874709-23508 https://line6.ideascale.com/a/dtd/add-more-banks-of-footswitches-in-stompbox-mode/900936-23508 https://line6.ideascale.com/a/dtd/More-than-10-block-bypass-footswitch-assignments/859185-23508 https://line6.ideascale.com/a/dtd/Expandable-of-foot-switches-virtual-or-physical/931308-23508

I have been having this exact same problem, and stumbled across something that seems like a little breakthrough to me (unless this is already being worked on). I have a Timeline and a Bigsky daisy chained in one FX loop. They are set to MIDI channels 4 and 5 respectively. In the preset I am setting up, I made two bypass toggle buttons on two footswitches using CC#102, dim value 0 and lit value 127. If I try to change snapshots, I get the aforementioned erratic behavior where on some snapshots, both are bypassed, on some only one is bypassed (but never the same one) and on some they are both engaged. I have tried to change snapshots both using the footswitches and using the dropdown menu inside HX Edit and it didn't matter. So in an attempt to solve this, I did what people have already been trying, and sent out instant PC commands with every snapshot. I set the values properly for every snapshot, and then tried changing snapshots. The instant commands seem to work as they should, changing to the presets I have specified on the Strymon pedals, it would just be really unrealiable as to whether they were engaged or disengaged. But, and here's the breakthrough. I then tried to change the MIDI channel on the two bypass footswitches I had set up, and once I did, everything worked fine. Every snapshot loads up with the Strymon presets I specified in the instant command engaged, and I can use another CC instant command to disengage them on snapshots I want them to be disengaged. This was weird, so I dropped the idea of a bypass toggle switch, and set it up so the Strymon presets were loaded in engaged mode, then tried to set up two footswitches to disengage them. I set up one footswitch for each pedal with CC#102 and a value of 0, which should disengage the pedal. I then tried to swap snapshots and the weird behavior was back. So the conclusion to me seems to be that when you set up a footswitch to send any MIDI command, the Helix somehow sends that command, or some times sends that command, or some of those commands as if they were an instant command. And it does this in an erratic and consistently inconsistent way. That doesn't seem to be the intended behavior. Could this be a bug with the Strymon pedals?

I start up Reason, load up a new audio track, then add Helix Native as an effect. It loads some preset by default, with a few EQ and dynamics blocks or something, because the sound of my guitar changes when I add Helix Native as an effect. When I click to open the Helix Native UI, the VST crashes however. So it definitely goes up and running, but doesn't let me open the UI. I am using a Scarlett Focusrite 18i8 1st gen and it is set to be my audio device when I try this. I have tried going into Windows settings and changing to the onboard soundcard, as well as the Helix ASIO driver, and it happens regardless. Reason is up to date, the driver to my Scarlett is up to date, my Helix Edit and Update and drivers are up to date, and my Helix Native is up to date. (2.70/1.70) So to stress that, I am able to load the VST plugin, and it loads fine, and it does affect the signal (meaning the VST runs initially after I load it). But If I try to actually open the Helix Native UI to add more blocks or whatever, it crashes and tells me to restart Reason. Clues??

Away from home for a week so can't check this, but didn't they add an option to disable mic emulation on the XLR out in the global settings? Making it basically an XLR through? If not, that lollipop is going up on ideascale yesterday! edit: lmao awesome curse filter :D

Submitted a suggestion for S/PDIF send, return and loop blocks. For connecting other modelers like Kemper without extra A/D D/A conversion, and more ease of DSP management when running stereo effects after. https://line6.ideascale.com/a/idea/940230

Let it be said that this is not an important issue to me. It's, however, significantly a "small" issue that it's likely to never be adressed. I get that. That's particularly why I'm making a thread about it. It's so random that I even noticed. If it's what you say about the calculations of the slope, it still doesn't make any sense. Listen: 1) parametric equalizer with five controllers (3 Qs and two slopes for high/low) 2 ) high cut equalizer with two controlles (0 Qs, two slopes for high/low) They must both have a curve calculation for the high and low cut, right? They are both digital and must both be coded. Even still, the one with only two calculations uses more computing power than the one with five calculations. Even though the two calculations must be the same or very similar in both effects, and the other has three extra calculations on top of that. Listen, it's not important to me to have this "fixed" or anything, but it is weird unless I am missing something obvious. At this point, all ll I want is for someone else to see it and agree that it's weird, lol. It's not important. But it also makes no sense unless it's the fact that it's a more "precise" slope than the equalizer has. That then opens a new set of questions, like what the actual difference is. If one leaves in more "upper lows" than the other, that's the one I'd prefer.

Oh, I actually mean it's the other way around to how you put it. The simple EQ, which has many features, uses less DSP than the simpler high/low cut, which has fewer features. I take that as meaning, the way that the high/low cut block does the high/low cut is somehow a larger operation for the processor. I then take that as meaning "more calculations involved", which leads me to "closer to real life results" Like how a 320kbps MP3 has more information about the sound it contains than a 192kbps MP3. Inaudible, possibly, but "more advanced" at the core of it nonetheless. Another possible scenario would be "bad coding", so I guess that's why I'm getting hung up on it. If it's the latter, it's something to look into, or if it's supposed to be this way, I'm still curious :P I do have some DSP power left in my patches, but on path 1 which sums to mono when it exits into the Kemper and back to path 2. That makes path 1 "unusable" for stereo effects if I want them to actually be in stereo. So I have a lot of mono effects and probably lots of free DSP on path 1, then usually have to make choices on path 2. Again, to keep it stereo, every EQ, compressor, etc. that I put after the Kemper (which I have to, because that's what colors the sound) have to be in stereo. I seem to max out with only around 4-5 effects. Reverb, delay, looper, Double Take and a chorus are usually standard for all my patches. That leaves me one more effect. I mean this is all for living room jamming so none of this really matters anyway, lol, but there seems to be something weird going on with the high/low cut block and I would love to understand what's up and/or find more effective ways to build patches :D

I stumbled over something I thought was weird. I am running my Helix with a Kemper. I use Path 1 as "before amp" with mono effects and path 2 as "after amp" with stereo effects. I've been messing around with a w/d/w setup just for fun, and so I ended up hitting the DSP roof on path 2 a lot. One thing I stumbled over was that I am running a parametric EQ right after the Kemper. For high and low cuts if nothing else. I tried replacing it with the simple "High/Low Cut" effect, and it turns out I couldn't. The simple high/low cut block uses more DSP power than the parametric equalizer block, even though the latter includes a high and low cut as well as many other features. That seemed to make little sense to me, and led me to two questions: 1) has anyone done any research and writeups about how much DSP power the different blocks use, or which ones use the most or least, or does anyone have any tricks or weird things they stumbled across regarding DSP power, like the high/low cut vs. parametric equalizer thing? 2) would it somehow be "better", "more accurate" or in any way preferable to use the high/low cut block over the high and low cut in the parametric eq block? If you can bare with me, lol

Following this as I plan to set it up too.

I know some bass amps/cabs have 15" speakers. How common are 12" speakers in bass cabinets? If the answer is "very", then the answer to the thread should be "yes". The Powercab emulates a 112 cab. The coloration of the sound is done by the amp, which in this case would be handled by the modeler. Using an amp model through a 112 emulated cabinet should be the same for bass as for guitar. The size of the speaker will however constrain how good it may ever sound in any case. It won't sound like a 15". I also doubt that many bass cabs have tweeters. Maybe the LF Raw mode would be good for bass. And I don't know which type of speaker element is common for bass cabs, but whichever speaker mode corresponds with that should be worth trying? I have a bass, but no bass experience, so I could hook it up and tell you it sounds awesome, but I wouldn't know what to listen for lol. I can hook it up and play some bass notes and then record it with an SM57 if that helps you get an idea of how it sounds lol. A mic recording a speaker emulating a mic in front of a speaker playing a Kemper profile made with a mic in front of a speaker. Where's Xzibit when you need him?

Bump... :D No but seriously, I only got a Helix a couple of months ago and haven't had one for very long, is there some kind of pattern to the frequency of their release? Or, if not, what's the longest and shortest time between two major patch releases, does anyone know? Rough estimates are welcome.

The setup is pretty new, I am waiting on two pedals from Mission Engineering. I got the one with the toe switch for the Helix, and the one with the toe switch for the kemper. And yeah, I leave a Boss AD10, some cables, capos, slides, picks, and plan to store the pedals in the drawer there. I have the rack in my living room so it's for convenience and keeping it out of the way when I'm not playing. I have a controller for the Helix and have the Kemper on the Helix' Send 3 / Return 3 & 4. I only bring this up to say I think I will leave the Helix pedal with its cables in the drawer, but the Kemper pedal has to be connected to the back of the Kemper, so I will likely find a neat way to have the two cables needed for it hanging on the side of the rack in a curl so I can easily connect it fast. Let me also say I just got a Line 6 G10 Relay today so I am now wireless and it was a mindblowingly awesome experience :D https://imgur.com/a/ZqUE2 Oh, and I lol'd when you said "venue". You have no idea the kinds of bad and undeserving of this equipment I am. :lol: :lol:

The controller needs 2U. I am running a 12U rack with a Helix (3U), Kemper Profiler (3U), Compressor/Gate/Enhancer/etc. (1U), 3U rack drawer and 2U slideout shelf. The controller fits perfectly in the slideout shelf, with just a tiny bit of clearance on all sides. It also fits in the drawer but if you have a door for your rack I would highly recommend you consider a drawer, it's really neat having it slide out.

I have a Helix rack and a Kemper rack hooked up to the Helix' FX loop. I have no prior experience with using MIDI, other than using a MIDI keyboard with a DAW years back. But everything was setup in such a way that I just plugged it in and played. So I want to use the Helix to control certain features of the Kemper. I want to be able to use the stomps on the Helix Controller to maybe scroll through rigs on the kemper. I want to see if I can set them up to turn off the "EFFECTS" or "STOMPS" section on the kemper, and possibly to "disable" the kemper so the signal goes through clean. I don't want guides on how to do this, I just want to learn to use MIDI so I can work these things out myself. I've read a little bit in the Helix/Kemper threads, and Helix as a MIDI controller threads, and most of everything goes over my head. I don't know about PC#s and CC#s and MIDI channels and what any of this is. So coming from that I'm asking if anyone can point me in a direction as far as learning MIDI goes. Anyone have a good guide/video/whatever that got you started?