I ve been using it for almost two weeks now and surely it is great.
But I have a couple of worries. Firstly I get some CPU spikes even if I only just start a project. And increasing block size doesnt help. Is this a known issue? From what I gather it might be, quite a lot of forum questions on presonus website. Is this something you guys experienced too?
Also, I just put my Bass station VST, mono version and the strangest thing happened. All of the sound was panned hard to the left. When I tried to use in a mixer to see what happens, it just acted as a volume knob. Maybe I need to set up something in particular? I never had any problems when using bass station in live

 

I've been using Studio One a while now without problems on my machine. I do realize that on some machines according to the video card configuration you can end up with spikes. However, you can check Presonus support if you have a problem. I always make it a point of purchasing my DAWs for this exact scenario. If anything goes wrong, I have a right to email or call them and have them sort out the issue.

 

+1, you can also join the S1 forum without needing to buy the software. You may be able to get some help there as well, just don't tell them you are using non legit software. You do know they also have a free version? might be worth seeing if you get the same problems with that and then reporting back to them with your problems

 

I've had problems including ridiculously high CPU consumption, MIDI timing issues, etc. I'm running it on an older computer but that to me is no excuse when Cubase 5 runs great and that was built when...2009? WTF?

 

What MrMusic says about spikes and gfx cards could be correct, if in Studio one you see spikes on CPU, Memory and Disc in the usage meter then this is likely the cause.
ATi cards have high latency by default using something like PCI Latency tool you can check pci bus latency and adjust.
PCI Latency tool does not work on all systems, it locks my computer up as soon as i open the program...
Another application that I use is double-dawg to adjust... however with the free version you need to set the timing everytime you boot.
Double-Dawg's web site no longer exists, so if you cant find this util i can send it to you, i dont have the full version.

You should also be able to do this with a registry entry, but i didnt try this yet and would need to research to tell you which entry needs changing!

 

The panning problem could be that you're using a mono plugin on a stereo track?

 

Ehm, I figure it's an instrument track so it doesn't have any audio inputs? I thought the same but I think it's a VSTi/MIDI track, not an FX VST or audio track. Plus, I think you mean "audio input" not mono plug-in. A mono plug-in should export sound at the center (except if you pan it).

 

Right guys, maybe I can give something back, you re always all really helpful. I found this presonus page
http://support.presonus.com/entries/119099-optimizing-your-computer-for-audio-windows-vista-windows-7
I followed all the steps exactly and there are no more cpu spikes so far!!! I tested especially with my vanguard which was causing most of the problems and it runs beautifully. So Catalyst, maybe you ought to give S One another go. Now the down side is that my windows 7 looks like Windows 3.1 . Apparently in order to optimize your computer for audio it has to look like shit. But that might not be the reason. There were quite a few steps I had to do. It took me about a couple of hours. And it says that a decent graphics card can make all the little windows animations run by itself. I have some 1gb nvidia, not sure which one, but this should be ok, no? Maybe I ll try putting a decent theme again and see if it changes anything. So all you people out there who have problems with spikes, deinitely try this.

However that bass station is still panned hard left. Really dont know what that is about. I mean its a mono version of the plugin, but are Studio One instrument tracks automatically stereo? I ve managed to get around this by putting that Binaural pan plug in and turning it all the way to 0% But I still wonder why this happened. Never had this problem in live with this synth

 

Thanks so much don_questo I will give that a shot. It's a real shame that I've been having issues because I really do like Studio One, it has some intuitive features for sure. Thanks again.

 

Yes, this is definetely not a S1 problem, because i haven't faced such a problem ever, is just a user or a hardware problem, but not the daw itself.

And Catalyst, when you compare the old 2009 C5 with the new S1, i think is pretty logical that a old daw to work on weak systems, due to the fact that it was made to be workable to the 2009 era systems, but the problems you had with S1 are clearly not because of the S1 itself, there was something else mate , if it was because of S1, then all the S1 users whould've face the same problem as yours. *yes*

Cheers

 

Stripping down the graphics won't give you much noticable performance boost (unless you have a really old computer), so I guess you could skip that part and go on working on a modern GUI. :dancing:

 

This is the only DAW that runs this bad on my system.

 

I don't want to be rude, but are you sure your sistem is not a old office-like pc? Every modern sistem with at least 4 cores (suitable for audio workstation) will work smoothly with S1. I have a old 6 core 1055t AMD cpu with 12gb ram and i squeeze every bit of S1 with it, being even more performance-wise than Ableton or Sonar. Even the track-transform feature is like a editable freezing option which you can re-freeze again and again, loading fx after fx, like a unlimited fx processing.

I don't bet for a sistem which is suitable on writin' documents with it , to be also suitable for a audio workstation. Is 2013, i never blame a new daw for it's lack of good working behavior with a old sistem. Ofthen, alot of crashes/problems comes from the plugins/other programs/hardware/user-errors.

I'm the one from the majority who never got problems with this daw. *yes*

Cheers

 

Another quick thing to take a look at is what exactly your cpu is doing, usually super high/sound card sputtering sorta spikes happen when the cpu decides to
change speeds real fast.....try having task manager or cpu z open and on top of studio one when your having this problem and see if your cpu is dramatically dropping speed...If so...Usually disabling most of the powersaving mechanisms in bios solves it... I use studio one on a mac and a pc and noticed that when my pc got slightly warm..it started to downshift speed for a moment..then gradually it would kick in to save my ass mode and it was all over the place...studio one wasnt having it...this was on a crappy i3.. now I have an i5 mac and an i7 pc..problem solved with simple sequences...the throttling happens when its hot and a super crazy sequence is playing..but no audio dropouts due to modern cpus kicking a little ass..even when speedstepped..


Paraphrased :
..Open task manager/cpu z
play your song..
watch the daw spike and see if the cpu's speed has shifted dramaticlly
if so..there you have it..disable that speedstep or c3 state shit!

 

You might already know this but it may be power settings related. I had the same issue when 2.6 came out, 2.5 was great on the CPU but 2.6 with the same setup just gave me tons of spikes. I checked my power management settings and it was switched from high performance back to Power-saving. Since reverting back it works a charm.

 

See this and download the power setting zip file, it worked very well for me

My link

 

Actually would be worth to try S1 again just when the V3 will get released , and i say that because i know how ugly the actual S1 looks to you (and honestly, to me too ). I just can't wait to see if the V3 will fix the actual lacking of S1, including an improved GUI, independent duplicated tracks, AA waveforms, global bypass, etc.