I've spent quite a bit of time trying different ways of running two instances
of mincer with the intent of resynthesizing stereo files. 

However, even when using the same table for both instances, they are
unpredictably out of phase.

I have verified that my tables are set up correctly, as I have tested with
other table lookup opcodes.

I have also tried both using the same set of krate variables, and unique
variables for each instance, without seeing better results.

The one thing I've seen make a significant difference was the fft size,
which at 4096 is entirely unpredictable, but at 128 was typically in phase
or inverted.

Phase Locking seems to reduce the number of possible phases, but never
assures that the relative phase between two instances will be predictable.

My question is if there's a way to assure a fixed relationship between the
phases of multiple instances of mincer (and ideally maintain a fairly large
fft size).

I'm not sure if this is user error, a bug in the opcode, or expected
behavior for fft-based resynthesis (or even phase-locked vocoders in
general).

If it is not possible to keep two output signals in phase using the mincer
opcode, would it be possible using the pvs opcodes instead or would I end up
running into the same result?

Thanks in advance for any help!

Best,
shensley



--
Sent from: http://csound.1045644.n5.nabble.com/Csound-General-f1093014.html

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here