Skip to content
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

BEES enhancements & features #283

Closed
wants to merge 66 commits into from
Closed

BEES enhancements & features #283

wants to merge 66 commits into from

Conversation

ghost
Copy link

@ghost ghost commented Apr 28, 2017

Added lots of new features & enhancements to BEES, some new ops & also compiled all BEES ops (including grid ops) into puredata externals. The focus-switching should also work within PD.

All these issues are fixed or partially fixed:

#278
#277
#280
#281
#276
#253
#169
#251

Also focus-swapping, per-instance op state allocation & pickling for meadowphysics, whitewhale, life (i.e you can fire up multiple of these now & save to a scene)

@ghost ghost changed the title Dev pullrequest BEES enhancements & features Apr 28, 2017
@catfact
Copy link
Collaborator

catfact commented Apr 29, 2017

hey rick, this looks great. i'm sorry that i'm slammed right now and really can't evaluate every change. but let me know when you consider it a good time to pull the trigger on the merge.

@ghost
Copy link
Author

ghost commented Apr 29, 2017

no rush! deep(ish) into hacking on new stuff again... My plan is to add the new (good) stuff on top of this branch (just want to add that tonality diamond operator), then self-impose a feature freeze, really test everything for a bit (though stability seems excellent so far)

do you reckon the avr32_lib PR from way back is ready to go (this one #268)? looked decent to me when I reviewed it, wouldn't hurt to go over it again I guess...

@ghost
Copy link
Author

ghost commented May 8, 2017

Right @catfact I'm pretty happy with all the stuff in this pull request. Stability seems good!

Reckon it's ready to merge with one caveat. That is, with the monster op_kria, the debug build blows the 640kb program size limit.

I think, along with the fixed waves, kria is a pretty killer op. But breaking printf debugging is obv far from ideal - can you think of anything else that could potentially be trimmed down to reduce program size & squeeze it all in there?

If not, I'm thinking leave the code where it is, but move kria to end of the oplist since it's hogging all the space. Maybe comment out all the meat of the operator on debug build so it effectively becomes like a null op when you need print_dbg (see https://github.com/rick-monster/aleph/commit/228d9f21ce88597872c903dcbc3a39a03271e93b). Any better ideas?

@ghost ghost closed this May 14, 2017
This pull request was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants