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


  • Posts

  • Joined

  • Last visited

Everything posted by JamieCrain

  1. thanks Lungho So yes there is latency. Got it. Snapshots is cool but I use approx 16 main patches on my current rig. Every single patch uses a different amp combo so Snapshots is limited for me. Trails in snapshots? Tick. Working around the limitation of the gear would be fine if we knew it wasn’t possible to achieve what I’m looking for. But we know it does exist on other brands. Hardware update to improve DSP performance? Yes, that’s exactly what I’m saying. But they should have done it from the outset. As for concentrating too much on the gear, I don’t agree. As a friend of mine said to me after showing him my L6 gear, the gear is as much the instrument as the guitar. Anyways, Helix is an amazing product, and I may get one when the next version comes out. I just wish it worked as seamlessly as my old Boss ME unit. cheers, J
  2. OK, so after nearly three years since my original post :) , I have learned the following about Helix: There is latency between patches on Helix, except when using Snapshots. Snapshots are limited though, so you don't really have total ability to use any pre-set tone and then use Snapshots to change to a completely different tone. There is still no delay/echo/reverb trails feature in Helix (a major shortfall, trails makes a massive difference to the audio experience in a live environment) DSP resources are still undercooked on Helix and L6 products more generally. I still don't understand why this is the case. How hard can it be to increase DSP by say 20%/30%/50% to handle the above given the availability of relatively cheap hardware these days. I love the individual tones I get out my L6 gear, but for me the above issues are still big ones. Apple eventually realised that gapless music on the iPod was a must, especially if you listened to an album where songs blended into each other. This is no different. Thanks for all the info! Jamie
  3. *significantly different. The L6 Elektrik sounds non FHFX sounds nothing like the Pod HD. Although the dual recto treadplate is pretty close.
  4. Try it. But yes I’d have thought the only difference running in stereo is the effects themselves.
  5. The FHFX has enough amps/FX in it already for the price, maybe with exception of a couple of things. But for me, the biggest things we can hope for in an update is: 1 Bluetooth reliability 2 No sound artefacts when switching patches 3 Zero lag between patches. They could do it on the POD HD, why not FHFX? 4 More intuitive iOS interface e.g. save, save as. If they fixed these bugs, I would 100% more satisfied with the unit.
  6. Sadly I have the exact same issue as the OP. Killing the app and logging in again fixes the issue, until the next time...
  7. No, but I run a line out from the headphone jack of the iPad to a different audio system and that separates it from the FHFX connection.
  8. Perrin1710, Yes absolutely. Remember one thing: the output from the FH amp block is *always* mono. If you want stereo effects, these need to come after the amp in your signal chain. This includes the FX loop. Any effects placed before the amp will be condensed into mono and run two identical signals to left and right if you are using two amps.
  9. Not sure that’s particularly helpful, especially in the short term. Duy, it sounds like another effect is assigned to the volume pedal. Or it could even be the amp. Try going through each block. If you can’t resolve it, start a new patch and delete the old one.
  10. Also, you may be saving patches only to the cloud, not the FHFX device. If you bring up a patch from your phone/tablet and edit and save, nothing on the FHFX will change, only the tone in the cloud. Confusing - yes, the GUI is not designed well and it’s not clear when you are editing a cloud patch vs a FHFX patch.
  11. It’s about 6 taps total on your iPad’s screen. Then it’s set permanently, no need to touch volume again.
  12. No, have you tested the headphones and adapter in a different device? Need to rule out a faulty adapter.
  13. Yes, it’s easy. Set up Patch 1 and save to the FH in your preferred location. Then go to the amp block in Edit mode, and adjust the volume parameter, Save as Patch 2 (which will save it to MyTones). Then save to FH in the next location. NB you need to save to FH for both patches if you want them on the FH device. The initial save will only put it in My Tones which is in the cloud.
  14. Save one of your problem patches in the ToneCloud with a unique name, tell me the name and I’ll try it on my unit. Even better, if you can do that AND record a sample of the tone in question so I can compare.
  15. JamieCrain


    Does it work through your headphones again?
  16. Try running the FH through a sound system rather than your amp. See if this addresses the issue. I run mine through FRFR powered PA speakers. They have a basic treble/bass Ed and the slightest tweak makes a big difference. Modellers work best through sound systems not amps. Going through an amp doubles up on some of the tone modelling.
  17. Are these your patches or did you inherit them?
  18. It’s an inherent problem with FHFX. Didn’t exist on POD HD, but does on FH. Even Helix has latency if you aren’t using snapshots.
  19. Sounds like a rotary or trem effect with a phaser. Or a ducking delay with phaser.
  20. What's the main advantage of Bluetooth over RF wireless headphones? Quality? I use the latter and there is no latency but there is some background hiss.
  21. I have the same issue. My fix is to kill the app on the iPad, restart the app, log in again, reconnect to FHFX, and it's sorted.
  22. Yep. I can't find any pitch effects that work well even for simple octave or harmonies. This area clearly an afterthought for Line 6.
  23. You create your own. Just clear down all the amps and effects and save to your tones. I have a few, one for each style which I use as a base and then build up from there.
  24. I tried that over the weekend and can confirm that removing the compressor did *not* fix the problem. As loud as ever.
  • Create New...