Script Table in "higher resolution"

[ps]

I'm using a table in scriptnode controlled by a clock ramp over 4 bars. I set the table points via an array. Somehow the timing was never super accurate so I thought it's the clock ramp but it isn't - if I split it into 4 tables it's perfectly fine so it only can be the "resolution" of the tables. Is there any way (in the code maybe) to be able to add points that won't lock to the full percent? Eg. 12.25% I don't care too much about the visual representation - just the accuracy of the processing.

[Christoph Hart]

@ps check redefining SAMPLE_LOOKUP_TABLE_SIZE to something like 1024 or 2048.

[ps]

@Christoph-Hart perfect. makes sense!

[ps]

@Christoph-Hart it worked! can't believe it was that simple :)
Probably some valuable info for anybody using the table in scriptnode for more complex timings. thank you

[tomekslesicki]

Hey @Christoph-Hart I tried this, hoping this would apply to group xfade curves, but it doesn't, unfortunately, and I'm getting strange zipper noises when crossfading between very fine values. Is there any way to force the xfade curves to the higher resolution, too?

[Matt_SF]

@tomekslesicki is the parameter modulated ? or simply user-controlled ?
Try using a control.smoothed_parameter node.

[tomekslesicki]

@Matt_SF both, and the issue occurs in both cases. When crossfade tables are set at around fine values (for example, set the first curve is: 0db at 0%, - 100db at 8%, and the 2nd curve is -100db at 0%, and 0db at 8%), any movement there will introduce zipper nosie.

Calling

Engine.setMaximumBlockSize(32);

...or something smaller helps to some extent, but the chirping is still there - just sounds a bit higher in frequency.

[Matt_SF]

@tomekslesicki can you make a minimal snippet ? Depending on how your network graph is build, you may need the control.smoothed_parameter or a block container...