Jump to content

stevekc

Members
  • Content Count

    655
  • Joined

  • Last visited

  • Days Won

    7

Everything posted by stevekc

  1. FWIW - on my FireHawk FX - I never could get the Firehawk FX Windows USB ASIO Driver to work until after i updated to FW 1.20 To verify the Firhawk ASIO driver is working, Be sure you see these options in your Windows Sound Devices Control panel
  2. Yes I wish! it just happens randomly when changing presets up and down "too fast" when NOT connected to the Bluetooth link
  3. Upon further testing, I now understand the Firehawk FX Firmware 1.10 vs 1.20 sounds identical - sorry for earlier confusion.
  4. 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'
  5. 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.
  6. 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 http://www.ampshow.com/ 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 http://line6.com/software/index.html 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
  7. 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
  8. 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.
  9. regarding state of my Firehawk FX today, it remains in the same condition accurately expressed here - just follow the steps on yours http://line6.com/support/topic/15814-firmware-120/?p=116088
  10. 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 -
  11. So we are clear, With FW 1.20 switch time is much faster and Noise anomalies on patch change have been tamed - there are only specific events to re-create the "bang on patch change" for specific patches - all described in my prior post above Just trying to find the switch sequence that triggers the " A/D Lights of Death" http://line6.com/support/topic/13591-a-d-patch-lights-of-death/
  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
  13. Hope you have better luck than me
  14. 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.
  15. Happy to hear Line-6 is listening to users experiences with their products - pass it up the chain of command.
  16. Headphone output feeding Audio -Tecnhica ATH M50X headphones. http://www.audio-technica.com/cms/headphones/99aff89488ddd6b1/ 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
  17. Updated to FW 1.20 and suddenly Windows ASIO driver is working for the first time here Here is Reaper Audio settings for Firehawk FX recording 24bit@44.1kHz
  18. Read my FW 1.20 experience here http://line6.com/support/topic/15814-firmware-120/?p=116088
  19. 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. http://line6.com/support/topic/15647-firehawk-fx-and-windows-usb-asio-audio-driver/ 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 or 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 http://line6.com/support/topic/13591-a-d-patch-lights-of-death/ 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
  20. One persons "very minimal " patch change lag is another persons eternity. and this reminds me of the old Marx Brothers line 1: Doc, it hurts when I do this... 2: Then don't do that. 3: Have you had this before? 1: Yes. 2: Well you've got it again. Ive since moved to a Vypyr Pro System for my live gig needs -that has instant patch changes and easy editing a patch mid song, while Line -6 spins a reality distortion field around the Firehawk FX patch change problems
  21. Firehawk FX is fixed at 48kHz clock rate
  22. I've been told by line-6 Workbench will not run on Firehawk FX, and no plans to make it occur. They will he too busy getting Workbench to work on their new focus, the Line-6 Helix (it does not work on Helix currently either)
×
×
  • Create New...