-
Notifications
You must be signed in to change notification settings - Fork 83
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
Tidal Modulator 2 crashes on Rack v1 #80
Comments
I can't reproduce this issue. I need more information, steps, platform details, etc. |
I can reproduce this. It doesn't crash every time but it happened with these settings (amongst others): The crash happens when you cycle through the modes on the left, usually on the second or third time through the cycle. Seems to happen regardless of what is patched in or out. I'm using linux if that's relevant, latest Rack and AI releases. Some system info:
The crash in the log:
My settings-v1.json:
|
Getting a crash as well when changing the frequency range:
|
I'm also seeing a crash: when randomizing the tidal modulator 2, a segmentation fault always occurs after some time. No inputs or outputs need to be patched to reproduce the issue, just the module itself. Edit: nope, still crashes actually |
Turn the SMOOTHNESS knob all the way to the RIGHT . then click the top left button a couple times. seems to crash it every time. |
The following patch file for me is in a simple state with only Tides2 with locked parameters that will consistently crash when the patch file is loaded and the "frequency range" is set to red by pressing the button. {
"version": "1.dev.476a49b",
"modules": [
{
"id": 8,
"plugin": "Core",
"version": "1.1.6",
"model": "Notes",
"params": [],
"leftModuleId": 149,
"text": "To crash, just change the ramp mode to red.\n\n\n\n\nTo get to the current state:\n1. Bring Frequency all the way down\n2. bring smoothness all the way up\n3. send slope to one side.\n4. set frequency range to red\n5. set frequency range back to yellow\n5. send slope to the other side.\n6. send frequency range to red\n7. crash\n",
"pos": [
14,
0
]
},
{
"id": 149,
"plugin": "AudibleInstruments",
"version": "1.3.1",
"model": "Tides2",
"params": [
{
"id": 0,
"value": 0.0
},
{
"id": 1,
"value": 0.0
},
{
"id": 2,
"value": 0.0
},
{
"id": 3,
"value": -48.0
},
{
"id": 4,
"value": 0.5
},
{
"id": 5,
"value": 1.0
},
{
"id": 6,
"value": 0.0
},
{
"id": 7,
"value": 0.5
},
{
"id": 8,
"value": 0.0
},
{
"id": 9,
"value": 0.0
},
{
"id": 10,
"value": 0.0
},
{
"id": 11,
"value": 0.0
},
{
"id": 12,
"value": 0.0
}
],
"rightModuleId": 8,
"data": {
"range": 1,
"output": 0,
"ramp": 1
},
"pos": [
0,
0
]
}
],
"cables": []
} To reproduce the patch / seg fault:
EDIT: This is reproducible for me on both MacOS and Ubuntu, but I have not tried a Windows machine. |
I can reproduce this on windows and linux. |
I dug into the code for a little while and discovered that it results from the call to the |
Hi, I know it is an old topic, but I have the same issue in the latest version. Is there an update on this bug? Info: Ubuntu Studio (based on Ubuntu 20.04.2 LTS), VCV Rack v1.1.6, Tidal Modulator 2 v1.5.0. Crash log: The crash happens cycling the Frequency Range (top left mode button). It is a persistent issue every time I cycle the modes a couple of times. If more info or testing is required, I'm happy to help solve this issue so please let me know. Kind regards, Henk |
This is still reproducible. I thought that v2 of Rack somehow fixed it but I was wrong.
|
So here is the topic. I noticed that it crashes when switching left modes under Frequency knob
The text was updated successfully, but these errors were encountered: