Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Osc t3d voice bug? #5

Open
KaiDrange opened this issue Nov 26, 2017 · 3 comments
Open

Osc t3d voice bug? #5

KaiDrange opened this issue Nov 26, 2017 · 3 comments

Comments

@KaiDrange
Copy link

Setup: Tau, 4 voices, osc to Aalto.

Issue: When “touch 0” and “touch 1” is down at the same time there seems to be some sort of conflict. It sounds like the pitches in the Aalto voices jump back and forth between the two keys. All other combos of touch # sounds fine.

@TheTechnobear
Copy link
Owner

can you get a dump from the osc messages.

@KaiDrange
Copy link
Author

Sure. From oscdump:
https://www.dropbox.com/s/erv5qiirzffs74m/Oscdump.txt?dl=0
...and this is the console output from MEC (same key presses)
https://www.dropbox.com/s/c0duo0tfw43v2f0/MEC_output.txt?dl=0

As oscdump was using the port, I didn't actually have Aalto running when I logged this (so can't say for sure it actually happened then). But I have been experimenting a bit and when I use Aalto I consistently get a weird "wobbly" sound whenever touch 0 and touch 1 is running at the same time. Other combos are fine.

I was running MEC on the rPI, using wifi for osc to Aalto on my mac. Same Aalto instance + your osc agent in EigenD (but running on the mac) works fine.

Hope it helps! And I'm not ruling out some silly mistake on my part. Just looked like something worth mentioning.

@TheTechnobear
Copy link
Owner

ok, Ive checked the logs... there is no interference between touches. if you look you will see the touch 1 and touch 0 hold the same pitch.
(search for tch1 etc in the osc logs, and you'll see it stays at the same pitch, its the last number in the log)

now.. there is no quantizing in place, so there will be some 'jitter around' , a fraction of a semi tone... again you can see this in the message

what i suspect your hearing, is the rate is actually slow down, so becomes noticeable, because you have kept logging turned on... console logging is only for debug, you should turn this off for normal use.

I'm not sure why 'other combos' would be fine, as id expect similar in those cases too.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants