Rendered file's intro is a little bit louder than realtime listening output.īut the difference (realtime listening versus file rendering) is not as big as with VST version ! With DSP version it is a similar (but not the same) discrepancy: So the biggest discrepancy is VST realtime listening (the most quiet) versus VST file rendered (the loudest). The VST rendered output file's intro is obvious louder than the one rendered with the DSP version (listening and visual comparing of waveforms). Used for realtime listening the VST version applies less gain than the DSP version.īut when I compare the VST and the DSP version and their rendered output files, it is the other way round: The point is (most obvious while listening to relative quiet intros):
#DSP QUATTRO VS WAVELAB FREE#
Sorry, for my naive words (so feel free to laugh).īut I hope it is clear what I wanted to say. to decide if 44100 samples are a second or 192000 samples are a second, etc.). The plugin must know what the sampling rate is and then apply this knowledge to its internal sample counting for processing (e.g. It must work with samples (=counting samples), or not ? I cannot believe that any calculation inside a plugin's core is based on realtime values. Sorry, I am not an expert (like Hans and others), but from my naive point of view I would expect, that there must be some kind of automatic detection/compensation whether a plugin is used in realtime or for file rendering ? So with hundreds of different VST plugins (even AGC type) I have tried over the years WYHIWYG works.Īnd I cannot understand why (maybe I am too stupid ?). There are differences whether you use the VST plugin in realtime - for example with Wavelabs FX rack - or listen to the rendered file (even without AGC usage). Having a VST version it means that it is intended to be used most of the time for file rendering (so not in realtime like SA for broadcasting).Īnd everybody that uses a VST plugin expects that WYHIWYG. I have concentrated on the VST version and there still is something wrong:
Though now it seems as if it is even more a topic about realtime listening versus file rendering. So my problem is, how can I add haar filter as the 3rd parameter for FWT_stat function on Matlab without Wavelet toolbox.I have to re-up this whole DSP versus VST topic (and the differences). If I used SWT function from wavelet toolbox, all I have to do is add wavelet name (e.g: harr) instead of wname and swt function take care of all other things. SWC = swt(X,N,'wname') computes the stationary wavelet decomposition of the signal X at level N, using 'wname'.įWT_Stat function asks for 3 parameters and final parameter is orthonormal quadrature mirror filter.But I couldn't find a way to add haar filter as the input for 3rd parameter.
StatWT stationary wavelet transform tableįormally same data structure as packet tableīelow shows information about SWT function from wavelet toolbox. They have defined a function called FWT_Stat to do Stationary wavelet transformation. I found a Matlab functions package called WaveLab. But since it is not free, I need to find a free function to do the exactly same thing SWT function of wavelet toolbox does. I found a perfect way to do the transformation using wavelet toolbox of the Matlab. I'm currently working on a project of mine where I have to use stationary wavelet transformation.
0 kommentar(er)
