The curve is gearriveerd voor introprijs 45 euro: http://shop.propellerheads.se/product/the-curve/
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
Is er eigenlijk al een goede organ simulator in Reason. Ik heb nog geen enkele inspanning verricht om te zoeken maar wellicht weet iemand dat zo uit zijn hoofd.
This is how it works.
The devices are rendered by three threads on your system. One is the main audio thread and two audio worker threads.
The audio worker threads are in a sleep state between audio callbacks and are woken by the main audio thread as soon as an audio callback starts. During the callback, the audio workers potentially can receive work to do anytime, because other threads may have rendered devices that resolve dependencies, and thus must be very alert. We can not have them sleep when there isn't any work to do because it takes too long time for them to wake up when it's time to do some rendering. Therefore they continuously check (but in a kind way to the system) for work to do and that shows up as CPU activity.
Your document has on purpose one long chain of CPU heavy devices. This means that only one rendering thread will do most of the work for an audio callback and the rest will wait for something to do. It will also vary which thread gets the heavy work and that will do that different cores will do the work for different audio callbacks.
Both the fact that the threads without work to do wait (but show up as CPU active) and the fact that the heavy work changes between the rendering threads does that it looks like all three rendering thread seems to do the same amount of work. This isn't the case.
I hope this didn't get too technical.
..........
Reason analyzes the rack with devices and cables and then the threads compete with each other to render the devices, but devices that is connected directly to another device automatically gets rendered by the same thread so if there is a long chain of devices in the document the devices get rendered by the same thread. If there are other devices or chains of devices which are independent of (i.e. not connected to) the first chain they can be rendered simultaneously by another rendering thread. No CPUs are reserved for anything. They all work together to render the devices as parallel as possible during the audio callback.
Laat es horen dan Nelis?
