hi there
passed 4 days since I bought sublab from PB with no luck to authorise (something is up 8)
what can I do to use what I bought ? I have written multiple notes to support and today Ellis gave me the latest beta 3 with is exactly the same with cannot be authorised… I m out of my nerves atm to be sincerely honest hahhahahahaa
sjcongo@gmail.com
1 Like
Hey @sjcongo
Can you send me your activation code via pm?
Also can you check this section of the support site, esp point 7:
PM sent!
Gavin.
@sjcongo just deleted your post as it was showing your activation code…
I’ve just looked in our database and that code doesn’t exist. Let me look into it more and I’ll get back asap
Ok, @sjcongo can you try again now? I’ve manually added the code to the database…
Ok, i will try asap… now i m with my dogs at the vet… best regards
1 Like
Well wishes to the doggo!
Hello
Now is working… Thanks a lot !!!
1 Like
Thanks Gavin ! She s ok thanks again 
1 Like
This is the final straw. I appreciate the awesome work FAW have done in making this phenomenal instrument. But it’s unparalleled how every single one of my many random VST’s from both independent to major plugin makers all work perfectly fine with the update (even if they’re not officially supported). And due to this instrument alone, I have had to wipe out my entire laptop to downgrade the OS, and manually reinstall each plugin every time I open a previous session to complete my projects. No matter how amazing the sound, this reliability issue has caused me to literally spend 90% of my limited session hours just troubleshooting instead of actually working on music. It’s been a great ride, but I can no longer use Sublab on my projects moving forward. I’m genuinely very disheartened about this, because it was in my absolute top 3 indispensable instruments in every one of my projects. These Beta’s are way too late and overdue. The new macOS update was announced nearly 6 months ago. I’m not a programmer. I don’t understand the architecture of how this stuff works. I’m sure you guys are working hard in making a stable release for Sequoia, but I’ve never had to experience any of this in my 10+ years of producing music. Thanks for everything, FAW.
@Kch,
I totally get what your saying.
We’re also frustrated when an API we use internally suddenly stops working and we have to spend weeks working through the issue.
I think its resolved now though? Also we have no problem in issuing you a full refund for SubLab and XL.
Thanks,
Gavin.
I have just bought a new m4 mac and it comes with SEQ 15.1, I purchased SubLab and XL from PB and Sublab gives me this rubbish…The only one of the 1400+ plugins on my system:
Hey @dre
Did you download this installer? https://cdn.futureaudioworkshop.com/downloads/sublab/SubLab-Installer-1.0.9-Sequoia-macOS-Release-181124.zip
Also, please make sure to quit your DAW before running the installer, then reboot your mac afterwards.
Let me know 
SubLab XL is working for you, correct?
I was getting a scan error initially, which prompted me to run the standalone app that gave me the above errror. I have installed the link you gave and the error has gone, maybe give that version to plugin boutique too…
1 Like
Hey @dre glad to hear that you’re up and running now! We’ve provided these installers to PIB, I’ll reach out again and make sure that they’re updating them.
1 Like
Hey @Gavin_FAW I’m using OSX 15.1.1 I installed the Sub XL Sequoia Fix and my standalone logs in fine but in Logic Pro it won’t let me click launch. It just hangs. When I try to re-open it I get the same login screen.