phil_m

No... The available DSP for a patch doesn't change based on whether the global EQ is on or not. That DSP is just always set aside for global EQ.

You need to program a CC to whatever the footswitch you want to use to control the H9's tempo. I assume you'll want to use the Helix's tap tempo switch since that means that whenever you tap a tempo in on the Helix, it will be sent to the H9 automatically. You'll have to set it up in every patch you use on the Helix, though. As far as how to do it on the Helix, you definitely don't want it as an instant command - it won't work that way. Follow the instructions on Page 37 of the manual about assigning a command to a footswitch. Select FS12 (the tap tempo switch) and pick a CC to send to the H9. The H9's tap tempo can be set to respond to whatever CC you want, so you can choose whatever you like. CC64 is what Line 6 uses, so it might be good practice to keep similar commands on the same CC.

I have the Mobius as well. I think with the Mobius' rotary, the Leslie cabinet itself doesn't seem to have such a large effect as it does with the Helix. If you use the Helix's rotary effects in place of the cabinet in your patch, it will sound a lot better, imo.

The TT comes with the DC-3g power supply. You can buy it directly from Line 6 from here: http://store.line6.com/accessories/power/dc-3g-power-supply.html Any 9V DC, center-negative power supply with the correct barrel size and sufficient current rating will work, too. I'm not sure what the actual current draw of the Amplifi is. I'd be surprised if it's actually that close to the 2.5A rating of the DC-3g, though. The Truetone (formerly Visual Sound) 1 Spot will fit, and probably work, but it's rating is only 1.7A, so officially not really supported.

Well, there you go... The external device isn't really necessary. Just program whatever CC you want to control the H9's tap tempo to the Helix's tap tempo switch (in every patch on the Helix), and it will be good to go. I missed the above info in the H9's manual, but I was just looking at the MIDI implementation chart at the back.

Food for thought... The owner of Logidy actually went on the record somewhat recommending against using this device as some sort cure-all for the HD500. http://www.thegearpage.net/board/index.php?threads/the-logidy-epsi-is-getting-an-update-to-run-irs-for-cab-sims.1392604/page-6#post-18089627

Well, I don't know if the designers made that assumption or not. I personally think that in the context of a full band, no one is going to notice if there's spillover between most transitions or not. I can seen if it's certain styles of music - ones where you depended on long delay and/or reverb trails to fill the audio space, yes, that would definitely be noticeable. But in a typical rock or pop song, no one is going to notice as long as your transitions are done in time with everything else. And, actually, having no spillover can actually be desirable in many transitions. The one singer I played with for a long time always got irritated if my delay tails bled into stops.

Well, the thing is that each thing listed is on its own update path/schedule. I imagine that the Helix firmware itself will always be at a higher number than the Helix app and the updater. Soon those numbers probably won't be all that close. The Line 6 Updater is actually used for a variety of Line 6 products, so it can't necessarily follow the Helix. I guess the most important thing is you can always find out which version is the latest by just checking the website.

Are you saying that's a bad thing? I actually like that feature - being able to jump from the lowercase to upper case to numbers, etc. quickly is really nice. I'm actually surprised how fast it is to enter a name with the joystick. It's not as fast as typing one in, but it's a lot faster than, say, the HD series.

I personally don't think any of those clips are necessarily playing to the strengths of either unit, but, yes, in a recording of raw amp tones, I don't think the differences are going to be very noticeable. To me the main difference with the Helix is that it feels a lot more responsive and lively overall. That's not to say the HD series was bad. I still think it's probably the most bang for the buck, but I also think that, all things considered, you get a huge bang for your buck with the Helix. And it's only going to get better as time goes on. I'm a little confused in regards to the recommendation about the Torpedo Studio. That's a $1900 piece of equipment in and of itself, unless you're actually talking the C.A.B. In either case, that combined with the HD500(X) might be a nice rig, but it's still going to be much more limited than the Helix. Yes, the Helix is 3X as much as the HD500X, but for my purposes, it's more than 3X as useful. People's personal experiences may vary. Personally, I have over $1500 invested in my pedalboard alone, and the Helix can pretty much replace everything on there and then some. Again, you won't find me saying anything negative about the HD series. It was and still is a great line. I think, though, that the Helix is a step beyond. I also think that once people see the way the Helix is developed, the differences will become even more clear.

This is kind of the case in the 3D modeling/architecture world as well. Sometimes I think the software I'm using now is actually slower than what I was using 10 years ago, although it's way more powerful. Gains in processing power are rarely used just to make existing algorithms run faster it seems. More often, they're used to let us run more complex algorithms.

Yes, you could use it to control the EXP1 and EXP2 controllers via MIDI, so it would control whatever parameters are assigned to those. One cool thing is that with a JTV or Variax Standard, you can use the volume and tone knobs on the Variax to do this same sort of thing when connected with a VDI cable - no modifications necessary.

Are you trying to download the firmware flash file itself or the updater? It looks like Windows is trying to open the file as text file, regardless. You need to download and install the latest version of Line 6 Updater, and then once installed and running with the Helix connected, it will download the firmware file for you and send it to the Helix.

There is a fade in and fade out when you go to a new preset. It's just really fast. But if it wasn't there, you would most likely hear an audible pop when changing presets.

I like that model, too. Although, that's not really a Line 6 Original. It was modeled after a real amp. It's a model of Pete Anderson's modified Deluxe Reverb. http://www.vintageguitar.com/17469/pete-anderson-5/

There is a tiny gap when you switch patches, yes. The HD500X doesn't have spillover between patches.

Yes, you can save up to six "instant commands" with a patch. These commands will be sent from the Helix as soon as you load the patch.

Well, the Helix doesn't have MIDI clock functionality yet so it can't send or receive tempo data that way (I would be surprised if this isn't added sometime in the future). The H9 doesn't appear to have a MIDI CC dedicated to tap tempo, so right now, if you want to control the H9's tempo from the Helix, you're going to need an external device like this: http://www.moltenvoltage.com/products/TEMPODE_by_PedalSync_-_PedalBoard_MIDI_Clock_Injector_by_Molten_Voltage.html With this, you could assign a MIDI CC to the Helix's tap tempo switch and that would be converted to MIDI clock data to be sent to the H9. The only downside is that it requires you to always update the tempo via tapping. You could also do it the other way around and have the H9 control the Helix's tempo. It would be more automatic since the H9 can send MIDI clock. It would always be syncing the Helix to the H9. http://www.moltenvoltage.com/products/SIXY_by_PedalSync_Line_6_Tempo_Control_by_Molten_Voltage.htmlThis device turns MIDI clock data into the correct MIDI CC for the Helix's tap tempo.

I haven't noticed any hiss from the the XLR outs either by going into my mixer or directly into my L2t speakers (I do have hiss with phantom power on and the ground lift switch off). It doesn't necessarily surprise me, though, that going into a DI might be quieter in some setups than using the XLR outs. A DI box is an electrically isolated connection to the PA. There is an actually transformer in a DI box so there's no physical link between the high and low impedance signals. It's a good way to ensure that you're not passing noise through the system.

I would say that the models on the HD500 and Helix react completely differently from each other, so your experience on the HD500 isn't really anything to go by... Personally, I do like the way many effects react after the amp block and before the cab block on the Helix. It's a nice feature.

Like anything, you'll get used to it to the point where it becomes second nature.

L6 Link from Helix to the L2t, and XLR out from Helix to FOH. You can connect the monitor send from the board to one of the mixer inputs on the L2t.

Are you running the latest firmware? This was a known bug in an earlier firmware, so if it's still showing up, it would be good to know. If you haven't installed the latest firmware, you should do it ASAP.

There's no way to control the 1500 with the FX. There's no communication protocol between the two devices.

Set the feedback higher. That's what it's there for.