You happy with Studio One 3?

[flugel45]

I was getting cpu spikes in this update until I unchecked enable low latency for instruments. Drop out protection set to minimum. Installed asio4all 256 samples.

I was using studio one 3.2 with stock windows driver just fine. Then comes this whole low latency 3.5 update. I couldn't get the spikes to resolve no matter what setting so went back to an earlier version. Thankfully somehow it is no longer an issue for me but still took trial and error to get rid of them. Hopefully they still consider this a bug and will put more work into it.

What sound card are you using? Can't tell from your comment if you're using asio4all as a workaround...

When you say "Studio One 3.2 with stock windows driver just fine" what are you referring to? Sound card drivers or something else?

[OreoSplitter]

I was getting cpu spikes in this update until I unchecked enable low latency for instruments. Drop out protection set to minimum. Installed asio4all 256 samples.

I was using studio one 3.2 with stock windows driver just fine. Then comes this whole low latency 3.5 update. I couldn't get the spikes to resolve no matter what setting so went back to an earlier version. Thankfully somehow it is no longer an issue for me but still took trial and error to get rid of them. Hopefully they still consider this a bug and will put more work into it.

What sound card are you using? Can't tell from your comment if you're using asio4all as a workaround...

When you say "Studio One 3.2 with stock windows driver just fine" what are you referring to? Sound card drivers or something else?

I don't have a dedicated sound card. Was using the stock driver, as in, the microsoft windows driver. I am using a tablet, acer switch 12. Basically, ever since 3.5 I had cpu spikes. Even installing a fresh copy of Studio one 3 version 3.5.2 I had cpu spike with a singe vst (zerbra) playing. I don't have an audio interface to make use of the zero latency kick they are so proud of, but to me, it has screwed over the regular users in terms of stability out of the box. The program shouldn't need tweaking to get stable cpu performance with the default settings. Regardless I am good but I can understand how others are having issues.

[nIGhT-SoN]

Do you use Asio4All? If not, you should. Also, you have to understand how the new features work, those can make your day or break it. The low latency recording is really amazing, I was never able to record through plugins or use plugins for monitoring without having huge latency. Now it's all possible and it works like a charm.

Keep in mind, if you have low latency monitoring, the track that has record button armed, will go into low latency this leading to an increase of cpu usage while it's armed. Try deactivating the record button on all tracks and see if you still have spike issues. If you don't, you can just deactivate the low latency feature and use it like in previous versions. To do that you just have to deactivate the Z button on the master track (that's for audio tracks) and for instrument tracks you have to open the instrument panel on the left of the mixer and it will open a new panel. At top of it there will be another Z button, deactivate it too (that's the low latency button for VSTis). That's all. When you want to monitor with lower latency you can activate the corresponding Z button.

If you really want to use it as before, and by that meaning you changing the latency, In Options -> Audio Setup set Device Block Size to what you used before then switch to the Processing tab. Here set the Dropout Protection to Minimum and make sure Enable low latency monitoring for instruments is unchecked. That should take care of it.

LE: You don't need a special interface to use Low Latency Monitoring that came with 3.5. It can be used with any card as long as it has decent drivers. Hell, it works with my E-MU 0404 USB which has not so good drivers. Also I would suggest you check you system latency with LatencyMon.

[flugel45]

.... You don't need a special interface to use Low Latency Monitoring that came with 3.5. It can be used with any card as long as it has decent drivers. Hell, it works with my E-MU 0404 USB which has not so good drivers. Also I would suggest you check you system latency with LatencyMon.

This is the key phrase here (In bold).

Just because it worked with your E-MU card, doesn't mean it will work with any onboard sound chip. That E-MU card had a lot of R&D behind it, and cost E-MU a lot more than the 30 cents or so these cheap sound cards cost their manufacturer.

Bottom line, if you don't have a decent audio interface (that comes with native ASIO drivers), you shouldn't assume any problems are caused by something else -- like the DAW, for instance. The issues are very likely due to the crap drivers for your cheap sound card.

Before someone jumps in saying they've used an onboard sound card with their DAW for years -- well, that's great. Yes, it can work with some configurations, But the drivers will be a problem MOST OF THE TIME. That's why the vast majority of people here have invested in an interface with proper drivers... That's just a fact of DAW recording.

[bundoo]

would like more editing / processing options

pitch bend on audio
proper tape style timestretch / resizing of regions
transpose up and down with key command (with a variety of timestretch options including tape)

thats about it

[c_voltage]

I pretty happy, but the only sometimes seems strange to me indifference relation of developers guys to built in tools, when they are broken, i speak about Mojito (was very usable synth especially for basses, and easy to cpu), so already a bunch of versions they can't repair Mojito's sub-osc, which generate saw wave instead sinus, you can compare how it works in v2. You can say that exists ocean of other synths, but i can't understand anyway, why it's so difficult to repair. (Here it's not that the criticality of the problem, but the principle, in a some sense showing the product support).

The same about some detected bugs related with old (pre i5-i7) processors, which also still not fixed after the many versions, though in oficial tech specs specify core2duo as compatible.

[Drogers]

Absolutely. I also own FLStudio and Cubase. FLStudio, I still use for certain projects, although I use it as a plugin directly in S1. Studio One is intuitive, stable and fast running on my i7 laptop with Windows 10. Great product that is getting better with every release.

[Robmobius]

Not particularly... CPU is very high. Workflow is not quite as fast as Ableton. I'd like to see some new effects.

Still getting strange crashes (and losing work) and when closing down a tune it shuts down the whole program. This was supposed to be fixed a few times now, but clearly isn't (for me anyway).

I'm staying with Ableton for the foreseeable future.

[szurcio]

CPU is still too high? I had the impression they finally fixed that in version 3.5 (?)

[starflakeprj]

I wouldn't say CPU usage is high. Comparing to my other DAWs FL Studio (12.5) and Reason (10) are using more CPU power than Studio One. Bitwig is about the same, and Reaper use less. Renoise I can't really tell, but my feeling is about the same or a little bit more CPU heavy.

They did a great job with the CPU load in v3.5, but mostly they got rid of the CPU spikes (which were really annoying). My problem with Studio One nowadays is that when a plugin is crashing, it's bringing the host along with it. If a plugin is crashing in Bitwig or Reason, it's only the plugin crashing.

[Robmobius]

CPU is still too high? I had the impression they finally fixed that in version 3.5 (?)

Well... I'm able to run way more instances of soft synths in Ableton. Unless it's just those particular synths that have some kind of issue. I'm running the latest version of it too. I dunno...

But there are other niggles as well. Especially, the crashing... When ableton crashes (which is quite rare) you only ever lose a step or two but it can be a pain with S1.

[braj]

I switched back to Reaper earlier this year, I'm happy with that decision, I wanted to edit video with my audio and Reaper just handles my specific needs better, and has better overall CPU performance. If it were just for audio I could have gone either way, but video was the deciding factor and I also needed cash, so Studio One got sold. I didn't use the Studio One instruments or rely on anything specific to Studio One so it was an easy decision.

[Muziksculp]

Hi,

I'm really loving Studio One Pro 3, mostly for the super fast workflow. I switched to Studio One from Cubase, which has a lot more features, bells and whistles, and a much more mature midi editing environment, but all of that didn't really matter much to me. Studio One was like finally trying the perfect pair of shoes. It was so natural, fast, and easy to feel comfortable with it, it's like it was designed for my brain, and the way I would go about doing things, Cubase never felt natural, and the workflow was a bit strange to the way I think.

My hopes are that Presonus will add some new features, and improvements to Studio One in version 4, especially in the area of midi, and improvements related to scoring to video, that will make Studio One the natural choice for film & media composers. Given that it already has very good audio editing features, I am quite confident the focus of improvements will be in the midi area for version 4.

Funny, but every time I launch Cubase, instead of Studio One, to work on a new project, I feel like I'm wearing a pair of uncomfortable shoes, and after a few minutes, take them off, launch Studio One, and I'm back being productive again.

[szurcio]

I heard that the Studio One X scripts (http://forums.narechk.net/viewtopic.php?t=25) improve some S1 deficiencies in the midi area.

[beatmangler443]

My hope is that Presonus continue to focus on fixing bugs and not get carried away by adding 100 plus like what steinberg use to do in the past (neglect fixing the bugs, and I use to own it). I want it to be a great tool for music producers, and engineers. All that film/composer features can wait.