-
Notifications
You must be signed in to change notification settings - Fork 3
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
research using odot bundle as main score structure #114
Comments
note: symbol numbering could be used for drawing layer, e.g. /symbol/0 is drawn first, on the bottom layer |
this may also possibly solve the
where the symbol
|
some ideas about how the score bundle should be structured:
|
I'm currently looking into whether we could use an odot bundle as the main Score data structure, rather than a vector of Symbols.
Having the full Score in a bundle would allow users to easily write o.expressions that refer to different Symbols; and since an odot bundle is already a hierarchy with the ability to store sub-bundles, it would make sense to go this route.
The idea would be that Components would link to an OSC message address, or ideally the OSC bundle stored at a message address.
One challenge at the moment is that the odot bundle structure historically has not been used in this way, so some work may be required to make sure that the memory addresses for sub-bundles remain constant.
Since the a Symbol's graphic Component should never outlive the Symbol, I think the pointer reference approach is viable.
The text was updated successfully, but these errors were encountered: