[ossia-max/pd] allow remote to use compatible units
Open
Nobody has claimed this yet.
enhancement
ossia-max
ossia-pd
- Dominant language
- C++
- Stars
- 231
- Forks
- 35
- Avg merge
- 8h 55m
- Merged PRs (30d)
- 14
Description
- it would be great if an [ø.remote] could use a different unit (from the same dataspace) than it's attached parameter
e.g. [ø.param foo @unit time.hz] and [ø.remote foo @unit s]
of course, then, we don't need to specify the dataspace to ø.remote
- pd
- max
- what would be even better, would be that we can access one member of a multi-dimensionnal unit from a remote, e.g. [ø.param bar @unit position.xyz] and [ø.remote bar @unit xyz.x]
- pd
- max
what do you think ?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing how [ø.remote] and [ø.param] represent dataspace and units, then review the existing unit handling for the completed pd and max cases. Define the expected behavior for compatible units and multidimensional members such as position.xyz and xyz.x, and verify both environments against those cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- distributed-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100