So far Mojave is treating me well- I’ve used Native Instruments, Waves, and a few other third party plugs and so far stuff seems pretty good.

I could be proven wrong quickly tho, knock on wood!

Thanks
I took the plunge and it’s working pretty great for me too.

Praise God🙏

Seems okay here since last night's upgrade - tested plugins like Waves, Korg, Helix Native, Superior Drummer and others etc - and all seem to be working. No issue with recording as the prompt for permission to access the microphone then added them to the Security preferences. Still testing but good so far.

Yes, working well for me also. If you perceive an issue with hardware, make sure you are up to date other drivers and firmware. Take the plunge, water is fine.

No issues at all with Mojave, it's running very smoothly with Studio One.

Just out of interest, even though I have a powerful computer with a 5K screen (iMac Pro) I didn't want to be wasting any CPU cycles (I'm not a tech nerd, and I may be wrong) but I set Studio One app to open in Low Resolution, and realtime scrolling, and manually scrolling is so much slicker. My eyes have adjusted to the not so good screen display (it's still very good, but obviously not in 5K.

You can tell Mojave to do this by selecting the Studio One app in the finder and then choosing 'Get Info' from the file menu, or just use command I

It may make a difference with people using MacBooks, you could always try it and see if it makes a difference for you.

Best
Scott

Thanks everyone👍

I installed Mojave yesterday on my MacBook Pro and Valhalla VintageVerb VST is now crashing S1 when opening a project containing it. I have disabled it (renamed VST) and S1 opens now. I am using the AU version of the plug in instead with no problems.

I have let Valhalla know (super-quick response to the support ticket) and they are looking at it. I will keep you updated.

Im now getting a message on S1 startup.....Studio One would like access you contacts ?

Denied ...

I spoke to soon. Everything was great until I tried to use my line 6 to reamp. I updated my drivers and basically panicked thinking somehow my line 6 or my Saffire Pro 40 was fried. Nope, I’m not getting any input from external sources other than Midi stuff. None of my hardware is being read. I’m restoring from my time capsule right now.

You have denied access to your microphone. When doing that you deny access to ALL audio inputs. Just make sure to enable the microphone input and everything should start working again.

frank.crow wroteI spoke to soon. Everything was great until I tried to use my line 6 to reamp. I updated my drivers and basically panicked thinking somehow my line 6 or my Saffire Pro 40 was fried. Nope, I’m not getting any input from external sources other than Midi stuff. None of my hardware is being read. I’m restoring from my time capsule right now.

This is due to a bug in the rewire component in studioone triggering this popup. Presonus needs to update this component.

timmorris wroteIm now getting a message on S1 startup.....Studio One would like access you contacts ?

Denied ...

roblof wroteYou have denied access to your microphone. When doing that you deny access to ALL audio inputs. Just make sure to enable the microphone input and everything should start working again.

frank.crow wroteI spoke to soon. Everything was great until I tried to use my line 6 to reamp. I updated my drivers and basically panicked thinking somehow my line 6 or my Saffire Pro 40 was fried. Nope, I’m not getting any input from external sources other than Midi stuff. None of my hardware is being read. I’m restoring from my time capsule right now.

Aaaaaaaargh🤮

I can’t believe I made such a boneheaded mistake. Yes, I specifically remember denying the microphone access too. I just spent forever restoring from time capsule and even had to go out and buy a corded mouse.

PS
I did see a little note while updating my Line 6 drivers that said something about a new protocol for those drivers/ permissions from High Sierra moving forward. Would you happen to know anything about that?

Had a few problems last night with the cursor tools not switching back when requested - both in Arrange page and Edit windows - never had this before so not sure if this is a S1 4.1 issue or Mojave - never had this before. I will continue to test and if necessary submit a bug report. Anyone else noticed this? The cursor seems stuck on a function (even in Smart cursor mode) so you try to change to cut or pencil, or general cursor and it appears to hang on the last tool - and the comping cursor does not always show up initially when editing takes, and the switch from cross hair to arrow in the main track also seems stuck on the previous tool.

I’m not sure of what you mean but what’s new with Mojave is that an application/driver will no longer gain access to your personal data like contacts, email, etc, including video and audio access, to protect you from malicious apps getting access to stuff it shouldn’t.

frank.crow wroteI did see a little note while updating my Line 6 drivers that said something about a new protocol for those drivers/ permissions from High Sierra moving forward. Would you happen to know anything about that?

i cant find my studio one vsts in mojave. any ideas. would love some feedback.

My mid2012 Macbook pro (16GB ram, 1T flash-drive) with Mojave and s1 is getting very sluggish when any multichannel audio-interface (>2 channels) is installed. Everything works eventually, but to start s1 may take 3-5 minutes. I don't think s1 is at fault because even a simple audio/video-app like the vlc-player is also slow. At times it feels like there is something at miss with i/o in general as any attempt to access the hard-drive sometimes can be very slow. Switched back to the older OS an every is OK again.

frank.crow wroteAaaaaaaargh🤮

I can’t believe I made such a boneheaded mistake. Yes, I specifically remember denying the microphone access too. I just spent forever restoring from time capsule and even had to go out and buy a corded mouse.

I do not agree you're one. I think the real boneheads came up with the idea to prevent a DAW from getting audio inputs into the system where it specifically asks to use your build in computer microphone. I think that is .

I also wonder how many hours are wasted around the planet that cannot be spend again doing something musically creative with this utter stupid mechanism. I feel that I missed an email to all Studio One users with a note from PreSonus to closely pay attention to enable this.

Why hasn't PreSonus updated the ReWire Support component so that it no longer seeks access to Contacts? And why would the ReWire Support component want access to my Contacts in the first place? It would appear to me that the ReWire Support component in Studio One has ALWAYS gotten access to Contacts, without having to ask for it, UNTL the new security protocols came out in macOS Mojave. What do you suppose the ReWire Support component has been doing with access to Contacts all this time?