Waveform automation comparison by AdmiralBumblebee didn't turn out well (last place)
-
- Beware the Quoth
- 35500 posts since 4 Sep, 2001 from R'lyeh Oceanic Amusement Park and Funfair
Renders should be highest possible quality by default, option to disable.
An idiot on Set Theory:
"In some cases there is an object called red that contains everything that is red. In much the same way a pot is a plate."
"In some cases there is an object called red that contains everything that is red. In much the same way a pot is a plate."
-
- KVRist
- 364 posts since 1 Jun, 2005 from Liverpool, UK
It should always render at high quality, no matter what.
That being the case, user options are then targeted towards real-time optimisation, and as such you only need to add an option for selection of real-time quality mode.
If it's only low or high quality playback as a binary option, it can go in the CPU Monitor window. You'd only want lower CPU usage if you're running out of CPU bandwidth and if you're running out of CPU bandwidth, you're probably going to open the CPU Monitor, so that seems like a good place to notice the "Reduce playback quality to Lower CPU" option, which should sit right next to the "Freeze Edit to Lower CPU" button. Importantly, this option should not be global and should be saved with the Edit or reset to Off when a new Edit is loaded.
That being the case, user options are then targeted towards real-time optimisation, and as such you only need to add an option for selection of real-time quality mode.
If it's only low or high quality playback as a binary option, it can go in the CPU Monitor window. You'd only want lower CPU usage if you're running out of CPU bandwidth and if you're running out of CPU bandwidth, you're probably going to open the CPU Monitor, so that seems like a good place to notice the "Reduce playback quality to Lower CPU" option, which should sit right next to the "Freeze Edit to Lower CPU" button. Importantly, this option should not be global and should be saved with the Edit or reset to Off when a new Edit is loaded.
i9-10980HK. Windows 10 (21H2). Komplete Audio 6. Studio One 5.4.1.
-
- KVRAF
- 1790 posts since 30 Dec, 2012
My problem with having a different option for rendering is that it makes it very difficult to mix.
If you're listening to subtle artifacts or phasing issues and trying to correct for them, then they disappear during a render, you might end up with having accidently added these back during the render process.
It's reasons like this that we render at the current block size of the audio device, in case plugins do something specific each block.
If you're listening to subtle artifacts or phasing issues and trying to correct for them, then they disappear during a render, you might end up with having accidently added these back during the render process.
It's reasons like this that we render at the current block size of the audio device, in case plugins do something specific each block.
-
- KVRist
- 364 posts since 1 Jun, 2005 from Liverpool, UK
I understand the line of thinking, but if that occurred, the user would have had to have manually enabled the low CPU mode and thus it's difficult to claim that any audible differences are the fault of Waveform.dRowAudio wrote: Tue Mar 12, 2019 5:58 pm My problem with having a different option for rendering is that it makes it very difficult to mix.
If you're listening to subtle artifacts or phasing issues and trying to correct for them, then they disappear during a render, you might end up with having accidently added these back during the render process.
If I'd done that, I'd call myself an idiot and then go and fix it. I wouldn't blame the software for the way I personally set it up.
i9-10980HK. Windows 10 (21H2). Komplete Audio 6. Studio One 5.4.1.
-
- KVRian
- 524 posts since 16 Mar, 2017
This assumes that the default setting is to do the same for both. In this case the default would need to be that the current method is used for both playback and rendering in order to avoid disturbing existing projects.fromwithin wrote: Tue Mar 12, 2019 7:51 pm I understand the line of thinking, but if that occurred, the user would have had to have manually enabled the low CPU mode and thus it's difficult to claim that any audible differences are the fault of Waveform.
Having this as an application-level setting would also mean potential issues with the portability of projects between users who might have it configured differently from each other.
-
- KVRist
- 364 posts since 1 Jun, 2005 from Liverpool, UK
I already said in my post: "Importantly, this option should not be global and should be saved with the Edit or reset to Off when a new Edit is loaded.".fde101 wrote: Tue Mar 12, 2019 9:50 pm Having this as an application-level setting would also mean potential issues with the portability of projects between users who might have it configured differently from each other.
i9-10980HK. Windows 10 (21H2). Komplete Audio 6. Studio One 5.4.1.
-
- KVRian
- 524 posts since 16 Mar, 2017
So you did... sorry, missed that as an assumption here. The earlier discussion with @dRowAudio seemed to be leaning away from that.fromwithin wrote: Wed Mar 13, 2019 1:45 pm I already said in my post: "Importantly, this option should not be global and should be saved with the Edit or reset to Off when a new Edit is loaded.".
-
- KVRAF
- 1790 posts since 30 Dec, 2012
I'm taking a look at this hopefully this week but there's a few approaches I could take.
This is example is specifically a linear volume change which is kind of a special case for automation that I can add artefact free for little overhead.
However, I'd like to see if I should go the full hog and make full bezier curves more accurate to avoid any artefacts in any curve shape. This is will be much less efficient though so I'd like to see if other hosts still render artefact free when using curved automation.
Has anyone run these tests?
This is example is specifically a linear volume change which is kind of a special case for automation that I can add artefact free for little overhead.
However, I'd like to see if I should go the full hog and make full bezier curves more accurate to avoid any artefacts in any curve shape. This is will be much less efficient though so I'd like to see if other hosts still render artefact free when using curved automation.
Has anyone run these tests?