Thanks, great work Rory!
An example for the macros with comma problem… after defining a macro, I can’t call it if a comma is touching it, like so:
image $INVIS_PLANT, bounds(...)
Which made me wonder, if an exception needs to be made for when a comma is touching the macro, would making a similar exception for { and } be a good idea? Perhaps anything else?
Very odd that the amprange is working for you. Every single one of my instruments using it crashes with the new version, and didn’t before. Simple removal of that section fixed it in every case (probably 4 or 5 different instruments). I can send you a few examples zipped up if you’re still having trouble recreating it.
That’s what I figured, and that’s perfectly fine… what I don’t understand tho, is if I call your example with a different namespace, it no longer functions. Is this intentional? I guess I just don’t really understand what or why
Sorry for opening that can of worms, but I had a funny feeling that might create an issue or two. On the plus side, might the reworking of that have any impact on the unsupported aspect of plants in plants? Seems like it’s heading down that road.
I agree, the question I was posing I guess is what do you consider a better/safer distribution method… having c2lite refer to the full c2’s examples, or packaging it with it’s own. Both seem to have advantages and disadvantages. Either way, being able to pull up examples from lite would be great!
Which very well might be why amprange breaks my stuff, but not yours
edit: In case it matters, I still have to go back to csound 6.07 for testing. Newer versions (up to .09) gave me issues with the string parsing at init and such, so nothing works properly. I don’t know if it will work properly in .10 or not.