Saving sounds from Firehawk FX

[ortnerh]

What's the best way to save all sounds of Firehawk FX to a Windows Computer?

What's the best way to save all sounds of Firehawk FX to a IPad with the app?
Is there a function like the saving option in line6 monkey?

Sorry for my bad english.

[silverhead]

You can't save FH presets to a computer (Windows or Mac).

The FH presets on an iPad are managed by and within the app. You don't save them separately to some other iPad location.

There is no function like the Monkey Save function.

 

The Firehawk app provides the only save/load options for Firehawk presets. The primary storage location is the Firehawk device itself. For backup purposes you can save to My Tones (private) or to the 'cloud' (public). Both of these storage areas are provided and managed by Line 6 somewhere in their corporate IT world.

[ZenBalancer]

I'm for the convenience of the feature!

 

Time to rant: check!

Although this might make this thread inconvenient.. so my bad on that regard. It's also addressed widely.

 

No plans are public, as far as I know, for a FH desktop Remote SW (unlikely to be soon either) with more features that would at least include Batch Patch Management (akin to saving/backup-restore Banks and Bundles in Workbench HD). Currently there is no obvious way to save multiple FH Patches in the Remote app. It's one by one. There is much more storage in their cloud, and Patches saved to preset-positions onboard survive reflashes. So unless the FH unit "dies", you don't have to worry about keeping track of the positions you saved which on. You have to save edited patches with the Remote to your "cloud account" for ease of mind. Like if you edit with or live-edit without the Remote, if you are really happy with the Tone, you should save to your "cloud account".

 

But the downside is also currently you can't easily sync all the positions and patches between multiple FH units. You could add a Remote app feature request on ideascale was it? For Batch Patch/Tone Management, or something of the like. Also handy for multiple preset-sets, to change lets say the entire or partial/significant number of the onboard set with a different set to minimize patch switching latency more conveniently for that set. And that on the go, without needing to pack in a laptop or purchase a MS Surface (non-RT) for instance (in case it becomes a desktop only feature; unlikely).

 

FH is introduced without a desktop Remote SW, probably for the same reason they didn't simply bring out a HD500X BT-edition with a Remote tablet app, instead of an Amplifi-PodFarm-HD-FSline6StandardisedColors(from another product) floorboard in the form of FHfx as the introduction of the FH product-line. Each product-line has a different focus. In the future I can imagine the lines bluring also between these two or more entry- to mid-range product-lines. Or even for the Helix-line after prices can drop significantly (Years? Upto around half a decade? More?). The whole reason in my view that they too don't do everything for all of the product-lines (if not from the start, then also not later), in one sequence: technology phesability progression, final product costs, return on investement, different market segment opportunities, a relatively small team with limited time and resources, and lets say humane productivity levels.

 

They did add special Patch-Packs for the HD500*, but for a price. Not many that choose a FH unit would want to pay for a relatively expensive desktop app ontop of it. But I imagine you could be one of them. For the tablet app version, they could make in-app purchases available for the extra development time. Although based on the Android app/Play Store download statistics it would currently be caped under 100.000$ (not taking multiple installs for the same user into account, not sure the statistics is based on unqiue users) of total potential project revenue for 10$ per user worth of in-app purchase added-value, that as an example. With a higher "user-conversion" rate, since we want to get the most out of the unit, so maybe 20% instead of the stereotypical 2%, it would be capped at 20.000$ budget potential for the Android version. I assume a shared-code base with the iOS version, so it should bring the total costs down with a significantly higher budget. They know their unit sales statistics, so they can easily make a fairly accurate estimate of financial pheasability.

They just have other things to do. And assuming that also due to the properitary nature/trade-secrets, they don't outsource specific EXTRA SW development on a project by project basis (if relevant for this case). There is no indication the FH Remote would get that much better soon. Only a few minor maintenance and compatibility updates were released, one coupled to the introduction of the FH 1500, the other preceded it with the most recent firmware, I think. The firmware update was a significant improvement to the experience however.

 

 

Line 6 like most commercial companies, has a policy that have been enforced consistently (not much leaked, with perhaps a handfull of "hypthetical exceptions"), they don't divulge all "internals" and roadmap specifics publically. That core attitude is even in their "company-DNA", from how the name even started.

 

For a relatively small team, there is still room for more agility to expand and/or improve their existing products. There are obstacles obviously, otherwise they would have done it already. I hope they work through that. They could just hire an additional dedicated "full-stack engineer" if necessary for expanding and/or improving SW with in-app purchases. It's just that there isn't a convincing overview to base that decision on. This post doesn't have a relevant chance, besides maybe a few moments of consideration.

 

Regardless, I will vote +1 on the following. Although currently I'm not in "dire need" of the feature (relatively new/healthy unit, that I'm carefull with, and don't need that many "live sets" to switch between, as I'm just a beginner), and also despite all of the above about the company being a given (repeatedly), can we know if the FH Remote would get Batch Patch Management at least? In case the staff coincidentally reads this, or someone else have been given that specific answer explicitly. My guess is, often they are uncertain if a feature is worth the diversion of attention, even if just temporarily for a minor feature, especially if it takes more time to implement than it would seem at first (especially when unprepared for it).

 

If I missed something, feel free to point that out.

At some point I too gotten used to using the term Patch or Tone for the multieffect units, and, Patch or Model for the Variax guitars, interchangibly within each set after hanging out on this and the vguitar forum.

Also they did once made it absolute through one of my Support Tickets that the Spider Online section is old, "frozen" (paraphrased) and won't be developed further. So they do give feedback within currently known plans at least, as long as "not too revealing" I guess, and or if internally whith the company, decision defered or uncertain.

 

On the one hand I'm hoping I missed something. On the other hand..

..is there actually already a way to save more than one Tone at a time from and to a FH unit?

[ZenBalancer]

I forgot a downside of the feature: simultanious multi-user batch-operation loads! Their "free Tones cloud" costs will rise, in IO-time and storage, and/or operation processing time will increase, because users can more easily save and load much more at the same time. But they don't have to limit it to the cloud alone imo. Local storage for them should be equivalent to the cloud private "My Tones" like silverhead mentioned, so strain on their servers would be minimum, if they allow local storage and/or set a free-quota per user per day, week or month. Or make it a global task-queue for batch operations! Everyone should see that their batch operation is waiting for the ones before it, and we would be inclined to only perform it when worth it. But at least we would do something else in the meantime while the relative grunt work is automated!

 

"Category/directory", tag filters, something, has to be added though to help in navigating and deal with the increase of the list sizes visually.