hard to say anything at all without knowing your system specs, but my latest-gen i5 has no trouble at all with large songs, VSTi's, several instances of CPU-intensive plugins... My system doesn't suck but it's still a long way from being "top of the line."
You'll know you're an old rock-n-roller when the only spandex in your pants is in the elastic waistband.
![]() Studio One Professional 4.1.4 i5-8400, 16GB RAM, 512 GB SSD, 2TB HD, Win10 Pro TASCAM US16x08, FaderPort 8, Console 1, JBL 306P Mk.II Monitors Hairball Copper, DIYRE CP5, Sound Skulptor CP5176, Peavey VMP-2, Suhr Reactive Load Lots of self-built tube amps, Carvin, Fender, G&L, Ibanez, PRS, Takamine guitars |
sorry - meant to give specs at end of the post. It's an older system but i really have no problems with it in other DAWs. I don't do huge track counts - maybe 30-40 including busses/sends and mostly audio tracks. I do program my drum parts using SDII or ADII and do keys/synths via MIDI. I try to use CPU-efficient VST and VST-i plugins. SDII is very efficient in Reaper and Reason.
Desktop Computer: AMD FX6200 6-core 3.8GHz / ASRock 970DE3-U3S3 / 16G Ram/ Win7 SP1/ 3 Hard Drives: 7200RPM SATA - 300Gb/500Gb/1Tb Latest version/update of Studio One 4 Pro darrenporter1 wrotehard to say anything at all without knowing your system specs, but my latest-gen i5 has no trouble at all with large songs, VSTi's, several instances of CPU-intensive plugins... My system doesn't suck but it's still a long way from being "top of the line." |
Well... I'm not surprised you are having issues honestly.
FL Studio has a good guide for choosing a CPU. Obviously it is written from their own DAW's perspective, but it is still good solid advice for any DAW. https://support.image-line.com/action/k ... se?ans=214 They recommend 7000 as a minimum and well you can see where your CPU is at... https://www.cpubenchmark.net/compare/In ... /3097vs259 There are things you can do, like printing your drum tracks to audio ASAP but also rather than looking at the CPU meter as a guide for how well you are doing, base it on how often S1 just bogs down and won't play back properly. I tend to notice that my CPU meter hovers around 35% regardless of what is going on in the song. Never really goes above that, never really goes below.
You'll know you're an old rock-n-roller when the only spandex in your pants is in the elastic waistband.
![]() Studio One Professional 4.1.4 i5-8400, 16GB RAM, 512 GB SSD, 2TB HD, Win10 Pro TASCAM US16x08, FaderPort 8, Console 1, JBL 306P Mk.II Monitors Hairball Copper, DIYRE CP5, Sound Skulptor CP5176, Peavey VMP-2, Suhr Reactive Load Lots of self-built tube amps, Carvin, Fender, G&L, Ibanez, PRS, Takamine guitars |
Yeah, the CPU is over six years old but i still get pretty good performance out of it for what i do. I'm planning on doing a new build this year (Intel-based).
Not relying too much on the CPU meter is good advice and i usually don't - i was just surprised to see the huge jump when I inserted SD. I'll have to try Addictive Drums and see how it behaves. Thanks for the help! |
vaboyz1 wroteI am new to the PreSonus family. I am a musician. I am using Studio One software and the StudioLive Ar16. Everything is working great, except I can play back my tracks after recording or listen to it when trying record additional tracks. Need help. I am using Windows 10 on a 64 bit system It could be that you have monitoring mutes playback (Tape Style) selected under the option or you have Replace selected under the record mode.
Studio One Pro 4.5.4 64 bit, Mac OS 10.12.6, Mac mini (Late 2012) 2.3GHz quad-core Intel Core i7 (Turbo Boost up to 3.3GHz) with 6MB L3 cache, Intel HD Graphics 4000, 16 GB ram, 240 GB OWC Extreme Pro 6G Solid State SATS Drive startup disk, 1 TB internal SATA Dive, (2x) 1 TB External Glyph Studio 7200RPM eSATA Drives, 500 GB External WD Drive
|
Users browsing this forum: No registered users and 12 guests