talonmm Posted October 19, 2016 Share Posted October 19, 2016 Apparently my posts were clear as mud. Sorry 'bout that; let's try bullets: We absolutely can improve Helix <â€”> DT integration and have several ideas mapped out already (actually, they were largely mapped out before Helix was even announced) More robust Helix <â€”> DT integration continues to be on our gargantuan list of things to do; its priority is largely determined by user demand More robust Helix <â€”> DT integration, if or when implemented, will not be like POD HD <â€”> DT integration, because POD HD <â€”> DT integration: doesn't apply to Helix's architecture takes forever to implement and debug, and diverts resources from features with bigger ROI is needlessly complicated for our users includes a ton of features for daisy-chaining more than one DTâ€”and almost no one daisy-chained more than one DT. There may be only one or two people worldwide who daisy-chained more than two Believe me, any DT integration we provide wouldn't be to push DT sales, as all DT50 SKUs have been discontinued. We'd do it because X number of users ask for it. We move features and models up and down the priority backlog every day. Thank you for the clarification. I had heard that the dt50 was discontinued, but hopefully the head and dt25 will continue. I have both a 50 and 25 and love them both (just not the weight of the 50). It's exciting that line 6 is thinking and/or planning how to come up with a simple integration of helix to the dt series. And congratulations on the helix - it is an amazing product and has brought a lot of satisfaction to me and plenty of users! Quote Link to comment Share on other sites More sharing options...
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.