beadsynt example

[csound-plugins]

beadsynt example

[gesellkammer]

These are binary flags, so without any flags (0) it is the cheapest possible: uniform noise, fast oscillator, no frequency interpolation.

+1 changes the noise type to gaussian, which sounds more natural (this used to be a very expensive option but I came up with a very ood optimization so at the moment gaussian noise is almost as cheap as uniform).

+2 sets linear interpolation for the sine oscillators,

+4 interpolates frequencies at audio level.

NB: Amplitudes are always linearly interpolated as audio level

[gesellkammer]

Try the one here:

https://github.com/csound-plugins/csound-plugins/blob/master/src/beosc/examples/fox.mtx

[tjingboem]

Yes, that one works. This fox.mtx is 2 x bigger in size than the one that is present in the examples folder of the Csound manual. I will remove that one from the repo to avoid further confusion.

And i was able to create a new mtx file with loristrck_pack!

menno@mennoASUSZ170 ~ $ loristrck_pack MathewsN.wav
Using dt = 1.30 ms
MathewsN.mtx

This is a good starting point, thanks for your help.

[tjingboem]

i have yet another question on the information i have on the beadsynt opcode.
It is about how to understand the flags.

iflags | Description
-- | --
+1 | Uniform noise / Gaussian noise
+2 | Fast (no interpolation) oscillator / Linear interpolation
+4 | No frequency interpolation / Frequency interpolation

i am not sure, for example, if '1' is or the uniform or the gaussian noise?
And does '2' mean 'no interpolation' or 'linear interpolation'?

The list i have gathered now looks like this:

[tjingboem]

Thanks for clearing that up!

I now have 2 instruments: one that is using loristrck_pack with no further arguments (produces a mtx file), after a few seconds the second instrument using beadsynt for playback.

This way, i analyzed the fox and play it back later. But i get a very different sounding result from your fox.mtx.

I have read that loristrck_analyze can be used before loristrck_pack for more control in the analysis stage. Is this combination needed to get the fox.mtx file that you produced?
What are the arguments?
.
my fox:
fox.mtx.zip

[gesellkammer]

loristrck_analyze --help

For any further inquiries, please consider reading the documentation first:

https://loristrck.readthedocs.io (https://loristrck.readthedocs.io/en/latest/commandline.html)

[tjingboem]

I have printed out these documents a week ago and going through them the best i can.
But i won't bother you again- which is a pity as i think your opcodes and other work are interesting.