If you get a chance, try this: create 60-70 tracks, each one with a native Reason instrument on them (say for instance, Subtractor or Thor). Then start adding 1 instance of Slate VBC onto each track, and see how many you can get then.davidvilla wrote: ↑20 Jun 2017Ok I see, so using 4 different instruments, piling Slate VBC on each of them, I can do 35 instances of VBC rack. Still nowhere close to Logic though.
Possible bug? Reason doesn't use all cores, but load metter is red.
- EnochLight
- Moderator
- Posts: 8405
- Joined: 17 Jan 2015
- Location: Imladris
Win 10 | Ableton Live 11 Suite | Reason 12 | i7 3770k @ 3.5 Ghz | 16 GB RAM | RME Babyface Pro | Akai MPC Live 2 & Akai Force | Roland System 8, MX1, TB3 | Dreadbox Typhon | Korg Minilogue XD
- davidvilla
- Posts: 208
- Joined: 16 Jan 2015
Keep in mind I'm on a 2012 mac mini. Did it a little different than your instructions : )
Started with a Thor + VBC, then duplicated both 'till it choked. I got to 45.
A Subtractor + VBC combo: 48 instances.
Thor and the newest plugin I have, Brauer Motion: 42 instances.
Thor + the oldest plugin I have, Waves Q-10: 156 instances!!!
EDIT: Just for f*ck's sake, I did a Thor + M-Class EQ test: 262 instances.
Edit #2: I did the same thing in Logic but with an ES2+ VBC rack: hit the max of 256 instances and the cpu meter looks like this:
My specs:
Sample rate: 44K
Buffer size: 512
Mac mini
Processor Name: Intel Core i7
Processor Speed: 2.3 GHz
Number of Processors: 1
Total Number of Cores: 4
L2 Cache (per Core): 256 KB
L3 Cache: 6 MB
Memory: 16 GB
Started with a Thor + VBC, then duplicated both 'till it choked. I got to 45.
A Subtractor + VBC combo: 48 instances.
Thor and the newest plugin I have, Brauer Motion: 42 instances.
Thor + the oldest plugin I have, Waves Q-10: 156 instances!!!
EDIT: Just for f*ck's sake, I did a Thor + M-Class EQ test: 262 instances.
Edit #2: I did the same thing in Logic but with an ES2+ VBC rack: hit the max of 256 instances and the cpu meter looks like this:
My specs:
Sample rate: 44K
Buffer size: 512
Mac mini
Processor Name: Intel Core i7
Processor Speed: 2.3 GHz
Number of Processors: 1
Total Number of Cores: 4
L2 Cache (per Core): 256 KB
L3 Cache: 6 MB
Memory: 16 GB
www.soundcloud.com/david-villa-lobos
https://www.instagram.com/dearestdavid/
My un-moderated & uncensored thoughts on Reason:
https://reasonablelogic.tumblr.com
https://www.instagram.com/dearestdavid/
My un-moderated & uncensored thoughts on Reason:
https://reasonablelogic.tumblr.com
This is good to know that we might see an update with a fix soon,EnochLight wrote: ↑20 Jun 2017Well that's good to know, and a stark difference from what James Benard claimed in his recent Spectrasonics demo video about Reason performance. Sadly, I was trying to buy a used copy of Omnisphere 2 from a user over at KVR, but he/she dropped off the face of the planet after they told me they had put in a request for license transfer over 3 weeks ago. Glad I didn't pick it up, if performance truly is an issue.
Yes, they are very aware and of course working to improve it, as mentioned by Mattias over at KVR here:
http://www.kvraudio.com/forum/viewtopic ... 5#p6811115
thanks for sharing it.
About Omnisphere performance just keep in mind I am using a mac mini server from 2012 (but it is quad core with 16gigs of ram), maybe on of those newer I7 it will work way better.
- davidvilla
- Posts: 208
- Joined: 16 Jan 2015
I'm on a 2012 mac mini and I don't have any problems with Omnisphere. It's my most used VST. What patch gave you the 'computer too slow ' message?
www.soundcloud.com/david-villa-lobos
https://www.instagram.com/dearestdavid/
My un-moderated & uncensored thoughts on Reason:
https://reasonablelogic.tumblr.com
https://www.instagram.com/dearestdavid/
My un-moderated & uncensored thoughts on Reason:
https://reasonablelogic.tumblr.com
davidvilla wrote: ↑21 Jun 2017I'm on a 2012 mac mini and I don't have any problems with Omnisphere. It's my most used VST. What patch gave you the 'computer too slow ' message?
Try "Waiting for the Horizon" @ 256 buffer size
- davidvilla
- Posts: 208
- Joined: 16 Jan 2015
"Waiting for the Horizon" - 3 DSP bars @ 256, playing a progression of 4 note chords. Something's up with your setup perhaps.
www.soundcloud.com/david-villa-lobos
https://www.instagram.com/dearestdavid/
My un-moderated & uncensored thoughts on Reason:
https://reasonablelogic.tumblr.com
https://www.instagram.com/dearestdavid/
My un-moderated & uncensored thoughts on Reason:
https://reasonablelogic.tumblr.com
This has been talked about in another thread. Reason doesn't use hyper-threading, thus uses only half of the logical cores (the cores you see in Windows). I'm sure they're optimizing the VST wrapper itself to increase performance that'll soon to be released, but there is still the hyper-threading issue here.
This is not a problem that's easily resolved, far from it. So don't expect it to be solved anytime soon, unless Props has been working on it for a while now and are soon to release that feature. I suspect that it's much harder to refactor a ton of legacy code to properly use hyper-threading. Props is proud of the fact that the core of Reason has remained basically unchanged. It's a testament of their forward thinking to see the same features after more than 15 years being still relevant without any modifications, but I think that a major part of it isn't easily redone without opening Pandora's box of shitty bugs and problems.
This is not a problem that's easily resolved, far from it. So don't expect it to be solved anytime soon, unless Props has been working on it for a while now and are soon to release that feature. I suspect that it's much harder to refactor a ton of legacy code to properly use hyper-threading. Props is proud of the fact that the core of Reason has remained basically unchanged. It's a testament of their forward thinking to see the same features after more than 15 years being still relevant without any modifications, but I think that a major part of it isn't easily redone without opening Pandora's box of shitty bugs and problems.
- EnochLight
- Moderator
- Posts: 8405
- Joined: 17 Jan 2015
- Location: Imladris
This has been discussed a million times, for sure, and to be clear - Reason does use Hyperthreading for practically everything except audio DSP. Examples of Hyperthreading in Reason are high quality stretch and resample, disc i/o, and GUI.
To see the effects of Hyperthreading in Reason, try taking a project with lots of audio recordings and drop the tempo drastically (for instance, from 120 BPM to 20 BPM), and watch all cores (both actual and virtual) ramp up.
Win 10 | Ableton Live 11 Suite | Reason 12 | i7 3770k @ 3.5 Ghz | 16 GB RAM | RME Babyface Pro | Akai MPC Live 2 & Akai Force | Roland System 8, MX1, TB3 | Dreadbox Typhon | Korg Minilogue XD
I think I maybe wouldn't mess with application priorities in the Task Manager. You'd possibly be delaying other important processes and causing trouble for yourself. But ... whatever. It's your computer, go for it.
Jon Heal • • Do not click this link!
It won't harm your PC at all, and after restarting Reason, process priority is back to default (normal).
For me increasing priority to high added some power to reason, like 20%.
It's nowhere close. I just mixed a song for a record label and made a video showing over 100 audio tracks in Reaper with 55 active, heavyweight VST's plus another 20 unactive VST's in a Reaper project.davidvilla wrote: ↑20 Jun 2017Ok I see, so using 4 different instruments, piling Slate VBC on each of them, I can do 35 instances of VBC rack. Still nowhere close to Logic though.
Reason, and I say this as a Reason power user, can not do anything near 100+ tracks + over 55 VST's. What some people say is neccesary for computer specs to run Reason compared to any other DAW, is really crazy and I've been saying this for years. Literally. I also said for years VST was coming
And it did. Reason definitely needs a massive performance update. "Higher tracks counts and better DSP processing on the same hardware" has been a feature in the last few Pro Tools versions. Other DAWs like Studio One are more efficient than the version before it. Is Reason? No. 9.2 saw a DSP increase for barely anything added to the core architecture.
Glad to see they're working on a performance update. Reason really, really needs it. If they can do it, Reason 10 will be very successful.
Just a thought, and of course it is total speculation, but I am thinking about Reason's incredibly complex and flexible routing capabilities. No other DAW remotely compares in this respect, yes? Anyway, to facilitate this routing, there must also be an incredible amount going on under the hood in terms of event listeners and the myriad of things to which they might be bound. Perhaps the price to pay for this incredible flexibility is a performance penalty. If that is the case, personally, I gladly accept the penalty.
Jon Heal • • Do not click this link!
- EnochLight
- Moderator
- Posts: 8405
- Joined: 17 Jan 2015
- Location: Imladris
No, actually. There are other DAWs that have just as flexible routing and modulation possibilities (as well as the equivalent of CV and Combinators). Bitwig is one that comes to mind.
But I still prefer Reason's workflow and GUI/UX.
Win 10 | Ableton Live 11 Suite | Reason 12 | i7 3770k @ 3.5 Ghz | 16 GB RAM | RME Babyface Pro | Akai MPC Live 2 & Akai Force | Roland System 8, MX1, TB3 | Dreadbox Typhon | Korg Minilogue XD
BOOM!jonheal wrote: ↑23 Jun 2017Just a thought, and of course it is total speculation, but I am thinking about Reason's incredibly complex and flexible routing capabilities. No other DAW remotely compares in this respect, yes? Anyway, to facilitate this routing, there must also be an incredible amount going on under the hood in terms of event listeners and the myriad of things to which they might be bound. Perhaps the price to pay for this incredible flexibility is a performance penalty. If that is the case, personally, I gladly accept the penalty.
You possibly just nailed it. The software either needs to be brought up to close to 50% what Reaper and other DAWs can do on the same hardware, OR, Props just need to admit or disclose that by the sheer routing and Graphical Requirements and issues due to the design actually PROHIBIT getting the software on par with other DAWS.
I know that's not the case, however. I know from using Reason to it's extremes since version 4, many small and insignificant additions have slowed the software down over the years and it's simply time for an overhaul. But I hear you, for sure.
Routing daws that exist are:
Ableton [max for live edition]
FL Studio [flowstone or the patcher]
Bitwig [I heard it's similar to ableton]
Usine hollyhock [really modular]
Reason [The analogue Gui is hopefully not the cause of that but I picked it for being analogue workflow]
Minihost modular
Kyma.
Hm...AH I FOUND WHY https://music.tutsplus.com/tutorials/10 ... audio-1075
Ableton [max for live edition]
FL Studio [flowstone or the patcher]
Bitwig [I heard it's similar to ableton]
Usine hollyhock [really modular]
Reason [The analogue Gui is hopefully not the cause of that but I picked it for being analogue workflow]
Minihost modular
Kyma.
Hm...AH I FOUND WHY https://music.tutsplus.com/tutorials/10 ... audio-1075
Producer/Programmer.
Reason, FLS and Cubase NFR user.
Reason, FLS and Cubase NFR user.
I understand that Ableton and Bitwig route audio in various ways through their FX. But what I'm talking about is not only that, but also the extensive CV routing that affects all manner of parameters in a myriad of ways.Oquasec wrote: ↑25 Jun 2017Routing daws that exist are:
Ableton [max for live edition]
FL Studio [flowstone or the patcher]
Bitwig [I heard it's similar to ableton]
Usine hollyhock [really modular]
Reason [The analogue Gui is hopefully not the cause of that but I picked it for being analogue workflow]
Minihost modular
Kyma.
Jon Heal • • Do not click this link!
What I didn't know was that reason uses alotta cpu when the instruments aren't minimized. so that analogue gui is the reason
"One of the more obvious suggestions that tends to be overlooked is to minimize instruments while you’re not editing them. You may not think it would make a big difference, but Reason puts a lot of CPU power into lighting up all those LEDs and cool patterns. It might not make a difference if you have 2 instruments, but what if you have 20? If you click the small arrow in the corner of the instrument, you can minimize and hide them, vastly improving Reason’s performance."
"One of the more obvious suggestions that tends to be overlooked is to minimize instruments while you’re not editing them. You may not think it would make a big difference, but Reason puts a lot of CPU power into lighting up all those LEDs and cool patterns. It might not make a difference if you have 2 instruments, but what if you have 20? If you click the small arrow in the corner of the instrument, you can minimize and hide them, vastly improving Reason’s performance."
Producer/Programmer.
Reason, FLS and Cubase NFR user.
Reason, FLS and Cubase NFR user.
That's an interesting idea. It's certainly possible that the UI would impact performance but I would like to see if tested out before I totally believed it.Oquasec wrote: ↑25 Jun 2017What I didn't know was that reason uses alotta cpu when the instruments aren't minimized. so that analogue gui is the reason
"One of the more obvious suggestions that tends to be overlooked is to minimize instruments while you’re not editing them. You may not think it would make a big difference, but Reason puts a lot of CPU power into lighting up all those LEDs and cool patterns. It might not make a difference if you have 2 instruments, but what if you have 20? If you click the small arrow in the corner of the instrument, you can minimize and hide them, vastly improving Reason’s performance."
Jon Heal • • Do not click this link!
- EnochLight
- Moderator
- Posts: 8405
- Joined: 17 Jan 2015
- Location: Imladris
Vastly? I've seen no evidence to support that statement, at least not on my machine. Maybe it depends on your specs? Beats me.jonheal wrote: ↑25 Jun 2017That's an interesting idea. It's certainly possible that the UI would impact performance but I would like to see if tested out before I totally believed it.Oquasec wrote: ↑25 Jun 2017What I didn't know was that reason uses alotta cpu when the instruments aren't minimized. so that analogue gui is the reason
"One of the more obvious suggestions that tends to be overlooked is to minimize instruments while you’re not editing them. You may not think it would make a big difference, but Reason puts a lot of CPU power into lighting up all those LEDs and cool patterns. It might not make a difference if you have 2 instruments, but what if you have 20? If you click the small arrow in the corner of the instrument, you can minimize and hide them, vastly improving Reason’s performance."
Win 10 | Ableton Live 11 Suite | Reason 12 | i7 3770k @ 3.5 Ghz | 16 GB RAM | RME Babyface Pro | Akai MPC Live 2 & Akai Force | Roland System 8, MX1, TB3 | Dreadbox Typhon | Korg Minilogue XD
- EnochLight
- Moderator
- Posts: 8405
- Joined: 17 Jan 2015
- Location: Imladris
Why would one intentionally leave their laptop on "balanced" mode or downclock their CPU if you're doing audio production?
Win 10 | Ableton Live 11 Suite | Reason 12 | i7 3770k @ 3.5 Ghz | 16 GB RAM | RME Babyface Pro | Akai MPC Live 2 & Akai Force | Roland System 8, MX1, TB3 | Dreadbox Typhon | Korg Minilogue XD
- EnochLight
- Moderator
- Posts: 8405
- Joined: 17 Jan 2015
- Location: Imladris
But doesn't your advice only pertain to laptops set in power savings mode?
Or are you just speculating?
Win 10 | Ableton Live 11 Suite | Reason 12 | i7 3770k @ 3.5 Ghz | 16 GB RAM | RME Babyface Pro | Akai MPC Live 2 & Akai Force | Roland System 8, MX1, TB3 | Dreadbox Typhon | Korg Minilogue XD
Reason may be a pokier than alternatives when loaded up with 900 VSTs, but it sure is fun to use! If you really need to load up 900 VSTs, use an alternative. If you like having fun, use Reason. That's my take on it.
Jon Heal • • Do not click this link!
-
- Information
-
Who is online
Users browsing this forum: Ahrefs [Bot] and 25 guests