phil_m

Well, the pedal send on the Shiva is an instrument level output, and the rack send is line level. You could use either one on the Helix, really. As far as going back into the Shiva, you'd want to use the return, not the power amp in, as the amp bypasses all the tone stack controls when you do that. I guess I may start with the Helix loop at line level and see how it goes. So just to make sure your connections are correct you'd be going (forgive me if this too elementary): --> = cable Guitar --> Helix Guitar in -> Helix Effects Send 1 (or whatever loop you're using) --> Shiva Rack Send --> Helix Effects Return 1 -> Helix Out --> Shiva Return.

Well, the Amplifi doesn't have bass amp models, per se (it does have two Fender Bassman models, which is technically a bass amp), but I've used my Amplifi 150 and my Amplifi TT paired with a StageSource L2t as a bass amp with success. I think I may have used one of the Bassman models. There's also the Tube Preamp model which can give passable bass sounds.

I used to work at a small music store... It was about 11 or 12 years ago. So it was right around the time when online stores were starting to have more of an impact on the market at large. The owner of that store always insisted on charging more than MAP - probably something like 5-10% more or something - and his reasoning was that people would pay for the extra service they receive from the store. Some people didn't mind, but even back then, many customers knew what the price on Musician's Friend was. It's a hard job to convince people that they should pay that extra $30 (plus tax) on a Squier starter pack... Honestly, it wasn't like we were doing anything special with the guitars we received from Fender, Ibanez, etc. anyway. Occasionally, if we got one where something seemed really off we might tweak the truss rod or adjust the bridge, but if something seemed really messed up, we'd send it back. So I guess, perhaps that initial inspection might be worth something. The other thing, though, is that many of the more expensive guitars stayed on the wall for months or even years. So I think many people simply don't like the idea of buying a guitar that's been touched and played by dozens of people. So personally, I don't really have any romantic notions about most mom and pop stores. Some of them deserve to fail because they aren't really trying any more. There are some that are doing some cool, innovative things, though. Those seem few and far between to me.

Not something I actually use, but I just wanted to test it out after some folks said they were having problems with it on the Helix Facebook group. Really, the thing with the CC Value and saving the value per snapshot isn't a big deal, and the workaround is simple (takes about all of 10 seconds to do in the editor), but the thing with looper is a big deal and could be a deal-breaker for some people.

One caveat with this workaround. I spent some time messing with this last week, and there are few issues. First of all, if you go into looper mode with this, you'll create a MIDI feedback loop. The reason for this is that the footswitches send out CC messages for each looper function. Right now, there's not a way to turn this functionality off. I have a MIDI Solutions Event Processor, so I was able to filter these messages out and get it to work. So basically, right now, if you use the looper, there's no way to make this trick work unless you have an external means of filtering the offending CCs. The other issue is the way the CC Value command works when you assign it to a footswitch. There's a bug right now that makes it so a specific CC value is saved with each snapshot. Beyond that, this value is treated an Instant Command, and it's shot out when the snapshot is triggered. For example, if you go into the Command Center and set up a footswitch for CC69, value 2 - that does call up Snapshot 3 (with the MIDI cable trick mentioned here). The issue is that the value for CC69 stays at 0 for the other snapshots until you go and change it in each one. So if you don't do that and hit this footswitch, you'll go to Snapshot 3, but upon loading Snapshot 3, CC69, Value 0 is shot out and you go right back to Snapshot 1. So the workaround is to go into the Command Center in each snapshot and make sure you set the CC69 value to be the same thing in every one.

Are you saying you only experienced freezing while connected to your Mac? Have you had any while not connected?

This sounds like the phantom power issue. It sounds like the sound guy was sending phantom power to the channel you were using for the Helix, and that will cause noise. So the options are to either turn phantom power off on that channel (if you can), use some sort of phantom power blocker (the DI box in this case is doing that), or use the 1/4" outs into a DI box. http://line6.com/support/page/kb/_/effects-controllers/helix/helix-xlr-outputs-and-48v-phantom-power-r771

You actually don't have to login to use the Updater... You can run it in offline mode. You just have to download the flash file manually this way. If you're having login issues with the Updater, that could a matter of a firewall or anti-virus setting on your system, though.

You can't assign snapshots to footswitches... There a few different ways to view snapshots, though. You can always get to snapshot mode by pressing the Bank Up and Bank Down footswitches simultaneously. You can also change Preset Mode to display snapshots - you can have all 8 footswitches show snapshots (effectively making preset mode the same as snapshot mode) or you can have the upper row of switches be 4 snapshots, and the lower row be 8 presets. Or you can have that reversed. Or you can have 4 stomp switches and 4 snapshots... Check out page 50 of the manual to get the full rundown.

I responded to your other post where you asked this, but upon further review, I believe I may have spoke to soon. It actually is possible for the G10 transmitter to communicate with the XD-V75 receiver, but the issue is that the G10 can only operate on RF2. The XD-V75 can operate on RF1 or RF2, so it actually is possible to get them to work with each other. If you want to use them both on the same stage and have them not interfere with each other, you need to follow the steps in the FAQ here: http://line6.com/support/page/kb/_/live-sound/relay-digital-wireless/relay-g10-faq-r808

I believe that one thing that came about from the Yamaha acquisition was that Line 6 is now depending on Yamaha for its international distribution channels. I'm not exactly sure how they were doing it before, in the sense that were handling it all themselves or what. But it could very well be the case that Yamaha requires larger orders from retailers in order to maintain a dealer status. That's the same reason why, for example, you hardly see any smaller shops who are Gibson dealers now. Gibson changed their policy a number of years ago so that the minimum orders they required simply priced smaller shops out of the market.

For the record, you can actually sync the slow and fast speeds for the rotary effects to the patch BPM and have them tied to the tempo you tap in. Just hit the knob under the slow or fast speed parameter to change that value to a note value. Or in the editor, just click the button to turn tempo sync on on the effect's home screen.

The funny thing to me is that I have the Peterson Strobe Tuner app, and in addition to showing the actual strobe display, it shows how off you are in +/- cents reading. I've got to say, it is nearly impossible for me to get any of my guitars to actually stay within 1 or 2 cents of pitch. The nice thing about that app is that it gives you an idea of how much instability there actually is in a pitch from a plucked string. This is why I'm still pretty skeptical when people are claiming to hear things being 3 cents off from pitch...

It's not a bug... It's per design. I didn't take the time to search for it on the Facebook group, but Ben Adrian, the Helix sound designer, explained it there. Basically, when you turn the bit depth parameter down, it actually lowers the headroom for the block, and instead of remaining a 32-bit floating point algorithm, it actually means the signal for the repeats block is being sampled at whatever frequency and bit depth you choose. So the key to not clipping at the low bit depth settings is to have a lower signal going into this block. I assume you have it after the amp and/or cab block, so just lower the channel volume parameter in the amp block, and you should be good to go.

Uh, what's the point of dragging this old post up? The post you quoted was something DI wrote even before the tuner was updated... You do realize it was updated, don't you?

I know getting the Workbench HD/Helix functionality up and running is on their list (Digital Igloo has said so here). It's just a matter of resources. Getting it to work requires not only an update to the Helix, but to Workbench HD as well, and that's another team of people to get things coordinated with.

You're looking at an outdated manual. Here's the latest: http://line6.com/data/6/0a06439c975d5787c3e351aa0/application/pdf/Helix%202.0%20Owners%20Manual%20-%20Rev%20D%20-%20English%20.pdf Pages 34-39 describe the Snapshots feature, which is what the camera icon is representing.

The TT doesn't send audio over Bluetooth... It only receives it. So if you want to actually stream audio from you device through the TT and hear it, you'll have to physically connect speakers to the TT. You could pair your speakers to your phone or whatever you're using, but you can't have the TT paired to your phone at the same time. With Bluetooth, you're limited to one pairing at a time.

I guess I have the opposite opinion when it comes to turning knobs, pressing buttons and whatnot. The duty cycle on these items should be in the hundreds of thousands, so even under the heaviest use, they shouldn't be expected to break. So if there is a defect in a component, you'd want it to show up early on. So that means you want to use it in the way it was designed to be used. You shouldn't be expected to treat it with kid gloves.

You'll need to open a support ticket to get the answer to this question. http://line6.com/support/tickets/add.html/

It's a different design than the HD500(X)... So, no, no attenuation, at least by default.

If you're using separate amp and cab blocks, and you have enough DSP, you could put multiple cab blocks in a preset and change their bypass state on a snapshot per snapshot basis.

Do you happen to have phantom power being sent to the Helix from the PA? That can cause noise.

How exactly did you come to the conclusion that the M13 was the problem? Usually these sorts of issues are related to guitar amps or PA systems not having the proper grounding.

Well, what you heard in that podcast was simply Pete's miced amp while the Helix was being used for effects... I don't know if Line 6 has any plans to model this particular amp or not.