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

[bug] Perlin: output mutes after a while. #3

Closed
phdsg opened this issue Nov 24, 2017 · 6 comments
Closed

[bug] Perlin: output mutes after a while. #3

phdsg opened this issue Nov 24, 2017 · 6 comments

Comments

@phdsg
Copy link

phdsg commented Nov 24, 2017

OS: win
Rack: dev
Plugins: dev

somehow the module just goes mute after a while and i can't turn it back on with any of the controls.
also tried the menu options initialize and randomize.
i have to delete the module and load a fresh instance.

great module ideas btw, thx so much.

@naus3a
Copy link
Owner

naus3a commented Nov 24, 2017

Hey, glad you like it :)
I did not test on win, but it could be way I increment the noise position: I'll add safety net around it.

@MarcBoule
Copy link

I'd like to echo @phdsg 's comment, the same happens to me after a short while. Perlin goes mute, then when I play with the speed button, I can get it back but it doesn't behave the same way afterwards (hard to describe, but it becomes broken). Hope you can figure this out, it's a neat module when speed is relatively low (we can hear a pattern in the sound when speed is high though).

@naus3a
Copy link
Owner

naus3a commented Nov 28, 2017

It probably has something to do with range/progression of values I feed: I already noticed that the lowest values I allowed were too low.
It's the first time I use this kind of noise with audio, so I just replicated what I normally do with graphics: let me figure out a couple sweet spots and it should start to behave ;)

@naus3a
Copy link
Owner

naus3a commented Nov 30, 2017

I think I could reproduce the issue: when noise speed became very low, noise position did not increase, causing a lock in the wave.

There might be a precision conversion issue between local variables and the value stored in the UI widgets: I'll investigate that. In the meantime I think I solved constraining the values on a slightly higher threshold.

@naus3a naus3a closed this as completed Nov 30, 2017
@phdsg
Copy link
Author

phdsg commented Nov 30, 2017

in my scenario i always had both knobs at "11" :)

@naus3a
Copy link
Owner

naus3a commented Nov 30, 2017

Good to know: I managed to make it happen by fiddling randomly :)

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

3 participants