So if what you hear reflects CPU limitations, then what you get sounds bad.whyterabbyt wrote:with this particular default, what you hear is what you get.
Kontakt sounds worse in Reaper when audio preferences are not set correctly
-
- Banned
- Topic Starter
- 228 posts since 3 Feb, 2014
If you criticize Spitfire Audio, the mods will lock the thread.
-
- KVRAF
- 5627 posts since 23 Mar, 2006 from pendeLondonmonium
Actually, this setting would be an issue for those who use synths like DCAM Synth Squad with independent oversampling modes.
If someone is using for example, Cypher with the real-time setting at 1x oversampling and the offline option set to, say, 8 x oversampling, the rendered audio would not sound right (with the Reaper 'Inform plugin of the offline render state' option not ticked).
When I saw this topic I was trying to remember how this option is set in Reaper, and yes, that option was not ticked, meaning all my DCAM Synth Squad tracks would have been rendered at the wrong quality setting. Luckily, I have always used Synth Squad in at least the 2x and 4 x oversampling real-time modes so the rendered tracks sounded ok. I'm saying 'ok' as my offline mode was always set to a minimum of 8x oversampling and for more complex presets (complex audio-rate modulation patches) it was set to 16x. Settings which would have been ignored by Reaper...hmm...
If someone is using for example, Cypher with the real-time setting at 1x oversampling and the offline option set to, say, 8 x oversampling, the rendered audio would not sound right (with the Reaper 'Inform plugin of the offline render state' option not ticked).
When I saw this topic I was trying to remember how this option is set in Reaper, and yes, that option was not ticked, meaning all my DCAM Synth Squad tracks would have been rendered at the wrong quality setting. Luckily, I have always used Synth Squad in at least the 2x and 4 x oversampling real-time modes so the rendered tracks sounded ok. I'm saying 'ok' as my offline mode was always set to a minimum of 8x oversampling and for more complex presets (complex audio-rate modulation patches) it was set to 16x. Settings which would have been ignored by Reaper...hmm...
Last edited by himalaya on Wed Jul 02, 2014 11:38 pm, edited 1 time in total.
-
- Banned
- Topic Starter
- 228 posts since 3 Feb, 2014
http://jvstwrapper.sourceforge.net/vst20spec.pdf , pp. 52-53a plug is like black box processing some audio coming in on some inputs (if any) and going out of some outputs (if any). this may be used to do offline or real-time processing, and sometimes it may be desirable to know the current context.Code: Select all
virtual long getCurrentProcessLevel (); // returns: 0: not supported, // 1: currently in user thread (gui) // 2: currently in audio thread or irq (where process is called) // 3: currently in 'sequencer' thread or irq (midi, timer etc) // 4: currently offline processing and thus in user thread // other: not defined, but probably pre-empting user thread.
If you criticize Spitfire Audio, the mods will lock the thread.
-
- Banned
- Topic Starter
- 228 posts since 3 Feb, 2014
You're talking about how Reaper actually sounds (bad), but if I understand the minions correctly, how it actually sounds doesn't matter, and what matters is how cool it is because it's so customizable, if you don't have a job or girlfriend and want to sit around customizing DAWs.himalaya wrote:Actually, this setting would be an issue for those who use synths like DCAM Synth Squad with independent oversampling modes....
http://www.fxpansion.com/forum/viewtopic.php?p=74328there is a preference in the Reaper preferences called "inform plugins of offline render state"Indeed I didn't have the setting enabled, thanks for the tip.
Switching it on fixes the issue
If you criticize Spitfire Audio, the mods will lock the thread.
-
- KVRist
- 227 posts since 26 Aug, 2010
The thread has got the right title, because otherwise it would not have caught my attention and now I am aware of a bug. Sometimes exaggerations are needed.
-
- Banned
- Topic Starter
- 228 posts since 3 Feb, 2014
"Because sound quality doesn't matter" should be the new Reaper slogan.hibidy wrote:Belly acher!!!!!!!
If you criticize Spitfire Audio, the mods will lock the thread.
- KVRAF
- 25053 posts since 20 Oct, 2007 from gonesville
IE: if we do not agree that <Kontakt's 'standard' interpolation> = The Sound of Reaper, we're incompetent.arkmabat wrote:trimph1 wrote:Daw Wars....fricking autocorrect..BachRules wrote:So Kontakt is lying when it says it's using lower-quality interpolation for online renders? Do you even begin to understand the issue? I programmed the world's first commercial software synth. I aced CCRMA. If you want to interpret the "Saw Wars chapter" as are you're doing, that's your problem.trimph1 wrote:You're being silly.BachRules wrote:That's silly.arkmabat wrote:I'm sure the sound is fine.
Check Image-line's site for their FL11 manual ...particularly the Saw Wars chapter.
There is no fracking difference between daws soundwise..
Yeah, your bona fides totally make this logical.
- Beware the Quoth
- 33177 posts since 4 Sep, 2001 from R'lyeh Oceanic Amusement Park and Funfair
I asked for a specific quote. You're still ducking on providing one. If you want to assert I'm missing something, try actually proving it.BachRules wrote:Then something's wrong with your seeing.whyterabbyt wrote:all I see there
My mistake; I forgot you'd be looking to focus on a different context from the one discussed and left it ('developer') too imprecisely open-ended. In case you think it helps you make that case you're failing to provide any evidence for, read that as 'one of the well-known reaper extension developers'. Now that that's cleared up, you'll have something concrete to back you up from the VST spec, yes?That guy is a developer for Reaper? Why do you believe that?whyterabbyt wrote:One of the developers says
Are you asking why I think not setting a preference which flags plugins to do special-case behaviour is going to produce the same results as the plugins not doing that special-case behaviour?Why do you believe that?whyterabbyt wrote:the intent of the default setting is to give you what you hear,
What are you claiming the results of not setting the special-case-behaviour flag should be? A different special-case-behaviour?
Last edited by whyterabbyt on Thu Jul 03, 2014 12:46 am, edited 1 time in total.
my other modular synth is a bugbrand
- Beware the Quoth
- 33177 posts since 4 Sep, 2001 from R'lyeh Oceanic Amusement Park and Funfair
So if what you hear reflects any limitations, then what you get reflects those limitations. Its not unknown; you'll be aware ProTools has only ever had realtime bouncing until v11, last year or so, of course?BachRules wrote:So if what you hear reflects CPU limitations, then what you get sounds bad.whyterabbyt wrote:with this particular default, what you hear is what you get.
my other modular synth is a bugbrand
- Beware the Quoth
- 33177 posts since 4 Sep, 2001 from R'lyeh Oceanic Amusement Park and Funfair
So, still nothing proving the thing you claimed was enshrined in the VST spec (which, in case you try and change the subject was specifically mandated, non-optional, offline host-side default behaviour)BachRules wrote:http://jvstwrapper.sourceforge.net/vst20spec.pdf , pp. 52-53a plug is like black box processing some audio coming in on some inputs (if any) and going out of some outputs (if any). this may be used to do offline or real-time processing, and sometimes it may be desirable to know the current context.Code: Select all
virtual long getCurrentProcessLevel (); // returns: 0: not supported, // 1: currently in user thread (gui) // 2: currently in audio thread or irq (where process is called) // 3: currently in 'sequencer' thread or irq (midi, timer etc) // 4: currently offline processing and thus in user thread // other: not defined, but probably pre-empting user thread.
my other modular synth is a bugbrand
-
- Banned
- Topic Starter
- 228 posts since 3 Feb, 2014
The sweet sound of Reaper:
I'm trying to track down a problem....
I did some more testing on this....
I'm not sure why the default is off.
I have this annoying problem....In Reaper you just have to check 'inform plug-ins of offline rendering state' checkbox in Preferences.
the spectrum above ~7KHz is audibly muffled even if the filter is fully opened.
Let's start a list of developers who think this is a good sound, so customers know what to expect.I noticed that one of my tracks sounded different when I froze it.Please try checking "Inform plug-ins of offline rendering state" in Preferences->Plug-ins->VST...Compatibility settings.
If you criticize Spitfire Audio, the mods will lock the thread.
-
- KVRAF
- 5067 posts since 30 May, 2006 from Hollow Earth
Move on boy...BachRules wrote:The sweet sound of Reaper:
I'm trying to track down a problem....
I did some more testing on this....
I'm not sure why the default is off.I have this annoying problem....In Reaper you just have to check 'inform plug-ins of offline rendering state' checkbox in Preferences.the spectrum above ~7KHz is audibly muffled even if the filter is fully opened.Let's start a list of developers who think this is a good sound, so customers know what to expect.I noticed that one of my tracks sounded different when I froze it.Please try checking "Inform plug-ins of offline rendering state" in Preferences->Plug-ins->VST...Compatibility settings.
MuLab-Reaper of course