I’ve always had an occasional problem with phrases not playing correctly. This time I thought it’s time to post on the forum since it’s degrading my quality of life!
1: ok
2: glitch
3: ok
4: almost ok… strange attack suggests something is happening with the envelopes?
5 glitch
I always thought it was due to my ‘soundcard stutters’ (buffers) that I’ve had a problem with, but it turns out this error is also audible when rendering to file. Perhaps even more so, as even the normal Gxx effect seems to get timing issues when rendering.
Is there some workaround or some mistake i’m making? I’m hoping to get to the bottom of this, finally.
version 3.4.2 - win x64
example file (edit: added some missing fade-out effect number) oddity2.xrns (8.5 KB)
The XRNS doesn’t sound like the MP3 file!? The XRNS file sound different as the notes don’t fade out making the discrepancy hard to hear.
I’ve tried add the missing fadeout, make five patterns and render it out and all patterns sounds the same to me and I can’t hear anything like what’s going on in your MP3 file. Hear my render.
Yeah, it’s strange. Any sound card settings shouldn’t have effect on a rendered file, so it’s a bit difficult understanding that inconsistency. Perhaps then it’s due to some other setting in preferences.
EDIT: added the missing fadeout effect in example.
I have found something interesting when rendering with DirectSound selected as Device Type versus ASIO.
Check out this image where I put the ASIO render on top and DirectSound on the bottom, ASIO consistently render the transients across all patterens but DirectSound appear to be losing transients beginning pattern 3…
See the bottom right cluster where it’s clearly missing transients:
So somehow the Audio device type has an influence on the render
TL;DR But tried the above xrns on macos Renoise 3.42 with different latencies (8ms vs 80ms). It appears to me that the sound is now completely dependent on latency (but it should not at all). At some point sub divisions or whatever are wrongly calculated. Maybe this was introduced with that recent bugfix…