• Hi and welcome to the Studio One User Forum!

    Please note that this is an independent, user-driven forum and is not endorsed by, affiliated with, or maintained by PreSonus. Learn more in the Welcome thread!

If you are having a problem logging into Studio One, please take a look at this article

Vocalpoint said:
What is even more confusing is that I did exactly nothing (outside of submitting a ticket) - and have the same expiry date - for a license that should not have ANY expiry date:

View attachment 1892

Also heard back from support with a bizarre solution stating that all I needed to do was "re-activate" the software.

However on Friday when I experienced the license lockout for the first time - I simply waited about 30 minutes, tried S1 again and it fired right up - so I did not have to "do" anything.

I am now really concerned about the "expiry" listed in the screencap above. Logically - I have not renewed my annual updates and therefore should be running on a "forever" perpetual license - which as I understand it - has no expiry.

So this date above is a mystery - and call me crazy - but whatever was done behind the scenes on 10-11-2025 to "fix" the bulk of us not being able to get into S1 - seems to now have the ability to start this chaos all over again on Oct 9, 2026.

Overall - it appears that Presonus really did not write this whole expiry process correctly and certainly has not tested it.

VP
Click to expand...

Does that give substance to it being a Server or database update transaction being a little slow?

But the rolling 12 month date does seem odd if it's a perpetual license? Couldn't agree more that there are some gremlins in the system.
Whatever is going on is very disorganised and if folk had been forwarned some of the concern could have been eased.

I just hope it all gets sorted for ppl.

Best of regards

Oh Ps. the "re-activate" would overwrite your "settings" again, yes you needent bother it gets done automatically?
😖😖
 
sintil8 said:
Does that give substance to it being a Server or database update transaction being a little slow?

But the rolling 12 month date does seem odd if it's a perpetual license? Couldn't agree more that there are some gremlins in the system.
Whatever is going on is very disorganised and if folk had been forwarned some of the concern could have been eased.

Oh Ps. the "re-activate" would overwrite your "settings" again, yes you needent bother it gets done automatically?
😖😖
Click to expand...

This whole thing (and with the speed in which it suddenly "resolved" itself) last Friday appears to be some sort of stopgap measure where the product authorization database was updated in the back end and then propagated out to us.

I do not believe this mysterious "09.10.2026" DB date has any actual meaning - it is simply there to ensure NO more failures while Presonus figures just what is going on here.

I am having a very hard time understanding how this system could have been in play for an entire year without incident and then suddenly as soon as Oct 9, 2025 comes screaming in - chaos ensues.

This shows a great lack of Q&A and poor support for a system that was promoted to be the "future" of S1 last September. With an entire year to test this thing - Oct 9 should have come and went without so much as a whimper.

I also cannot honestly express how furious I am that after any attempt to "re-authorize" (mind you in my case there was none at all) - simply starting S1 30 minutes after the intial error this past Friday - how this application thinks it is cool to completely erase ALL my customizations.

Took me 20 minutes to recover the backup and put everything right again. So very sad how this great app has seemed to have fallen.

VP
 
@Vocalpoint
I was hoping it might slip by without a murmer, but I understand "hope" was the last thing out of Pandoras box. Backup is king (keep 2 one active)
is the maxim. We used to say that if data does not exist in 3 places at once it does not exist!

Crazy as it sounds SO1 works so well, yet the web is full of gremlins. I'm not too concerned as surely all this will be rectified at some point.

Take care all the best.
 
I wonder if it was one of those things where the team said 'no worries; we've got a year to sort this out' and then forgot about it! I hope that shifting the date a year doesn't mean they're going to forget about it again... And having all your customisations negated by a reactivation (at either end) is just not cool on any level. Perhaps Fender has made PreSonus take too many eyes off the ball while they've been developing Fender Studio (and whatever else is waiting in the wings)?
 
TimC340 said:
I wonder if it was one of those things where the team said 'no worries; we've got a year to sort this out' and then forgot about it! I hope that shifting the date a year doesn't mean they're going to forget about it again... And having all your customisations negated by a reactivation (at either end) is just not cool on any level. Perhaps Fender has made PreSonus take too many eyes off the ball while they've been developing Fender Studio (and whatever else is waiting in the wings)?
Click to expand...

Have no idea but it would be prudent for someone (anyone?) to at least issue an "official" communication as to what is going on.

This discussion appears to be rampant across a number of different forums and it is clear that there is a major issue going on out there.

VP
 
Yes, this (the Fender/PreSonus login unification) should have been done with a lot of notice and even more testing. NI have taken ages over their integration beween iZotope and NI logins, and that cautious approach is the correct one.
 
TimC340 said:
Yes, this (the Fender/PreSonus login unification) should have been done with a lot of notice and even more testing. NI have taken ages over their integration beween iZotope and NI logins, and that cautious approach is the correct one.
Click to expand...
Yet, some of my Izotope stuff, albeit old versions, are not showing up in Native Access ?
I have yet to get round to raising a ticket with NI support as they all work but are beyond any update support, so it's not been a priority.
I suppose I should get it sorted, as I may want to update them at some point. I mention this whilst NI spending time over the Izotope integration their process may also be flawed...

At least NI gave plenty of notice to their user's

Best of regards
 
sintil8 said:
Yet, some of my Izotope stuff, albeit old versions, are not showing up in Native Access ?
Click to expand...

I can answer this one - the stuff you WILL see in NA for iZotope will only go back so far - regardless of what you had in your old iZotope Account.

The older versions of ALL iZotope software - used a much older installer technology that clashes with current requirements that Native Access uses to do it's updates.

So I you are expecting say - Ozone 5 to show up in Native Access - you will be waiting a long time.

VP
 
@Vocalpoint
Thanks for that, I will contact NI to sort out what action I need to take.
Could be an interesting exchange.

Take care got to do some real world stuff...later
 
It used to be I couldn't check for updates now I can't even launch Studio One Pro.
I am completly shut out of Studio One.
It wants me to activate the product but when I give it my credentials it doesn't activate the product.
There is an activate-offline option which will give you a code but it requires you to login at My.Presonus.com but guess what?
My.Presonus.com will not allow me to log in. The tail-chasing activity icon just spins and spins.

Does ANYONE have any useful info on this disaster??
 
Vocalpoint said:
[...]Have no idea but it would be prudent for someone (anyone?) to at least issue an "official" communication as to what is going on [...]VP
Click to expand...
Its nowhere near official, but it is something...
To view this content we will need your consent to set third party cookies.
For more detailed information, see our cookies page.
 
eon said:
And if you do this you get this auto response:

We apologize for the inconvenience; please log in to your account and create a support ticket via our support portal.
Click to expand...
Hmmzz, that was what Jonny Lipsham was referring to in the video.
 
I might actually have something useful to share, although my problem is yet to be resolved.

I called 225-216-7887 and instead of waiting in the queue I selected to have them call me.
Lo and behold within an hour this true professional (Shane) called. He couldn't help me directly because he's in the Fender group and deals with guitars and amps. But he did take my info and promised to forward it to the proper Presonus people for them to contact me.

This guy Shane is a hell of a nice guy and pro all the way. He did say that this issue is not the result of malware but directly associated with the "migration" of business systems from Presonus to Fender.

I know this is not much, but it's at least something.
Let's hope they resolve this mess soon.

As a side note, if you have Fender hardware issues, ask for him by name.
 
Gerran said:
Its nowhere near official, but it is something...
To view this content we will need your consent to set third party cookies.
For more detailed information, see our cookies page.
Click to expand...
So the Fender Presonus merging of data *is* causing the issue. I watched the first half of the video and it looks pretty close to what I imagined might be going on from what folk have posted on here.
Thanks for posting :cool:

Best regards
 
Ah, so that's why I don't still have an issue. I don't have a Fender account.

This world is not kind to guitarists!

;)
 
Gerran said:
Its nowhere near official, but it is something...
To view this content we will need your consent to set third party cookies.
For more detailed information, see our cookies page.
Click to expand...

1760423189514.png


1760423234477.png


1760423170851.png


I think this is the issue, at least for me (used an auto-generated password by Bitwarden).

So why on earth does the system accept "special characters" in the password if it "mess up the system"?
 
eon said:
View attachment 1895

View attachment 1896

View attachment 1894

I think this is the issue, at least for me (used an auto-generated password by Bitwarden).

So why on earth does the system accept "special characters" in the password if it "mess up the system"?
Click to expand...
The better question should be: Why does the system have a problem with specials characters? It shouldn‘t. Special characters should not be a problem to any system nowadays!
 
  • Like
Reactions: eon
You must log in or register to reply here.
Back
Top