Jump to content


  • Posts

  • Joined

  • Last visited

  • Days Won


Posts posted by stevekc

  1. Suggest watch this video and the 16:30 minute mark they talk about High freq cut EQ required for some helix amp models 



    Or there is the "final solution"


    this works well with my Firehawk FX  - 


    Palmer PDI-09




    The PDI-09 is a passive filtered direct box specially designed for guitarists. It can be used with line level preamps or connected between the amp speaker out and the speaker for direct input to a console via the XLR balanced output. This eliminates the need for a microphone in recording and live situations. The three position attenuator and tone switchs give you all the control you need in a small, sturdy DI box.







    s it's a harsh buzz that just shouldn't be there.. 


    If you have a steady buzz, even without playing guitar - check if it goes away when the USB Cable is removed from the Helix.


    its common for DC Switching power brick supplies used for laptops/ Computer to inject noise via a USB connection into the audio stream 

  3. I'm using the Alesis Alpha 112A's  successfully with Boss GP-10, VG-99, Peavey Vypyr Pro , Fractal Axe-FX II Ultra+


    I do not own a Helix, but I do hear high end fizz on the Alpha 112A's  when i use my Firehawk FX with FW 1.20 - rolling down the high EQ on Firehawk helps.


    I imagine similar procedure can be performed with Helix.


    FWIW - when I demoed the Helix at LA amp show, I thought it was a bit too bright and could benefit with some EQ with lowering the high Frequencies above 8Khz  


    But wanted to inform any fizz you hear would also occur on other powered cabs  - Alto TS112A ( which the Alesis Alpha 112A is based upon),  QSC K12, Yamaha  DXR10, EV ELX112P , etc.  sounds like a gain mis-match, or ground loop  / switching power supply issue in your configuration.



    Are you still experiencing the 'lights of death' based only on v1.2 factory presets






    ? If so can you provide a recipe to reproduce the symptom?


    I wish! it just happens randomly when changing presets up and down "too fast" when NOT connected to the Bluetooth link

    • Downvote 1


    Maybe I'm over complicating things... Maybe I could just use headphones out set to multi, split it with a y cable and use a small mixer like the Yamaha mg06 to mix the helix with the aux from FOH and send te output to to IEM. What do you say guys???

    I use this 




    Can you downgrade firmware back to 1.10? 


    Using the USB connection to Firehawk FX and Line-6 Updater Application for Win/Mac  - yes


    just be sure you have



    1 ) Installed the USB Driver  - I used a USB 2.0 port and this for Win8.1 "Line6Driver2FirehawkAudiov1.70Installer.exe"


    2) Installed Line-6 Updater = "Line6Updaterv1.03Installer.exe"



    3 ) Download the Firehawk FX Firmware files to a local drive



    "FW 1.10 = "Firehawk_FX_1_10_00.tmf'


    "FW 1.20 = "Firehawk_FX_v1_20_00.tmf'



    This is not the case. Firmware v1.10 and v1.20 use the exact same DSP algorithms. As a reaction to the statements here we are currently measuring Firehawk FX v1.20 to see if anything unexpected happened here. So far we have not found any difference.

    Glad to hear Line-6 is checking this ( Ive been wrong before!)


    Now If I could only trust that ths A/D lights of death lock up wont happen at a gig  


    But I'll make comparison measurements of FW 1.10 vs FW 1.20  -  next week - after the LA Amp Show.


  8. It will be a while - heading 200 miles south after work today to attend LA Amp show this weekend with Thomas Nordegg and compare Helix with Fractal AX-8 





    * If you want more sonic detail in Studio session - use Firmware 1.10


    * If you want faster patch to patch change time with no gaps / chirps for live gigs  - with a bit less sonic detail  - use Firmware 1.20 


    The good news  -  all Firehawk FX owners can try this test  above and compare  and judge what firmware version works best for your needs


    All the Firmware files and Firmware updater App you need are here - so any Firehawk FX owner can test the sonic differences between firmware 




    I suggest avoid using an iPad  / iphone as the wireless Firehawk FX Firmware update path - its very sluggish and prone to failure -


    instead download the files and use the Line-6 Updater App on your Windows  / Mac and a USB cable 



    Are people experiencing this 'thinner / fizzier / hollow' sound change over just headphones or is it the same using xlr / 1/4 jack outputs into a desk / PA?


    its everywhere for me - and I understand the hurdle  / balancing act in place under the hood here. if you want faster patch changes, you must make the DSP algorithm less articulate and smaller data size  - this allows faster preset load time.


    So I have the Firmware Updater for Windows 8.1 and locally stored copies of the  Firehawk FX firmware, will use this strategy:


    * If you want more sonic detail in Studio session - use Firmware 1.10


    * If you want faster patch to patch change time with no gaps / chirps for live gigs  - with a bit less sonic detail  - use Firmware 1.20 



    I own a 69 and 89F.  I notice that the models on my 89F sound radically differnent than my 69. 


    I have similar experience


    I own a 2011 JTV-59 and JTV-69 - load them with the same Workbench models and they sound radically different -My JTV-69 sounds better to my ears - while my  JTV-59, I must go into Workbench HD and boost the output gain of the models and save each  - that gets my JTV-59 closer to the Variax model sound of my JTV-69  


    like most products - when you get access to a population of them, thats when you can observe there can be differences with individual units. But Ive never seen a dealer with an array of Tyler Variax's on the wall to try - and most Guitar Centers have one JTV-69 hung 20 feet up the wall

    Last time I was at the Guitar Center in Brea, CA. their only Variax in stock was a JTV-69 hung 15 feet up on wall, high above the acoustic guitar room


    also know the LR Baggs Piezos can vary in output between production build batches - I attribute my issue above to the higher output level of my JTV-69 Piezos vs the lower output level of my JTV-59 Piezos.   

    • Upvote 1
  11. FWIW  -Only after I installed this FW 1.20 update and performed  a factory reset and using the factory presets  (no cloud) - was the 1st time I experienced the  " A/D Lights of Death"  issue  -

    • Upvote 1
    • Downvote 1
  12. I just wish they used the same "stepped chassis" design  as HD500 / HD500X / FBV 


    with raised rear row of switches


    This is basic "user ergonomics 101" design practice for a live gig foot switch




    In 2015  - even Peavey understands the need for this type  design 



    This is weird, but another plus of the 500x over the FH is, the back row of switches on the 500X are stepped up, the Firehawk switches are not. I had to come up with little risers for the back row of switches on the FH so as to not hit a front row switch by mistake, which could switch a patch. A real drag under fire of a performance, thinking I have switched an effect, and actually switched a patch, so while playing, I have to figure out what I have switched, undo it, and engage the effect that I was going for in the first place.


    Agreed 100% - too bad Helix shares the Firehawk FX poor foot switch design  - its tough to hit the back row of stomp FX and not accidentally change patches on the front row switches. 

  14. Headphone output feeding Audio -Tecnhica ATH M50X headphones.


    Also with FW 1.20 I hear less sonic detail and new Fizz and sizzle on the high end

    Old FW 1.10 has more body to the tone and sonic detail and sounds better , just don't change patches while guitar strings are vibrating  - else you have birds chirps if delay is active but set to different delay times during patch changes

    Or build patches with a clean amp and use a Tube screamer stomp FX. But that's limiting

  15. I did the update to FW 1.20 


    Good news is  after the firmware 1.20 update, (after 4 months of struggle) for the first time ever I finally have a working ASIO Driver I can finally set Firehawk to 16bits or 24bits @ 44.1khz or 48kHz  - this never worked on my windows machine with prior firmware 

    Despite asking weeks ago if any other Firehak FX owners have this working.

    With Firehawk FX Firmware 1.20 the patch change time is much lower  -but still  not as fast as the  HD500X



    And  I  still get a "bang" on specific patch to patch transitions. 


    try yourself by following these steps ( These are factory patches after a system reset - and no "Cloud" patches)


    1 ) Select factory patch#  09A Another Brick ,


    2 ) Strum a chord and  let it ring out,  


    3 ) then hear the loud "Bang" as you select  factory patch#  09B Own A Lonely Hrt








    1 ) Select  Patch#  13A Streets no Name


    2 ) Strum a chord and  let it ring out,  


    3 ) Then hear the loud "Bang" as you select  factory patch# 13B Hysteria Octave



    And this is new, I can report with FW 1.20 I am now experiencing the famous "A/D" Lights of death - with a  Locked up silent Firehawk FX with no sound and only a steady "stuck" glowing Preset  A  &  Preset D - occurs just random

    First time Ive seen this well known "bug" on my hardware 





    Not happy to have wasted 4 months for a solution - and still find remaining bugs which means this Firehawk FX is not reliable enough to use at gigs in my trio. 


    Rule #1 for Firehawk FX is mute your strings before changing patches.

    But the music style I play does not allow that

  • Create New...