Find answers, ask questions, and connect with our
community around the world.

Source-Connect Certification Courses Forums Source-Nexus Source Nexus Control DEAD?!

  • Source Nexus Control DEAD?!

     Gregory updated 1 month, 4 weeks ago 3 Members · 9 Posts
  • Gregory

    June 15, 2021 at 7:26 pm

    Hi there! I’m a little concerned as I’ve been a Source Nexus Pro user for quite sometime, but never had the opportunity to use it until this age of pandemia we’re all in together.

    I noticed I can’t find the Source Nexus Control app for sale any longer on the site, and when I purchased it via a Source Connect partner (, they promptly reimbursed me.

    Oddly enough, I’m able to work with a fully operating trial version, but am I missing something? I’ve got potential business riding on this feature (multi-conferencing for audio post), and I’m really hoping there’s some new replacement or solution within the Source Elements realm.

  • Gregory

    June 15, 2021 at 11:28 pm

    Ah. Nevermind! It seems it’s been included in the 1.3 update!

    Thanks anyway!

  • mattrixx

    June 16, 2021 at 12:52 am

    Yes, it’s included in Nexus 1.3, but it seems there’s a big “gotcha” if you’ve been using it for a while and then upgrade.

    It hoses your old settings.

    Then if you rebuild them, with exactly the same names etc etc…. and then load up your previous Pro Tools Ultimate (communications template in my case) session, it still doesn’t see them, requiring you to go through and re-assign all the Nexus plugins.

    A real PITA and I wouldn’t have upgraded if I knew this.

    Which is kind of ironic, as interoperability between systems, was the only reason I updated.

    Would love to hear SourceElements take on all this ???



    • mattrixx

      June 16, 2021 at 1:01 am

      **also meant to add… the when you reload up said previous session as above, you’ll get full range feedback through all you’re Nexus routings, so you’d better have you monitors turned down. Damn. Damage warning!!

  • mattrixx

    June 16, 2021 at 2:55 am

    Just thought I had better follow up, that the new update should not have overwritten my previously setup and named drivers.

    Apparently I was the first of a lot of people to update, that has run into this problem.

    Working with support to try to get to the bottom of why, but will report more as I know more.

    • Gregory

      June 16, 2021 at 2:59 am

      Thanks so much for all the great feedback! I’m enjoying the trial in the meantime. I hope you get good news from support that you can share!

      I still have 14 days remaining so there’s time.

  • Kristie

    June 18, 2021 at 4:17 am

    Unfortunately there were some unexpected results for some users upgrading from Source-Nexus 1.2 A warning has now been added to the installer until this is resolved.

    You can see the list of known issues here:

    The Source-Nexus devs are working very hard on a fix for this.

    • Gregory

      June 18, 2021 at 8:34 am

      Hi Kristie,

      I’m discovering that as well since I impatiently made the plunge a few days ago. The trial still runs like a dream though, so it seems I’m in the clear, at least for now.

      Thanks for the link to the known issues page. I’ll be sure to check it out. I appreciate you!

    • Gregory

      August 25, 2021 at 11:52 am

      Hi Kristie,

      Happy updates! I’m all squared away now, but I think it’s important to document what I did this time on my own (without contacting support) to get things going.

      The first step that wasn’t immediately clear was re-downloading the old (legacy) installers of both Nexus Pro 1.2x as well as the stand alone Nexus Pro Control. I have this habit of replying yes when my mac asks me to trash installers.

      Once I knew I was free and clear, I discovered the NEW Nexus Pro 1.3 installer AFTER I transferred the license to my iLok.

      I then followed the instructions in the installer, making sure to select the fresh install option and everything is working great now!

      It sucks that I have to re-create my drivers via the control panel, but it’s a minor nuisance compared to being utterly confused before.

      Thanks again for send the link of known issues back in June. I think I would’ve been lost without that resource.

Viewing 1 - 5 of 5 replies

Original Post
0 of 0 posts June 2018