Hey Guys,
I'm a Studio One user, and have been working on putting together a full course on Udemy for it.
In the meantime , I've put up a short free preview course of it up on Udemy. Sort of a teaser on what the full course would be. If you keen to see what you can do on Studio One, check it out. I'll take you through a walk around on the software, plus show how to record to audio track, MIDI to instruments tracks, and take a look at the Mix Console.
The full course will go into more detail on putting together a song in Studio One by making use of the tools like the Arranger Track, Audio Comping, Using the integrated Melodyne, and sketching out alternative ideas with the ScratchPads.
Here's the link:
https://www.udemy.com/taking-a-peek-at- ... tudio-one/
Studio One - Free Course on Udemy
-
- KVRer
- 22 posts since 22 Feb, 2017
Last edited by ontracktuts on Sun Mar 12, 2017 1:28 pm, edited 2 times in total.
-
- KVRAF
- 5564 posts since 13 Jan, 2005 from the bottom of my heart
Great looking teaser! Good luck with it!
Whoever wants music instead of noise, joy instead of pleasure, soul instead of gold, creative work instead of business, passion instead of foolery, finds no home in this trivial world of ours.
-
- KVRian
- 570 posts since 9 Jan, 2012 from Dona Ana, New Mexiico in the US of A
Since you brought this subject off topic I feel the urge to ask a question with all these claims of CPU loading. If you can go to the presonus forum and read up on this subject to better inform yourself just why this is the case. Seems its more the way the cores are utilized than anything else nefarious. In otherwords the meter within the software. If you check the system task meters it may be a little or a whole lot different.elmuz wrote:I'm testing now a demo version of Studio One 3.3
I like it, but the CPU load discourages me to Studio One.
Do you know when it will be fixed?
Frankly this excuse seems the SOP around here and even there on their own forum "CPU Usage sucks" , calls for fixes and optimization abound. How is it than there are those who can use it with such poor performance? I mean music production is still being done with Studio One.
I suspect some of these replies boarder on carping rather than actual lack of real use as with any other DAW.
As for the OP it is great that anyone takes the time to make a tutorial in a DAW or anything else for that matter.
-
- KVRAF
- 35692 posts since 11 Apr, 2010 from Germany
I see... a long discussion coming up.CTStump wrote:Since you brought this subject off topic I feel the urge to ask a question with all these claims of CPU loading. If you can go to the presonus forum and read up on this subject to better inform yourself just why this is the case. Seems its more the way the cores are utilized than anything else nefarious. In otherwords the meter within the software. If you check the system task meters it may be a little or a whole lot different.elmuz wrote:I'm testing now a demo version of Studio One 3.3
I like it, but the CPU load discourages me to Studio One.
Do you know when it will be fixed?
Frankly this excuse seems the SOP around here and even there on their own forum "CPU Usage sucks" , calls for fixes and optimization abound. How is it than there are those who can use it with such poor performance? I mean music production is still being done with Studio One.
I suspect some of these replies boarder on carping rather than actual lack of real use as with any other DAW.
As for the OP it is great that anyone takes the time to make a tutorial in a DAW or anything else for that matter.
You raised a good point though. "How is it than there are those who can use it with such poor performance? I mean music production is still being done with Studio One." Maybe one of the "Everyone has performance issues with Studio One" people could explain that. Or not.
-
- KVRian
- 711 posts since 19 Jan, 2008
I've explained in other threads why dsp meter in Studio One shouldn't be taken seriously, especially when you have few plugins, but I also explained that Studio One it's using a little more cpu than Bitwig for example.
For the first part, DSP/CPU meter in Studio One is reporting the core with heaviest load, not the load overall. That's why when you start a project it feels like it's using a lot more cpu than other daws, but as you continue working that load will spread on all cores and you'll be fine.
For the second part, I did a test. On my Q6600 added Serum in Studio One with a preset that uses a lot of voices and huge amounts of CPU. Studio One started to drop out, ~90-99% cpu usage showing the meter inside Studio One, while Bitwig was doing fine, 60% cpu usage showing the meter inside Bitwig.
My conclusion to this test, looking at Task Manager too, is that Studio One doesn't spread the load of one plugin on more cores. One plugin is using only one core. As you add more plugins Studio One will decide on which core to be processed. Bitwig on the other hand was using all cores, one plugin was able to be processed on all cores. That's what Task Manager showed, Studio One loaded Core 0 to 95-99% while 1,2,3 where using 9-15%, Bitwig was using all cores, 0,1,2,3, at about 60-70%
Now, can music be made in Studio One? Yes, especially if you don't use Serum with lots of voices on an old CPU like mine. There is a guy, SceneOfAction that streams live how he makes music and he's using Studio One. He does lots of recordings, processing, using 64-128samples buffer and never seen him complain that he can't do work. Here is the list of his videos if you want to check for yourself: https://www.twitch.tv/sceneofactionmusic/videos/all
His system spec:
He acknowledged at some point that Studio One is using a little more cpu, but nothing that can stop him from making music. Exactly what I've noticed.
Sorry for my long off topic, but I hope this wall of text will make people test Studio One more thoroughly, actually making music without looking at the DSP/CPU meter. Just ignore it and continue your work. You'll see you are able to add lots of stuff before you get dropouts.
For the first part, DSP/CPU meter in Studio One is reporting the core with heaviest load, not the load overall. That's why when you start a project it feels like it's using a lot more cpu than other daws, but as you continue working that load will spread on all cores and you'll be fine.
For the second part, I did a test. On my Q6600 added Serum in Studio One with a preset that uses a lot of voices and huge amounts of CPU. Studio One started to drop out, ~90-99% cpu usage showing the meter inside Studio One, while Bitwig was doing fine, 60% cpu usage showing the meter inside Bitwig.
My conclusion to this test, looking at Task Manager too, is that Studio One doesn't spread the load of one plugin on more cores. One plugin is using only one core. As you add more plugins Studio One will decide on which core to be processed. Bitwig on the other hand was using all cores, one plugin was able to be processed on all cores. That's what Task Manager showed, Studio One loaded Core 0 to 95-99% while 1,2,3 where using 9-15%, Bitwig was using all cores, 0,1,2,3, at about 60-70%
Now, can music be made in Studio One? Yes, especially if you don't use Serum with lots of voices on an old CPU like mine. There is a guy, SceneOfAction that streams live how he makes music and he's using Studio One. He does lots of recordings, processing, using 64-128samples buffer and never seen him complain that he can't do work. Here is the list of his videos if you want to check for yourself: https://www.twitch.tv/sceneofactionmusic/videos/all
His system spec:
Code: Select all
CPU - I7 5820k OC 4.2 Ghz
Memory - 32 Gb DDR3-2133 Ram
Graphics - EVGA GTX 970
OS Drive - Samsung EVO 840 250gb SSD Drive (OSX)
Project Drive - 2x Samsung EVO 840 250Gb RAID 0Sorry for my long off topic, but I hope this wall of text will make people test Studio One more thoroughly, actually making music without looking at the DSP/CPU meter. Just ignore it and continue your work. You'll see you are able to add lots of stuff before you get dropouts.
-
- KVRAF
- 5564 posts since 13 Jan, 2005 from the bottom of my heart
Also not to forget that the freeze tracks option in StudioOne is working!
Whoever wants music instead of noise, joy instead of pleasure, soul instead of gold, creative work instead of business, passion instead of foolery, finds no home in this trivial world of ours.
-
- KVRian
- 570 posts since 9 Jan, 2012 from Dona Ana, New Mexiico in the US of A
First off, sorry to the OP... I should have seen this coming.
On the other hand I did feel the need to respond in my earlier reply. Why would a guy creating a tutorial have any idea if CPU loading is fixed? Anyone asking him such is presumptous in believing he or she can answer that as if they represent Presonus just because they made a tutorial on Studio One. On the face that's ludicrous but maybe the OP could answer that and we will see.
I think it is just another opportunity for those with an axe to grind to hijack another Studio One thread and not to answer issues. It's great that the discussion is continuing in a sensible manner however a can of worms may have been opened and is driving this post off topic which may hurt its original intention... The tutorial.
For this I hope the discussion stays civil and not devolve into a tit for tat.good points are being made but there are those with opposing positions that will feel the urge to post their opinions also. It could also be an opportunity for good old fashioned trolling.
Everyone sometimes believes what is happening to them must be happening to everyone else. Not true in reality but validated on the Internet with only one post that supports their particular issue.
On the other hand I did feel the need to respond in my earlier reply. Why would a guy creating a tutorial have any idea if CPU loading is fixed? Anyone asking him such is presumptous in believing he or she can answer that as if they represent Presonus just because they made a tutorial on Studio One. On the face that's ludicrous but maybe the OP could answer that and we will see.
I think it is just another opportunity for those with an axe to grind to hijack another Studio One thread and not to answer issues. It's great that the discussion is continuing in a sensible manner however a can of worms may have been opened and is driving this post off topic which may hurt its original intention... The tutorial.
For this I hope the discussion stays civil and not devolve into a tit for tat.good points are being made but there are those with opposing positions that will feel the urge to post their opinions also. It could also be an opportunity for good old fashioned trolling.
Everyone sometimes believes what is happening to them must be happening to everyone else. Not true in reality but validated on the Internet with only one post that supports their particular issue.
-
- KVRer
- 7 posts since 3 Feb, 2014
I'm very sorry. I did not want to start a thread off topic. I only recognize Studio One for a few days. Only now I see that the CPU is a sensitive topic S1. Each tutorial will be helpful for me. Ontracktuts, thank you for the tutorial!
-
- KVRer
- Topic Starter
- 22 posts since 22 Feb, 2017
My full Presonus Studio One course has gone up on Udemy. This course will go in more depth than the free course and covers features like the Arranger, the ScratchPad, using the integrated Melodyne, plus some great mixing tips like bus processing and using the new Mix Engine.
You can check the course outline over here:
http://bit.ly/studiooneudemy
And Udemy are having a huge sale across their courses for the next 21 hours where all courses are going for $10.
So if you keen to check my course out, grab it using the following coupon code:
TRANSFORM202
And you'll get it for $10
Appreciate the support, and hope to see you in the course.
You can check the course outline over here:
http://bit.ly/studiooneudemy
And Udemy are having a huge sale across their courses for the next 21 hours where all courses are going for $10.
So if you keen to check my course out, grab it using the following coupon code:
TRANSFORM202
And you'll get it for $10
Appreciate the support, and hope to see you in the course.