-
Notifications
You must be signed in to change notification settings - Fork 2
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
Modules still crashing in Windows #6
Comments
hi thx for reporting, on my windows installation it does not crash, could you provide the log file? |
ok
Envoyé à partir de Outlook pour iOS<https://aka.ms/o0ukef>
…________________________________
De : docb ***@***.***>
Envoyé : Friday, October 28, 2022 11:14:34 PM
À : docb/dbRackCsound ***@***.***>
Cc : caecos ***@***.***>; Author ***@***.***>
Objet : Re: [docb/dbRackCsound] Modules still crashing in Windows (Issue #6)
hi thx for reporting, on my windows installation it does not crash, could you provide the log file?
—
Reply to this email directly, view it on GitHub<#6 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AHSGFA47NJWYZEVXHOJGIWLWFSJBVANCNFSM6AAAAAARRMYJNY>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
[0.041 info adapters/standalone.cpp:129 main] VCV Rack Free v2.1.2 |
could you please try this one, i have added a bunch of log statements to better figure out what goes wrong, thx. |
Idem, same behavior, VCVRack crashes when I tried to open a module!? |
yes but now i would like have a look at the logfile |
[0.004 info adapters/standalone.cpp:129 main] VCV Rack Free v2.1.2 |
ok, this is not in my code. did you have installed csound before and is it running? |
yes, latest version 6.18.0...I used Csound since 1989... |
ok i have at least found a correlation between installing csound 6.18 and a crash. on my side it crashes when i delete a csound module , albeit it can be loaded and used. |
ok thank’s for your fast replies…
Envoyé à partir de Outlook pour iOS<https://aka.ms/o0ukef>
…________________________________
De : docb ***@***.***>
Envoyé : Saturday, October 29, 2022 3:48:01 PM
À : docb/dbRackCsound ***@***.***>
Cc : caecos ***@***.***>; Author ***@***.***>
Objet : Re: [docb/dbRackCsound] Modules still crashing in Windows (Issue #6)
ok i have at least found a correlation between installing csound 6.18 and a crash. on my side it crashes when i delete a csound module , albeit it can be loaded and used.
this behavior is not there if csound is uninstalled. i would as next step upgrade csound to 6.18 in the plugin (is currently 6.17).
—
Reply to this email directly, view it on GitHub<#6 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AHSGFA2KKAS4NCKYPIGKYGLWFV5PDANCNFSM6AAAAAARRMYJNY>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
dbRackCsoundWin2.0.3a.zip |
Nope still the same behaviour: [0.112 info adapters/standalone.cpp:129 main] VCV Rack Free v2.1.2 |
could you please try the following for testing: |
Same behavior, no changes... |
sorry now i am stuck, i cannot reproduce anything (e.g. running a debugger on your computer ;-) , so i cannot help -- the problem lies probably somewhere inside the csound code as the first call to csound does not return. i also have no other report where new aspects of the problem could emerge. |
OK I will take look at the makefile and how Csound behave… it can be on my side too… my laptop is running a lot of stuff… regards and mille mercis for your help…
Envoyé à partir de Outlook pour iOS<https://aka.ms/o0ukef>
…________________________________
De : docb ***@***.***>
Envoyé : Sunday, October 30, 2022 10:52:55 AM
À : docb/dbRackCsound ***@***.***>
Cc : caecos ***@***.***>; Author ***@***.***>
Objet : Re: [docb/dbRackCsound] Modules still crashing in Windows (Issue #6)
sorry now i am stuck, i cannot reproduce anything (e.g. running a debugger on your computer ;-) , so i cannot help -- the problem lies probably somewhere inside the csound code as the first call to csound does not return. i also have no other report where new aspects of the problem could emerge.
—
Reply to this email directly, view it on GitHub<#6 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AHSGFAZ6FS6V4TN2I7ATXKTWFZ4TPANCNFSM6AAAAAARRMYJNY>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Two issues:
It is quite strange since all your others modules works fine...
The text was updated successfully, but these errors were encountered: