CWITEC

Dandruff · Post by **Dandruff** » Wed Jun 04, 2014 8:57 pm

I'm pretty new to TX16Wx.

Version 2.3.1c in REAPER 4.62 (64bit)

-> load TX16Wx and put a sample on C3
-> insert MIDI item with some notes

=> playback = fine

-> duplicate the tack
-> playback

Result: no audio output on the duplicated track unless you open the GUI once

SOLVED

elcallio · Post by **elcallio** » Thu Jun 05, 2014 2:17 pm

This seems to work fine for me. Are you sure this is not a reaper setup issue?

Dandruff · Post by **Dandruff** » Thu Jun 05, 2014 2:42 pm

Don't know. Opening a saved projects also give me no output on all TX16Wx tracks. I have to open to GUI to get sound!

SOLVED

Dandruff · Post by **Dandruff** » Thu Jun 05, 2014 2:51 pm

With the same project (bassdrum sample) I also have overload problems. TX16Wx outputs high levels so that REAPER's track muting kicks in very often (set to >24dBFS getting muted). This Bassdrum (mono) sample peaks at -12.7dBFS so it's shouldn't overload on TX16Wx.

Weird.

Sample = 48kHz
Project (ASIO)= 48kHz

SOLVED

Dandruff · Post by **Dandruff** » Thu Jun 05, 2014 3:07 pm

Found the culprit for the overload problem: It's the Sinc128 resample mode! Setting it to Sinc64 fixes the problem. Obviously the Sinc128 does add some weird spike sometimes.

But why does the resample mode is active in this case at all?

48kHz sample + 48kHz output at root key shouldn't need resampling. Or I'm wrong?

elcallio · Post by **elcallio** » Thu Jun 05, 2014 3:09 pm

Please send me the offending project + samples. That sounds weird.

elcallio · Post by **elcallio** » Thu Jun 05, 2014 3:33 pm

Also, interpolation is not set automatically. If its set to something, its because you changed it.
I've verified that Sinc128 works as expected on some test material, including 1:1 sample rate, non pitch-shifting playback. It is not just simply the fact that Sinc128 is _very_ CPU intensive? Since the render callback to the plug-in might take longer than the time slice rendered, you could get choppy audio / spikes just because of CPU load (do not look at full CPU load, you most likely need to look per core, since a single track will usually be rendered on a single core).
Sinc interpolation >32 should really only be used for offline rendering.

Dandruff · Post by **Dandruff** » Thu Jun 05, 2014 3:34 pm

Ok, sent to info@cwitec.com.

Dandruff · Post by **Dandruff** » Thu Jun 05, 2014 3:38 pm

elcallio wrote:Also, interpolation is not set automatically. If its set to something, its because you changed it.
I've verified that Sinc128 works as expected on some test material, including 1:1 sample rate, non pitch-shifting playback. It is not just simply the fact that Sinc128 is _very_ CPU intensive? Since the render callback to the plug-in might take longer than the time slice rendered, you could get choppy audio / spikes just because of CPU load (do not look at full CPU load, you most likely need to look per core, since a single track will usually be rendered on a single core).
Sinc interpolation >32 should really only be used for offline rendering.

Ok, I change the playback mode to Sinc32.

Any idea with the non-opened GUI = no playback on track duplicate and project load issue?

SOLVED

elcallio · Post by **elcallio** » Thu Jun 05, 2014 3:50 pm

I checked the file you sent. You are running reaper with Settings->Plugins->Compatibility->Disable saving full plug-in state On. This will cause reaper to only save a "preset" (VST FXP) when storing the project. TX16Wx handles this less than perfect, and while (most) of the relevant data is stored, some is not, including performance assignment. Thus when loading, no performance is selected -> no sound. Opening the UI will force select the first (must show something), thus you get sound then.
While I should fix so that FXP saving is a bit more consistent, the fact is still that this is _NOT_ the option you want turned on in this case.

Dandruff · Post by **Dandruff** » Thu Jun 05, 2014 4:00 pm

You're right. Seems to be the first plugin I own that requires VST bank saving.

Working fine now. Also no overloads anymore with the Sinc32 setting. Cool, thanks!

elcallio · Post by **elcallio** » Thu Jun 05, 2014 8:00 pm

While I can (and probably should) fix so that FXP:s make more sense, they (i.e. "minimal" plugin state) is not a good option for a sampler. A TX bank consists of N performances, each using M programs and K waves/matrices. Logically, a FXP would be a performance, the referenced program(s) and waves. But suppose you are working on a song using more than one perf (program change?) or you simply want to preserve the state of your work, i.e. including for example loaded but unused waves (wip)? If we use FXP saving and the previous logic, data would be lost on project saving. Less than ideal (imho).
Sure, I could _ignore_ the difference and save the same data, but then the whole "export FXP" becomes meaningless. Also bad.
Maybe this sheds some light on why things are as they are.
/C

Dandruff · Post by **Dandruff** » Thu Jun 05, 2014 8:28 pm

Alright. No prob. Just new for me

Dandruff · Post by **Dandruff** » Sun Aug 31, 2014 8:18 am

elcallio wrote:Sinc interpolation >32 should really only be used for offline rendering.

I'm still getting overshoots (> +32dB) with the Sinc128 setting during offline rendering (kick drum track). Sinc64 doesn't do this.

Is this expected behaviour or is this a bug in the Sinc128 algorithm?

elcallio · Post by **elcallio** » Sun Aug 31, 2014 11:12 am

Can you give me an example project (with audio) so I can see the problem? I will try to pin point if there is something wrong.

CWITEC

KVR Audio

No audio output (SOLVED)