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

Splash (two bumps) out of tune #24

Open
martin-lueders opened this issue Apr 25, 2018 · 2 comments
Open

Splash (two bumps) out of tune #24

martin-lueders opened this issue Apr 25, 2018 · 2 comments

Comments

@martin-lueders
Copy link

Hi Gerhard,

something goes wrong in your calculation of the pitch in the "two bumps" mode.
It is fine for samplerates of 48000 and 96000 but is out of tune for 44100 and 88200.

I have the impression that it was ok in older versions. I have a patch using the two bumps which worked fine in Rack 0.5. In 0.6, after renaming the module in my patch file (see other issue), it is out of tune.

Also, the patch now consumes MUCH more CPU and is basically unplayable. Not sure though which plugin is causing that...

Cheers,
Martin

@gbrandt1
Copy link
Owner

the API for samplerate calculations changed indeed, will check if i messed something up.

can't help with your patch since i have no idea what is in it, you'd have to send it to me for debugging.

gerhard

@martin-lueders
Copy link
Author

Hi Gerhard,

dont worry too much about my patch. I guess many modules are currently not fully optimized.

I had a look at your code for the Splash Parasites, and noticed a few things which could be optimized more. For instance, the log2f you use in the ptich calculation is quite expensive. You dont need to call that for every buffer, but only if the sample rate has changed. You could replace it be a variable which you update only in the onSamplerateChange() function. and also call that function in your Constructor to make sure it is run when you start the module.

I am currently also going through my own plugins to try to optimize them better.

Cheers,
Martin

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