hi, in my experience the crash you will get always when loading a preset of a different module (i.e. CsoundModule), so you can’t do that. In CsoundModulePoly there are no presets yet, you may be able to port some by loading a preset into CsoundModule and then copy paste the text. But then you have to adapt the inputs and outputs like in the default preset of CsoundModulePoly .
My apologies! I thought the presets referred to.csd files… lol
thanks again for this module!
another reference to Csound
I’ve been using its examples to create new presets. Also from here:
Lots of cool things from Ian McCurdy:
Vcv crashes? If so, report it.
ha, because of your answer i have tested again: take a module X, right click Preset → Open and choose a preset of a module Y. => crash. if you can confirm this, then may be you can report it?
Yes this closes rack to desktop
could you please make an issue in github with your suggestions and ideas. i think in the current layout there could be space for additional knobs or inputs.
i personally have given this issue very low priority as i always accepted the preset structure of rack where it never occurs to load a preset from another module. and no one else seemed to discover this issue either. so should we really make an elephant out of it?
Yes and No, I think it would be reasonable for Rack to just give a POP-UP with “This preset is not for this module” instead of CTD.
yes sure this is nice to have!
Say you downloaded a preset from the web and put it in the wrong folder, than it would be nice to have the above message.
No software should ever crash. Period. No matter what the user does.
may be, but i think its always a matter of priority.
@Yeager could you report this?
@Yeager, would you mind posting the
log.txt after the crash you found? I would be curious to see it. I suspect the crash is caused not by VCV Rack itself, but the particular module that’s trying to parse an unexpected JSON format. If so, the individual plugin developer needs to know about it, not VCV Rack developers.
Well… what if the user bombards the CPU with high energy neutrons and gamma rays? (Runs and hides…) Just kidding… totally agree with your sentiment.
You can try this yourself CTD guaranteed, open a new project rightclick the mixer try to load a preset from the VCO in to the mixer…CTD.
[112.339 info src/app/ModuleWidget.cpp:584 load] Loading preset C:\Users\Me\Documents\Rack2\presets\Fundamental\VCO2\PPG00.vcvm [112.739 fatal adapters/standalone.cpp:49 fatalSignalHandler] Fatal signal 11. Stack trace: 27: 0x0 26: 0x0 25: _C_specific_handler 0x7ffdce8d7f60 24: _chkstk 0x7ffdcf1f2300 23: RtlRaiseException 0x7ffdcf1a1070 22: KiUserExceptionDispatcher 0x7ffdcf1f0f20 21: ZN4rack7history12ModuleChangeD0Ev 0x7ffd7b2e3b30 20: ZN4rack3app12ModuleWidget10loadActionENSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE 0x7ffd7b31bd70 19: ZN4rack3app12ModuleWidget10loadDialogEv 0x7ffd7b31c130 18: ZZN4rack14createMenuItemINS_2ui8MenuItemEEEPT_NSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESA_St8functionIFvvEEbbEN4Item8onActionERKNS_6widget6Widget11ActionEventE 0x7ffd7b800720 17: ZN4rack2ui8MenuItem8doActionEb 0x7ffd7b34bf90 16: ZN4rack6widget10EventState12handleButtonENS_4math3VecEiii 0x7ffd7b351550 15: ZN4rack6window3Svg4loadERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE 0x7ffd7b3564e0 14: glfwGetWin32Monitor 0x7ffd7b399e90 13: CallWindowProcW 0x7ffdcd5be3f0 12: CallWindowProcW 0x7ffdcd5be3f0 11: glPushClientAttrib 0x7ffdb7b19560 10: CallWindowProcW 0x7ffdcd5be3f0 9: DispatchMessageW 0x7ffdcd5bdfd0 8: glfwPollEventsWin32 0x7ffd7b39dc50 7: ZN4rack6window6Window4stepEv 0x7ffd7b357340 6: ZN4rack6window6Window3runEv 0x7ffd7b357d40 5: ZN4rack6window6Window3runEv 0x7ffd7b357d40 4: ZN4rack6window6Window3runEv 0x7ffd7b357d40 3: ZN4rack6window6Window3runEv 0x7ffd7b357d40 2: ZN4rack6window6Window3runEv 0x7ffd7b357d40 1: BaseThreadInitThunk 0x7ffdce457600 0: RtlUserThreadStart 0x7ffdcf1a2680
may be it makes sense to put this into another topic as it seems to be a general issue not related to dbRackCsound.