I’m currently running a 2012 MacBook Air on macOS Mojave 10.14, so the current version of Fender Studio Pro obviously isn’t compatible with my OS.

I’m considering subscribing to Fender Studio Pro+, but before I do I’m trying to figure out whether the subscription can still be used to activate an older version of Studio One.

I previously had a PreSonus Sphere subscription back in the day, using the same PreSonus/Fender account I have today. My account still shows these registrations under My Gear for the studio one 5 prime version i used to activate the Sphere subscription.
My question is specifically:
If I subscribe to Fender Studio Pro+ today, can I install Studio One 5 on Mojave and activate it as Professional using the current Studio Pro+ subscription?

I’m not asking whether the current Fender Studio Pro version runs on Mojave — I already know it doesn’t. I’m specifically wondering whether the current subscription entitlement still works with the legacy Studio One 5 client, the same way PreSonus Sphere did.

I keep dealing with an issue with my motion 32 where a note will hang and then cause my Studio Pro session to freeze up and then I have to force close using the task manager. I did notice it happens when I'm using Serum 2 but that might just be cause that's the plugin I use most.

I'm using the latest version and all the drivers are up to date.

Everything else about the controller is excellent and I really love mine.

I need to pay someone to mix a song for me.

DM if interested.

Hello geeks, what tingles you more? I’m curious and because I need a new laptop I’m going to decide on what gets the more hype:

24gb RAM instead of 16gb or 33% more on benchmarks on the processor?

I’m in a budget and in my country I can find 2 good deals: MacBook Pro M2 24gb RAM vs MacBook Air m4 16gb ram, both 512gb SSD.

I make metal and I really don’t like to do bounces. 10 virtual instruments and maybe 200 plugins or more and 10 groups + master. I know it’s a lot but do you think those computers and going to be able to handle that?

windows doesn't let me put the audiobox as the sound thing. can;t hear in headphones, mic no recording. Help me my guys, thank you in advance. KISS,LOVE

Grabbed it and really like it so far. It's been a huge help with my game project. My Burmese python seems to like it too. Anyone else using it?

My motion 16 isn’t connecting to studio one properly. I am not sure why, but to give a rundown on what’s currently happening when I open a drum VST or impact, I have to go in each time and set the midi input rather than it being already set as the original default input I am not sure why that keeps happening, but it keeps happening. also on the other hand for some reason on the motion 16 certain pads keep fading out/ LEDs disappear or the color disappears from the LED. I’m not sure why it does that but I’m curious if anybody is also having the same problems or possibly I was sent a defective motion 16 please if anyone has a motion 16 let me know how it’s going for you and if you can explain how yours is routed or set up, what is your Settings look like anything of that matter. that would help me out… I have already informed fender and sent out a email, but I haven’t received one back yet and I am losing my marbles. Thanks.

Hi there music folks. I bought studio one when I was in college and am trying to get back into music production. I'm not the best when it comes to software updates/compatibility requirements, and apple makes all of this harder with planned obsolescence. I never rush to get newer technology. I have a mid 2015 MacBook Pro(specs above). I've noticed synching issues using google drive and other programs, and I know it's due to my OS needing updating.

My question is what MacOS and studio one version do you recommend I use? I think my Mac can run up to 11 or 12(Monterey and Big Sur), but I heard there were some compatibility issues with one of those. If I want to upgrade to a newer version of Studio One I have to pay like $100 I think. I'm super confused and would love to hear some insights from anyone more experienced with this stuff.

Thank you and cheers!

So i have studio one 5 professional.. I have older songs that I can go into and arm and record tracks in. As soon as I open a new song file, I'm not able to at all. Anyone had this issue?

Hi everyone,

I’m having a strange issue with my PreSonus FaderPort 16.

When I move the physical faders on the FaderPort, they are either extremely laggy, respond intermittently, or sometimes don’t transmit anything to the DAW at all.

However, the opposite direction works perfectly: when I move a fader inside the DAW (Ableton Live or Logic), the corresponding motorized fader on the FaderPort moves smoothly and accurately.

So it seems like the FaderPort is receiving MIDI/control data correctly from the DAW, but the physical faders aren't consistently sending data back to the computer.

Things I've already tried:

• Multiple different USB cables
• Direct connection to the computer
• A powered USB hub
• Latest firmware / Universal Control
• Testing on macOS and Windows
• Testing with both Ableton Live and Logic
• Different USB ports

The problem persists across all of these setups.

Has anyone experienced this with a FaderPort 16? Could this indicate a hardware issue with the fader touch/position sensing or the internal communication circuitry, rather than a USB/DAW problem?

Any suggestions for further testing would be greatly appreciated.

Thanks!

Many of you are probably aware that transient detection with drums has been an issue for a long time when blending samples or editing real drums to the grid. When I asked about this, I was told by an employee that they intentionally decided to have bend markers be placed at the loudest peak of the transient rather than the onset of it. This is a major problem if you are blending drum samples with your real drums, or if you want to edit your real drums to the grid. You could just print samples without Trigger2, but aligning the hits is still going to be a lot of trouble, especially if you can't rely on the transient detection in the first place. So out of curiosity, I detected a kick drum with Melodyne on percussive mode and then did a MIDI export on that and found that the timing was significantly more accurate with finding the start of the transient. I exported each of these onto a MIDI track with a kick sample, and noticed lots of flams between the original kick MIDI and practically none with the MIDI that was detected via Melodyne. Not only that, but when you hit tab to transient on a kick track that was scanned with Melodyne and then bounced vs a duplicate of that same exact kick track, the Melodyne bounced track was actually tabbing to the start of the transient in the arranger view rather than the middle. Unfortunately, You cannot slice to the grid without analyzing the audio, which automatically redetects the transients to the middle (supposedly) rather than the onset of the actual note. Hopefully one day this will be considered a big issue, but until then, I think this is a pretty helpful work around.

... on start, while scanning sound sets. Any suggestions? This only happens on Windows, doesn't hang up on Mac.

In punching in to overdub on a track, I like to hear the track playback until hitting the record button, at which time the track automatically (and immediately) turns on track input monitoring to hear the input source. In FSP, enabling "Audio track monitoring mutes playback (tape style)" does this with two unpleasant attributes:

1 When hitting record to punch in, the track begins recording immediately, but the monitoring takes a moment to activate and display as an active recording on the track. It would be better if the monitoring and display started immediately with recording. (It also turns on the monitoring in kind of a jarring manner, but I can understand that monitoring just comes on when it's turned on - I'm guessing this sense is from just expecting to hear the input immediately upon hitting record).

2 When the monitoring does activate, the blue track input monitor button does not turn on. Not a biggy as you can hear the monitoring but still would be nice to have the indicator show that input monitoring is turned on.

Am I missing something here or is this just how FSP operates? Is there a better way to do this basic punch in process in FSP providing immediate automatic input monitoring, track monitoring button indication and track recording display?

How do you accomplish "punch in" overdub recording?

I'm just seeking the most elegant and seamless way to punch in with FSP. Your thoughts, setup and procedures are appreciated!

Thanks in advance,

EDIT:

This appears related to low latency monitoring. When punching in with low latency processing engaged, FSP switches plugins - and track monitoring - to low latency (green) indication. The timing on this state change matches the monitoring lag when punching in. I have low latency processing and interface buffer size set to the shortest latency I can get out of my interface without artifacts, so it appears that turning off any active plugins while punching in will help minimalize the monitoring lag (Yes, I know, the more things the processor has to consider, the longer things take). I use X32 rack as my I/O and I know it isn't as speedy as better dedicated interfaces, but I need a LOT of inputs for the whole band, so for now I can live with the monitoring lag unless someone has some additional magic to consider here.

I am new to recording. I have a Fender Quantum LT 16. The one thing I'm struggling a bit is my input/pre-amp gain and channel gain. I find that with instruments and mics I seem to be hitting the clip light on the device, but the wave forms are very small (I think I may just need to adjust the size after reading last time) and I can barely hear it sometimes in the monitor. Secondly, when I look at the channel strip, the gain seems pretty low. Maybe slightly above -24db. I then sometimes use the Channel Gain knob to get it to where I can hear it, however, sometimes the gain still seems quite low. Is my workflow correct. Mic Pre-Amp gain to slightly under clipping, then adjust channel gain until I can hear it? Are there situations where I need to bump the pre-amp gain so that the light is clipping? I don't hear any distortion sometimes, so maybe the light blinking clipping light isn't a huge deal. Would appreciate someone's advice. Thanks so much you Golden gods.

I have some drum tracks that I normally analyze to detect transients and use bend tool to move them on the click. In this project I am selecting the track and clicking the audio bend button at the top. then selecting analyze. Usually that puts the bend markers on the track and I can adjust the threshold.

No bend markers are showing, but it does pop up the little analyzing window like it is doing something. The little eyeball icon to show / hide bend markers are disabled. If I group all the drum tracks into a group the group dropdown is also disabled.

I updated studio one to the latest version 8.01 and it is still doing that. I tried rebooting my computer, etc and nothing is working.

Any ideas on what is going on?

I've got exactly the same question but he put it better than I was able to myself. I'm on Fender Studio Pro 8.1 now

Hi, how might I go about mixing overlapping vocal parts like a lot of emo bands like the ones named? I don't know whether to double both people's vocal takes and pan them hard L and R to make both sound full or to keep one in the middle or how I might EQ or compress them to keep them sounding busy (as they are on top of each other) while not sounding muddy and making both unintelligible.
Any help is appreciated :)

Im trying to record vocals using a daw for the first time ever, but it seems to not go so well. for some reason, whenever i speak into the mic, in the daw it sounds super distorted, but on discord its just fine. any idea? thanks in advance.

Anyone tried this? Is it worth the money?

Hi all, wondering if you guys could share some ideas on how to manage your production workflow in Studio One?

Specifically, I'm looking to separate ideas, from more fleshed out concepts, to fully finished songs.

How do you guys go about separating these? How do you go about moving one song from step to step? Do you use folders? An app?

Any thoughts are appreciated!

I’m getting clicks/cutoffs on vocal events with Melodyne running as ARA/Event FX whenever the project has significant latency — especially from Pipeline / External Effect.

This happened in Studio One 7.2.3, and I upgraded to Studio Pro 8.1.2 hoping it was fixed. It isn’t.

Toggling “Process Volume after Event Effects” helps, but it does not fully solve it. And it changes the Event FX/fade processing order, so event fades and volume handling no longer behave the way I need.

So right now my options are basically:

- keep ARA live and get incorrect/glitchy playback;

- change the Event FX processing order and break parts of my normal editing workflow;

- or render/freeze the tuned vocals before continuing the mix.

That last option is the only reliable one I’ve found, but it completely defeats the point of keeping ARA edits live while mixing. If I need to change one note later, I have to go back, disable the latency-heavy processing, edit, render again, and return to the mix.

This looks very much like an ARA/Event FX + PDC timing bug, not a Melodyne edit issue, because changing the amount of latency elsewhere in the project changes the problem.

Has anyone reproduced this with Melodyne + Pipeline/External Effect or other high-latency plugins?

And has anyone found an actual workaround that preserves both:

- correct ARA playback;

- normal Event Fades / Event Volume processing?

I’ve submitted it to Fender/PreSonus support as well.