Cabbage Logo
Back to Cabbage Site

Little GUI widget slugs and wishes

#81

Thanks for testing. I didn’t have a chance to give it a proper go. I’ve merged the the cmake branch into the develop branch. So do this:

git checkout develop

python build.py --config=Debug --project=Cabbage --build=False

Then go to your build folder and open the Cabage.xcodeproj file. Hit the green play button to build. Wait for the crash. You should get a stack trace which will show the methods that were called right up to the point of the crash. See if you can spot the last Cabbage method called. That would be mot helpful.

#82

hmmm… build.py nowhere to be found, before I had it in cabbage-cmake?

#83

Pull from develop after you check it out. You can check the contents against what you see when you visit the GitHub repo online…

#84

Thanks for your patient guiding! Got it from develop (ver. 2.8.40). Couldn’t make it crash yet :slight_smile: I’ll use this build and let you know.

#85

Great. You can keep running Cabbage from xcode and that way, if you do crash, Xcode should provide some useful information. Great that you have it all set up.

#86

OK. I got a crash now. I’m not sure what info would be useful to you?

I guess I need to leave it in the running/debugging mode after it crashes (not press the stop button) in order to see the stack trace (where is it?) - I know, stupid questions… :persevere:

Maybe you could point me to the right place?
Here is a screenshot maybe holding some info?

image
image2266×1180 1.24 MB

…and the error is: com.apple.audio.IOThread.client (12): EXC_BAD_ACCESS (code=1, address=0x0)

#87

Thanks for this. Does it crash at this point consistently?

#88

Yes, it seems so. This only happens when I stop the instrument. Not every time though. The stopping seems a bit slow…

#89

This could definitely be a side-effect of my last fix. In order to address that issue, I need to put in a recompile, just before killing an instrument. This was the only way to return the widgets states all back to tabula rasa. I will search for a better way :+1:

#90

Ok, I just pushed another possible solution now. I think it’s cleaner as we don’t have to recompile, or do anything with Csound when we stop or enter edit mode. To build, just do git pull origin develop from the Cabbage dir and update your build project. Can you let me know if it works?

#91

Great you found a possible solution. I’ll of course let you know. Btw. super easy to update this way :slight_smile:
I can already tell that stopping my instrument is now (v. 2.8.44) noticeably faster, more tests on the way. Thanks!

#92

Have you reverted back to the previous behaviour? Ver. 2.8. 44 seems to be again updating csd code. :confused:

#93

Do you mean regarding the custom identifier stuff?

#94

Yes, custom identifier stuff.
Image and label seem to be fine - no code update there.

#95

I just tried here and I can’t seem to create the same issues we have before, whereby the custom identifiers would get removed when entering edit mode?

#96

It’s not that, but this:

#97

I still don’t see any problems here:

#98

This is puzzling… On my side it behaves differently.

#99

Can you try removing the build folder and building again? After you remove the build dir, you need to run this command again

python build.py --project=Cabbage --config=Debug

1 Like
#100

I just did that. The same behaviour as before.