Page 1 of 1
Preview & Render modes in DAW
Posted: Thu Jul 02, 2015 9:39 pm
by Father
2 things i have to ask
- I don't know if this has been talked about before but, is there a way to see if the DAW is in recording mode or not?
- how can we process a signal at a lower sample rate than the original sample rate?
The goal is to have a low CPU usage while editing and previewing and full quality while recording.
Re: Preview & Render modes in DAW
Posted: Thu Jul 02, 2015 10:16 pm
by Tronic
Tool Box
Offline Mode Primitive
Re: Preview & Render modes in DAW
Posted: Thu Jul 02, 2015 11:16 pm
by Father
Tronic wrote:Tool Box
Offline Mode Primitive
Oh yeah now i get. i thought that was for internet connection! Silly me

Say in offline mode we want our plugin to work at half sample rate. Is this possible or even relevant? I don't know anything about this subject so any information or examples are much appreciated.
Re: Preview & Render modes in DAW
Posted: Fri Jul 03, 2015 1:05 am
by KG_is_back
Unfortunately, Flowstone can't down nor upsample its processing as a whole in a simple way. However, all code written in "hop()" code parts is "downsampled". You may put some CPU intensive parts of code in there for "realtime" version and have an non-hopped version for "offline" processing. For example filter coefficient calculation is often done this way.
Some parts of schematic may also be upsampled (search for oversampling toolkit and related articles) to for example reduce aliasing. You may have non-antialiased version of oscillators and distortion modules for "realtime" version and oversampled/antialiased for "offline" version.
Re: Preview & Render modes in DAW
Posted: Fri Jul 03, 2015 2:10 am
by Father
Thanks KG. That was all i wanted to know. So if you use for example hope (2) the code will be processed at half sample rate, correct? I try using hop on some code to see how it goes.
Re: Preview & Render modes in DAW
Posted: Fri Jul 03, 2015 3:41 am
by tulamide
Father wrote:Thanks KG. That was all i wanted to know. So if you use for example hope (2) the code will be processed at half sample rate, correct? I try using hop on some code to see how it goes.
The sample rate stays the same, but only every second sample is processed (which means half of the work = less cpu load)