Currently, Oderk4 tries to load the "odes" (the dynamically generated .so files) with a relative path to odes/. This forces scsynth and sclang* to be run at the lib/ directory.
It would be better to not enforce this and make it configurable, like a global setting on sclang, e.g.
Oderk4.lode_path = "~/lode"
For this to work, I think we'd need to pass a string to the UGen constructor (using the ugly "size+ascii char array" hack).
*Actually, sclang can be started anywhere, but scsynth must be able to find the odes relative to the current working dir, which is where it was run in the first place. Sclang starts the server in the same current directory she's in.
Currently, Oderk4 tries to load the "odes" (the dynamically generated .so files) with a relative path to
odes/. This forces scsynth and sclang* to be run at thelib/directory.It would be better to not enforce this and make it configurable, like a global setting on sclang, e.g.
For this to work, I think we'd need to pass a string to the UGen constructor (using the ugly "size+ascii char array" hack).
*Actually, sclang can be started anywhere, but scsynth must be able to find the odes relative to the current working dir, which is where it was run in the first place. Sclang starts the server in the same current directory she's in.