-
Notifications
You must be signed in to change notification settings - Fork 13
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
Functional VCO locks up with NAN output #66
Comments
Of course it works for me (if I select the correct audio output, otherwise it is frozen ). If I want to fix this I need to be able to reproduce I am afraid. Are you on windows too? Robert |
Sorry about having a couple of self-built, not-yet-in-V2 library modules. This version just has Impromptu, Nysthi, VCV, Squinky modules. I also blanked the audio output device. I am on Windows 11 Home Version 21H2, Dell XPS 8940: Core I7-10700 , 32gb memory, NVidia GeForce GT 1030 The behavior is that it generates audio for a couple of seconds, and then the Saw output goes to NAN. I don't have this problem with the other Squinky VCOs... |
Runs perfectly here. Also on Win11. Anything interesting in the log file ? |
This is what I'm seeing. Nothing out of the ordinary in the log. I'll download and build from source with debugging and see if anything turns up. What happens is that when I restart Rack, I get a signal out of the Saw outputs, but after a variable length of time (usually a few seconds) the output goes to NaN and stops making any sound. |
wow - functuinal - that's a blast from the past! Doesn't the manual say it's deprecated? It's just a clone of the old VCV Fundamental 0.6. When they went to 1.0 they totally re-wrote it. |
Never run into this before but with this patch, the Saw output of Functional VO gets stuck with no audible output.
2022-05-01-SquinkyBug.zip
The text was updated successfully, but these errors were encountered: