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

surfsup1955

Members
  • Posts

    222
  • Joined

  • Last visited

Posts posted by surfsup1955

  1. 21 hours ago, faidilarbi said:

    Why doesn't the device run with me? toneport ux2 On the Windows 10 computer Knowing that he was working with me on a Windows 7 computer Is it possible to put the appropriate driver link for downloading?

    line 6 monkey ?

    GearBox ?

     

    Did you intend for this post to go somewhere else?  I'm only asking because it has zero to do with this thread.  

    • Haha 1
  2. Gerry, I trimmed the preset to load up on HX Stomp (ver 3.0 or higher) and it's up on CustomTone:

     

    https://line6.com/customtone/tone/5257476/

     

    CustomTone comments:  IR used is 3 Sigma Mart 45 Soundhole 1b.  Guitar is a Martin D18 with a K&K Pure Mini pickup.  Typically tuned to Eb w/light gauge bronze strings using a medium pick.  Preset contains 3 snapshots EQ'd differently using the new Acoustic Sim on side chain.  Only 7 fx blocks, HX Stomp compatible.  Requires HX 3.0 or higher.

    • Like 1
  3. 1 hour ago, silverhead said:


    Just to clarify, you can import a single path Helix Floor preset into HX Stomp. You’re correct that you can’t use a dual path preset.

     

    Thanks, I didn't know that.  This means my son and I can swap presets, awesome!  However, my preset in this discussion is using both paths.  

  4. 4 hours ago, gerryCol said:

    Hi Surfsup, 

    Sorry i missed your reply to my post somehow. I would love to hear your patch, I have the same IR's. Funny you mentioned the K&K pure mini  pickup. I have the K&K Trinity ordered and should have it tomorrow. Great time to take your patch for a spin. 

    Thank you and sorry for missing this to begin with,  just goes to show you how long I have been fighting with this one.

    Gerry

     

    Hey Gerry, as is typical, my main acoustic preset has morphed into something different than what i described above, which I now prefer.  It still requires 3 Sigma IRs.  Also I have had a chance to piddle around with an HX Stomp (my son bought one) and I know for a fact you can't use a Helix Floor preset in your HX as it doesn't have the dual DSP paths.  However, I will be glad to send.

  5. 4 minutes ago, phil_m said:

    Yeah, if I had to guess, I'd say that the people who post here probably represent less than 1% of the Line 6 user base. I'm kind of surprised they've kept them running in one sense, but on the other hand, it doesn't cost them much to do it. But it's not like there's a full-time employee for the forums. There are a few people who check in every now and then. I've talked a little to them about the log-in stuff, so I think there's some awareness to it. I'm sure it's just one those things that's easy to push to the back burner.

     

    I can image there are a lot of HX owners who don't search forums for advice or even update their units, my oldest son being one of them.  So yea, I'd guess this is a small sample of owners.

     

    He's visiting in Dec and I told him to bring his HX and we'll update it to 3.0..lol

  6. 1 hour ago, phil_m said:

    I usually stay signed in between visits. There are occasional weird things, though. The most annoying thing is that often when I click on a thread on my iPhone I’ll be logged out when I get in the thread. The weird thing is if I hit the back button, I’ll be logged in again when back at the main page. The software just seems finicky.


    Yea, lots of anomalies.  Doesn’t seem to have a pattern.  
     

    This is the second time it’s taken me right to this thread without having to log in.  Both times using the provided email link notifying me someone commented on the thread.  
     

    I assume L6 is not interested in fixing the issue?

  7. OK, thanks for the confirmation.  I don't come here as often as I used to, but don't recall this being such a nagging issue before.

     

    Funny though, I didn't have to log in this time, haha..

  8. 3 hours ago, adamsguitar said:

    This has been my point for this entire discussion: they do. The audio industry (particularly hardware manufacturers) are notorious for not being ready for the release of a new OS version.

     

    This coming February I will have owned my Helix 5 years, in that time my Mac OS has updated every year (Yosemite to Catalina), including a multitude of interim patch fixes.  Big Sur is the first time I have had to roll back to the previous OS due to HX incompatibility - or any reason for that matter.  That speaks well of Apple and L6 in my humble opinion.  I don't see a pattern with L6 that indicates they just sit on their hands waiting for the final release of operating systems.  Maybe?!?  But, if that's  their method of operation, they've been extremely lucky. 

  9. 6 minutes ago, adamsguitar said:


    You said that it seemed like a long time for manufacturers to respond given that Big Sur was released in September and it’s now almost December. I’m pointing out that Big Sur was released on November 12 (not in September), so as if today it has been out for less than two weeks. 
     

    The gist of my argument the whole time is that manufacturers should be doing this work during the prerelease time (developer and/or public beta periods) but that music manufacturers rarely do that. Instead they wait until official release, so from that perspective no, two weeks is not a long time for a manufacturer to get out an update. 

     
    Sorry, I was editing my post while you were responding.

     

    I doubt they all waited until the release?

     

    The link above confirms to me a more complex issue is going on rather than mass incompetence of the audio industry.

     

     

  10. 20 minutes ago, adamsguitar said:


    Big Sur was released on November 12. The public beta was made available in September.


    Yep, and I expect the Public Beta date is when these companies started working towards compatibility?

  11. 7 hours ago, adamsguitar said:

     

    Sure, but when is this ever not the case?


    It’s not something I track but Big Sur was released in September and it’s almost now December, that seems a bit long in terms of catching up regarding this many manufacturers?  

  12. On 11/17/2020 at 5:06 PM, Drybonz said:

    I think the more people who are on these forums encouraging them to update certainly can't hurt.  The thing that hurts is many people excusing them from the responsibility of keeping up to date.

     

    I'm also hoping you are right.

     

    https://www.sweetwater.com/sweetcare/articles/macos-11-big-sur-compatibility-guide/#macOS-11-Big-Sur-Compatibility-List

     

    Yea, me too, but after looking at the recent list of audio companies that still have NOT been able to resolve Big Sur compatibility issues - and it's a long damn list - I decided to bounce back to Catalina to get fully on board with HX 3.0.

     

  13. 6 hours ago, SaschaFranck said:

     

    Using the Line 6 Updater is even recommended by Line 6 in case updating via HX Edit fails. Nothing to do with being an outlaw.

     

    I used HX Updater on my floor unit for 3.0 only because the HX Editor will not update inside Big Sur OS.

     

    It worked fine.

  14. 59 minutes ago, adamsguitar said:

     

     I would think that the size of the user base who:

    1. Bought a brand new Mac that came with Big Sur preinstalled (are they doing that yet?) or have chosen to install the update intentionally
    2. Just bought a Helix

    Is probably pretty small. 


    Maybe - but either way they're dead in the water.  They now own a brand new $1700 L6 product they can't update or edit as advertised.  My experience with L6 is;  they won't let that scenario go unresolved for very long..

    • Like 1
  15. Big Sur is a huge update, so we all expected issues.  Regarding Helix and MacOS compatibility issues, this is the first time the OS refused to allow a forced install.  Wasn't expecting that!?   

  16. 4 hours ago, adamsguitar said:

     

    I suspect that if the 3.0 firmware entails significant changes to HX Edit or the other tools that they are planning on rolling them all out at the same time (presumably with the Big Sur fixes in them). It will likely just be a matter of downloading and installing the updated version of HX Edit to gain both Big Sur compatibility and update the firmware on the unit.

     

    Total speculation, though, obviously.

     

    I speculate there are new Helix owners coming on board every day.  Lot's of them use Mac OS and IOS DAW products and have been running Big Sur and have move into the latest's versions of those DAWs respectively.  L6 will want to get those folks healed asap.  As far as ver 3.0 goes, like all L6 updates, it'll come out when it comes out and the incompatibility issues will get fixed via parallel efforts.

  17. 18 hours ago, datacommando said:


    Fine. It just seems that there was also a lot of grumbling about how Big Sur rolled out. It was hardly perfect.
     

    Plus as I mentioned in a prior post, I would guess that Line 6 a busy at the moment getting ready to roll out their new firmware. Any intermediate fixes for bugs in Apple’s OS only detracts from the bigger thing. Consider the investment in making a temporary patch for HX Edit when the fully tested version is probably just over the horizon.

     

    Personally, I will wait.


    That’s not a great idea for L6, since the Big Sur folks wouldn’t be able to upgrade to the new Helix version.  At the moment L6 Editor and the Updater are locked out by Big Sur so any new Helix version would be unobtainable.  

  18. 2 hours ago, datacommando said:


    That’s correct, but from what I found out, the Gatekeeper issue with Big Sur was slightly different as the problem was more to do with Apple’s Servers.


    Quote:

    “The problem was determined to be server-related, with an issue on Apple's side preventing Apple's certificate checking function from working properly.”

     

    That contains a link to appleinsider.com

     

    Thanks, I was not aware of that. 

    • Thanks 1
×
×
  • Create New...